Who this suits
Businesses connecting ERPNext to sales, payments or fulfilment systems.
When a simpler option is a better fit
Keep a controlled export if synchronisation is infrequent and no customer-facing process needs current information.
Implementation approach
List systems and the transactions they exchange
Assign ownership for each field and write operation
Pilot one direction with reconciliation and exception review
Illustrative operating rules
Integration discovery matrix and records that ERPNext should own
Illustrative design example. Adapt these rules with the responsible team before implementation.
| Record or decision | Illustrative rule | Accountable owner |
|---|---|---|
| Stock balance | ERPNext supplies authoritative quantity after agreed posting | Inventory manager |
| Customer enquiry | CRM owns sales conversation, ERP stores approved customer data | Sales operations |
| Payment draft | Finance reviews receipt allocation before posting | Finance lead |
Dependencies and access
- ERP version and API access
- System inventories and example records
- Owners for customer, stock and accounting data
Limits and exceptions
Two systems updating the same field can create a loop. Keep external identifiers and sync timestamps, and route incompatible states to review rather than overwriting the newest-looking value.
Scope and cost drivers
Discovery cost depends on systems, transaction types and unknown data quality. Pair-specific implementation is a separate scope after access is verified.
Acceptance and measurement
A useful discovery deliverable identifies direction, keys, owners, frequency, access gaps and failure handling for every proposed connection.
Questions before starting
What must be ready before implementation?
ERP version and API access; System inventories and example records; Owners for customer, stock and accounting data.
Product documentation
Documentation checked 11 October 2026. Access and costs must be confirmed for your account and intended workflow.
Discuss the scope and availability
Tell CraftDuka about the task, your current systems and the people who will use it. Our team is based in Nairobi and serves Kenya and East Africa. We will assess the fit and availability before agreeing a project.