Skip to main content
Demystify OS

Retail and distribution

Demystify OS for FMCG distribution

FMCG distribution: A distributor or stockist who buys from FMCG principals, holds stock in godowns, sells on credit to many retailers along fixed weekly beats (often from a van), and claims scheme money back from the principal.

Demystify OS lists 6 workflows for this industry, each step with the proof you check, and 1 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.

Ask what OS runs for FMCG distributionAll industries

The moment that matters

A scheme ends and nobody files the claim, or a van comes back short and nobody knows until weeks later. The money is made or lost in the scheme, the claim, the overdue retailer and the van.

What Demystify OS runs for FMCG distribution

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

Workflows

  • Beat order sheet

    Early access

    Book the retailer's order on the phone. The salesman opens today's beat, books an order in cases and pieces, and sees the scheme price and free units while booking. Orders queue offline and send when the signal returns.

    Proof: The scheme shows at the shop while the order is booked.

    Done by: Finocket

  • Overdue retailer list

    Early access

    See who is overdue before you book. The order and the invoice show a credit warning for the retailer. Outstanding by beat and by retailer sits in one place, with collections by beat or collector and cheque states.

    Proof: Outstanding is read from Finocket before you book. The warning does not block a sale.

    Done by: Finocket

  • Principal claim draft

    Early access

    File every principal claim. Scheme, damage, expiry and rate-difference claims go on one board with ageing by principal. You export them as a CSV for the principal.

    Proof: Principal claims are filed in Finocket, and unfiled ones are listed.

    Done by: Finocket

  • Van day close draft

    Early access

    Close the van day. Load the van against a challan, sell from the van, bring unsold stock back, then close the day with expected against counted stock and cash.

    Proof: A short van is shown at day end on the van day close.

    Done by: Finocket

  • Weekly secondary sales note

    Early access

    Read secondary sales and scheme leakage. Reports show secondary sales by principal, brand, item, beat and salesman, plus outlet coverage and beat productivity. A scheme leakage report shows what was given, claimed and settled.

    Proof: The week is read from reports.

    Done by: Finocket

  • Month-end report pack

    Available

    Hand the CA the month-end reports. Receivable and payable ageing, GSTR-1, GSTR-3B, GSTR-2B and HSN summary come from the books as reports.

    Proof: Ageing and GST reports come 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

  • Beat order sheetOn the roadmap
  • Overdue retailer listOn the roadmap
  • Principal claim draftOn the roadmap
  • Van day close draftOn the roadmap
  • Weekly secondary sales noteOn the roadmap
  • Month-end report packOn the roadmap

Integrations and distribution channels

  • CRM

    Early access

    Keep the retailer list with beat, outlet type and credit days in one place, and import it from a spreadsheet.

    Through: Finocket

  • Web

    On the roadmap

    A retailer page to see price and offers for their tier and reorder. The source says retailer login and ordering are not built, so this is planned.

    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 claim draft before it goes to the principal

  • On the roadmap

    Approve or reject the van day close draft

  • On the roadmap

    Approve or send back the month-end report pack for the accountant

Memory and governance

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

Once, for every agent: each retailer's beat, outlet type and credit days, the scheme and price rules by tier, the principals with their claim types, and the vans and godowns.

  • 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

    Orders are booked once, on the phone, with the scheme price in view.

  • Errors

    The scheme price and free units show while the order is booked.

  • Cash

    Overdue retailers and unfiled principal claims sit in lists with ageing.

  • Control

    The van day close sets expected stock and cash against counted.

Before you start
For four weeks before you switch on, note by hand each week: the share of secondary orders booked on the phone, the retailers overdue beyond their credit days on the last day of the week, and the sales invoices that carry a credit note for a wrong scheme or price.
Every month after
Each month, read the same counts again and compare them to your four-week baseline.
Who reads it
Distributor owner, with the accounts or collections person
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

  • Orders booked on the phone

    What it is
    Share of secondary orders that the salesmen book on the phone, rather than by call or on paper.
    Formula
    orders booked on phone / all secondary orders x 100
    Where the number comes from
    manual count: not captured today (the source lists it as a measure; the events are not yet emitted)
    How often
    monthly
    Better is
    higher

  • Retailers overdue beyond credit days

    What it is
    Share of active retailers whose oldest unpaid bill is older than their credit days.
    Formula
    overdue retailers / active retailers x 100
    Where the number comes from
    Finocket beat outstanding report
    How often
    monthly
    Better is
    lower

Errors: count them as errors over transactions

  • Invoices corrected for a wrong scheme or price

    What it is
    Share of the sales invoices raised in the period that carry a credit note tagged as a wrong scheme or price.
    Formula
    invoices with a credit note for a wrong scheme or price / invoices raised x 100
    Where the number comes from
    Finocket sales credit notes, tagged by hand as an error (manual tag)
    How often
    monthly
    Better is
    lower
    One error is
    One sales invoice with a credit note tagged as a wrong scheme or price counts as one error, however many credit notes touch it. Count only invoices raised in the period you are measuring.

Start with a four-week baseline

  1. Step 1. Write down your four-week baseline: phone orders, overdue retailers and wrong-scheme credit notes at each week end.
  2. Step 2. Load your retailers into Finocket (a CSV import is built) and set up one beat with its retailers and your current schemes.
  3. Step 3. Run one van and one salesman for a week: book orders on the phone, close the van day, and file one claim from the board.

What OS does not do for you yet

OS warns on credit but does not block a sale yet, has no retailer ordering app, and cannot write into a principal's own system.

Most distribution modules are built but sit behind a pack flag and wait on database steps, so they are marked BUILT, not LIVE. Seasonality and size are not in the source. Targets for the measures are an owner decision, not set here. The credit days per retailer are stored but their use in due dates is not yet verified.

Sources: art:finocket-usecase-map-fmcg-distribution-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.

Free Demystify Tools for FMCG distribution

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 FMCG distribution

Questions

What does Demystify OS do for FMCG distribution?
It lists 6 workflows, such as Book the retailer's order on the phone and See who is overdue before you 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.

Next to this industry

Looking for the wider picture? Industry view by Demystify Systems (opens a different site)