Sales Force Automation for FMCG field teams.

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.

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.

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.

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.

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.

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.

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.

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.

Define users, outlets, devices and integrations. Pilot one route, including offline capture and sync recovery. Android and iOS apps are available.