Middleware Architectures

Multi-system commerce integration is rarely a single pattern. Product data flows in real time from the PIM, master data and inventory sync periodically from the ERP, orders flow back to the ERP for fulfillment, and search needs continuous catalog indexing. Each flow has its own data shape, frequency, and timing requirements.

An Azure-based middleware orchestrates three distinct integration flows, each using the integration pattern that matches its requirements. Inriver PIM pushes product updates via Service Bus. ERP master data syncs via FTP and API delta requests with Cosmos DB as the change store. Orders route through Service Bus and FTP to the fulfillment ERP.

Inventory and pricing data has to move reliably between the ERP, the PIM, the OMS, and commerce, often with two competing needs: business needs control over when bulk updates land, and operations needs fast, low-latency updates when a single SKU's stock or price changes mid-day.

An Azure-based middleware orchestrates both modes through one path. Bulk files arrive via SFTP with event-driven or scheduled processing and a business-controlled release gate. Partial updates arrive through a separate API and pass through the identical validation, active-SKU filtering, and Cosmos DB staging path, so a single-SKU change reaches the storefront through the same pipeline as a bulk file.

A comprehensive integration architecture starts with a clearly defined Digital Experience Platform at the center, owning catalog, subscriptions, pricing, commerce, content, and customer management, with every external system connected through a structured middleware layer rather than direct point-to-point integrations.

In this architecture, Boomi serves as the integration platform orchestrating three distinct sync flows to Salesforce CRM: master data and CRM sync (customers, contacts, accounts), account and order sync (orders and status updates), and other data sync (inventories, reference data, web order updates). Stripe handles payment processing with webhook-based response handling. Okta manages identity and new user provisioning. A tax provider, search and navigation layer, scheduled data reconciliation jobs, analytics platform, BNPL provider, and address validation service each connect at the appropriate layer, all coordinated through the same integration platform.