You know this already.
None of this is a software problem yet. It is just the second night.
Someone at the door squinting at a screenshot, deciding whether it has already been used.
Two people tapped buy on the last ticket at the same instant, and one of them gets an apology in the morning.
Cash at a festival is a leak with a queue attached, and the takings get argued about at 2am.
The poster, the radio spot and the WhatsApp blast all went out. None of them reported back.
Gate to bar to the last plate, on one system that packs down when you do.
Tickets are QR codes on the buyer’s “My tickets” page and in their email. The door is a proper operations station, and it needs a data connection. Capacity is enforced race-safe at purchase: two people tapping buy on the last ticket, one gets it.
Nothing to divide up at 2am and no dispute about who sold what. Where cash is unavoidable it runs through till sessions with a float, a count and a variance attached to a name — the same discipline a restaurant gets, on a field.
Stalls are provisioned quickly with menus scoped to the event, so a stall that has never used the platform can be trading the same day — and the whole thing packs down cleanly when the festival ends.
Named tracking links per channel. Promo codes apply at payment and never stack. Abandoned checkouts are listed, and you can email the buyers who were signed in.
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 organisers say next.
Then plan the gate around it, because door scanning needs a data connection. We will say so before you commit, and look at where your gate sits and what connection it can have. Stalls confirm payments on their own M-Pesa, which needs signal too.
Setup is an afternoon and stalls bring their own menus. There is nothing to install and nothing to return afterwards. When the next edition comes around, duplicate the whole event and edit rather than rebuild.
Then you do not get one. An organiser account covers events and nothing else — no kitchen, no menu, no stock. If you later run a bar or bring in food stalls, the rest is already there.
What you actually get.
Questions we get about festivals and events.
Buyers get a QR ticket on their “My tickets” page and in their email. At the gate, door scanning runs as an operations station on a data connection: staff scan the code and the ticket validates once. An already-used ticket is refused on the spot.
Talk to us before your next date.
Tell us the date and the stall count. We’ll tell you what setup looks like.
Three details. Tell us the date and the stall count, and we’ll tell you what setup looks like.
One call, and if it isn’t for you that’s the end of it.