Connected Liquor Commerce: How a Distributor–Retailer Network Keeps Stock in Sync

A distributor and the retailers it supplies usually run on separate books, re-keying every order by phone or WhatsApp. Here is how a connected distributor–retailer network works — retailers raise orders, the distributor fulfils them, and stock updates on both sides from one linked transaction.

Most liquor distributors and the shops they supply run on two disconnected sets of books. The retailer phones or WhatsApps an order; someone at the distributor writes it down, packs it, and keys a sale into their own system; the retailer later keys the same items again as a purchase. The same transaction is typed twice, stock is guessed at on both ends, and nobody has a live view of what’s actually moving. This is the problem a connected distributor–retailer network solves — and this post lays out how we’re designing it before we build it.

The shape of the network

A distributor sits in the middle of the chain. Above it is the manufacturer or state corporation it buys from; below it are the many retailers (and, later, bars/restaurants) it supplies. In our model:

• The distributor owns the catalog and the upstream stock. Products, pack sizes, MRP and pricing live with the distributor as the source of truth for what can be ordered.
• Retailers are linked under the distributor. Each retail shop is its own outlet with its own stock and billing, but it’s connected to its distributor so it can order from that distributor’s live catalog.
• One transaction, two ledgers. When goods move, the distributor’s stock goes down and the retailer’s stock goes up — from a single linked document, not two separate manual entries.

        MANUFACTURER / STATE CORPORATION
                     │   (primary sales)
                     ▼
   ┌─────────────  DISTRIBUTOR  ─────────────┐
   │            catalog + upstream stock      │
   │   (secondary sales / "indents")          │
   ▼            ▼            ▼            ▼
 RETAILER    RETAILER    RETAILER    (BAR — later)
   │  each its own stock + billing            │
   ▼   (tertiary sales)
 CONSUMER

The vocabulary worth getting right

The distribution trade already has precise names for each leg of the chain. Using them keeps reports and conversations unambiguous:

In Indian liquor specifically, a retailer “raising an indent” on a wholesaler or depot is the established term — the retailer requests brands and quantities, and the supply is released against a permit. That maps cleanly onto a B2B purchase order, which is the generic name we’ll use in the UI.

The core idea: one order, seen from both sides

The heart of the design is that a retailer’s purchase order and the distributor’s sales order are the same record viewed from two ends — not two documents that have to be reconciled. The retailer creates demand; the distributor sees it instantly; one fulfilment event settles both books.

  RETAILER                         DISTRIBUTOR
  ────────                         ───────────
  Raise purchase order  ───────▶   Appears as a sales order
  (pick from catalog)              (review / approve / price)

                                   Dispatch (transport pass)
                                        │  distributor stock ↓
                                        ▼  goods move "in transit"
  Receive goods (GRN)  ◀───────────────┘
       retailer stock ↑

  ONE linked order · NO double data entry

How the stock actually moves (the part to get right)

The instinct is “a sale updates stock in both places at once.” That’s the right outcome, but the robust convention splits it across the fulfilment steps so the numbers are never wrong while a delivery is on a truck:

• On dispatch — the distributor’s stock is reduced and the quantity becomes in-transit. The goods have left the distributor but haven’t reached the shop yet.
• On goods receipt — the retailer confirms what arrived, and that quantity is added to the retailer’s stock. In-transit clears.
• Short or damaged? The retailer receives the actual quantity; the difference stays visible as a discrepancy to resolve (claim / return), so the two ledgers always reconcile to reality.

The order lifecycle

Every linked order moves through a small, auditable set of states:

The Indian liquor reality this has to respect

Liquor isn’t a generic FMCG line — the secondary-sales leg is regulated, and the software has to fit the paperwork rather than fight it:

• Permits & transport passes. Movement from a wholesaler/depot to a retailer is released against a permit / transport pass tied to the indent. The order record should carry that reference.
• Excise is realised before release. In many states duty is ensured paid on the ordered quantity before a transport permit issues — so an order’s tax footprint matters at dispatch, not just at the retailer’s till.
• State models differ. Where the state corporation is the wholesaler (TASMAC, BEVCO, etc.), the “distributor” may be a government depot; where private L-1 wholesalers operate, it’s a private distributor. The network model fits both — only who plays the distributor role changes.

What this unlocks once it’s connected

• No double data entry. The retailer’s purchase and the distributor’s sale are one keystroke set, not two.
• Live two-way stock. Both sides see real quantities, including what’s in transit — no overselling, no phantom stock.
• Real secondary-sales visibility. The distributor finally sees what each retailer actually pulls, by brand and period — the metric distribution businesses live by.
• Per-retailer pricing & credit. Rates, schemes and outstanding balances attach to each linked retailer, not a generic price list.
• One catalog, many shops. A new brand or MRP change at the distributor propagates to every retailer’s order screen at once.

How LiKAR will model it

LiKAR already runs each shop as its own isolated database under a thin control plane. A distributor network fits naturally on top: the distributor is an outlet with the master catalog and upstream stock; retailers are outlets linked to it; and a linked order document writes a sale on the distributor’s books and a purchase on the retailer’s — moving stock on each side at the right step. Bars/restaurants slot in later as just another kind of downstream outlet under the distributor.

See the current LiKAR demo →

References: Distributor Management System concepts and primary/secondary/tertiary sales (FieldAssist, BeatRoute), B2B order-to-inventory synchronisation (Blue Link ERP, DDI System), and Indian liquor indent / transport-pass / permit procedures (state excise portals — Jharkhand, Delhi, Maharashtra). Conventions vary by state and company; specifics will be confirmed during implementation.