Your ERP stays the system of record
DigiTS is the operational layer your ERP cannot reach — the offline rep, the driver at the door, the merchandiser at the shelf. Results post back in near real time, not overnight batch.
SAP
S/4HANA, ECC and Business One
Oracle
Fusion, EBS and NetSuite
Microsoft Dynamics
365 Business Central and F&O
Odoo
Community and Enterprise
Sage
X3, 300 and 200
Infor
M3 and CloudSuite
Tally
Prime and ERP 9
Custom / in-house
REST, SOAP or file exchange
Not listed? Integration is built against whatever your system exposes — REST, SOAP, database views or structured file exchange.
Bidirectional by design — masters down, transactions up
The field always trades against current prices and credit positions, and head office always sees today's market rather than yesterday's.
Flows down to the field
- Customer master with credit limits and terms
- SKU master, hierarchy and pack configuration
- Price lists and customer-specific contracted pricing
- Promotions, schemes, rebates and free-goods rules
- Warehouse and depot stock positions
- Open invoices and receivables for collection
Posts back to the ERP
- Sales, return and free-goods invoices
- Sales orders raised by field, telesales and the portal
- AR receipts, settlements and payment allocations
- Stock movements: load-out, transfer, offload and adjustment
- Delivery confirmations with proof of delivery references
- New outlet records and master data change requests
Integrations fail. The question is what happens next
Queue and replay
Failed postings are retained with their error and replayed once the ERP is available.
Reconciliation reporting
Any transaction present in DigiTS but missing in the ERP is surfaced immediately.
Exception alerting
Integration failures raise alerts rather than sitting silently in a log file.
Idempotent posting
Replays cannot create duplicate invoices or double-count receipts.
Integration questions
How does DigiTS integrate with our ERP?
Through REST APIs, middleware connectors or scheduled file exchange, depending on what your ERP exposes and what your IT team prefers to support. The integration is bidirectional: customer, SKU, pricing and promotion masters flow down to the field, and invoices, receipts, stock movements and delivery confirmations post back.
Is integration real time or batch?
Transactions post in near real time as devices sync, rather than in an overnight batch. Master data refresh is usually scheduled, since prices and product hierarchies change far less often than transactions. Exact latency commitments are agreed during discovery.
What happens if the ERP is down or a posting fails?
Failed postings are queued with the error retained, and replayed once the ERP is available. Reconciliation reporting shows any transaction that exists in DigiTS but not in the ERP, so discrepancies surface immediately rather than at month end.
Our ERP is heavily customised. Is that a problem?
It is common rather than exceptional in distribution. Discovery includes mapping your actual field and document structures, not the vendor's standard ones. Where your ERP has no suitable API, middleware or structured file exchange is used instead.
Can DigiTS run without an ERP at all?
Yes. Smaller distributors and some channel partners run DigiTS standalone, using it as the operational and reporting system. If an ERP is introduced later, the integration is added without re-implementing the field operation.
Bring your ERP to the conversation
Tell us which system you run and how it is customised. We will tell you honestly what the integration looks like — including where it gets difficult.
Or email sales@digitsrtm.com