Ordering Platform for a Multi-Restaurant Chain
Every channel lands in one kitchen queue, with fewer missed orders and menus in sync across outlets.
- Sector
- Food & Hospitality · Restaurants · Food delivery
- Built with
- Next.js
- Node.js
- PostgreSQL
- Webhooks
01 · Discover
What the client needed
A restaurant chain took orders from several delivery apps on separate tablets, plus phone orders. Menus and prices drifted between apps and outlets.
Requirements
- Every delivery app’s orders in one kitchen queue
- Direct online ordering to reduce commission on repeat customers
- One menu with prices and availability per outlet
- Mark items sold out everywhere at once
- QR ordering at the table
- Sales and order reports by outlet and channel
Constraints
- Kitchens are busy: screens must be simple and fast
- Unreliable internet in some outlets
- Delivery app integrations have strict rules and rate limits
02 · Pitch
What we proposed
We spent time in two kitchens during service before proposing anything.
Options we weighed
What we agreed
- Order intake from delivery apps first, then direct and QR ordering
- A central menu manager with per-outlet overrides
- Offline-tolerant kitchen screens
03 · Build
How we built it
Orders from every channel are normalised into one format and sent to the right outlet’s kitchen screen.
Every requirement, and what we built for it
| Requirement | What we built |
|---|---|
| One kitchen queue | Delivery app orders received by webhook and shown on a single kitchen display |
| Direct ordering | A fast web ordering site and checkout under the chain’s own brand |
| Menus in sync | A central menu with per-outlet prices and availability, pushed to every channel |
| Sold out everywhere | One switch that updates the item across all apps and the website |
| Table ordering | QR codes per table that open the outlet’s live menu |
| Reporting | Sales and order volume by outlet, channel, and time of day |
Platform and architecture
- Ordering site and kitchen display
- Next.js
- Order service
- Node.js with webhooks for each delivery platform
- Data
- PostgreSQL for menus, outlets, and orders
- Resilience
- Kitchen screens that queue actions and catch up after a dropped connection
04 · Handover
Launch and handover
We rolled out one outlet at a time and trained each kitchen during a quiet shift.
- Pilot outlet, then a staged rollout
- Hands-on training for kitchen and front-of-house staff
- Menu manager training for the central team
- Support during the first weekends of each outlet
05 · Outcome
The outcome
Every channel lands in one kitchen queue, with fewer missed orders and menus in sync across outlets.
Every channel lands in one kitchen queue, and the central team controls menus for all outlets from one place.
- Fewer missed orders and no more tablet juggling
- Menus and prices consistent across apps and outlets
- A direct ordering channel the chain owns
More case studies
Have a project like this?
A few lines is enough. You’ll hear back from an engineer, not a salesperson.