ERP–CRM sync: what happens when the API fails
This is an internal demo with fictional data. No real company appears in the flow. It exists to show what is almost never shown: what happens when the integration fails.
The flow
- A new ERP record propagates to the CRM carrying its source identifier.
- The second call returns a 500 from the provider.
- The flow retries with backoff and, once attempts are exhausted, parks the record in a review queue instead of losing it.
- When the service recovers, the record is reprocessed without duplicating.
Why duplicate control is the hard part
Retrying is easy; retrying without duplicating requires an idempotency key that is stable across both systems. Without one, every retry creates a new record and the problem surfaces weeks later, at month-end close.
What the demo leaves out
There is no real volume, no production latency and none of the quirks of a specific ERP. A real integration starts by reviewing exactly those three things.
Related service
API, ERP and CRM integrations that hold up when something fails
Synchronisation between systems with error handling, retries, duplicate control and monitoring.
Are your systems talking properly?
Tell us which systems need connecting and in which direction. We review authentication, errors, retries and duplicates before proposing anything.