Insight
The local commerce operating system, explained
A local commerce operating system runs the whole operation of a local business — catalogue, orders, payments, customers, delivery and discovery — on one shared software core. Here is why the category exists and what it takes to build one.
In short
A local commerce operating system is a single software layer that runs a local business end to end — catalogue, orders, payments, customer records, delivery and online discovery — instead of solving one of those problems in isolation. Deelo is building one for India, spanning six business platforms on one shared technology core.
Why point solutions stopped working
A local shop in 2026 already has the ingredients of a digital business. It has a smartphone on the counter, a UPI QR code beside the till, and a WhatsApp thread with most of its regular customers. What it does not have is a system. Orders arrive as voice notes, prices are quoted from memory, and there is no record of who bought what.
The market answered this with point solutions: a billing app here, a delivery aggregator there, a catalogue tool somewhere else. Each solves one slice and none of them talk to each other. The merchant ends up operating four tools and reconciling them by hand, which is worse than the paper ledger it replaced.
An operating system takes the opposite approach. One identity, one catalogue, one order object, one payment ledger, one customer record — and every surface reads from the same core.
What the layer actually has to contain
The bar for calling something an operating system rather than an app is that a business can run its entire day inside it. In practice that means ten shared services, each of which is expensive to build once and nearly free to reuse.
- Authentication and one customer account across every service
- Payments and settlement, including cash reconciliation
- A wallet that holds balance across categories
- Maps, addressing and geocoding accurate enough for last-mile dispatch
- Notifications across push, SMS and WhatsApp
- Reviews and a portable verification record
- AI for matching, pricing hints and demand forecasting
- Analytics that a shopkeeper can actually read
- Customer accounts and CRM owned by the merchant
- A delivery network that any category can call
The economics of building it once
The reason this category is attractive to investors is the marginal cost of the next industry. Once authentication, payments, dispatch and analytics exist, launching a new vertical is largely configuration and go-to-market, not new infrastructure.
That inverts the usual marketplace problem. A single-category marketplace has to re-earn density in every new city and gets no leverage from adjacent categories. A commerce operating system compounds: each new industry raises utilisation of the shared fleet and spreads the fixed cost of the core across more revenue lines.
| Single-category marketplace | Commerce operating system | |
|---|---|---|
| Revenue shape | Commission on GMV | Subscription plus fees |
| New category cost | Rebuild most of the stack | Configure the existing core |
| Fleet utilisation | One demand curve | Several demand curves, shared |
| Merchant relationship | Platform owns the customer | Merchant keeps the customer |
| Margin profile | Thin, volume-dependent | Software margin with logistics moat |
What this looks like in the field
Deelo runs six platforms on one core: Shops for retail and grocery, Home Services for verified professionals, Agency for staffing and facilities firms, Therapists for appointment-led practices, Parcels for same-city courier, and Runner as the managed delivery network underneath all of them.
A customer uses one app and one wallet across all six. A merchant gets a console, a public storefront and indexed pages that make them findable in local search. A runner sees a single queue batched across categories, which is what makes the unit economics work in a city the size of Kottayam rather than a metro.
Frequently asked questions
Is a local commerce operating system the same as a marketplace?
No. A marketplace matches buyers and sellers and takes a commission. An operating system runs the seller's business — catalogue, orders, payments, customers and delivery — and charges a subscription for doing so. Deelo runs marketplaces on top of an operating system, which is why subscription rather than commission is its primary revenue.
Why does the merchant keeping the customer matter?
Because it changes the merchant's incentive. When an aggregator owns the customer, the merchant is a replaceable supplier and will leave the moment margins tighten. When the merchant keeps the relationship, the software becomes infrastructure they defend rather than a cost they resent, which shows up directly in retention.
Related reading
- Merchant SaaS and the shift from commission to subscriptionMerchant SaaS is software sold to a local business on subscription that runs its operations — orders, catalogu…
- Why hyperlocal delivery needs better infrastructure, not more ridersHyperlocal delivery infrastructure is the dispatch, routing and proof-of-delivery layer that lets many busines…
- Network effects in local commerce, and the one most models missLocal commerce marketplaces have three network effects: the two-sided effect between supply and demand, the de…
Reviewing Deelo as an investment?
The full investor deck runs as a single scrolling brief — problem, solution, product, market, model, financials and team.