ERP API Integration Explained: REST, Webhooks, Auth and Idempotency
A plain-English explanation of ERP API integration: REST APIs, webhooks, authentication methods, idempotency, pagination, rate limits and error handling.
Integration · Commerce
Overview
We build Magento integrations on its REST API, with clear ownership rules per data type and a reconciliation job that catches anything missed.
01Data
| Entity | Direction | Notes |
|---|---|---|
| Orders | App → ERP | Orders imported with lines, discounts, shipping, taxes and payment method, per store view. |
| Customers & B2B companies | App → ERP | Customers matched by email; B2B companies mapped to ERP accounts with credit terms. |
| Products & prices | ERP → App | ERP owns SKUs, cost and base prices; Magento keeps descriptions, images and SEO content. |
| Inventory | ERP → App | Salable quantity per source pushed to Magento's multi-source inventory. |
| Shipments & tracking | ERP → App | Shipments created in Magento with tracking numbers when the ERP delivery is validated. |
| Credit memos | App → ERP | Refunds create credit notes and return receipts in the ERP. |
02Use cases
Thousands of SKUs and configurable products kept in sync.
Company accounts, negotiated prices and retail on one ERP.
Per-source availability from real warehouse stock.
Orders, refunds and payments posted without manual journals.
03 — Architecture
Orders are pulled on a short schedule or pushed by an extension into a queue, then processed asynchronously so storefront performance is never affected. Stock and price updates are batched, and large catalogue updates run off-peak.
A nightly reconciliation compares orders, shipments and stock on both sides and reports differences.
04Reliability
An integration user with token-based access limited to the required API resources. Tokens are kept in a secrets manager.
Orders are processed idempotently using the Magento increment ID. Validation errors go to an exception queue with the reason, for the operations team to fix and replay.
Network and rate-limit failures retry with exponential backoff, then move to a dead-letter queue with an alert.
05 — Data mapping
| Adobe Commerce (Magento) | ERP |
|---|---|
| increment_id | Sales order reference |
| items.sku | Product internal reference |
| store_id | Sales channel / companyPer store view |
| source_code | WarehouseMulti-source inventory |
06 — Automation
07 — Security
TLS everywhere, least-privilege API scopes, no card data stored in the ERP, and logs that exclude personal data where possible.
Related
Other integrations
Insights
A plain-English explanation of ERP API integration: REST APIs, webhooks, authentication methods, idempotency, pagination, rate limits and error handling.
How to integrate an ERP with eCommerce, CRM, payments and other systems: data ownership, integration patterns, middleware, error handling, monitoring and common failure modes.
How to integrate RFID readers with Odoo inventory: middleware design, mapping EPCs to products and serials, receiving and counting flows, performance and what to build vs buy.
FAQ
Yes. Both expose the same core REST API; Adobe Commerce B2B features add company and shared catalogue data.
Yes. A common split is ERP for SKUs, prices and stock, Magento for marketing content.
Next step
Tell us your volumes, channels and data rules. We will outline the architecture and the risks before anything is built.