Beats planned on paper. Orders lost to no-signal zones. Schemes nobody can reconcile. Fix the route to market.
Ten topics make up the route to market. Each links to the reference that defines it and the product that runs it.
The path a product takes from your warehouse to the shelf — distributors, beats, vans, and the money on the way back. xMatix runs the whole loop on one data model, so the plan, the visit, the order and the settlement are the same records.
Distributor accounts, their orders, outstandings and claims, kept on the same ledger as your own books. A dealer’s purchase order becomes your sales order in one step — no rekeying, no reconciliation file.
Beats generate on schedule, sequence by territory, and execute against a geofenced agenda. Coverage and productive-visit rates come from the visits themselves, not a self-reported tracker.
Every route carries three sequences: the one planned, the one the optimizer proposes, and the one reps actually follow — learned from execution history. The learned sequence feeds the next plan.
The van is a stock location in its own right: load in the morning, sell and invoice on route, take back and settle at day end. Damaged stock lands in its own bucket, shortages get flagged, and the books never lose the truck.
What distributors sell onward, captured at the outlet visit and reported on the same records the field wrote. Coverage, productivity and order value roll up without an import step.
The rep photographs the shelf; Sense Vision scores compliance, share of shelf and facings against plan. The gap becomes a nudge to the manager, not a debate.
Slabs apply at the order and recompute authoritatively at posting; budgets live per account. Scheme-linked rules turn executed schemes into claim lines that reconcile line by line — approved, rejected or short-paid.
Three replenishment engines propose what to buy, netting stock on hand, in-transit shipments, pending orders and open demand. Every suggested line carries its own arithmetic — the quantity is checkable, not a black box.
Orders, visits and payments work in no-signal zones and sync when the network returns. The engine is the same one product-wide — the field never waits for coverage.
Scheme-linked generation rules turn executed schemes into claim lines. Distributor batches route for approval, and reconciliation happens at line level — approved, rejected, or short-paid — not at “the cheque looked about right”.
Each page explains the discipline first and the machinery second — what it is, where it breaks, and exactly how xMatix runs it.
Beats designed on a map, optimized sequences, geo-verified visits, plan-versus-day.
Read the deep diveThe catalogue, pricing and schemes on the device; orders in a durable queue.
Read the deep diveDefined once, recomputed by the server, accrued into claimable settlements.
Read the deep diveInvoice-level dues on the route, credit limits with teeth, ageing that ties out.
Read the deep diveLoad out, sell and invoice at the doorstep, reconcile to the last unit.
Read the deep diveSell-through captured at source — not a month-old distributor statement.
Read the deep diveStructured in-store work, and shelf photos that become measurements.
Read the deep diveCoverage, productivity and spend — and Sense to ask questions in plain language.
Read the deep diveVisit plans, suggested orders and nudges that work the night shift — approval-gated.
Read the deep diveDaily beats, van sales, and empties & crates on a real stock ledger.
Read the deep diveFMCG brands in India sell through a chain they do not own: the brand's primary sale goes to a distributor, the distributor sells on to lakhs of kirana and general-trade outlets, and the field team in between works beats that run through Tier-2 and Tier-3 towns where the network drops out. FMCG distribution management software has to carry that whole chain on one set of records: the beat and the visit, the order and its scheme, the distributor's GST invoice and e-way bill, the claim, and the collection. xMatix runs sales force automation (SFA) for the field team and a distributor management system (DMS) for the distributor on one platform, so the order the rep captures is the order the distributor invoices and the number the brand reports.
The field side is a working day: a beat generated on schedule, geo-verified visits, stock checks and shelf work, an order priced with the running schemes, a collection against open invoices — all on a phone that keeps working offline. That is SFA software for FMCG. The distributor side is a business: stock by location and batch, retailer invoicing with GST and e-invoicing, credit limits, claims and collections. That is FMCG distributor management system software. Most brands buy the two from different vendors and spend the next year reconciling them; on xMatix they are the same records, so there is nothing to reconcile.

The demos all show a clean order screen. These are the checks that decide whether the system survives its first season in the field:
| Check | What good looks like | Where it is on xMatix |
|---|---|---|
| Offline order entry | Catalogue, prices and schemes on the device; orders queue durably and sync later | Offline order capture |
| Scheme calculation | One definition, applied identically in the app, the distributor invoice and the portal; recomputed at posting | Schemes & promotions |
| Scheme-to-claim reconciliation | Claims generated from the qualifying lines and settled line by line | Trade claims |
| GST e-invoice and e-way bill | Raised from the distributor's own invoices and despatches, not re-keyed | e-Invoicing · e-Way bill |
| Secondary-sales visibility | Sell-through captured at source, not a monthly distributor statement | Secondary sales |
| Credit and collections | Limits that gate the order; collections allocated to invoices on the visit | Collections & outstanding |
| ERP sync | A defined integration for primary sales and masters, with run history you can replay | Integrations |
Each topic above has its own page; the category definitions are in the glossary, and the comparison that sorts the acronyms is DMS vs SFA vs CRM.
Personal care and cosmetics brands run this chain with more SKUs, more launches and beauty retail alongside the kirana beat — see personal care and cosmetics distribution management.
SFA runs the field team's day — beats, visits, orders and collections at the outlet. A DMS runs the distributor's business — stock, retailer invoicing, schemes, claims and cash. FMCG brands usually need both; on xMatix they share one data model, so the field order and the distributor invoice are the same record.
Yes. Distributor invoices carry GST on the line and generate e-invoices, e-way bills are raised from the despatches that need them, and the field app keeps working offline in Tier-2, Tier-3 and rural markets where coverage drops, syncing when the network returns.
Yes. Schemes are defined once — slabs, free goods, item-group conditions, budgets — applied by the server on every order, and scheme-linked rules turn executed schemes into claim lines that are approved, rejected or short-paid line by line.
Yes, and we recommend it: map one territory's distributors, outlets and beats, load items, prices and schemes, reconcile opening stock and receivables, and pilot the full order-to-invoice-to- collection cycle before adding territories.