ERP Integrations2 min read
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
WooCommerce ERP integration that survives plugin updates
WooCommerce gives you full control of your store — and full responsibility for it. Plugins add fields, change checkout behaviour and occasionally break APIs. An ERP integration has to be resilient to that variability.
Overview
What this integration is for
We integrate WooCommerce through its REST API and signed webhooks, with explicit mapping for custom fields that plugins add.
01Data
What data syncs, and in which direction
| Entity | Direction | Notes |
|---|---|---|
| Orders | App → ERP | Orders imported on creation or payment, including meta fields added by plugins. |
| Order status | ERP → App | Processing, completed and tracking numbers updated from the ERP. |
| Products | ERP → App | SKUs, prices and stock status; descriptions may remain WooCommerce-managed. |
| Stock quantities | ERP → App | Available stock pushed per product and variation. |
| Customers | App → ERP | Registered customers and guest buyers matched by email. |
02Use cases
Common use cases
01
Eliminate order re-keying
Orders arrive in the ERP automatically with correct prices and taxes.
02
Prevent overselling
Stock levels kept current from ERP inventory.
03
Wholesale and retail on one stock
B2B orders in ERP, retail via WooCommerce.
03 — Architecture
API architecture
WooCommerce webhooks notify an integration endpoint of new or updated orders. The endpoint verifies the signature, queues the event and fetches the full order through the REST API before processing — which also protects against partial payloads.
Stock and status updates flow outbound in batches using the REST API's batch endpoints, reducing load on the WordPress server.
04Reliability
Authentication, errors and retries
01
Authentication
REST API consumer key and secret generated for a dedicated integration user with the minimum required permissions, over HTTPS only.
02
Error handling
Orders are processed idempotently by WooCommerce order ID. Mapping failures — unknown SKUs, invalid addresses — are held in an exception queue with clear reasons.
03
Retry strategy
Failed API calls retry with backoff, accounting for hosting limits on shared WordPress servers. Persistent failures alert the team and a nightly reconciliation catches gaps.
05 — Data mapping
Field mapping essentials
| WooCommerce | ERP |
|---|---|
| id / number | Sales order reference |
| line_items.sku | Product reference |
| billing.email | Partner |
| meta_data (plugin fields) | Mapped custom fieldsDocumented per plugin |
| shipping_lines.method_id | Delivery method |
06 — Automation
Automation opportunities
- Mark orders completed and add tracking when shipped from the ERP
- Update stock status to 'out of stock' when ERP availability reaches zero
- Route orders to the nearest warehouse with stock
- Flag orders with unusual quantities for review
07 — Security
Security considerations
Webhook signatures (HMAC-SHA256) are verified. API keys are scoped to a dedicated user and rotated periodically. WordPress and WooCommerce should be kept patched, because the integration is only as secure as the store.
Related
Where this integration fits
Other integrations
Often connected together
ShopifyOrders, customers, products, stock and fulfilment synchronised between Shopify and your ERP.StripeStripe payments, subscriptions, refunds, fees and payouts reconciled in your ERP.PayPalPayPal payments, refunds, fees and settlements reconciled with ERP orders and invoices.AmazonAmazon Seller Central and FBA orders, inventory, fees and settlements connected via SP-API.
Insights
Related reading
ERP Integrations2 min read
ERP Integration Guide: Patterns, Data Ownership and Reliability
How to integrate an ERP with eCommerce, CRM, payments and other systems: data ownership, integration patterns, middleware, error handling, monitoring and common failure modes.
ERP Integrations2 min read
RFID Integration with Odoo: A Practical Architecture
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
Frequently asked questions
Will plugin updates break the integration?
They can if plugins change data structures. We document dependencies and include integration checks in your update routine.
Can our hosting handle the API load?
Batching and scheduling outbound updates keeps load modest. Very large catalogues may need better hosting.
Can we sync product descriptions?
Yes, but many clients keep marketing content in WooCommerce and sync only operational data.
Next step
Connecting WooCommerce to your ERP?
Tell us your volumes, channels and data rules. We will outline the architecture and the risks before anything is built.