Skip to main content
Demystify OS

Retail and distribution

Demystify OS for Kirana and grocery retail

Kirana and grocery retail: A neighbourhood kirana or general store, or a grocery mini-mart with a counter and a delivery boy, where the owner is often also the cashier.

Demystify OS lists 6 workflows for this industry, each step with the proof you check, and 3 of them are available today.

Every status on this page is shown as recorded: available, in beta, early access, on the roadmap, or on request.

Demystify OS Cloud Starter, 25 people: from ₹14,999 a month plus GST.

Demystify OS Cloud is an invite-only beta from 1 November 2026, public from 1 January 2027.

The moment that matters

Late at night the owner adds up the till and the UPI app by hand, and the udhaar still lives in a notebook, so nobody knows who owes what or which item will be gone by morning.

What Demystify OS runs for Kirana and grocery retail

Counted on 2 November 2026. A job we have not built is shown as on the roadmap, never as live.

Workflows

  • Night closing summary

    Available

    Close the counter honestly. The Z-report shows the day's takings by cash, UPI and other tenders, bills, returns, discounts and over or short, and you can print it.

    Proof: The day's takings from the till and the UPI app close in one Z-report.

    Done by: Finocket

  • Udhaar balance list

    Early access

    Keep the udhaar book. The khata view shows each regular's balance, open bills, oldest bill and credit limit, with Settle and Remind actions.

    Proof: The udhaar book shows who owes what on one screen.

    Done by: Finocket

  • Long-pending udhaar list

    In beta, invite-only

    Ask Mysty who owes you. Ask Mysty in chat which regulars have unpaid bills, then work from the outstanding and ageing list it reads.

    Proof: Mysty answers who owes you from the udhaar records.

    Done by: Mysty chat

  • Reorder list

    Available

    Reorder before the shelf is empty. A low-stock list and a dashboard card show items at or below their reorder level.

    Proof: A low-stock list shows what to reorder.

    Done by: Finocket

  • Near-expiry shelf list

    Early access

    Watch near-expiry stock. A near-expiry card on the inventory page lists items close to or past their date, for items that carry batches and dates.

    Proof: One near-expiry card lists stock to push or pull. A kirana cannot yet capture batch and date when goods arrive.

    Done by: Finocket

  • GST file pack for the CA

    Available

    Hand the CA the GST files. GSTR-1, GSTR-3B, GSTR-2B, HSN summary, CMP-08 and GSTR-4 come as CSV files the CA carries to the portal.

    Proof: The GST files are prepared from the same records.

    Done by: Finocket

Routines

  • Four-week baseline, then a monthly read

    Early access

    Cadence: Four weeks first, then every month

    You receive: Each metric below names where its number comes from; where it says a manual count, keep that count in a sheet.

Skills

  • Night closing summaryOn the roadmap
  • Udhaar balance listOn the roadmap
  • Long-pending udhaar listOn the roadmap
  • Reorder listOn the roadmap
  • Near-expiry shelf listOn the roadmap
  • GST file pack for the CAOn the roadmap

Integrations and distribution channels

  • CRM

    Early access

    Keep regular customers with their phone and udhaar balance, and import them from a spreadsheet or another billing app's export.

    Through: Finocket

  • Web

    Early access

    The shop's own online catalogue, cart and checkout with cash on delivery or manual UPI. The source says it is built, with limits on loose weights and delivery slots.

    Through: Finocket

  • Outreach

    On the roadmap

    Through: Connector Hub

  • Email

    On the roadmap

    Through: Connector Hub

You approve

Approvals themselves are in beta, invite-only. Each card approves the work of an agent that is on the roadmap for this industry, so each is shown as planned.

  • On the roadmap

    Approve or reject the reorder list before an order goes to the distributor

  • On the roadmap

    Approve or skip each udhaar reminder before it is sent

  • On the roadmap

    Approve or send back the GST file pack for the CA

Memory and governance

One memory for every agent, and the controls around it.

Once, for every agent: each regular's udhaar limit and balance, each item's HSN, rate, reorder level and batch dates, and the distributors you buy from.

  • Memory fabric

    Built, not launched to customers

    One memory shared by every agent: your parties, items, price lists and decisions are held once, with where each came from, so an agent does not ask you the same thing again.

  • Approvals

    In beta, invite-only

    Anything with a consequence waits for you. You tap approve or reject on your phone, and Mysty acts only after you do.

  • Evidence ledger

    Built, not launched to customers

    Every action leaves a receipt, and the receipts are kept in one ledger you can check later, for your own auditor.

  • Guardrails

    Built, not launched to customers

    Each agent has one role, a limit on what it may do and a named checker. Nobody marks their own work done. Money, publishing and outreach stay a person's decision.

Time and errors back: how you will see it

Measure first, then compare. Your own four weeks are the only baseline that counts. We print no promised saving.

  • Time

    The Z-report gives the day's takings by tender in one printout.

  • Cash

    Udhaar balances and the oldest open bill sit in one list.

  • Control

    The till records register open and close with over or short.

  • Errors

    Finocket has a low-stock list and a near-expiry card.

Before you start
For four weeks before you switch on, note by hand each week: the items at or below their reorder level on the day you check, the register closes with cash over or short, and the bills returned or reversed for your own counter mistake.
Every month after
Each month, read the same counts again and compare them to your four-week baseline.
Who reads it
Owner, with the CA for the GST lines
Where it shows
Each metric below names where its number comes from; where it says a manual count, keep that count in a sheet.

Metrics to adopt: how the business runs

  • Items at or below reorder level

    What it is
    Share of the items you stock that are at or below their reorder level on the day you check.
    Formula
    items at or below reorder level / items stocked x 100
    Where the number comes from
    Finocket low-stock list
    How often
    weekly
    Better is
    lower

Errors: count them as errors over transactions

  • Registers closed with cash over or short

    What it is
    Share of the register closes where counted cash was over or short of the expected cash.
    Formula
    registers closed with over or short / registers closed x 100
    Where the number comes from
    Finocket Z-report (over or short line)
    How often
    weekly
    Better is
    lower
    One error is
    One register close with any over or short amount is one reconciliation exception.
  • Bills returned or reversed for a counter mistake

    What it is
    Share of the bills rung in the period that were returned or reversed because of a counter mistake, each bill counted once.
    Formula
    bills returned or reversed for a counter mistake / bills rung x 100
    Where the number comes from
    Finocket Z-report (bills and returns), tagged by hand as a mistake (manual tag)
    How often
    monthly
    Better is
    lower
    One error is
    One bill rung in the month that is returned or reversed because of a counter mistake counts as one error, however many returns it has. Count only bills rung in the period you are measuring.

Start with a four-week baseline

  1. Step 1. Write down your four-week baseline: low-stock items, cash over or short at closing and bills reversed for a counter mistake at each week end.
  2. Step 2. Enter your regular customers with their opening udhaar balance, and your top-selling items with their HSN, rate and reorder level.
  3. Step 3. Run one counter for a week: ring sales, close the register with the Z-report each night, and review the low-stock list every Monday.

What OS does not do for you yet

OS does not yet link a weighing scale, scan with a phone camera, print the FSSAI number on a kirana bill, or send udhaar reminders on WhatsApp.

The khata view and some counter features sit behind a pack flag, so they are marked BUILT. Shop size and seasonality are not in the source. Some error measures need a manual count because the till does not record them. Tax and food-licence wording is with counsel, so this page makes no compliance claim.

Sources: art:finocket-usecase-map-kirana-grocery-1028, art:vocabulary-of-record@1.

The mix for your business

Pick what fits. Each product keeps its own site, and each link below says where it goes.

Start with the Diagnostic

Start with the Diagnostic: ₹1 L plus GST, ten working days, read-only connectors. The fee is credited to your plan.

Demystify OS Cloud is from ₹14,999 a month for 25 people. Invite-only beta; public from 1 January 2027.

Ask what Demystify OS runs for Kirana and grocery retail

Questions

What does Demystify OS do for Kirana and grocery retail?
It lists 6 workflows, such as Close the counter honestly and Keep the udhaar book, and shows each one's status, so you can see which are available and which are on the roadmap.
What is available today and what is not?
Each workflow, routine and integration carries a status chip: available, in beta, early access, on the roadmap or on request. A job we have not built is never shown as live.
What does it cost?
Demystify OS Cloud Starter, 25 people: from ₹14,999 a month plus GST. Start with the Diagnostic: ₹1 L plus GST, ten working days, read-only connectors. The fee is credited to your plan.
When can I start?
Demystify OS Cloud is an invite-only beta from 1 November 2026, public from 1 January 2027.
How does this connect to Finocket?
Finocket has a vertical kit for this industry on finocket.com, linked from this page. Demystify OS works alongside it: Finocket keeps the books and stock, OS runs the routines around them.
Who sees my data?
Connectors start read only, anything with a consequence waits for your approval, and every action leaves a receipt in a ledger you can check. Demystify is DPDP-aligned and has SOC 2 on the roadmap.