The counter checks messages
Changes sit beside the order instead of becoming the order.
Skip to operator pitch
J'Toye / operator pilot
Built for the service you already run
One London cluster · owner-led food businesses
Keep the order. Keep the customer. Keep the kitchen moving.
An assisted pilot for established Nigerian and West African takeaway and catering operators with recurring order volume — built around your direct customer relationship, not a marketplace.
Service railOnline orders
Your direct storefront
A customer path you control.
Your browser kitchen display
For online orders while connected.
Your service decisions
You set the menu, hours and handover.
The service leak
One change. Three channels. Two versions of the order.
The kitchen works from memory
Availability, portions and handover details become verbal.
The owner carries the risk
The customer still expects one accurate promise.
J'Toye's pilot tests one practical result: can a direct order move from customer agreement to kitchen handover with fewer places to check?
Two jobs. Different pressure.
Choose the part of service you need to steady first.
One pilot can learn from both paths, but they should not be sold as the same job.
Daily service
Takeaway: protect the regular order
Give repeat customers a direct way to order, and give the counter a clearer handover when the kitchen is busy.
- Direct storefront, menus and trading hours
- Online-order visibility in the browser kitchen display
- Vendor-controlled customer and menu information
Event service
Catering: make the handover legible
Explore how event details, dietary notes and a final handover could be kept clearer for the people doing the work.
Catering and WhatsApp are validation tracks. They are not current, guaranteed production workflows.
Assisted, not abstract
A four-step pilot that respects the shift.
- 01
Map your service
Work through your menu, trading hours and the customer journey you already run.
- 02
Set up the direct path
Prepare your storefront and ordering flow together, rather than handing over a blank dashboard.
- 03
Run a real service
Use the browser kitchen display for online orders while you remain responsible for fulfilment.
- 04
Review before expanding
Look at what worked in the pilot and agree the next operating step together.
Pilot terms, plainly stated
No mystery maths at the counter.
Core
£39 per location, per month
Assisted setup
From £99, scoped to the work agreed
Pricing test
0.5% of direct sales or £79–£119 fixed
High volume
£149–£199 option, agreed for higher-volume operations
Card fees are shown transparently. Payment arrangements must be confirmed before taking payments; the current platform is not production connected-account settlement.
A responsible pilot is clear about the edges
Useful help does not remove operator responsibility.
What the pilot can support
- A direct storefront does not generate demand; you remain responsible for bringing customers to it.
- The browser kitchen display works for online orders while it is connected; it is not an offline KDS.
- You retain responsibility for your menu, prices, fulfilment and customer relationship.
What needs your judgement
- Allergen information is vendor-entered assistance, not a compliance service or legal advice.
- Catering and WhatsApp are validation tracks, not promised production capabilities.
- Payment arrangements must be confirmed; this is not production connected-account settlement.
No form. No lead capture.
Check your pilot fit.
Make a short local summary for your own discussion. Nothing is sent anywhere.
If this sounds like your service, return this pack to the person who shared it and ask for a pilot-fit conversation.
Bring your current order channels, a typical busy-service example, and the one handover problem you most want to remove. No acceptance or payment is implied by the conversation.
J'Toye operator pilot packEdition 10 July 2026 · UK pilot hypothesis