Launching a New Item Across Forty Outlets Without It Drifting

New product development in F&B gets almost all of its attention at the front end. Months go into the concept, the tasting panel, the costing, and the photography. Then the item ships to the network, and the same organisation that agonised over two grams of seasoning stops measuring anything at all.

What follows is familiar. Sales are strong in week one, drift by week four, and the post-mortem produces a conclusion nobody can verify: the market didn’t want it. Sometimes true. Often, what the market didn’t want was the version it actually received — which had stopped resembling the item that was approved somewhere around outlet fifteen.

The three gaps a launch has to survive

The specification gap. The recipe leaves the test kitchen as a document. It arrives at the outlet as a PDF in a group chat, a laminated card, or a verbal briefing to whoever was on shift. Yields, sub-recipes, and substitutions get interpreted locally. Nobody intends to deviate; they’re reconciling an instruction with the equipment and ingredients actually in front of them.

The supply gap. A new item introduces new SKUs into a supply chain built around the existing menu. Forecasting demand for something with no sales history is genuinely hard, so outlets either run out during the launch window — the one period where trial matters most — or over-order and quietly write off the difference. Both outcomes get read as a demand signal. Neither is one.

The measurement gap. Launch performance is usually judged on units sold. Units sold conflates the item’s appeal with its availability, its execution, its placement on the menu, and whatever else was happening in the category that month. A weak number tells you something went wrong. It doesn’t tell you which of those five things it was — and without that, the next launch repeats whichever mistake it was.

Governing the recipe rather than distributing it

The difference between a recipe that holds and one that drifts is whether it lives in a system or in a document.

The Resource Management System (RMS) governs recipes, sub-recipes, yields, and BOMs centrally and pushes them to every outlet without version drift. When the test kitchen finalises the item, that specification is what production runs against — with batch tickets and pick lists generated from it, and theoretical usage derived from it. A version-two tweak in week three reaches every outlet at once, instead of reaching the outlets whose managers read the message.

That also makes the economics real rather than projected. A launch costing built on the test-kitchen recipe assumes perfect yield. Actual usage against theoretical usage, measured per outlet from the first week, tells you whether the margin you approved is the margin you’re earning — and which outlets are executing it as specified.

Because the same system carries production planning, replenishment, and inter-branch transfers, the supply problem gets smaller too. Launch stock can be positioned against rolling outlet demand rather than a flat allocation, and the outlets that sell faster can be replenished from the ones that don’t — instead of the network simultaneously stocking out and writing off.

Reading the launch signal properly

Internal sales data tells you what happened inside your business. It can’t tell you why, because the cause is often outside it.

Adqlo measures the conversation — engagement, sentiment, creator activity, and share of voice across TikTok, Instagram, X, Facebook, and YouTube — for your brands and the competitors in your category. During a launch, that’s the difference between two very different diagnoses of the same soft number: an item nobody is talking about, or an item people are talking about warmly that isn’t converting at the counter. The first is a product or marketing problem. The second is an execution or availability problem. They have opposite remedies, and units sold alone cannot distinguish them.

The AI-Kitchen Command Center is where those streams meet. Sales, production, stock, and social signal in one place turns a launch review into a specific question rather than a general one: which outlets are underperforming relative to their footfall, whether their variance suggests execution drift, whether the soft regions are the ones where a competitor is loudest, and whether the pattern started on a particular date.

And for the human layer, MindFlow Online Academy turns launch training into something that scales past a briefing — structured modules with examinations, so the thirtieth outlet gets the same instruction as the pilot store rather than a summary of a summary.

What a well-run launch looks like

• One specification, everywhere. The item that sells is the item that was approved, because the recipe is governed rather than distributed.
• Margin measured from week one. Theoretical-versus-actual usage per outlet exposes drift while it’s still correctable.
• Stock follows demand. Replenishment and transfers respond to what’s actually selling, not to a launch allocation set before anyone knew.
• The verdict is diagnostic. You know whether the item failed, the execution failed, the supply failed, or the category moved.
• The next launch is better. Because the post-mortem produced a cause instead of a consensus.

The uncomfortable part

Most F&B groups have discontinued items that would have worked. They were withdrawn on evidence that couldn’t separate a weak concept from a weak rollout, and the organisation drew a lesson about customer taste from what was really a lesson about its own operations.

That’s an expensive way to learn, and it compounds — because each wrongly-read launch narrows what the business is willing to try next.

The alternative isn’t more caution at the front end. Development is already the well-resourced part. It’s applying the same rigour to the two hundred metres between the test kitchen and the pass.

---

Make your next launch land the way it was designed. Book a demo to see how RMS and Adqlo keep a new item consistent — and tell you honestly how it performed.