The system of execution for FMCG distribution
Your ERP is the financial system of record. FieldDNA is the system of execution for everything that happens past the distributor's door: secondary sales, schemes, collections and store visits.
FieldDNA vs the alternatives
Compared against categories, not named products.
| FieldDNA | ERP-only | Point SFA/DMS tools | Spreadsheets | |
|---|---|---|---|---|
| Secondary sales visibility | Standard secondary flow, rolled up live to HO | Stops at the distributor | Siloed, partial | Manual and lagging |
| Promotion consistency online and offline | One engine, same answer everywhere | Not covered | Online only, drifts offline | None |
| Free-goods tracking and reversal | Tracked and reversed on returns | Not covered | Rarely tracked | None |
| Batch and expiry | FEFO with alerts | Basic | Varies | None |
| GST returns | GSTR-1/3B/2B built in | In the ERP | No | Manual |
| Distributor standardisation | One governed core for all | No | Per-tool | No |
| Offline field execution | Fully offline-first app | No | Some, connected | No |
| Approvals with delegation | Unified Approval Center | Limited | Varies | No |
| Tenant isolation | One database per tenant | Shared or on-prem | Shared multi-tenant | No |
| Cloud portability | Same binaries on any cloud or on-prem | Vendor-bound | Vendor-bound | No |
| Configurability | Configure, not customise | Heavy customisation | Limited | No |
| ERP coexistence | Standalone or ERP-connected | Is the ERP | Bolt-on | No |
Seven principles
The decisions behind the platform.
- 1
Isolated by default
One dedicated database per tenant, no shared transactional tables.
- 2
Cloud-portable
The same binaries run on AWS, Azure, GCP or on-premise.
- 3
Auditable by construction
Append-only audit with before and after, 7-year retention.
- 4
Configurable, not custom
Value sets, custom fields and feature toggles instead of forks.
- 5
Offline-first in the field
On-device promotion evaluation, syncing when signal returns.
- 6
ERP-agnostic
Standalone out of the box, ERP-connected through one adapter seam.
- 7
Secure by design
RBAC, encryption at rest, and governed support access.
Frequently asked questions
Do we need SAP?
No. FieldDNA runs standalone out of the box. SAP S/4HANA is a named adapter target when you want to connect an ERP.
Does it replace our ERP?
No. The ERP remains your financial system of record. FieldDNA gives you visibility and control over the secondary sales flow the ERP does not reach.
Does the field app work offline?
Yes. It is a fully offline-first PWA: attendance, beat plans, orders, collections and on-device promotions all work without signal and sync later.
Can we run different scheme rules per region?
Yes. Promotions target by Product List, Customer List, distributor scope and channel, with approvals by type.
Where is our data?
In your own isolated database, one per tenant, in your chosen region, with in-region backups by default.
Can distributors use their own tool?
The goal is one standard for every distributor. Distributors get a simple web app; brands enable the modules each distributor needs through feature toggles.
How is data kept separate between tenants?
There are no cross-tenant tables or foreign keys, and tenant binding happens at request time, with per-tenant storage and backups.
How long does it take to get started?
You can start standalone quickly and connect an ERP later. Onboarding imports or connects masters, configures modules and enables distributors.
Ready to run your distribution chain from one platform?
Live walkthrough on Microsoft Teams · Tailored to your distribution model · Works on web, Android and iOS