Skip to content

Showing Kenya — M-Pesa, card or cash, VAT wording.

Multi-branch restaurant POS in Kenya

Run five branches like one. See them like five.

Tumikia is a multi-branch restaurant POS for Kenyan chains and restaurant groups. One organisation holds many locations, each with its own M-Pesa till, its own KRA PIN and its own staff, all reporting into a single dashboard. Head office controls the master menu; branches override prices and availability locally. Billing arrives as one consolidated invoice with a line per location.

One master menu, local overrides
Each branch paid into its own M-Pesa till
One consolidated invoice
Step 1 of 2
Bring us your two slowest branches.

Three details. We’ll set both up and show you the comparison view with your own numbers in it.

+254

One call, and if it isn’t for you that’s the end of it.

One master menu, local overrides
Each branch paid into its own M-Pesa till
One consolidated invoice

You know this already.

None of this is a software problem yet. It is just how the week ends.

Head office finds out on Monday what happened on Saturday.

Branch managers send photos of till counts. Someone builds a spreadsheet on Tuesday. By then Bustani’s bad Saturday has had two more.

The Mnara price is wrong again.

Nobody decided that. It happened, and it has been happening for months.

You know one branch is worse. You can’t say why.

A hunch you cannot take to a manager, because there is no number attached to it.

Your regulars eat at three branches and are a stranger at two.

Points earned at Bustani mean nothing at Kilele, so the group’s best customers look like nobody’s.

What changes

Every location on the same system, reporting the same day.

Every branch on the same system, so the comparison is finally like for like.
Comparing locations
The comparison view states the difference in a sentence, not a chart.

Revenue, orders, average ticket, prep time against target, waste in KSh, refund rate and QR adoption, side by side over any period — with the delta called out: “Mnara prep is 22% slower than Bustani.”

Menu management
Change a dish once and it lands everywhere it should, and nowhere it shouldn’t.

A master menu lives at group level — items, descriptions, photos, video, modifiers. Each location inherits it and overrides only what genuinely differs: its own price, its own availability, its own local specials.

A loyalty change awaiting approval
One loyalty programme across the group, or one per branch.

Run one shared programme, separate ones, or a mix, managed from the main location. Central coupons count their limits across every location. Every rate change is approved inside your organisation and applies from a date. Group loyalty is an add-on.

Different prices per channel
Takeout and delivery prices that differ from the dining room, only where you choose.

Channel prices are an add-on: a different takeout or delivery price on the dishes you pick. Availability per channel is on every plan, so a dish can stay dine-in only.

Orders today
Your accountant gets the numbers without getting the keys.

A read-only accountant role reaches orders, payments, refunds and exports — and nothing else. Sales, refunds, payments and VAT summaries, per branch or consolidated, every export logged with who pulled it.

Kitchen station
The same kitchen discipline in every site, whoever is on shift.

Station routing, course pacing and urgency colours are group standards rather than branch habits. A branch 86ing an ingredient never affects another branch.

Built for here

Your M-Pesa money never touches us.

Straight to your till

Diners pay your own M-Pesa till or Paybill. The money never passes through Tumikia, and we add nothing to it.

Every code checked

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.

Cards, settled in 2 days

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.

No app for diners

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.

Why this and not a till

Four things a till with a QR code bolted on cannot do.

No app. No signup. No download.

The diner scans and orders. Anything you have to convince someone to install, they won’t.

Your M-Pesa money never touches us.

Diners pay your own till or Paybill. Cards on the diner’s phone, card terminals and cash sit on the same tab.

The diner’s data stays with Tumikia.

You reach your customers; you never hold their contact details. One fewer compliance surface for your business.

Diner-first, not POS-first.

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.

Straight answers

The three things groups say next.

Could one of my managers see another branch’s numbers?

No, and it is not a policy — it is built that way. The tablet is bound to its location when it is set up, with no screen anywhere that lets a location be chosen. The staff session inherits that binding and cannot widen it. Every query on our side is scoped to the person asking, and the live updates are partitioned per location.

Where does each branch’s M-Pesa money go?

Into that branch’s own till or Paybill. Each location carries its own till, so diners at Bustani pay Bustani, and the money never passes through Tumikia or through head office. The day close at each branch matches its own codes, terminal references and cash.

Every branch bills separately and my accountant re-types everything.

One consolidated invoice per cycle with a line per location, so you can see exactly what each branch costs. Plans and features are assigned per location, so you can switch a capability on at one branch, run it a month, and roll it out when it has earned it.

Everything included

What you actually get.

Hierarchy
Group and location model with inherited menus and local overrides
Comparison
Side-by-side branch comparison with plain-language deltas
Access
Group-wide or single-branch roles, plus a read-only accountant role
Payments
An M-Pesa till or Paybill per location, card on the diner’s phone, card terminals, cash
Tax
Own KRA PIN and VAT mode per location. eTIMS integration coming
Billing
One consolidated invoice with a line per location
Rollout
Per-location feature and plan assignment
Add-on
Group loyalty — shared, separate or mixed programmes, central coupons with limits counted across locations
Add-on
Channel prices for takeout and delivery, on the dishes you choose
Everything else
The full single-location product, at every location
Questions

Questions we get about chains and groups.

Yes. Tumikia is built around an organisation-and-locations model. One group holds many locations, each with its own menu overrides, M-Pesa till, KRA PIN and staff, all reporting into one dashboard with per-branch and consolidated views.

Bring us your two slowest branches.

We’ll set both up and show you the comparison view with your own numbers in it.

Step 1 of 2
Bring us your two slowest branches.

Three details. We’ll set both up and show you the comparison view with your own numbers in it.

+254

One call, and if it isn’t for you that’s the end of it.