Design ecommerce integrations for failure and replay
CodeAstra Tech · Engineering decision guide
Start with the problem
An integration is incomplete if it works only when every request succeeds. Duplicate events, timeouts and out-of-order updates are normal cases to design for.
Define the scope
Define a stable event key and store processing results durably. A retry should reuse the original key so a repeated delivery does not create another order.
Check the failure cases
Separate temporary failures from invalid data. Retry temporary errors with limits; route malformed or unmapped records to a visible queue with enough context for a person to correct them.
Make the decision
Reconcile source and destination periodically. An execution log alone cannot prove every business record arrived correctly.