CUSTOMER / WEB
Scan. Browse. Order.
A QR code will open a mobile-friendly menu in the browser. Tourists, event visitors and first-timers will not need an app to order.


Web + app platform
A fast browser path for first-time customers. Purpose-built apps for regulars, vendors and kitchens—around the same order journey.
No mandatory customer download. QR codes will open the current menu on the web; the optional app will make repeat ordering faster.
Explore each surfaceCONNECTED SURFACES
Not a single customer screen. Each surface will expose the controls its part of the service needs.
Pre-launch preview. The capabilities below are planned, are not available today, and may change or may not all be included at initial UK launch.
CUSTOMER / WEB
A QR code will open a mobile-friendly menu in the browser. Tourists, event visitors and first-timers will not need an app to order.
CUSTOMER / APP
Repeat ordering, favourites, preferences, loyalty, order history and order-status updates.
VENDOR / WEB + APP
Create menus, update availability, accept orders, manage fulfilment and see day-to-day reporting.
KITCHEN / DISPLAY
A kitchen display system will turn incoming orders into a visible preparation queue with clear status and collection hand-off.
DRIVER / DELIVERY APP
A Driver app for vendor-managed delivery is in scope for initial UK launch: delivery requests, pickup status, customer hand-off and proof of delivery. Delivery will be an optional paid add-on that vendors will be able to switch on.
Made for real service patterns. Vendors will update where they are trading, customers will pre-order collection slots, and groups will build one shared order that reaches the kitchen as one consolidated ticket.
DELIVERY AT INITIAL LAUNCH
Vendor-managed delivery is in scope for initial UK launch, as an optional paid add-on that vendors will be able to switch on. Drivers will be the restaurant’s own staff or contractors, vetted by the restaurant. UrbanBite will not vet, employ, supply or allocate drivers; it will provide the customer-facing app so that the delivery status travels with the order.
Customers will follow the delivery status, not the driver. The steps a customer will see are accepted, picked up, on its way and handed over, ending with proof of delivery, so a customer will not have to telephone the counter for an update. Third-party delivery integrations remain a later path, not an initial-launch promise.
CUSTOMER ORDER FLOW
Customers will scan and order instantly on the web. The app will make repeat ordering faster.
A QR code will open a vendor’s current menu straight in the browser.
Customers will browse item details, options and vendor-selected allergen information. Menu translations may be AI-assisted.
Customers will place the order on the web or in the app; the vendor will accept it before it is confirmed.
Order progress, then a clear ready-for-collection signal.
ALLERGEN SUPPORT
Written allergen information at the point of ordering is where UK food service is heading. A vendor moving to a digital menu now will have it built in already, whatever the regulatory outcome.
The Food Standards Agency’s best-practice guidance points one way: give customers written allergen information when they order. The proposal known as Owen’s Law — the campaign for mandatory written allergen information on menus, named for a young man who died after an allergic reaction to a restaurant meal — argues for the same thing. Where that settles is not for UrbanBite to predict. What a vendor decides now is whether the capability is already in place when it matters.
A customer will set their allergens in the app, choosing from the controlled UK allergen categories. The choices stay in their profile rather than on a note somebody has to repeat at every counter.
Placing an order will attach the allergen categories that were selected to that order, so the declaration is part of the order rather than something said across a busy counter and remembered second-hand.
The customer’s declared allergens travel with the order and are shown on the kitchen display alongside the items, so the chef sees them at the point of preparation.
The gap this closes is between what a customer tells the counter and what the chef actually sees.
An allergy mentioned at the till, on a phone order or in a note can stop at the till. With the declaration on the kitchen display in front of the person cooking, the kitchen has what it needs to look at its own preparation for that order — a shared fryer, cross-contact on a surface, a substitution made earlier in the shift — before the dish is made. Checking preparation for a declared allergen remains the kitchen’s responsibility. UrbanBite carries the declaration; the kitchen makes the judgement.
Allergen categories will come from a controlled UK list. A vendor selects from that list; nobody types an allergen name into an empty box.
Menu item names and descriptions may be AI-assisted. Allergen categories are handled differently: they use controlled local-language labels, so a customer reading the menu in another language sees the same category the vendor picked. AI will not translate allergen categories.
When a recipe changes, the vendor changes a label rather than reprinting a board, and the published menu updates with it.
FOR THE PERSON ORDERING
The best ordering experience leaves room for the food, the place and the people behind the counter.
SEE THE STARTING PATH
See how the business profile and menu come together before activation.