The ability to pull or push data as needed is one of Adobe Commerce’s real strengths. Four standard methods cover most integration scenarios.
Data is king — four integration patterns
- API (SOAP or REST) — Real-time or near-real-time data movement between two systems. Best for low-latency, transactional sync.
- Files (CSV or XML) — Either as a one-time data migration at project start, or as ongoing batch transfers. Best for high-volume, periodic sync.
- PaaS integration platform — Cloud-based connectors (Mulesoft, Boomi, etc.) with pre-built integrations for common systems. Best when you need ETL, transformation, and multiple endpoints.
- Manual updates — Admin portal supports import/export of products, customers, and other records. Best for low-volume, ad-hoc changes.
How to choose the pattern
The right pattern depends on three factors: volume (how many records), frequency (how often), and latency tolerance (how fresh does the data need to be).
- High volume, low frequency, latency-tolerant — file-based batch.
- Low volume, high frequency, latency-sensitive — API.
- Mixed — PaaS integration platform handles the orchestration.
- One-off corrections — manual admin updates.
Common integration targets
- ERP — NetSuite, SAP, Microsoft Dynamics, Sage.
- OMS — IBM Sterling, NetSuite, Manhattan.
- CRM — Salesforce, HubSpot, Microsoft Dynamics 365.
- Tax — Avalara, TaxJar, Vertex.
- PIM — Akeneo, Pimcore, Salsify.
- Marketing — Klaviyo, Mailchimp, dotDigital, Emarsys, Adobe Campaign.
Adapted from the Adobe Commerce Primer, slide 25. Last reviewed May 2026.