How to integrate Magento / Adobe Commerce with ERP and CRM without blocking checkout (a RabbitMQ architecture)

The classic mistake: synchronous integration at checkout

Many stores call the ERP, anti-fraud or CRM in the middle of placing the order. It works on a normal day. On sale day the ERP slows down, checkout waits, times out and the customer gives up, or worse: pays and the order never reaches the ERP.

Every external system will go down one day. The architecture has to assume that.

Asynchronous integration with queues

Magento 2 and Adobe Commerce have a Message Queue framework that works with RabbitMQ. The design I use:

• The event happens in the store (order placed, customer registered, lead created) and is saved to the database as usual.
• A publisher puts a message on the queue with the data needed.
• Consumers process the queue in the background and call the ERP or CRM.
• If the call fails, the message is retried; after N failures it goes to an error queue, with a log and an alert.

A real example (no names)

On a used-vehicle marketplace for a global automaker, on Adobe Commerce Cloud, the platform had 14 custom modules, leads routed to the CRM and multiple payment gateways. RabbitMQ queues ensured no lead was lost when an external system wobbled. I joined as Senior Frontend and, at the client's request, was named project architect.

Details that make the difference

• Idempotency: reprocessing the same message must not duplicate an order in the ERP.
• Documented, versioned contracts (REST or GraphQL).
• Explicit status mapping between the store and the ERP.
• Observability: knowing how many messages are queued, how many failed and why.
• Payment stays synchronous where it must (authorisation), but reconciliation can be asynchronous.

When synchronous integration still makes sense

Fast, essential lookups such as shipping rates or card authorisation stay real-time, with a short timeout and a fallback response. Whatever doesn't need to happen in front of the customer goes to the queue.