HyperBridge Platformhyperbridge.digital ↗
QuantumOS
Book a demo
QuantumOS Route · Channel

Distributor network, secondary sales and supplier purchasing

Distributor network, secondary sales, supplier purchase orders and a staged Day End close.

5 kinds of network member
from C&F agent to dealer
8-step Day End close
resumes where it stopped after a failure
Credit-checked purchase orders
against each distributor's limit
About

What QuantumOS Channel is

Channel is where a brand sees its selling network and the paperwork that moves through it. It holds C&F agents, distributors, sub-distributors, retailers and dealers, and the documents between them: secondary sales (fed by Relay or by Field), distributor stock, collections, supplier purchase orders, purchase returns and supplier credit or debit notes. Day End closes a business date in eight steps that can resume after a failure. It is an admin workspace with three tabs, Overview, Purchases and Day End. A few functions are available through the API only, and each capability below says so.

At a glance

What is available and what is not

9 capabilities: 8 available, 1 built and tested, 0 on the roadmap.

  • Available

    In production and usable in the QuantumOS admin workspace by customers who have the module.

  • Built and tested

    Built and tested, but not yet a finished feature. It may not be in production on its own, or may have no workspace screen yet. The description says which.

  • Roadmap

    Planned only. Nothing runs yet.

Capabilities

What Channel actually does

Each entry says where to find it in the product. Where a capability stops short of what its name suggests, the detail says so.

01

Distribution hierarchy

Available

Add each C&F agent, distributor, retailer or dealer to your network, with the member above it.

The Overview tab lists every member with its code, name, type, status and parent, and a short form adds new ones. The other modules build on this list: a Trade claim is made by a member, a Partner is a member, and a Signal recommendation is about a member.

  • Types you can add: C&F / super-stockist, distributor, sub-distributor, retailer, dealer
  • Each member has a code and a name, and optionally a parent, a territory and a tax ID
  • You can add and list members; editing, moving or deactivating one is not built yet
  • Supply links and other cross-links between members are not built yet

Where to find it: Channel workspace, Overview tab

02

Retailer, dealer and outlet master

Available

Retailers and dealers are ordinary members of the network, so outlets share one identity with the distributors that serve them.

There is no separate outlet list: an outlet is a retailer or dealer in the network. The Overview counts active outlets, Field visits are recorded against them, Signal classifies them, and a Partner invitation creates one. The trade-off is that outlet details beyond code, name, parent, territory and tax ID are not captured in the workspace yet.

  • The Overview counts active outlets: active retailers and dealers
  • Visits, recommendations and partner records all point to the same outlet
  • Location and contact details cannot be entered in the workspace yet

Where to find it: Channel workspace, Overview tab

03

Regions, zones and territories

Available

Create and list territories through the API and attach them to network members.

A territory has a code, a name, a type and an optional parent. Members can be attached to a territory, and Trade schemes can be limited to territories. There is no territory screen in the workspace yet, so today this is reached through the API rather than on screen.

  • Territory types: region, zone, territory
  • Territory codes are unique within your business
  • No workspace screen for territories yet

Where to find it: Available through the API; no workspace screen yet

04

Secondary-sales ledger without duplicates

Available

Sales invoices and related documents from the network are stored once, however many times they arrive.

Each document is identified by its source system, source company, document type, number and date, so an invoice that is sent again is recognised and stored once. Documents carry line items, with prices held in whole paise. The ledger view lists the latest 50 documents with number, date, buyer, seller and value. Relay feeds it from Tally exports and Field feeds it by converting order drafts.

  • Document types the ledger can store: sales and purchase invoices, sales and purchase returns, credit and debit notes, receipts
  • Tally exports and Field order drafts feed it today; Busy, manual entry and the B2B portal are not connected yet
  • Amounts are held in whole paise, so totals do not drift from rounding
  • The Overview reads the last 30 days of sales invoices

Where to find it: Channel workspace, Overview tab

05

Distributor stock snapshots

Available

A running stock position per distributor and SKU, moved by goods receipts and purchase returns.

Receiving a purchase order adds its quantities, including free quantity, to the distributor's stock for that day, and recording a purchase return takes them off. Each stock movement is applied exactly once, even if the same request arrives twice. The stock list is available through the API; the workspace does not show stock yet.

  • Saleable and unsaleable quantities are tracked separately
  • A receipt and a return on different days still give the true position
  • No stock screen in the workspace yet

Where to find it: Available through the API; no workspace screen yet

06

Collections and outstanding balances

Available

Record money collected from an outlet against a distributor. Recording the same collection twice books it once.

A collection has an amount, a payment mode (cash, UPI, cheque, NEFT or adjustment), a reference number and a reconciliation state. If the same collection is sent again, the original is returned instead of a second booking. The Overview shows the last 30 days of collections. Recording and listing work through the API; there is no collection form in the workspace yet.

  • Sending the same collection again returns the original
  • Amounts must be greater than zero
  • No collection screen in the workspace yet

Where to find it: 30-day total on the Channel Overview tab; recording is through the API

07

Purchase returns limited to what was received

Available

Return goods against a received purchase order, with a reason code and a limit based on what was received.

A return is recorded against a received purchase order with a reason code. The system rejects a return larger than the quantity received minus what was already returned, moves stock once, and treats a repeated request as the same return rather than a second one.

  • Reason codes: damage, expiry, shortage, quality, pricing, wrong item, other
  • The quantity on each PO line is limited to received minus already returned
  • A repeated return creates neither a second return nor a second stock movement

Where to find it: Channel workspace, Purchases tab, Returns

08

Supplier purchasing, credit and Day End

Available

Suppliers, purchase orders with credit validation, goods receipt, supplier notes and a staged Day End close.

Purchases holds suppliers (code, name, GSTIN, payment terms), a credit limit per distributor, and the purchase-order lifecycle. Totals are calculated by the system, including GST rounding on each line and free quantity. Submitting a PO checks available credit (limit, minus credit used, minus open commitments) and records the credit position at that moment. Supplier credit and debit notes adjust the credit used. Day End then closes a business date in eight steps; the closing snapshot is written once, and reopening needs an approver and a written reason.

  • Approval needs a different person from the PO's creator
  • PO lines can be imported from CSV with a dry-run check before anything is saved (columns: sku, quantity, uom, rate, free, gst)
  • Day End blockers: date already closed, close already running, a distributor over its credit limit
  • Day End warnings: submitted POs awaiting approval, open Trade claims, Field order drafts not yet converted, no stock snapshot for the day
  • Sending the same create request twice returns the original draft and does not use a second bill number

Where to find it: Channel workspace, Purchases and Day End tabs

09

Overview KPIs

Built and tested

Four figures: active distributors, active outlets, 30-day secondary sales and 30-day collections.

The Overview tab shows these four figures, with clear messages when there is no data yet or something fails. It is marked built and tested rather than available because it has not been checked against a live database in an automated test yet. Fill rate, numeric distribution and primary-to-secondary ratios are not calculated by the workspace.

  • Distributors include sub-distributors; outlets are retailers and dealers
  • Secondary sales means sales invoices dated in the last 30 days
  • Fill rate, numeric distribution and the primary-to-secondary ratio are not calculated today

Where to find it: Channel workspace, Overview tab

Workflows

How the work moves

Purchase order lifecycle

Each step has its own checks.

  1. 01Draft — lines added by hand, imported from CSV, or created from a Signal recommendation
  2. 02Submit — the system checks available credit and records the credit position
  3. 03Approve or reject — the approver must differ from the creator; rejection needs a reason
  4. 04Receive goods — stock moves and the credit used goes up
  5. 05Cancel — available, with a recorded reason

Day End close

Eight stages. Each is saved on its own, so a close that fails can resume instead of starting over.

  1. 01Pre-close validation
  2. 02Purchase reconciliation
  3. 03Billing reconciliation
  4. 04Collection reconciliation
  5. 05Return reconciliation
  6. 06Payment reconciliation
  7. 07Closing stock
  8. 08Snapshot and close
Connections

How it connects to the other modules

These are the hand-offs that work today. They are optional, so you can use one module without the others.

Relay feeds Channel

Tally exports become secondary-sales documents, and a document that arrives twice is stored once.

Field feeds Channel

An accepted field order converts into a sales invoice. Converting twice returns the same invoice.

Trade reads Channel

Claims are built from a claimant's sales invoices inside a scheme's effective window.

Signal reads and writes Channel

Outlet health and order suggestions read sales-invoice history. An accepted suggestion drafts one purchase order.

Boundaries

What is not built, and where it stops

Roadmap

Not built yet

  • Fill rate, numeric distribution and primary-to-secondary measures on the Overview
  • Editing, moving or deactivating a network member; a member detail view
  • Workspace screens for territories, stock and collections (available through the API only today)
  • A dedicated exceptions inbox beyond Day End blockers and warnings
  • Editing draft purchase orders and attaching documents
Limits

Worth knowing

  • Amounts are in INR in the workspace today.
  • Approvals and Day End reopen depend on separate people holding the right permissions.
  • Audit entries and event notifications are written just after a change is saved, on a best-effort basis. They are not part of the same save.