The problem is validated. The solution is still fragmented.
Several companies already solve important parts of fresh-retail forecasting, quality inspection, shelf monitoring and markdown optimisation — some of them well, and at scale. Departmint is testing the layer between them.
Most tools answer one question in the chain. Very few answer the one after it.
Nothing here says these companies cannot move into the decision stage. Several plainly could, and Smartway and Wasteless already operate there. The bet is narrower: that a decision layer built from the economics outward, specialised in fresh produce and GCC retail workflows, is a different product from a markdown engine bolted to a waste tool.
This table is more useful than any feature grid.
HYPOTHESIS“When should I intervene on this fresh inventory, and which action creates the best economic outcome?”Head of Fresh / Produce / Store opsIncremental recovered margin
Read down the “primary question” column and the whitespace is visible: forecasting, observation, quality and pricing each have owners. The question of timing — measured in incremental margin rather than tonnes — is the one Departmint is testing.
Capabilities as publicly documented — not as we would like them to be.
| CAPABILITY | SMARTWAY | WASTELESS | FRESHFLOW | ONETHIRD | CLARIFRESH | FOCAL | DEPARTMINT |
|---|---|---|---|---|---|---|---|
| Fresh demand forecasting | ADJ — Related, not the core product | — — Not clearly public | CORE — Presented as a major capability | — — Not clearly public | — — Not clearly public | ADJ — Related, not the core product | — — Not clearly public |
| Ordering / replenishment | AVAIL — Publicly documented | — — Not clearly public | CORE — Presented as a major capability | — — Not clearly public | — — Not clearly public | AVAIL — Publicly documented | — — Not clearly public |
| Shelf-level computer vision | — — Not clearly public | — — Not clearly public | — — Not clearly public | ADJ — Related, not the core product | ADJ — Related, not the core product | CORE — Presented as a major capability | PLAN — Departmint — planned |
| Visual produce-quality analysis | — — Not clearly public | — — Not clearly public | — — Not clearly public | CORE — Presented as a major capability | CORE — Presented as a major capability | — — Not clearly public | PLAN — Departmint — planned |
| Shelf-life / commercial-life prediction | — — Not clearly public | — — Not clearly public | ADJ — Related, not the core product | CORE — Presented as a major capability | ADJ — Related, not the core product | — — Not clearly public | PLAN — Departmint — planned |
| Near-expiry / at-risk detection | CORE — Presented as a major capability | AVAIL — Publicly documented | ADJ — Related, not the core product | ADJ — Related, not the core product | — — Not clearly public | — — Not clearly public | VALID — Departmint — validating now |
| Markdown recommendations | CORE — Presented as a major capability | CORE — Presented as a major capability | — — Not clearly public | ADJ — Related, not the core product | — — Not clearly public | — — Not clearly public | VALID — Departmint — validating now |
| Dynamic pricing engine | AVAIL — Publicly documented | CORE — Presented as a major capability | — — Not clearly public | — — Not clearly public | — — Not clearly public | — — Not clearly public | — — Not clearly public |
| Inspection prioritisation | AVAIL — Publicly documented | — — Not clearly public | — — Not clearly public | AVAIL — Publicly documented | AVAIL — Publicly documented | ADJ — Related, not the core product | VALID — Departmint — validating now |
| Employee action workflow | CORE — Presented as a major capability | — — Not clearly public | CORE — Presented as a major capability | AVAIL — Publicly documented | AVAIL — Publicly documented | CORE — Presented as a major capability | VALID — Departmint — validating now |
| Economic-outcome optimisation | ADJ — Related, not the core product | AVAIL — Publicly documented | ADJ — Related, not the core product | — — Not clearly public | — — Not clearly public | — — Not clearly public | VALID — Departmint — validating now |
| False-positive / intervention-cost tracking | — — Not clearly public | — — Not clearly public | — — Not clearly public | — — Not clearly public | — — Not clearly public | — — Not clearly public | VALID — Departmint — validating now |
| Multi-store analytics | CORE — Presented as a major capability | AVAIL — Publicly documented | AVAIL — Publicly documented | AVAIL — Publicly documented | AVAIL — Publicly documented | CORE — Presented as a major capability | PLAN — Departmint — planned |
| Supply-chain freshness intelligence | — — Not clearly public | — — Not clearly public | ADJ — Related, not the core product | CORE — Presented as a major capability | CORE — Presented as a major capability | — — Not clearly public | PLAN — Departmint — planned |
| GCC deployment focus | — — Not clearly public | — — Not clearly public | — — Not clearly public | AVAIL — Publicly documented | — — Not clearly public | — — Not clearly public | CORE STRATEGY — Departmint — core strategy |
STRATEGY — Departmint — core strategy
Departmint has three columns' worth of dashes for a reason. No computer vision, no shelf-life model, no multi-store analytics, no pricing engine. Six rows are marked VALID — meaning we are testing whether we can do them at all, not claiming we do them well.
One row is genuinely unusual. We could not find any of these companies publicly presenting false-positive and intervention-cost tracking as a capability. That may simply be because it is not a selling point — but it is central to our thesis, so we are building the measurement in from the first pilot.
OneThird's GCC row is marked available, not ours. Its avocado scanners are publicly reported in the Emirates among 25+ countries. Being in the region first is a fact worth stating plainly on our own competitive page.
Five layers. Most companies own one of them well.
TARGET POSITION — NOT YET VALIDATEDLayers 1 to 4 have capable, funded companies inside them, several operating at a scale Departmint will not approach. The bet is that layer 5 — combining observed physical condition with commercial reality to choose an intervention — is a different product, and that it is currently underserved. That is a hypothesis, not a finding.
Documented geography — offices, customers and deployments.
Our first competitor is not a company. It's the way the store already works.
In every pilot conversation, the alternative to Departmint is not Smartway or Wasteless. It is a store manager with fifteen years of experience, a printed report, and a markdown routine that runs at the same time every day.
That incumbent is free, already deployed, requires no integration, and the team already trusts it. Departmint's first pilot has to beat that before beating anything on the matrix above matters.
No integration required
Staff understand it
No new vendor cost
Deep local knowledge
May respond late in the day
May not combine all signals
Economic feedback may be limited
Condition intelligence and commercial decisions are usually separate products.
The vertical axis is knowing what state the product is in. The horizontal axis is knowing what to do about it, and whether doing it paid. Most companies are strong on one.
NOT PRODUCT QUALITY OR COMPANY SCALE.
DEPARTMINT IS SHOWN AS A TARGET, NOT A POSITION.
Not every competitor has to be replaced.
A retailer already running an enterprise planning platform still has to decide what to do with the inventory physically sitting on the shelf this afternoon. That decision layer may sit on top of those systems rather than instead of them.
AS EVERY OTHER COMPANY ON THIS PAGE
+ COMMERCIAL DATA
+ INTERVENTION DECISION
Shown as a possible architecture only. Departmint has no partnerships, integrations or agreements with any company named on this page.
Because the thesis is not that retailers need another dashboard.
Physical perishable inventory may contain information that traditional retail systems do not fully capture. If that information materially changes commercial decisions, there is an opportunity for a specialised condition-intelligence layer. If it does not, there isn't — and that is the first thing worth finding out.
Competition is the strongest evidence we have that the problem is worth solving.
Smartway reports deployments in 12 countries and over 2,000 stores. Freshflow raised a $10M Series A in 2026 for fresh replenishment alone. Focal Systems runs shelf cameras with Walmart. OneThird sells scanners in more than 25 countries. Retailers are demonstrably willing to buy technology for fresh operations — so we are not betting on whether the problem exists.
The demand is proven
One narrow question
Built around GCC workflows
Measure the whole equation
Condition intelligence, later
Where the position could go — stated as a path, not a claim.
No established moat
Six companies, read from their own public materials.
We don't need every competitor to be wrong.
Departmint's first job is simpler than beating anyone: prove that one fresh-retail decision can be made earlier and more profitably than it is today, against the retailer's own current process.