SaaS Dashboard for Kirana Shops and SMBs: Inventory, Billing, and Supplier Management

Who does it: The shop owner (often called the "bahri" or managing partner) plus one to three staff. In most kirana shops with annual turnover under ₹1 crore, the owner does the inventory and supplier work personally — it never gets handed off. In slightly larger general trade shops (₹1–5 crore), a "stock boy" or the owner's son handles physical counting while the owner negotiates with suppliers. For billing, either the owner or a cashier-grade staff member keys in GST invoices on a computer or (increasingly) a tablet.

What they use, in order of frequency:

• Phone (feature phone or smartphone): calling distributors to place orders, texting availability queries. Average kirana owner makes 15–30 supplier calls per day.
• WhatsApp: sending order lists as voice notes or typed texts to distributors. Groups with 5–10 suppliers are common. Order confirmations come back as text or sometimes a photo of a handwritten gate-pass.
• Physical register or rikaan bahi: a bound book, sometimes with carbon copies. One copy stays in the shop, one goes with the delivery person.
• Excel or Tally (for shops above ~₹50 lakh turnover): Tally Prime is the dominant accounting software in this segment. Most owners use it for GST filing only — not for real-time inventory. Excel is used ad hoc for stock lists, usually maintained by whoever is most comfortable with it.
• Spreadsheet on phone: Google Sheets shared between the owner and one staff member, but sync conflicts and version confusion are constant.
• Whiteboard or chit system: some shops maintain a running stock count on a whiteboard near the godown entrance. It goes out of sync the moment anyone forgets to update it.

Where time and money leak:

• Stockouts on top 20 SKUs: The owner cannot track what sold until the shelf is empty. By then, a competitor has already sold to the customer. This happens weekly on fast-moving staples — oil,atta, sugar, biscuits, milk products — and is invisible because there is no data.
• Overordering from pushy distributors: FMCG company sales reps visit weekly and push stock. The owner, without sell-through data, often overorders to maintain the relationship, leading to expiry waste. This is particularly acute for products with 30–60 day shelf life.
• Manual GST reconciliation: GST invoices are issued but not linked to inventory movement. At month-end, the owner or his CA spends 2–4 hours manually matching Tally entries with physical bills. Errors result in input tax credit mismatches.
• No credit float tracking: Kirana shops extend credit to their customers (the "credit khata") and also receive credit from distributors. Most owners track this on a loose sheet or a notebook. Duplication, omission, and plain forgetting result in genuine losses estimated by trade bodies at 3–8% of gross margin annually — but nobody has clean data on this.
• Supplier delivery non-compliance: Distributors promise delivery by a certain time or quantity and partially deliver or delay. Without a structured order acknowledgment system, the shop has no recourse and no record.

Who profits from it staying manual:

• Distributor sales reps: A manual, relationship-driven ordering system keeps them relevant. If a shop owner can order directly through an app with one click, the rep's periodic visit and relationship maintenance become unnecessary. The largest FMCG companies (Hindustan Unilever, ITC, Nestle, Proctor & Gamble) have their own distributor management systems, but their field sales teams still depend on the personal relationship to push stock and collect payments.
• Unorganized loan providers: Many kirana shops are financed informally by distributors (stock on credit) and by local moneylenders who know the shop's cash cycle. A transparent digital record reduces the opacity on which these informal lenders depend for their margin.
• Unscrupulous distributors: Partial delivery, wrong quantity, delayed delivery — all of these are easier to deny without a digital record. The absence of documentation protects bad actors.
• Some small accounting firms: The monthly reconciliation chaos described above is billable work for CAs and accounting shops. Digital GST reconciliation reduces their billable hours.

Who is hurt and wants to change it:

• Shop owners themselves: Especially those with two or more staff, those with GST registration, those doing ₹50 lakh+ annual turnover, and those in competitive locations (near a Reliance Smart, Dmart Local, or major temple market). These owners feel the pain most acutely and are the earliest adopters.
• Second-generation family members joining the business: Young people with any exposure to software (college, previous job) find the manual system embarrassing and are actively lobbying for change.
• Modern retail format operators who compete with kiranas: BigBasket SmartBazaar, JioMart Partner, and similar franchise models can list their own inventory digitally and gain operational efficiency. The unorganized kirana feels this competitive pressure but lacks the tools to respond.
• FMCG category managers at large companies: They cannot get reliable sell-through data from kirana channels. The estimate is that 90%+ of distribution data from kiranas is reported by distributors (who have an incentive to overstate), not verified by actual retail movement.

Who would pay to change it:

• Primary: Shop owners doing ₹30 lakh+ annual turnover who already have a smartphone, have GST registration, and have at least one staff member. They feel competitive pressure and have a minimum viable ability to pay ₹500–2,000 per month for software that genuinely reduces their pain.
• Secondary: Distributor relationship managers at FMCG companies who want verified retail movement data — they would pay for a channel that delivers this, though the buyer-user alignment is misaligned (the person who pays is not the person who uses it daily).

The narrow product to start with: An Android mobile app (not a web dashboard — this audience is mobile-first and often on the shop floor, not a desk) that does one thing: digital purchase order creation and supplier confirmation tracking.

On day one it does this:

• The owner selects from their saved supplier list (imported from a simple setup or WhatsApp contact list)
• Creates a purchase order by adding SKUs with quantities
• Sends the order to the supplier via WhatsApp or SMS (with a structured format that the supplier can read and confirm)
• Tracks order status: sent, confirmed, partially confirmed, delivered, disputed
• Maintains a simple running stock count for the top 50 SKUs (entered manually at first, scanned later)

No billing module on day one. No GST filing. No inventory forecasting. No POS.

Who pays and how much:

• SHAPE: Per confirmed order placed. ₹15–25 per purchase order that gets a supplier confirmation response. The owner pays only when the system produces a confirmed, documented order.
• Alternative SHAPE if that is too behavioral: Per active supplier connected, ₹100–200 per month per supplier the shop has active communication with through the app.
• The owner will not pay for a dashboard they have to stare at. They will pay for a task that gets done — an order placed and confirmed — if the outcome is visible and the alternative is the phone-and-WhatsApp grind.

Why this wedge: It is the most painful daily task that is also the most documentable and the least threatening to existing supplier relationships. The supplier receives a WhatsApp message and responds normally. No retraining. No new app for the supplier required.

Real players in this space:

• Vyapar: Indian-made accounting and inventory app for SMBs. Android-first. GST-compliant billing, inventory, party management. Pricing around ₹999–₹4,999 per year. Has a significant kirana user base. Strong in North and Central India. Weak on supplier-side order workflow — it is primarily an internal shop tool.
• Khatath (formerly known in some markets): A kirana-focused app that attempted the purchase-order-to-supplier workflow. Status of current operations unverified as of this writing — multiple iterations and pivots reported in trade press.
• OwnBooks : GST and inventory app. Smaller user base than Vyapar. Android app. Order management exists but is not the primary workflow.
• SpiceMoney : Focuses on banking and financial services for rural and semi-urban shops, with some inventory capability. More financial services wedge than pure inventory.
• capillarytech.com : Enterprise-focused loyalty and engagement platform. Not a kirana tool.
• Amazon Haath (now largely wound down or pivoted): Amazon India's attempt to digitize kirana supply chain. Faced adoption challenges.
• JioMart Connect : Reliance's distributor and kirana digitization play. Operates through the Jio ecosystem. Adoption varies by region.

Unverified: Multiple regional apps and WhatsApp-based order management pilots operated by individual distributors or small startups. No reliable aggregate data on how many exist or how many shops use them.

What none of them have cracked: A product that the kirana owner uses daily for the purchase ordering workflow (not just billing at month-end), where the supplier is also gently pulled into the confirmation loop without having to install an app themselves.

Fact 1: Kirana owners will not adopt any software without a persistent, trusted human intermediary.

The hypothesis: An Android app that sends WhatsApp messages is sufficient — the owner will use it daily.

The kill condition: If more than 70% of target kirana owners in a test cohort stop using the app within 30 days of initial setup despite free onboarding, the friction is too high and the model requires a human SaaS agent (relationship manager) on every account, which makes unit economics fail.

How to check cheaply: Select 20 shops in one city block (one distributor's catchment area), spend ₹15,000 on a field person to personally onboard each owner over two weeks, and measure 30-day active usage. Pass mark: at least 12 of 20 are placing at least 3 orders per week through the app without being prompted.

Fact 2: Suppliers will not respond to digital order confirmations reliably enough for the system to create value.

The hypothesis: A WhatsApp message or SMS with a structured order is sufficient to get a confirmed or disputed response from the supplier within 24 hours.

The kill condition: If more than 40% of orders sent digitally get no supplier response at all (neither confirmed nor disputed — just silence), the system does not create the confirmation record that is the core value proposition.

How to check cheaply: Run a 10-day test sending 5 sample structured order messages per day to existing supplier contacts from 15 shops. Measure response rate. Pass mark: at least 65% of messages get a substantive response within one business day.

Fact 3: The owner's time savings do not translate to willingness to pay at the SHAPE required.

The hypothesis: Owners will pay ₹15–25 per confirmed order placed digitally.

The kill condition: If the maximum price point at which more than 50% of active users in a pilot would subscribe is below ₹8 per confirmed order, the unit economics for a SaaS business (server costs, support, sales) do not work at this SHAPE.

How to check cheaply: In the same 20-shop cohort from Fact 1, introduce a ₹20-per-order pricing after 60 days of free usage. Track how many continue placing orders and paying. Pass mark: at least 8 of 20 shops remain active and paying after 30 days of paid usage.

Budget: ₹75,000

Breakdown:

• Field outreach and onboarding (one city, one district market): ₹20,000 for a part-time field person over 8 weeks
• App setup, WhatsApp API costs, and hosting for pilot: ₹15,000
• Mobile data and device support for owners who need help: ₹10,000
• Supplier outreach and relationship building in pilot area: ₹10,000
• Contingency and miscellaneous: ₹20,000

Phase 1 (Days 1–30): Foundation

• Select one geographic cluster: 25–30 kirana shops within a 2 km radius sharing 3–4 common distributors
• Onboard 20 of these shops personally
• Connect each shop to their top 3 suppliers by exporting existing contacts and creating structured supplier profiles
• Train each owner on creating a digital purchase order and sending it via WhatsApp
• Do not introduce any other feature — no billing, no inventory count, no analytics dashboard

Phase 2 (Days 31–60): Usage and Observation

• Track order placement frequency per shop daily
• Track supplier response rate per order
• Collect qualitative feedback weekly from owners (2–3 shops per week, in person or phone)
• Identify the 5 most engaged shops as reference cases
• Do not introduce paid pricing yet

Phase 3 (Days 61–90): Pricing Signal and Falsification

• Introduce ₹20 per confirmed order pricing to the 20-shop cohort
• Continue tracking: active shops, orders placed, orders confirmed, revenue collected
• Run the three falsification checks from Section 5 in parallel
• Document: which shops churned, which stayed, and why based on owner feedback

Pass mark for the 90 days: At least 12 of 20 shops are placing orders through the app at least 3 times per week, supplier response rate is above 65%, and at least 8 shops are paying. If all three are true, the idea is live enough to proceed to a city-level expansion test. If two of three falsification conditions from Section 5 trigger, the verdict defaults to AGENCIFY (see Section 7).

AGENCIFY first, with a clear productize path.

The manual purchase-order workflow is the most acute daily pain point for the target user, the easiest to digitize without requiring supplier-side behavioral change, and the most falsifiable in 90 days. However, the adoption challenge in this segment is not software — it is trust and habit. A human-led agency model (where a relationship manager onboards, supports, and collects payment from 20–30 shops per territory) de-risks the adoption problem that kills pure SaaS plays in this segment. The productize path is to extract the digital workflow from the agency model once usage patterns are proven: the app becomes the product, the agent becomes the support layer.

AI-fy is premature — the data set is too sparse, the workflow too fragmented, and the cost of an AI agent doing the work (rather than the owner doing the work assisted by software) cannot yet be justified at kirana price points.

Availability confirmed against the .in registry (RDAP) on 2026-09-20. Prices and ownership read from our own intelligence tables. Nothing here is estimated.

Single-word, available now

• bekabus.in — available
• bekabus.com — available
• bekabu.co.in — available
• bekabus.co.in — available

Also available (compound)

• bekabuhub.in
• bekabumart.in
• bekabukart.in
• bekabumandi.in
• bekabubazaar.in
• bekabudirect.in
• bekabusupply.in
• bekabuconnect.in

Listed for sale

• bekabu.com · price not listed on afternic · seller holds 936325 domains

In the expiry pipeline — watch

• bekabu.in · dropped · score 35

Taken and developed — do not chase

• saas.com · entropy 5.05
• saa.co.in · entropy 4.81
• saasconnect.in · entropy 4.55
• mysaa.in · entropy 5.34
• dashboardhub.in · entropy 6.30

---

Generated 2026-09-20 16:42 UTC. Topic from our research queue; no market-size figure appears here unless a source is named. The domain block above is read from our own intelligence tables and confirmed at the .in registry (RDAP); the model wrote the analysis, not the domain facts.