HyperBridge Platformhyperbridge.digital ↗
QuantumOS
Book a demo
QuantumOS Route · Route to Market

Distributor-led sales, run on QuantumOS

Six modules for brands that sell through C&F agents, distributors and retailers. Each is entitled separately.

6 modules
entitled separately
17 of 35
capabilities are available today
Tally and GST
built for Indian distribution, in INR
Modules

Six modules, described at the size they are

Some are substantial and some are thin. Each page says which, and lists what is not built.

QuantumOS ChannelDistributor network, secondary sales and supplier purchasingDistributor network, secondary-sales ledger, supplier purchase orders with credit checks, and a staged Day End close.8 available · 1 built and tested · 0 roadmapQuantumOS FieldBeat plans, outlet visits and an offline operation queueBeat plans, outlet visits and an offline operation queue; accepted field orders convert into Channel invoices. There is no field mobile app yet.2 available · 1 built and tested · 3 roadmapQuantumOS PartnerInvite, onboard and revoke retailers and dealersAdmin-side lifecycle for retailers and dealers — invite, record agreement acceptance, scope entitlements, suspend or revoke. The partner-facing app is not built.1 available · 0 built and tested · 2 roadmapQuantumOS TradeTrade promotion schemes, claims and settlementTrade promotion schemes for distributor networks — slab-based discounts, two-person approval, claims built from Channel invoices, settlement by credit note or payment.2 available · 3 built and tested · 0 roadmapQuantumOS RelayBring distributor data in from Tally exportsLoads distributor sales from Tally XML exports into the Channel ledger — grant-scoped, safe to repeat, with retries and a safety net for repeated failures. Busy is not supported yet.3 available · 0 built and tested · 3 roadmapQuantumOS SignalOutlet health and suggested orders you can inspectFlags outlets whose orders are falling and suggests reorder quantities from purchase history; accepting a suggestion drafts a Channel purchase order.1 available · 4 built and tested · 1 roadmap
Status

What is available today

35 capabilities across the six modules: 17 available, 9 built and tested, 9 on the roadmap. The same counts appear on each module page.

  • 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 by module and state
ModuleAvailableBuilt and testedRoadmap
Channel810
Field213
Partner102
Trade schemes230
Relay303
Signal141
Total1799
Connections

How the modules hand work to each other

These hand-offs work today. They are optional, so a business can have one module without the others.

  • Relay to Channel

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

  • Field to Channel

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

  • Channel to Trade

    Scheme claims are built from a claimant's Channel sales invoices inside the scheme's effective window.

  • Channel to Signal

    Outlet health and suggested order quantities read Channel sales-invoice history.

  • Signal to Channel

    An accepted suggestion drafts one supplier purchase order in Channel Purchases.

  • Partner to Channel

    A partner is a retailer or dealer in the network with a lifecycle record, so it appears in Channel.

  • Trade and Field to Channel Day End

    Day End warns about open Trade claims and about accepted Field order drafts that have not been converted.

Shared foundation

What all six modules share

Every module rests on the same foundation for network members, money, offline sync and events. It comes with every module and is not a seventh product.

Each business's data stays separate

Every record belongs to one business, and every request is limited to the business making it, so one business does not see another's network, invoices or claims. Records can also link only to records inside the same business.

Separate access for each module, closed by default

Each module is its own entitlement, and every action checks both the module access and the user's permission. A business that has not been given a module gets nothing from it.

Money without rounding errors

Amounts are held in whole paise from start to finish, including GST rounding, scheme benefits and claim totals.

Retries that do not double-book

Collections, purchase orders, returns, supplier notes and visits can be sent again safely. A repeat returns the original record, and stock and credit move exactly once.

Separation of duties

A purchase order, a scheme and a claim cannot be approved by the person who created or submitted it.

Audit trail and named events

Changes write an audit entry and send a named event that matching webhook subscriptions can receive. Both are written just after the change is saved, on a best-effort basis.

Packaging and limits

Bundles, and what to know first

Packaging

Planned bundles

  • Route Core — Channel + Trade schemes
  • Route Field — Field
  • Route Partner — Partner
  • Route Intelligence — Relay + Signal

These are planned groupings of modules. No pricing or billing plan is defined, and access is set up for each business.

Limits

Worth knowing first

  • Everything here is an admin workspace. The field-sales mobile app, the partner-facing app and the partner portal are not built.
  • The workspaces are built around INR and Indian distribution practice (Tally, GSTIN).
  • Access is set up for each business. Bundles are groupings of modules; no pricing or billing plan is defined.
  • Target-setting and fraud-signal calculations are built but cannot be reached from the Signal workspace.
  • The workspaces are not localised yet.