Multi-ERP Integrations

Some organizations run parallel ERPs, often as a result of acquisitions, regional splits, or legacy systems still in production, and commerce has to integrate with both without forcing one into the other's model.

Microsoft Dynamics 365 and Dynamics AX both feed product, pricing, and inventory data into inRiver PIM and Optimizely through a custom middleware layer using message queues, with file-based integration for bulk data (pricing, inventory, media) and API-based integration for real-time flows (orders, customers).

Running two ERPs in parallel means commerce has to integrate with both without treating one as a copy of the other. Each system owns different data, uses a different integration pattern, and evolves on its own timeline.

Prophet 21 serves as the primary system of record, connected through a two-way integration layer. Prelude operates as the secondary ERP for customer data, with subscription-based events triggering automatic synchronization on every create, modify, or delete.

Commerce platforms rarely connect to ERP through a single integration point. Orders, pricing, inventory, customers, invoices, tax, freight, and document generation each follow their own data model and timing requirements. In this environment, without a structured middleware layer, every new feature would have become another custom integration project.

This middleware consolidates 38 dedicated API endpoints across seven business domains (orders, pricing, inventory, freight, customers, invoices and finance, tax, documents, account flags) into a single orchestration layer. A single connector manages authentication, serialization, error handling, and response mapping for every call, keeping the integration surface consistent and maintainable as new endpoints are added.