Platforms / 04
Bring your ERP and WooCommerce into sync.
Products are maintained in the ERP, edited again in the shop and updated through files. We connect the data models and clarify which information is owned by the ERP and which remains in the shop.
The starting point
A product number is not a complete mapping.
WooCommerce distinguishes products and variants; an ERP may also have tenants, warehouses and price lists. A SKU needs to be unique in its business context. Descriptions, images and SEO text may instead be maintained in the shop.
We review supported ERP access and the installation's WooCommerce REST API. Currency, tax logic, units and the meaning of an inventory quantity need to be clarified before the first transfer.
What DataSource delivers
Identities and variants. Field ownership. Runs and reconciliation.
Identities and variants
Map ERP products to shop IDs. Handle variant attributes, parent products and discontinued products separately.
Field ownership
Import master data, prices and available quantities from the system of record. Preserve shop-owned text and campaign fields as agreed.
Runs and reconciliation
Import the initial dataset in a controlled way, then transfer changes and reprocess failed records selectively.
Technical scenario / Illustrative example
From an ERP product to an existing shop product.
Illustrative mapping of a simple product. Prices are passed as decimal strings here. Whether a quantity is available for sale and whether tax is included are defined by the business rules.
Example data and proposed rules. The actual interfaces and business rules are assessed for your project.
ERP.artikelnummer → sku: "004218"
ERP.verkaufspreis → regular_price: "49.90"
ERP.verfuegbar → stock_quantity: 12
Integration → manage_stock: true
Shop.redaktion → description bleibt im ShopError handling, security and operations
Access: validate and operate.
Access
Limit WooCommerce API keys to the required scope and use them over HTTPS. Do not place keys in request URLs or general logs.
Inventory semantics
Distinguish physical stock, reserved quantities and available quantities. An integration does not replace business reservation logic.
Exceptions
Handle orphaned variants, duplicate SKUs and blocked products separately. Shop changes and ERP changes receive traceable priorities.
Technical questions
Details that matter before implementation.
WooCommerce · ERP · SKU · Variants · Prices · Inventory
Which system owns the product description?
This is decided per field. For example, the ERP owns technical data while the shop owns editorial sales copy.
Are orders also transferred to the ERP?
That is a separate data flow with status, payment and retry rules. It can be part of the same project but is specified separately.
Can an existing plugin remain in use?
Yes, if it supports the agreed task. We check for overlapping responsibilities so that two processes do not update the same fields in conflict.
For technical clarification
Start with your actual workflow.
Gather the ERP version and access options, product model, variant examples, inventory and pricing rules, and existing shop plugins. An anonymized problematic product is particularly helpful.
In our initial discussion, we clarify available access, data ownership and a narrowly scoped first data flow. We then agree on scope, responsibilities and commercial terms.
Anonymized examples are enough to get started. Please do not send passwords, tokens or personal data from production systems in your initial inquiry.
Related challenges
Your next connection in context.
Automate product data workflows
The ERP supplies master data, the PIM supplies text and a supplier provides technical attributes. Manual lists connect this information only temporarily. We create a defined data flow from each authoritative field to a validated channel export.
Synchronize orders & status updates
The shop reports payment, the ERP has no order yet and shipping already has a tracking number. We connect these steps with defined states, unique order references and planned recovery.
ERP and CRM interfaces
Sales and accounting work with the same customer for different purposes. DataSource connects the supported interfaces and clarifies which data is transferred, and when, between prospect, customer and debtor records.
Technical references
Official documentation, reviewed on October 6, 2026. Suitability depends on the specific installation and version.