Magento integrations for catalogue and orders in 2026
When Magento CRM integrations share customer and order data, check field ownership, API limits and store views before relying on the connection.
- Published
- Last updated
Yes, Magento integrations can connect catalogue, customer and order data through APIs, compatible extensions or file transfers. The right route depends on your edition, product structure and store scope. A successful product import can still leave customers choosing a size that has no sellable variant behind it.
Identify the Magento environment
Identify your edition and deployment before choosing authentication or a connector. Magento Open Source and Adobe Commerce share platform APIs, but an Adobe service’s documentation doesn’t establish its availability in Open Source.
Record the installed version and enabled modules for Magento Open Source or Adobe Commerce on cloud infrastructure or on-premises. Treat Adobe Commerce as a Cloud Service as a separate environment. Adobe’s GraphQL overview documents different endpoints and schema behaviour for these deployments. Its Cloud Service product queries aren’t backward compatible with the corresponding core queries.
For a traditional Magento integration, create a dedicated integration in Admin and grant only the API resources the connection needs. Adobe documents OAuth 1.0a authentication for this route. Adobe Commerce as a Cloud Service instead uses Adobe’s Identity Management System (IMS) and OAuth 2 for REST authentication.
Write down the objects and permissions before connecting. A product information management (PIM) system may write descriptions and attributes. An enterprise resource planning (ERP) system may supply source quantities and receive orders. Magento CRM integrations need separate decisions about customer records, consent fields and which system can change an address. Catalogue read access alone doesn’t authorise customer or shipment writes.
Choose the supported connection route
Choose the connection by the task it must perform and the objects it can actually read or write. Magento 2 integrations often combine an initial import with later API updates.
Connection routes and responsibilities
| Route | Useful task | Direction and timing | Work you must allow for |
|---|---|---|---|
| REST API | Administrative catalogue, customer and order operations exposed by the installed platform | Reads or writes through specific endpoints, on your integration’s schedule | Authentication, field mapping and recovery after failed requests |
| GraphQL | Storefront product queries and supported customer or basket operations | Queries and mutations supported by that deployment’s schema | Store context and schema-specific fields; it isn’t a universal administrative write API |
| Import and export | Initial catalogue loads or batch exchange | A file moves in one direction per operation | File preparation, validation and an agreed batch frequency |
| Compatible extension or connector | A packaged connection to another system | Only the objects and update frequency its documentation supports | Version support, configuration and separate licence or service costs |
| Middleware or custom development | Transforming data or coordinating several systems | Your implementation controls the flow | Mapping code, scheduling, monitoring and operational ownership |
Adobe’s web API framework guide describes resource-based permissions and exposed services. Use the endpoint specification for each operation before treating an API connection as complete.
For files, use the sample supplied by your installation and validate it before import. Adobe’s import guidance distinguishes Add/Update from Replace. Replace clears existing product data and references. An omitted website in an Add/Update file also doesn’t remove an existing website assignment.
An extension’s Magento compatibility claim must cover your exact edition and version. Check its supported product types and custom attributes. Confirm that it preserves store-view values. Adobe’s App Builder compatibility guidance also distinguishes Cloud Service authentication and request conventions from traditional deployments. Include custom development or middleware costs when a connector cannot preserve those differences.
Map products across store scopes
Keep each product’s identity separate from its translated presentation and its inventory records. Adobe’s catalogue scope guidance explains how website assignment and store-view values affect what customers see.
Preserve the parent SKU and the child SKUs for configurable products. Each sellable variation is a simple product with its own SKU and inventory. Map the attribute set as well as the attribute codes and option values. Otherwise, the destination may receive product rows without the fields needed to select their variations.
Adobe’s configurable product requirements require variation attributes to have global scope. Store-view labels can still present those options in another language.
For example, imagine a configurable jacket with a child SKU JACKET-NAVY-M. Its global colour option identifies navy and its size option identifies medium. An English description and a French description can differ for that same child. Both still describe the same physical units at a warehouse.
Carry the store-view code with the description and retain whether the value inherits its default or overrides it. Keep website membership explicit. Never add the English and French records’ quantities together merely because the destination stores one row per language.
Reconcile stock and orders
Use the inventory source for physical quantities and the website’s stock for sellable availability. Inventory Management exists in Magento Open Source and Adobe Commerce, so first establish whether the installation uses it and which inventory modules are active.
Adobe’s inventory API documentation distinguishes sources, stocks and reservations. A source is a physical stock location. A stock connects sources to website sales channels. Reservations reduce the quantity available to sell before physical stock leaves a source.
Assign one system responsibility for dispatch. If an ERP or Magento fulfilment service sends the goods, agree how it receives authorised orders and returns shipment records. Publishing a product description must never trigger stock allocation or warehouse dispatch.
An illustrative partial-shipment flow
This example follows the traditional Inventory Management flow. Assume one source holds 10 units of JACKET-NAVY-M, with no backorders, safety-stock adjustment or competing orders. Read the authorised Magento order and its line identifiers before sending the warehouse request.
| Event | Source units | Sellable units | Expected order or shipment result |
|---|---|---|---|
| Customer orders 3 | 10 | 7 | Magento records the order and reserves 3 |
| Payment is invoiced and 2 units ship | 8 | 7 | A partial shipment records 2 against the order line; 1 remains reserved |
| The last unit ships | 7 | 7 | A second shipment records 1; the fully paid and shipped order is Complete |
| One shipped unit is refunded and returned to stock | 8 | 8 | A credit memo records the refund and the selected return-to-stock action |
Adobe’s order-creation example shows the reservation occurring before source quantities change. Its shipment example documents the source selection and order-line quantities used at shipment. Record the chosen source and carrier tracking against each shipment, so a partial dispatch doesn’t appear as a fully delivered order.
For a separate unpaid order of 3 units, cancellation before shipment releases the reservation. The source stays at 10 and sellable quantity returns to 10. After goods ship, use the refund and return process. Adobe’s order and reservation guidance explains cancellation compensation and the credit memo’s Return to Stock option.
Repeated warehouse messages need reconciliation. Save the warehouse event identifier beside the Magento shipment identifier. Before retrying a timed-out request, read existing shipments and quantities. Adobe recommends the order-specific ship endpoint because it validates total shipped quantity. That safeguard doesn’t replace your duplicate-event record: replaying a 2-unit dispatch must leave one 2-unit shipment, one stock deduction and one warehouse dispatch.
Carry reliable facts into buying assistance
Give buying assistance the store-view description and the exact sellable child, together with availability for the customer’s website. A parent jacket record cannot establish that the navy medium variation is available.
A useful comparison needs the variation’s size and colour alongside material, price and other relevant attributes. If an import drops configurable attributes, a product may appear in search while customers cannot identify the variation they want. Check the destination’s product-selection result as well as its import success count.
Keep delivery policy separate from dispatch evidence. A warehouse’s quantity doesn’t establish an arrival promise. Before purchase, use the retailer’s delivery rules and applicable stock availability. After purchase, answer from the authorised order and its shipments. When 2 of 3 units have shipped, name that partial quantity and its tracking instead of reporting the whole order as shipped.
Validate the connection after changes
Validate Magento integrations with controlled changes whose expected destination values are written down first. Run these acceptance cases in a non-production environment after changing mappings, credentials or connector versions.
Acceptance cases for catalogue and orders
| Change | Expected destination result | Failure to catch |
|---|---|---|
| Edit only the French jacket description | French copy changes; English copy and the child SKU stay unchanged | A scoped edit overwrites the global record |
| Change a child’s source quantity from 10 to 0 | The child’s availability reflects the website stock calculation; other children retain their quantities | The parent’s old stock value hides an unavailable option |
| Ship 2 units of a 3-unit order, then replay the warehouse event | One 2-unit shipment exists, with the chosen source and tracking; 1 remains unshipped | Duplicate shipment creation or dispatch |
| Cancel an eligible unpaid order before shipment | Its reservation releases and source quantity stays unchanged | A cancellation adds physical stock that never left |
| Refund a returned item with Return to Stock selected | The credit memo and source quantity agree | Refund status changes while inventory remains wrong |
Use the installation’s configured API input limits when setting page and batch sizes. Those limits are configurable, so a published default isn’t a throughput promise. Record the integration’s polling interval or event trigger and alert when updates exceed that interval. Keep a reconciliation job that compares changed records and resumes failed batches without repeating completed writes.
Plan credential renewal for the chosen authentication flow. Traditional integration OAuth access tokens remain valid until revoked. Cloud Service integrations obtain IMS tokens and must manage their expiry and renewal. Test replacement credentials before retiring the old connection, then confirm the next catalogue read and permitted order operation succeed.
Keep the platform choice separate from these acceptance results. The catalogue integrations guide helps you compare connection approaches across platforms. For Magento, release the connection when the scoped catalogue changes and order quantities agree at both ends.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.