You know this already.
None of this is a software problem yet. It is just lunchtime.
Signing a court onto one platform normally means asking ten independent businesses to abandon their own systems and trust the landlord with their sales.
A diner sitting at your table wants food from three stalls, and pays for that in walking.
Your tables aren’t any stall’s tables, so no stall’s screen shows them and no stall manages them.
Which is the question every operator asks, and the one every tenant fears.
The court behaves like one dining room with ten kitchens behind it.
Each stall’s order is paid separately, straight to that stall’s own till, before it reaches that stall’s kitchen. No queuing at one counter then another, no buzzer to carry and return.
Every stall’s orders on one venue-wide board, so a diner watches a screen instead of standing in three queues to feed two people.
Each stall stays its own organisation — its own menu, staff, till, money, KRA PIN and dashboard. Joining is a two-way handshake: the venue invites, the stall accepts, and either side can leave.
Order volume, peak hours, category mix and how the court is trending. You do not get a named tenant’s individual sales — the operator view is aggregate by construction, not by policy, and that limit is why stalls sign.
Your M-Pesa money never touches us.
Diners pay your own M-Pesa till or Paybill. The money never passes through Tumikia, and we add nothing to it.
The diner enters the code from their SMS. Staff confirm it on your own M-Pesa before the kitchen sees the order, and a code used before is refused.
Card payments on the diner’s phone have 3-D Secure on every one, and settle to your M-Pesa or bank within 2 business days.
A camera and a browser. That is the entire requirement on their side.
eTIMS integration coming. VAT is calculated on every bill by your location’s VAT mode. eTIMS integration is coming, and isn’t switched on yet.
Four things a till with a QR code bolted on cannot do.
The diner scans and orders. Anything you have to convince someone to install, they won’t.
Diners pay your own till or Paybill. Cards on the diner’s phone, card terminals and cash sit on the same tab.
You reach your customers; you never hold their contact details. One fewer compliance surface for your business.
Most QR ordering is a utility bolted onto a till system, and it shows on the phone. Tumikia started at the table and worked backwards.
The three things venues say next.
Joining is a two-way handshake — the venue invites and the stall accepts, and either side can leave. That one design decision turns the tenant conversation from a negotiation into a short yes. Court QRs work with the stalls that are live, and the rest join when they watch the queue move past them.
The stall’s, from the first shilling. Each stall’s order is paid separately, straight to that stall’s own till. Nothing is pooled, nothing is split afterwards, and nothing passes through the venue or through Tumikia.
Court QRs go on venue tables and reach every stall. Because the seating belongs to the court rather than any single tenant, your courtesy tables stay out of stalls’ own floor views — no stall’s screen fills up with tables they do not serve.
Your menu, your money, your customers, your KRA PIN, your dashboard. The court sees the court — never your books.
What you actually get.
Questions we get about food courts and malls.
A food court ordering system lets diners order from several stalls in a shared dining area from their table, usually by scanning a QR code. In Tumikia each stall’s order is paid separately, straight to that stall’s own till.
Pilot one court.
Start with three stalls and one row of tables. We handle stall onboarding.
Three details. Start with three stalls and one row of tables — we handle stall onboarding.
One call, and if it isn’t for you that’s the end of it.