Integration Library
Mikro ERP–WooCommerce Stock Integration: Architecture and Checklist
Data mapping, synchronisation and error-handling considerations when planning stock transfers between Mikro ERP and WooCommerce.
- Mikro ERPApproved available stock
- Authorised integration serviceSKU/variant mapping and queue
- WooCommerceQuantity update on the matched product
If stock shown to online shoppers differs from actual ERP stock, cancellations, delays and manual corrections increase. When designing stock integration between Mikro ERP and WooCommerce, first decide which system is the authoritative stock source. This guide explains how to assess a technical solution; it does not claim that the integration already exists automatically.
Data access offered by the systems
Mikro's official MikroAPI documentation describes StokListesiV2 for listing existing stock records and StokKaydetV2 for creating stock records. The WooCommerce REST API supports reading and updating products. These capabilities are a starting point for integration; how to obtain available quantities by warehouse must be tested separately.
Recommended data flow
This section covers stock transfers from ERP to store. If the project also transfers store orders to ERP, plan that as a separate flow. If order notifications are missing, the WooCommerce webhook troubleshooting and missing-order reconciliation guide helps distinguish event creation from ERP acceptance.
- Link products on both sides using a shared SKU or an explicit mapping table.
- Map product codes, variants, units, warehouses and active/inactive statuses.
- Define the formula for available stock in the ERP: assess physical stock, reservations and open orders separately.
- Choose events or controlled periodic queries to transfer only changed records.
- Record WooCommerce update results; put failed operations in a retry queue.
- Use an end-of-day reconciliation report to identify missing or mismatched SKUs.
Pilot test matrix
| Scenario | Expected behaviour |
|---|---|
| New SKU | Send it to a review list if no mapping is found |
| Product with variants | Do not confuse parent product and variant codes |
| Concurrent orders | Account for reserved stock |
| Lost connection | Preserve the last successful synchronisation point |
| The same event arrives twice | Idempotent processing prevents a duplicate update |
Common design decisions
One-way or two-way? If the ERP is the stock authority, writing stock back from WooCommerce may create inconsistencies. Are there multiple warehouses? The store quantity should include only warehouses available for sales. How frequent should synchronisation be? Measure according to transaction volume and API capacity; do not make arbitrary “real-time” promises.
When is custom integration needed?
Businesses with one warehouse and a simple catalogue may be served by an existing connector. The need for custom design increases with specialised price lists, dealer-specific stock, multiple warehouses, approval workflows or custom ERP rules.
Why can stock still be wrong for a correctly matched product?
Example scenario: In the ERP, KOLİ-01 represents a box, while the store sells the same product individually. Mapping product codes alone is insufficient; define the units per box and which unit is deducted from stock. Likewise, updating the parent product's stock field does not update a variant whose stock is managed separately.
| Data | Authoritative source | Transfer rule |
|---|---|---|
| Product/SKU mapping | Approved mapping list | An unknown code does not automatically create a product |
| Sellable quantity | The agreed ERP calculation | Apply the selected warehouse and reservation rules |
| Store order (additional scope) | WooCommerce | Track ERP acceptance using a stable external reference |
| Cancellation or return (additional scope) | According to the business rule | Repeated events do not increase stock twice |
Stock synchronisation alone does not guarantee protection against overselling. Test when concurrent sales in the store and ERP reserve stock. For an initial setup, the stock Excel template, and for authorisation problems, the WooCommerce 401 guide are available.
Which versions and permissions are required before connecting?
This flow is an architectural recommendation for a store using on-premises MikroAPI and the WooCommerce REST API. Record the Mikro product family/version and API service, WordPress/WooCommerce versions, product/variant structure and stock-management plugins together. Verify the Mikro API licence and fields exposed by the stock method, and the necessary access for the WooCommerce API key tied to its user. MikroAPI access requirements; WooCommerce authorisation.
Before the pilot: Prepare a test store, test company, sample SKU/variant list, sale-enabled warehouses, reservation calculation and expected sales behaviour when stock updates are delayed. Start with read-only comparisons on a few products, then controlled quantity updates in the test store. No real client connection has been tested for this page.
Sources and verification
Example flows are architectural recommendations, not claims of completed client projects or vendor partnerships. Technical sources checked: 17 October 2026. Installation version, licence and permissions must be verified separately.
Adapt it to your business workflow
ERP integration planning guide. Explore the B2B portal development scope for further reading; we can assess your current process together.
Let's discuss your needs →