One ticket, six stages, and no way to skip one.
Every move is stamped with who made it and when, and the chain only runs forward. An order cannot quietly go back to being someone else’s problem.
- 01
Tagging
Each piece is entered with its colour and any damage it already has. QR tags print per piece.
- 02
Pending
Order accepted. The customer gets an SMS with their own first name on it.
- 03
Processing
Work in progress. Status only moves forward, and every move is stamped with who and when.
- 04
Ready
A shelf location is assigned — one order or in bulk — and it prints on the receipt and the tags.
- 05
Completed
Handed over as pickup or delivery. Cashback is credited, 5% by default.
The one exit that isn’t forward. The cashback is reclaimed and the customer is told why.
Every terminal sees the same order, the moment it changes.
The counter, the pressing table and the office stay in step over a live connection — seven event types, scoped to your shop alone. Each company runs on its own database, so one shop’s data never touches another’s.
7 EVENT TYPES · ROOM PER COMPANY · ONE DATABASE EACH
| #004182 | A. Warsame3 pcs | Ready | B-14 | 1,450 |
| #004181 | Hotel Jubba · rm 2149 pcs | Processing | — | 4,300 |
| #004180 | F. Abdi2 pcs | Ready | A-03 | 700 |
| #004179 | M. Osman6 pcs | Pending | — | 2,150 |
| #004178 | Ward 4 · Bed 124 pcs | Tagging | — | 980 |
What the counter actually does.
- Payments are a ledger
- One lump payment lands across several unpaid orders. Cash and mobile money split on the same receipt. The balance updates live.
- Reconciliation
- Over- and under-payments are detected, not guessed. Export to CSV or Excel. Refunds need a two-step delete approval before anything disappears.
- Lost items
- A register kept outside order pricing, so a completed order stays as it was: lost, then found, compensated, or forgiven.
- Hotels and hospitals
- Guests by room with check-in and check-out; ward accounts that close on discharge. “Charged to the hotel account” and “left without payment” are real states, not notes in a margin.
- Delivery
- Assign a driver, then pending, assigned, in transit, delivered or failed. Reschedule with the count kept. Capture proof at the door.
- Money out
- Expenses go approve, then pay. Payroll covers four salary types and five deduction types. Treasury accounts close daily and monthly.
- The price book
- Three services, each at regular or express — six price points per item across eleven default groups. Bulk CSV upload, and a bulk percentage increase when your costs move.
- Who did what
- Three built-in roles, a super admin, and up to twenty roles you define across fifteen permission areas. Full audit log. PIN quick-switch when someone steps away from the counter.
- Your currency
- KES, USD, SOS, ETB, UGX, TZS and more, set per company — not a conversion, the actual books.
- UNDER 3 DAYS41
- 3–6 DAYS18
- 7–14 DAYS9
- OVER 14 DAYS4
| Age | Orders |
|---|---|
| UNDER 3 DAYS | 41 |
| 3–6 DAYS | 18 |
| 7–14 DAYS | 9 |
| OVER 14 DAYS | 4 |
The orders nobody came back for.
Ageing splits uncollected orders into four buckets, so the ones going stale are the ones you see first. Anything past fourteen days is the shop’s problem, not the customer’s memory.
What it doesn’t do.
There’s no customer app and no public order tracking — the ticket number and the SMS are the customer’s receipt. No online booking, and no sign-up: accounts are created by your administrator. Notifications go out over SMS, not WhatsApp or email. Payments are recorded, not collected — mobile money is a method you log, not a gateway you connect. Tags are printed, not scanned.
If you need one of those, say so. We’d rather tell you no than sell you a claim.
Sign in and get back to the counter.
ACCOUNTS ARE CREATED BY YOUR ADMINISTRATOR · THERE IS NO SELF SIGN-UP