Business

Restaurant Stock Across Delivery Platforms (2026)

K By Kev 22 November 2026 10 min read
Share
Business guide

Managing restaurant inventory across delivery platforms is the problem behind a complaint most kitchen owners make in a different form: the stock count is never right. It is usually short, it is usually short by roughly the volume that went out on delivery, and the reason is simple — the counter draws down inventory and the delivery tablets do not.

On this page▾
  1. Why delivery volume vanishes from a stock count
  2. Holding one stock position behind every channel
  3. Where kitchens get stock wrong
  4. A worked example: a grill kitchen losing chicken
  5. How Veira handles stock behind several channels
  6. Frequently asked questions

Why delivery volume vanishes from a stock count

A stock position is only as good as the events that move it. When a counter sale rings through a POS, the ingredients behind that dish are accounted for. When an order arrives on a delivery tablet, cooked and sent, nothing moves: the platform recorded a sale, your inventory did not hear about it.

The effect compounds in a way that is easy to misread. Each individual discrepancy is small enough to blame on waste, portioning or staff, and all three are real problems that genuinely exist in kitchens. So owners spend months tightening portions and watching people, when the single largest line in the gap is simply unrecorded delivery volume.

There is a second, more expensive effect. If the stock position is wrong, every decision downstream of it is wrong too — reorder timing, supplier quantities, which items to promote, and whether a dish is actually profitable. A kitchen running 45% of its revenue through channels its inventory cannot see is not managing food cost. It is estimating it.

Want to see it running in your own business first?

Sign Up

Holding one stock position behind every channel

The aim is one inventory, drawn down by every sale regardless of channel. These are the steps in the order they pay off.

  1. 1

    Get every channel recording sales into one system

    Inventory moves on sales events. Until a delivery order is a sale in the system that holds your stock, no amount of counting will reconcile. This is the prerequisite for everything below.

  2. 2

    Build the recipe behind each sellable item

    A sale of a dish has to know what it consumes. Without that mapping, a sale reduces a dish count rather than an ingredient, and ingredient-level stock stays manual. This is the step kitchens most often skip and most often regret.

  3. 3

    Count once properly, as a baseline

    A full physical count gives the system a true starting position. Doing this badly poisons months of data, so it is worth closing for it or doing it after service with two people.

  4. 4

    Reconcile weekly on fast movers only

    Counting everything weekly will not happen. Counting your ten fastest-moving and highest-value ingredients weekly will, and it catches drift while the cause is still identifiable.

  5. 5

    Read the variance by channel before blaming the line

    With channel-tagged sales and one stock position, variance can be examined per channel. A gap concentrated in one platform is usually a portioning or packing issue specific to how that channel's orders are made up — a different problem from general waste.

  6. 6

    Set reorder points from real consumption, including delivery

    Once consumption includes delivery volume, reorder points stop being guesses. This is the step that turns the whole exercise from bookkeeping into money: fewer stockouts on your busiest items, less cash tied up in slow ones.

Where kitchens get stock wrong

Blaming waste and staff before checking the channels

Both are real, both deserve attention, and neither is usually the biggest line. Check whether the delivery volume is even in the count before investigating anybody.

Tracking dishes instead of ingredients

Dish-level counts tell you what sold. Ingredient-level counts tell you what it cost and when to reorder. Only the second one prevents a Friday stockout.

Expecting a POS to stop a platform selling a sold-out item

Availability on a marketplace listing is managed in that marketplace. A POS that holds your stock position can tell you an item has run out; pushing that state out to a platform listing in real time is a different capability, and Veira does not do it. Plan the manual step rather than assume it away.

Reconciling monthly

A monthly variance is a number you cannot act on. A weekly variance on ten items is a question with an answer.

Treating the first month of data as truth

Early variance is usually recipe mapping being wrong rather than stock walking out. Fix the recipes, then start trusting the numbers.

A worked example: a grill kitchen losing chicken

Worked example

A grill kitchen in Nairobi was running a persistent variance on chicken — around 8% of consumption, month after month, with no obvious cause. Portions had been re-weighed twice, the walk-in had a lock, and the owner had reached the uncomfortable point of suspecting staff.

The kitchen was doing roughly 40% of its volume on two delivery platforms, and none of it was drawing down stock. Once those orders were recorded as sales against the same inventory as the counter, the 8% did not disappear — it resolved into two different things. About six points of it was simply delivery consumption that had never been recorded. The remaining two points stayed, and that genuinely was portioning, concentrated in one dish that was awkward to plate into a delivery container.

The second finding was worth more than the first. With delivery consumption visible, the chicken reorder point was obviously wrong: the kitchen had been ordering to a counter-only consumption rate and running out most Saturdays, which it had been treating as a supplier reliability problem. It was an arithmetic problem, and it had been costing a weekend of lost sales most weeks.

Business impact

In a busy kitchen, unrecorded orders, comped meals and stock leaving the back door quietly eat the margin you worked all service to earn.

Veira ties every order to the bill and the stockroom, so covers, voids and portions all reconcile at close.

How Veira handles stock behind several channels

When Veira records an Uber Eats, Glovo or Bolt Food order as a sale, that sale draws from the same stock position the counter draws from. One kitchen, one inventory, moved by every sale regardless of which door it came through. That is the whole mechanism, and it is what makes the count reconcilable.

On top of that, Veira tracks ingredient consumption behind sellable items, flags low stock, records stock adjustments and transfers between branches, and reports inventory by channel — so variance can be examined per platform rather than as one unexplained number. Expiry dates are tracked where they matter, which in a kitchen is most of the fresh line.

The boundary to be clear about: Veira holds and reports your stock position, but it does not change an item's availability on a delivery marketplace listing. If something runs out, taking it off a platform menu is still a step someone takes in that platform's portal. Any vendor claiming otherwise should be asked to demonstrate it live.

Frequently asked questions

Why is my restaurant stock count always short?
Most often because delivery sales are not drawing down inventory. The counter reduces stock through the POS; a tablet order does not reduce anything. Waste and portioning matter too, but check whether delivery volume is in the count before investigating either.
Can one inventory serve the counter and every delivery platform?
Yes, if every channel records its sales into the system that holds the stock. In Veira the delivery integrations do exactly that, so all channels draw from one position.
Does a POS track ingredients or just dishes?
Veira tracks ingredient consumption behind the items you sell, which is what you need for food cost and reorder points. Dish counts alone tell you what sold but not what it consumed.
Can I stop a delivery platform selling an item that has run out?
Veira will show you that it has run out. Taking it off the listing happens in the platform's own portal — Veira does not change marketplace menus or availability. Build that step into your routine rather than relying on automation that is not there.
How often should a kitchen count stock?
A full count periodically as a baseline, and a weekly count of your ten fastest-moving and highest-value items. Weekly on everything does not survive contact with a real kitchen.
Can I see stock variance by delivery platform?
Yes. Because sales are tagged by channel and draw from one position, inventory reports can be read per channel, which is how you tell a packing problem on one platform from general waste.
Does this work across more than one branch?
Yes. Stock positions are held per branch with transfers between them recorded, so a multi-outlet operator can see each kitchen and the group.

A stock count that ignores half your sales is not a count, and no amount of portion discipline will fix it. Book a demo and bring one month of delivery volume — the reorder points are usually where the money turns up.

Need help, or want to talk it through first? Chat with us on WhatsApp
Terms explained

Keep reading

See all Business guides

Veira for your business

Want the full picture for this trade? Veira for restaurants covers the counter, the stock and the KRA side together.

On the Veira side of this: how orders reach the kitchen without a printed chit.

Browse Veira by business type · Who we serve