SFA and DMS for FMCG distribution without blind spots. One source of truth.

The first production-ready scope can go live in as little as four weeks. The timeline depends on three things: how many loops you launch at once, which integrations your accounting or ERP system requires, and the quality of customer, outlet and SKU master data. A full scope across several thousand outlets is typically rolled out in stages over one or two quarters rather than in a single big-bang launch.

You do not need to replace them. Your ERP remains the system of record and owner of master data. Smartup operates above it and manages what happens between plan and actual execution across the field, shelf, distributor network, warehouse and receivables. Data is exchanged through APIs, with direction and synchronization frequency configured around your period-closing process.

Data is hosted in Tier III data centers. Clients in Uzbekistan can choose in-country hosting in line with personal-data requirements. On-premise deployment inside your environment is also available when required by security policy. Role-based access is enforced and every action is written to an audit log.

The field-sales app is offline-first: store visits, GPS evidence, mandatory steps, shelf photos and outcomes are stored locally and synchronized when connectivity returns. Event order and timestamps are preserved, so visit evidence cannot be rewritten after the fact.

Pricing combines a base subscription, user licenses and the modules you activate. Implementation — configuration, integrations and team training — is scoped separately. The final configuration depends on field-team size, selected loops and integration depth, so we calculate it after reviewing your process.

Technical support, platform updates and integration support are included. Response levels and service hours are fixed in the SLA at contracting and depend on the selected support tier.

Before the pilot, we establish a baseline across field execution, shelf, distributor network and cash. We agree 3–5 KPIs that matter to your business and define the pilot boundaries — territory, roles and data. We compare the result with the baseline and scale only what is proven. If the KPIs do not move, that is an honest no-go.

Yes. A pilot starts with one execution loop, one territory, named roles and 3–5 KPIs. The shared data and integration foundation is established from day one, while additional modules are activated only after the pilot result is compared with the baseline.

The minimum set is customer, outlet and SKU master data plus users and roles. We then add the data needed by the selected loop: routes, prices, assortment, orders, inventory or receivables. Before integration, we validate duplicates, external IDs, required fields and data ownership.

Integration uses APIs, scheduled exchanges or events. Every flow defines its source system, external ID, frequency, retry rules, idempotency and error monitoring. ERP remains the system of record, while Smartup returns verified execution facts.