What changes when the storefront is WooCommerce rather than a hosted platform — and what that means for the integration.
A WooCommerce integration connects a WordPress storefront to the ERP through the WooCommerce REST API, so orders flow in and stock, pricing and fulfilment flow out. The mechanics resemble a Shopify integration. What differs is that WooCommerce is self-hosted and plugin-driven, so the environment it runs in is yours to manage and yours to break.
Self-hosting is the whole difference. On a hosted platform the API behaves predictably because the vendor controls the stack. On WooCommerce, a plugin update, a PHP version change or a caching layer can alter behaviour between one week and the next. The integration therefore has to be defensive in ways a hosted-platform integration does not.
Consumer key and secret over HTTPS. Credentials are scoped, so grant only what the integration needs.
Polling on a schedule or webhook-driven. Webhooks are faster; polling is more resilient when the site is under load.
WooCommerce variations must map to distinct ERP items. This is the most common source of mapping errors.
From the ERP outward, on schedule or on change, with the ERP as system of record.
Order status and tracking written back so the customer notification fires from the store.
An integration maps WooCommerce products to ERP items by SKU. Testing passes. Within a fortnight, roughly four percent of orders fail to import.
The failures share a cause. WooCommerce SKUs were maintained by the marketing team, who added suffixes for bundles and seasonal variants, used lowercase inconsistently, and in a few cases left variations without a SKU at all. The ERP item codes never changed. The mapping worked for every product that existed at build time and broke for everything created afterwards, because nobody owned the rule.
The fix has two parts and the second is the one that lasts. Technically, normalise on both sides and hold an explicit mapping table for the exceptions rather than relying on string equality. Procedurally, decide who owns product creation and require the ERP item to exist first, so a product cannot be published without a mapping. Integrations do not usually break because of code; they break because somebody creates data on one side that the other side has never heard of.
| Term | What it means |
|---|---|
| REST API | WooCommerce's interface for reading and writing orders, products and stock. |
| Webhook | A callback fired on an event, used to push orders to the ERP as they are placed. |
| SKU | The field that normally maps a WooCommerce product to an ERP item. It must be unique and must match. |
| Order status | WooCommerce's lifecycle states — processing, completed, cancelled — which the ERP writes back. |
| Variable product | A product with variations, each of which maps to its own ERP item. |
A tax or shipping plugin update can alter the order structure. Validate incoming payloads rather than assuming shape.
Aggressive page caching can display stock levels the API has already changed. Exclude the relevant endpoints.
A variation that does not map to a distinct ERP item produces wrong stock and wrong fulfilment.
WooCommerce webhooks can fail silently under load. Reconcile periodically against order IDs rather than trusting delivery.
| Metric | What it tells you | What distorts it |
|---|---|---|
| Order import failure rate | The headline health check, and it should be near zero after the first fortnight. | |
| Unmapped SKUs | Products on the storefront with no ERP item. A leading indicator of failures to come. | |
| Stock sync lag | Minutes between an ERP change and the storefront reflecting it. | |
| Orders in WooCommerce vs ERP | The daily reconciliation that catches anything the error log missed. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.