Kiryana restocking is 12 phone calls, 3 missing items, and a wasted morning — every week, 800,000 stores
Our family shop in Ichhra restocks the way it did in 1985. Monday morning: call the sugar distributor (busy), the ghee distributor's salesman (coming 'today' — Wednesday), WhatsApp the confectionery agent (blue-ticked), and physically send my nephew to the wholesale market for the items whose reps no longer visit small accounts. Prices move without notice; the invoice never matches the phone quote; the FMCG order-booker shows up on his schedule, not mine, and pushes whatever his target needs. Several startups tried fixing this with apps and burned out on delivery economics — I watched their reps come and go. What survived is instructive: WhatsApp ordering with specific distributors who kept their existing delivery routes. The playbook that could actually work is boring: digitize the order and the price list, ride on distributors' existing trucks instead of building parallel delivery, and give the shopkeeper one interface across his fifteen suppliers with a visible price history so the quiet weekly price creep becomes negotiable. I have mapped how forty stores in my area order across every category. That research is what convinced me to stop complaining and start building — this problem is my full-time work now.
A high-conviction problem with strong founder-market fit signals. The combination of severe price asymmetry, accessible demographics, and existing infrastructure makes this buildable within 9 months by a small team.
Solutions · 4
Ride the distributor trucks: unified ordering layer on existing delivery routes, price history as the killer feature
From twelve years running FMCG routes, the model that survives: do NOT build delivery — every failed kiryana startup died buying vans to replace trucks that already run. Build the ordering brain on top: one interface where the shopkeeper orders across his fifteen suppliers, orders routed to each distributor's existing booker-and-truck system, delivered on the routes they already drive. Distributors join because pre-booked orders densify their routes and kill the booker's guesswork (I can sign three distributors in Lahore on relationship alone). The shopkeeper's killer feature: visible price history per SKU per supplier — the quiet weekly creep becomes a negotiation he can finally see. Layer khata-style credit tracking later and the working-capital lenders will come asking for the data. Hassan's forty-store research plus my distributor side covers the full loop; committing to this Build Space as co-founder.
The order-booker becomes the onboarding force: pay bookers per active store instead of fighting them
Everyone designs around eliminating the order-booker; he then sabotages the app from the shop counter, and he wins because the shopkeeper trusts him. Flip it: the booker onboards his own route onto the platform, earns per active ordering store monthly, keeps the relationship and the target bonuses, and stops hand-writing orders. Distributors save the transcription errors; bookers earn more for less paperwork; the platform gets 200 stores per booker per city. From my POS sales scars: the counter-side human decides your fate in kiryana tech. Hire him.
The demand data layer: anonymized order flows become FMCG market intelligence that funds the free tier
The ordering layer incidentally captures what FMCG companies pay fortunes to sample badly: SKU-level demand by neighborhood, price elasticity in the wild, competitor stocking patterns, new-product uptake at ground truth. Anonymized and aggregated (with consent framed honestly — 'your data funds your free app'), a market intelligence subscription for brands and distributors carries the platform's economics so shopkeepers never pay. My marketplace-analytics day job prices this data annually in crores for cruder versions. Design the consent and anonymization correctly from day one, and audit it — this only works as a trusted rail.
Do not forget the customer khata: the shop's credit book to households is the other half of its working capital
A homemaker's addendum: the shop's problem is not only ordering stock — it is that half the mohalla owes him money in a notebook, and he floats us all between paydays. If the platform digitizes his supplier side, add the customer khata gently too: SMS reminders that spare him the awkward doorstep conversation, records both sides can see, dignity preserved. His collection improving means his ordering improves — the two books are one cash cycle. The aunties will resist for a month and then never go back; that is how we always are with things that work.
Discussion
Customer-side view of the same shop: stockouts of my staples follow his ordering chaos. When the app fixes his Monday, it fixes my Wednesday. Nobody maps how retail friction flows downstream to kitchens.
This downstream framing is exactly right and underused in our pitches. Shelf availability for the mohalla is the social good; route efficiency is the business case. Both are true simultaneously.
Online seller with kiryana family roots: the price-history feature is the killer. My uncle discovers distributor overcharging months late through gossip. Visible history converts gossip into negotiation.
Village shop version: our kiryana orders through a fortnightly van that shows up or does not. Rural retail supply is this problem squared. Remember us in phase three.
The graveyard of kiryana startups makes investors flinch at this space — but the asset-light ordering-layer model in solutions dodges exactly what killed them. The autopsy has been read correctly this time.
Accountant: kiryana purchase records via a platform would incidentally create the books that make these stores creditworthy — connecting straight to the khata-score thread. The data exhaust is the second business.
Dadu shop already agent-listed for parcels in the other thread, now eyeing HattiLink's phase three: rural shops need the ordering layer more than city ones — our supply van's mood decides our shelves. One counter, three platform ventures. Sign me up for all of it.