Tablebond

Guide

How much your cloud kitchen loses on every delivery order

A 15-dollar dish nets 10.50 after a 30 percent commission. If it costs 11 dollars to make and deliver, you lose money on every order, while your POS cheerfully records a sale. Cloud kitchens run several brands on thin data across platforms that own the customer and set the rules. The leaks below are the ones the platforms will never point out.

Price parity: the un-marked-up ticket

Menus get priced for the kitchen's own economics, then copied to aggregators without absorbing the commission. All-in delivery costs often reach 30 to 40 percent of an order once commissions, promos, and error charges stack. Any item not marked up accordingly sells at a loss, invisibly, at volume.

The fix is a watchdog, not a memory: a dashboard built from your menu and cost exports that flags every item whose platform price minus commission minus food cost falls below your margin floor, and suggests the corrected price.

Per-brand blindness: one kitchen, five P&Ls

A well-run single-brand cloud kitchen nets 15 to 20 percent; heavy aggregator dependence drags that to 8 to 12. Run five virtual brands off one prep line with one blended number, and a brand can lose money for months while the kitchen total looks fine.

Per-brand, per-platform P&L from your order exports turns that into a decision: fix the two mispriced items dragging a brand down, or retire the brand and give its prep time to a winner.

The phantom 86: sold out in the kitchen, live on the app

An item runs out mid-rush and nobody toggles it off. Every resulting cancellation counts against you: platforms deprioritize listings once avoidable cancellations pass about 1.1 percent, which on 50 orders a day is just two mistakes. The penalty is a quiet visibility cut across the whole menu.

A one-tap 86 flow, mark it out everywhere, alert the line, remind you to relist, keeps a stockout from becoming an algorithm problem.

Error charges: the refunds nobody disputes

Roughly 3 percent of aggregator orders get refunded, versus 0.1 to 0.2 percent on first-party channels, and each claim is deducted from your payout, often at full value. Operators who dispute with evidence recover around 60 percent. Most never dispute, because nobody logs the claims or watches the deadlines.

A deduction ledger fixes the bookkeeping half: every error charge logged with its evidence and its dispute window, and a reminder before the window closes.

The structural fix: own some of your customers

Every lever above protects margin inside the aggregators' walls. The bigger move is routing repeat customers to a direct channel, your own ordering site or WhatsApp flow, where commission is zero and the customer is yours. Direct customers also spend 15 to 20 percent more over their lifetime.

You do not need to leave the platforms. You need the platforms to be your customer-acquisition cost, not your entire business model.

Key takeaways

Find out which orders are losing money

Tablebond builds the margin control room for cloud kitchens: per-brand P&L, price-parity flags, deduction tracking, and direct ordering. One-time setup from $1,000.

Protect my delivery margins

Questions, answered

Take each item's platform price, subtract the commission and your food cost, and compare against your margin floor. A watchdog dashboard does this from your menu and cost exports and flags the failures automatically.

Almost always yes. Most operators mark up aggregator menus 20 to 30 percent to absorb commission. Platforms allow it, customers expect it, and not doing it means selling at a loss.

Yes. Claims are deducted automatically, but operators who dispute with evidence, photos at handoff, order logs, recover around 60 percent. The money is lost only when nobody tracks the deadline.

For repeat customers, yes. A direct ordering flow with zero commission, plus a nudge in every bag, shifts your regulars over time. Each migrated customer is margin recovered on every future order.