Beats on a map, not a spreadsheet.
Plan beats and routes visually, optimize stop sequence, and allocate from a live console that shows every rep's position. When the day slips, drag the plan — not the team.
Every visit, guided and verified.
Geofenced start and end, activity checklists, photos and signatures — and when a rep has slack time, "nearby outlets to onboard" fills it. All of it works offline.
Orders that survive dead zones.
Catalog with barcode scan, schemes and price lists applied automatically, offline cart that syncs when signal returns. Van load and unload tracked to day-end reconciliation — no evening spreadsheet.
The day accounted for. The effort rewarded.
Check-in and check-out with selfie and geo-stamp, pause and resume for breaks — feeding incentive plans and trade schemes the team can see, not guess at.
All of it works offline.
Every screen on this page runs on the offline-first mobile app — no signal needed, writes queued durably until sync.
Planned. Optimized. Actually followed.
Every route carries three sequences: the one that was planned, the one the optimizer proposes, and the one reps actually follow — learned from execution history. The learned sequence feeds the next plan, so the route improves from the ground truth of the field rather than a one-time setup. Stops transfer between beats, and territories plan across field staff.
Inside the route-optimization architecture →The capabilities, stated plainly.
Every row ships today and traces to a capability described on this page.
| Capability | xMatix Field Sales |
|---|---|
| Beat planning and territory rhythm | Native |
| Auto-generated visit plans | Native |
| Road-network route optimisation | Native |
| Visit execution with an activity catalog | Native |
| Order capture without connectivity | Offline |
| Van sales and van reconciliation | Native |
| Scheme and discount execution | Native |
| Attendance, geofencing and incentives | Native |
| GPS trails with offline capture and replay | Native |
| Nearby-outlet discovery and onboarding | Native |
| Shelf photo analysis | Integrated — Sense Vision |
| Learned route sequence from execution history | Native |
| Territory planning across field staff | Native |
| Stop transfer between beats | Native |
Everything in Field Sales.
The questions evaluators ask.
Does xMatix Field Sales work without an internet connection?
Yes — the whole visit runs with no signal at all. Screens read from data already on the device, so the app opens instantly in a basement or on a highway. Check-ins, activities, photos and orders queue in a durable outbox and send themselves when coverage returns — even if the phone restarts first. Nothing is lost and nothing is retyped. The same offline-first architecture carries every xMatix field app; read how the mobile app works offline.
Does it support van sales?
Yes — the van is treated as a store that has to balance. Stock loads onto the vehicle in the morning, sells off it during the day, and reconciles at day's end: loaded, sold and returned units are counted against each other, so shrinkage shows up the same evening instead of at month-end. Cash collected on the route is part of the same settlement, and the day closes without an evening spreadsheet.
What is beat planning and does xMatix generate the routes?
Beat planning divides a territory into repeating visit patterns — beats — so every outlet gets covered on a rhythm rather than by accident. Yes, xMatix generates the routes: visit plans write themselves from the beat each day, and the stop sequence optimises over the real road network, across multiple vehicles. Reps start the day selling instead of scheduling, and when the day slips, the allocation console lets a planner drag work between reps.
Can reps take orders for out-of-stock items?
Yes. An order in the field is a statement of demand, not a stock reservation — the rep captures it offline, regardless of what is on hand at that moment. Availability is resolved when the order syncs and moves into xMatix Sales, where partial fulfilment is the normal case: what's ready ships and invoices, and the rest of the order waits intact. The rep never loses a sale to a temporary stockout.
Does it enforce schemes and discount rules, or just record them?
It enforces them. Live scheme estimates show in the cart while the rep is standing in the outlet, so the offer lands at the moment of truth — and the final math is re-run on the server when the order goes through. The cart's promise and the invoiced offer always agree, because the same rule engine computes both. Discounts follow price lists and discount groups, so the rate is policy, not negotiation.
Can reps collect payments against invoices?
On the van, yes — cash collected on the route is recorded and reconciled in the day-end settlement. Collections against open invoices are handled in xMatix Sales on the same data model: payments record against open documents with the balance always live, and receipts knock off partially or in full, so the customer statement reconciles. Because both run on one record, a collection entered anywhere shows against the same outstanding everywhere.
How is a rep's attendance and visit location verified?
Three ways, all server-checked. Attendance takes a selfie inside a geofence, so present means actually there. Each visit starts and ends against the outlet's own geofence, with every activity time-stamped in between. And GPS trails record the route actually driven from check-in to check-out — captured even offline, disclosed to the rep, and replayable on a map when a customer disputes that the visit happened.
Does it work on both Android and iOS?
Yes — xMatix ships native Android and iOS apps, both offline-first. Screens are designed once in the platform's designer and render as true native UI on each, so the two stay consistent without separate builds. Layout changes reach every device over the air, which means a new field or a new visit type never waits on an app-store release or leaves half the team on an old version.
Does the plan improve from what reps actually do?
Yes — that is the point of the three-sequence model. Each route keeps the planned sequence, the optimized sequence and the most-followed sequence learned from execution history, side by side. When the order reps actually run consistently beats the plan, that learned sequence is there to adopt — the plan improves from ground truth rather than assumption. Coverage and productivity reporting come from the same visit records, so the comparison is always available, route by route.
Beats, van sales, schemes, and GST on the road.
Explore the FMCG & Distribution solution →Field teams for dealer networks and service territories.
Explore the Automotive & Dealerships solution →"Routes, orders, and day-end settlement finally live in one system. We stopped reconciling three tools every night."