How an order moves through Ukoni: two doors in, one validated record, a dispatch agent that checks every order, and payment before the kitchen fires.
Scroll for the six stops
Every order, whichever door it comes through, walks the same path. Nothing is special-cased, nothing is lost.
Customer orders on the website or by WhatsApp message.
CustomerThe order API writes one record: items, requirements, contact, reference.
SystemDispatch agent checks the order, de-duplicates, confirms details and stock.
Dispatch agentPayment received before the kitchen starts. No payment, no prep.
CustomerFinal dispatch hands the confirmed, paid order to the kitchen.
KitchenOrder leaves the kitchen, reaches the customer, and the record closes.
CustomerA customer can order two ways. Both land in the same API, so the kitchen sees the same order either way.
The menu page carries a built-in order widget. The customer browses the menu, builds a cart, and checks out.
The customer gets an order reference like UK-4FT9X2 and a status link on the spot.
The restaurant's WhatsApp number is the second door. A customer can message an order in plain text or use a deep link from the site.
Either way the order becomes the same record with the same reference format.
The order API validates and stores every order in a single store. The record keeps the food required, the requirements added, the customer, and the money.
The record stores the items with quantities and prices, plus any note the customer adds. Nothing about the order lives outside the record.
Every order gets a unique UK-XXXXXX reference. The customer, the dispatch agent and the kitchen all talk in that reference.
The API checks name, phone, items and notes before anything is stored. Bad payloads are rejected before they reach the kitchen queue.
Each record carries a status that starts at received and moves forward in a controlled sequence. At any time, someone can ask: where is this order?
Before the kitchen spends time or fuel, the dispatch agent runs the checks that keep the queue clean. This is where duplicates die.
Same phone, same items, too fast to be two real orders? The agent flags it. The rate limit already blocks more than three orders per phone per hour, and the agent catches repeats the filter misses.
The agent confirms the order with the customer by phone or WhatsApp before it moves on: items, requirements, total, delivery or pickup.
Is the catfish in? Is the kitchen already stacked? The agent only pushes orders the kitchen can actually produce.
A clean order moves to confirmed. A duplicate or a dead end gets cancelled early, before anyone cooks it.
The kitchen does not fire on promises. Payment is the gate between a confirmed order and food on the fire.
Once the customer pays, the dispatch agent sends the order to final dispatch and the kitchen starts preparing.
The kitchen starts when the money is in. No wasted ingredients, no ghost orders holding a spot in the queue.
The record carries the exact total from the start. Payment matches the record; the customer is never surprised at the door.
Because every order is confirmed, validated and paid before prep, the kitchen produces to a plan instead of reacting.
After payment, the order walks a visible status journey. The customer and the restaurant watch the same line.
The order API stores the record and issues the reference. This is where every order starts.
Validated, de-duplicated, and confirmed with the customer. Ready for payment.
Payment received. Final dispatch hands the order to the kitchen and cooking starts.
The food leaves the kitchen, on the way to the customer or ready for pickup.
Food in hand, record closed. Cancelled is the only exit before delivery.
Satisfaction is not a slogan. It is a status link the customer can open, a reference that works, and a kitchen that only takes orders it can actually serve.
Every order has a status link. The customer pastes the reference and sees where the order stands, no login, no app.
/api/order/status?ref=UK-4FT9X2Questions, changes, a delay? The same WhatsApp number that took the order answers it. The agent sees the record instantly.
No payment-before-prep means no cancelled surprise. The customer only waits for food that is actually on the fire.