The main workflow, step by step
The window follows one delivery order from the customer's phone to the door, and the head office view behind it. Choose a step to see its screen. The restaurant group, the branch and the order are invented for the demonstration.
Order
Saffron Road KitchensBasket- Branch
- Chosen from the delivery address
- Items
- Two mains, one side
- Changes
- No onion, extra sauce
- Ready in
- Estimate from the kitchen load
Off the pathAn address outside every branch's delivery area is offered collection from the nearest branch instead.
Checkout
ORD-58231Paid| Line | Detail |
|---|---|
| Payment | Card, saved for next time |
| Loyalty | Points added to the account |
| Updates | By notification and text |
Off the pathIf payment fails, the basket is kept and the customer is offered another method without starting again.
Kitchen screen
ORD-58231Cooking| Item | Note |
|---|---|
| Chicken biryani | No onion |
| Lamb karahi | Extra sauce |
| Garlic naan | Bake last |
Off the pathAn item that has just run out is marked unavailable by the kitchen, and the customer is asked to choose a replacement or a refund.
Delivery
ORD-58231On the way- Pickup
- Branch, bag sealed and checked
- Drop
- Address with gate code
- Customer
- Sees the driver approaching
- Proof
- Handover confirmed
Off the pathA customer who cannot be reached triggers a call from the branch, and the order follows the rule you set for no-shows.
Head office
All branchesOne branch paused| Branch | State |
|---|---|
| City centre | Normal, on time |
| Riverside | Busy, longer estimates |
| Airport road | Delivery paused by manager |
Off the pathWhen a branch pauses delivery, its area passes to a neighbouring branch only if you have allowed that overlap.
Who uses it, and what each role can do
Head office wants consistency and each branch needs control over its own service. The roles divide menu, pricing and daily operation between them.
| Role | Sees | Can do |
|---|---|---|
| Customer | Menu for their branch, their orders and loyalty | Order, pay, track and reorder |
| Branch manager | Orders, stock availability and opening hours | Pause items or delivery, issue refunds within limits |
| Kitchen staff | The order screen for their station | Accept, mark ready and flag missing items |
| Driver | Assigned deliveries with addresses | Collect, deliver and confirm handover |
| Operations manager | All branches, menus, prices and reports | Change the menu, set delivery areas and rules |
When the work leaves the usual path
A dinner service produces every kind of problem in an evening. The platform has to deal with these without a phone call to head office.
| Situation | What the system does | Who decides |
|---|---|---|
| Address outside all delivery areas | Offers collection from the nearest branch | Operations manager |
| Item runs out mid-service | Kitchen marks it off and customers are told | Branch manager |
| Branch too busy to keep its promise | Lengthens estimates or pauses new orders | Branch manager |
| Payment fails | Keeps the basket and offers another method | Customer |
| Customer not reachable at the door | Prompts a call and applies your no-show rule | Branch manager |
| Order wrong or late | Records the complaint and the refund or credit | Branch manager |
| Till or printer offline at a branch | Holds orders on the kitchen screen and alerts | Operations manager |
What it connects to
Orders must reach the kitchen and the till without retyping. Which of these connections is possible depends on the point-of-sale system each branch runs.
| System | What moves | Direction |
|---|---|---|
| Point-of-sale system | Menu items, prices and incoming orders | Both ways |
| Payment provider | Card and wallet payments, refunds | Both ways |
| Delivery partner or own fleet | Jobs, driver location and status | Both ways |
| Loyalty or CRM | Customers, points and offers | Both ways |
| Accounting | Daily sales by branch and channel | Out of the platform |
What a first release includes
Web and app ordering
Ordering for delivery, collection and the table, under your brand, on the web and in the app stores.
Central menu management
One menu with modifiers and photographs, with prices, availability and hours controlled per branch.
Order routing
Delivery areas per branch, with the order sent to the right kitchen and a realistic time estimate.
Kitchen screens
A display for each station showing what to cook next, with notes and allergens highlighted.
Delivery tracking
Driver assignment, live status the customer can follow and proof of handover at the door.
Loyalty and reorder
Accounts with points, saved addresses and one-tap reordering of a favourite meal.
Often added after the first release
- Table ordering by code at the table
- Catering and large advance orders
- Gift cards
- Kiosk ordering in the branch
- Reservations
What we need from you
- Your menu with modifiers, and how it differs by branch
- The point-of-sale system in each branch and what it can connect to
- Delivery areas and whether you use your own drivers
- Your payment provider and loyalty rules
- A branch manager and a head chef to test during a real service
Ownership and licensing terms are defined in the project agreement.
What to do next
Send us your menu and a list of your branches with their point-of-sale systems. We reply with what can be connected, a first release and a proposal. Start a conversation or book a 30-minute call.
Common questions
Can this replace the delivery marketplaces?
It gives you your own channel alongside them. Regular customers who already know you can order directly, with your prices, your loyalty scheme and no commission. Marketplaces still bring in people who have not heard of you. Many groups keep both and move existing customers to direct ordering over time.
Will it connect to our point-of-sale system?
That depends on the system. Many offer an interface for menus and orders, some through an approved partner, and a few offer none. We check each branch's system before promising anything. Where no connection is possible, orders arrive on a kitchen screen and a printer, and sales are reported to accounting separately.
How are allergens handled?
Allergen information is entered per menu item by your team and shown to customers before they order, with customer notes highlighted on the kitchen screen. The platform displays what you provide. Food information rules differ by country, and responsibility for the accuracy of allergen data and for kitchen practice remains with the restaurant.
Do we need our own drivers?
No. The platform can assign orders to your own drivers, pass them to a delivery partner or support collection only. Some groups use their own drivers at busy branches and a partner elsewhere. The choice affects cost and control, and it can differ from one branch to the next.