Par Levels Are Last Year's Guess: Replenishment Across an Outlet Network

Somewhere in every outlet network there is a par sheet. It lists what each outlet should hold of each item, and it was written — carefully, by someone competent — around the time the outlet opened. Since then the menu has changed twice, the neighbourhood has changed, delivery has become a large part of the business, and the person who wrote it has moved on. The numbers haven’t changed at all.

For most operators, that sheet is the heart of the supply chain. Every order an outlet places on the central kitchen is some version of “par minus what’s on the shelf.” When par is wrong, everything upstream is planned against the wrong number.

How a network amplifies small errors

Replenishment in a central kitchen network is a chain of people, each making a sensible local decision.

The outlet manager ran out of something on a busy night, got an earful for it, and now orders a little over par to be safe. The central kitchen sees orders from every outlet, knows some are padded but not which, and produces a little over total demand to be safe. Purchasing sees a production plan with a buffer already built in and buys a little over that to be safe — because a supplier shortfall would stop the kitchen.

None of these people is wrong. Each buffer is small and defensible. Stacked together, the network holds far more stock than demand requires, and the extra sits exactly where F&B can least afford it: in perishables, ageing in chillers, across twenty locations.

Supply chain specialists call this the bullwhip effect — small swings in demand at the counter becoming large swings in orders further up the chain. In F&B it has a recognisable signature: rising waste at the outlets, rising production at the central kitchen, and stockouts anyway, because the buffers were built on the wrong items.

Why par levels go stale

They are static in a dynamic business. A par level is a single number for a quantity that varies by day of the week, season, promotion, and weather. Friday and Tuesday share the same par, which means one of them is always wrong.

They’re set by the outlet, for the outlet. Local knowledge is valuable, but an outlet only sees its own shelf. It can’t see that the outlet two kilometres away is overstocked on the same item, or that the central kitchen is short of capacity on that product this week.

Nobody owns reviewing them. Setting pars is part of opening an outlet. Reviewing them is part of nobody’s job. New items get pars when they launch; pars for retired items linger, quietly reserving shelf space and cash.

The data that would fix them lives somewhere else. Actual consumption is in the POS and the stock movements. Pars sit on a sheet, or in a field nobody updates. Unless the two are connected, the gap between them only grows.

From par sheets to demand-driven replenishment

The answer isn’t to abolish outlet judgement. It’s to give replenishment a better starting number, and to make the whole network visible to the people placing orders.

Start from consumption, not habit. A suggested order should come from what the outlet actually sold and used — by item and by day of the week — plus what’s expected over the coming days, minus what’s genuinely on hand. The outlet manager can still adjust it. The difference is that they’re adjusting a number grounded in evidence, not a guess from two years ago.

Keep stock live, so “on hand” means on hand. A suggested order is only as good as the stock figure it subtracts. If on-hand is last night’s count adjusted by memory, the order will be off in both directions. RMS keeps stock-on-hand live across outlets and central kitchens — receipts, production, transfers, sales, and wastage all moving the same record — so the starting position is real.

Plan production against the whole network. When outlet demand flows into one place, the central kitchen can plan against rolling outlet demand instead of a pile of padded orders. RMS turns that plan into pick lists and batch tickets, so what gets produced is what the network actually needs.

Transfer before you produce. An item that is short at one outlet and overstocked at another is a transfer, not a new order. Recording inter-branch transfers in the same system means the surplus gets used and the trail stays intact — batch and expiry travel with the stock.

Let something watch the drift. Even good suggested orders need oversight. The AI-Kitchen Command Center watches each outlet and product against its own baseline and flags when ordering, waste, or stockouts move out of pattern — the outlet that consistently orders well above what it consumes, the item whose waste is climbing while its sales are flat. Those are exactly the local buffers that add up to a network problem.

What changes when replenishment follows demand

• Less stock at every link, because buffers are sized to real variability rather than anxiety.
• Less waste, because perishables are ordered close to consumption.
• Fewer stockouts where they matter, because safety stock goes where demand is volatile, not everywhere equally.
• A calmer central kitchen, producing to a plan instead of reacting to whichever outlet shouted loudest.
• Better conversations with outlet managers, because the question shifts from “why did you run out?” to “the system suggested this and you ordered that — what did you know that it didn’t?”

A quick diagnostic

Take one outlet and five of its highest-volume perishable items. Compare the par level on file with the last four weeks of actual daily usage for each.

If the pars sit within a reasonable range of real usage on most days, replenishment is in decent shape. If they’re comfortably above usage on quiet days and short on busy ones — which is exactly what a single static number does — then the central kitchen is planning against fiction, and the waste line on your P&L is what it costs.

---

Replenish against demand, not habit. Book a demo and we’ll look at how RMS would plan replenishment across your outlets and central kitchen — starting from the consumption data you already have.