006 The screens
Customer, console, courier, cash, paperwork.
Five surfaces, one dataset — and no spreadsheet in between.
Storefront, delivery operations and GST-clean books as one layer — sitting on the commerce backend you already run, and the fleet you already use. Your own riders, a delivery partner, or both on the same screen.
Basket to reconciled, and what every system is holding at each step. No cuts, no voiceover, nothing hidden between the stages.
Your cart is good at taking money. It has nothing to say about the ninety minutes after — the picking, the routing, the cash, the invoice, the customer asking where it is.
The cart knows your delivery geography. The dispatch screen knows the invoice. The books know both. Nothing is re-keyed between them.
Serviceability, guided choice and a returning customer who never retypes anything.
Your own riders on their phones, a delivery partner over an API, or a mix by pincode.
GST-correct paperwork, and a nightly check that every system still agrees.
No migration, no rip-and-replace. Catalogue and orders sync with the backend you have; fulfilment goes to whoever is actually carrying the box. Both sides are adapters — swap one without touching the other.
Read the catalogue, write the orders, keep one record of truth — wherever that record lives.
Shopify is in production today. The others connect through the same adapter interface — catalogue in, orders out, money reconciled. Running without any backend is supported too: the platform can hold the catalogue itself.
Own fleet, contracted riders or a national partner — the same order states either way.
The in-house rider app is in production. Partner integrations use the same manifest and status model, so an order handed to a courier reports against the same SLA board as one on your own bike.
Five surfaces, one dataset — and no spreadsheet in between.
The admin console and the store-ops panel, tab by tab, on seeded data: MIS, orders, aging, rejected writes, cash custody, the money trail, reconciliation and settings — then the pick list, routing, dispatch and returns.
A cart sees a transaction. This sees a household, a route and a ledger — over time. Every model below runs on your own order history; none of it needs a data team.
Per customer, per product, we learn the actual gap between orders — then flag the ones due this week and put a one-tap basket in front of them.
Consumption is derived from what was actually delivered — quantities, weights, composition. Gaps in the basket drive the next recommendation.
Km per delivery, cost per drop, on-time rate — own fleet against partner, by pincode. The basis for deciding who should carry which order.
Cash that doesn't match the order, orders stuck past their stage limit, books that stopped agreeing with the backend — surfaced the morning it happens.
You pay when you sell. No platform fee, no per-user licence, no annual lock-in — and nothing at all until you are past a hundred orders a month.
Tiers apply to the whole month, not in bands — cross into Scale and every order that month is at the Scale rate. Modules are per delivered order, and a cancelled order is never billed. Payment gateway and WhatsApp template charges are billed by those providers at cost. Annual commitment takes a further 15% off; we will tell you which tier you actually land in after the first month rather than guessing now.
Because it does — cash in a rider's pocket, refunds to a customer's card, and numbers a chartered accountant will read line by line.
Tell us what you sell and how it reaches the door. We'll walk you through the cart, the console and the courier app — and show the reconciliation report from a live store.