Invafresh: fresh item management for grocery

What Invafresh is

Invafresh builds software for the fresh departments of grocery retailers: the produce, meat, seafood, deli, bakery and prepared-food areas where the product has a shelf life measured in days. The company's own boilerplate describes it as "the leader of Freshology," a term it coined, and states that Invafresh is "deployed in more than 25,000 grocery stores spanning a global reach of 35 countries with $100's of millions of Fresh revenue being transacted daily, to provide AI-enhanced demand forecasting, merchandising, replenishment, and sustainability and compliance."

That last clause is the product scope in one line. Invafresh is not a general merchandising system that happens to handle produce. It is built around the constraint that makes fresh different from every other part of the store.

Why fresh is a separate software category

Centre-store replenishment and fresh replenishment look like the same problem and are not. The difference is what happens to a wrong answer.

A centre-store buyer who over-orders a case of crackers has made a working capital mistake. A produce manager who over-orders strawberries has destroyed the product. That asymmetry is why fresh forecasting runs at a different cadence and tolerates a different kind of error, and why software built for one tends to be wrong for the other.

The in-store transformation step compounds it. A case of chicken arrives as one item and leaves as several: whole birds, breasts trimmed in the back room, marinated portions in the service case, and cooked product in hot foods. The system has to hold a recipe-like relationship between what was received and what is sold, which is not a relationship centre-store inventory models represent at all.

The waste-versus-availability trade

Every fresh decision sits on one axis with a bad outcome at each end. Order tight and the case is empty by Saturday afternoon, which costs the sale and trains the shopper to buy that category elsewhere. Order loose and the margin goes into the shrink bin on Monday.

Consider an illustrative week for one item at Sunrise Market:

Take a 40% gross margin, which is ordinary for fresh. Contribution is units sold at margin, less units wasted at cost, and the ranking comes out balanced (49% of one unit's retail price), then tight (46%), then loose (30%).

Two things follow, and neither is visible from a single column.

The waste report picks the wrong winner. Tight wastes 2 units and looks excellent on the metric fresh managers are most often held to. It still loses to balanced, because the 21 extra units balanced sells earn full margin while the 9 extra units it wastes cost only cost. That trade favours balanced at any margin above 30%.

Loose is the genuinely bad policy, and the waste report is right about it. Forty-six units in the bin is a third of the order destroyed. Loose only beats tight if margin runs above about 63% of retail, which no fresh department sees.

So neither number is decisive alone: waste alone would pick tight, availability alone would pick loose, and both are wrong. That is the analytical reason fresh platforms report the pair together, and why the margin assumption belongs alongside them.

What its data holds, and what it does not

For a brand-side analyst, the useful thing to know is what kind of record this is. A fresh item management system is a retailer-operations system. It holds that retailer's own forecast, order, receipt, production and shrink data at store and item level.

Three consequences follow:

It is one retailer's view, not the market's. Invafresh data describes the chain running it. It carries no category benchmark and no competitor movement, so it cannot tell you whether a decline is yours or the category's. That question needs syndicated data.

Its shrink figures are operational, not promotional. Waste in a fresh system is product discarded. It is not the same number as retail shrink in a loss-prevention sense, and the two get conflated in conversation constantly.

Weight-based items break unit math. Where product is sold by weight, "units sold" is a derived figure and depends on average weight assumptions that the retailer sets and periodically revises. Comparing unit velocity across a revision is comparing two different definitions.

Fresh is also the part of the store where on-shelf availability is hardest to measure honestly, because a case can be full of product that is technically in date and visibly past its best, and no system field records that.

The short version

• Invafresh builds fresh item management software for grocery: produce, meat, seafood, deli, bakery and prepared foods.
• The company states it is deployed in more than 25,000 stores across 35 countries, covering demand forecasting, merchandising, replenishment, and sustainability and compliance.
• Fresh is a distinct category because an over-order is destroyed product, the horizon is often same-day, and items are transformed in store.
• Waste and lost sales have to be read as a pair. Optimising either alone reliably produces the wrong policy.
• Its data is one retailer's operational record, with no market view and with weight-derived unit counts that need their assumptions stated.

Sources: Invafresh company boilerplate, "Invafresh Strengthens Capabilities of its AI-Enhanced Fresh Retail Platform Solution".