The problem
“We activate a promotion in the ERP, but the website still shows the old price. Someone has to remember to update it.”
Context
- Operation
- Retail chain, Nicaragua
- Systems involved
- Retail ERP · integration · e-commerce
The approach
An event-driven integration carries each promotion from the ERP to the online store. The ERP owns the promotion definition; the store receives a version it can apply without manual entry.
Retail ERPQueue + integrationOnline store
Latency and ordering
The latency target is agreed based on the available APIs. A version per promotion makes out-of-order events detectable.
Retries without duplicates
An event key makes repeated delivery safe: the same promotion update is applied once. Retries use backoff and a limit.
When the store is unavailable
The queue retains pending work. Persistent failures move to review, with an alert and a replay path.
Security and traceability
Credentials stay outside source code, with least-privilege access and encrypted connections. Logs trace events without exposing sensitive data.
Outcome
- A single promotion definition.
- Fewer manual updates between systems.
- Visibility into applied updates and those needing attention.