Takeaways and delivery operators — Deliveroo / Just Eat / Uber Eats consolidation, kitchen prep, customer comms, refund flow. Order in, out, delivered — one screen.
01 · Multi-platform consolidation
Deliveroo, Just Eat, Uber Eats — one queue.
Three tablets become one screen. Order tickets unified, menu sync built in, mismatch alerts when a platform price drifts from the master menu. The 7pm chaos engineered down.
Deliveroo + Just Eat + Uber Eats
Master menu, single source
Price drift alerts
Order ticket unification
02 · Kitchen display & prep
KDS, prep, pass — synced.
Kitchen display system grouped by station, prep generated from rolling order projections, pass-side ticket clearance audited. Less printer paper, less lost ticket, less reheat.
Station-grouped KDS
Rolling prep projections
Pass clearance audit
Reheat / remake tracking
03 · Customer comms
Delays, status, the awkward call.
Order delayed twenty minutes because the rider didn't show? The customer hears it from you, not the platform's auto-message. Templated, owner-tone, sent via SMS / WhatsApp / platform-native.
Delay + status SMS / WhatsApp
Templated owner-tone copy
Platform-native fallback
Resolution log per order
04 · Refund flow + dispute
Refunds, disputes, evidence.
Platform refund disputes captured with the evidence — KDS timestamp, prep photo, rider handoff log — so the platform can't quietly absorb the cost on you. Pattern-watching for habitual abusers.
Refund evidence pack
Platform dispute workflow
Habitual abuser pattern
Per-platform refund rate
05 · Per-platform margin
Which platform actually pays.
Revenue minus commission minus packaging minus refund leakage, per platform, live. The conversation the operator needs to have but never has the data for. Sometimes Just Eat is the loss leader.
Per-platform commission tracked
Packaging + driver allocated
Refund leakage netted
Per-platform margin dashboard
06 · BrainBase
Recipes, packaging, training — indexed.
Recipe specs, packaging spec per item, allergen reference, training videos, opening checklists — findable from the kitchen tablet or the new prep cook's phone. Multi-brand kitchens stop confusing the brands.
Recipe + packaging spec
Per-brand allergen reference
Training video stack
Opening + closing checklists
Sample engagement
The 3-brand cloud kitchen that lifted on-time delivery eighteen percent.
Three brands. Three tablets. 600 orders a week. Friday night a printer war.
A cloud kitchen ran three brands off three platform tablets, one printer, and a head cook calling out tickets. Friday on-time rate was 71%. Three-week build: consolidated KDS pulling from all three platforms, station-grouped tickets, prep projection from rolling 4-week order history, delay-comm SMS templated to the brand. Three months in: on-time delivery up to 89%, refund rate down 34%, head cook stopped shouting.
How we measure: On-time delivery measured as platform-reported delivery time vs promise (n = 7,800 orders, 12 weeks); refund rate from platform exports; head-cook shift stress logged via daily check-in.
+18%on-time delivery
−34%refund rate
+£11kmonthly margin recovered
Builds for restaurants & food
Use cases that fit.
Each is a tightly-scoped build, fixed price, owned by you.