Skip to main content
Talk to an expert
WooCommerce logo

WooCommerce marketplace integration for ecommerce

Unified stock and orders across WooCommerce and every sales channel. iWeb connects WooCommerce to OMS, ERP and fulfillment systems so inventory is allocated fairly, orders flow consistently and customers see accurate stock status regardless of channel. Works with Adobe Commerce, Magento Open Source, Shopify Plus, BigCommerce and other storefronts.

Also searched as: marketplace connector, feed integration, channel plugin, app.

WooCommerceiWeb integration layeryour storefront
Talk to an expertSee the estate map ↓
Works with - Magento Open Source · Adobe Commerce · Shopify Plus · BigCommerce · Other storefronts
On this pageGet a brief reviewed
01 · What you get

What a WooCommerce integration gives you.

Stock accuracy across channels

Inventory is allocated fairly across WooCommerce, physical stores and other storefronts. Oversell is prevented and customers see realistic delivery windows based on actual available-to-sell stock.

Consistent order-to-cash flow

Orders placed on WooCommerce flow through OMS and into ERP with the same rigour as other channels. Acknowledgement, dispatch and billing happen consistently regardless of which channel the order came from.

Operational visibility

Order and inventory exceptions on WooCommerce are surfaced to the right teams in real time. Stuck orders, sync failures and stock mismatches do not hide in logs; they are tracked and resolved.

Simplified product governance

Product content, images and pricing are maintained in PIM once and published to WooCommerce alongside other channels. There is one source of truth, and channel-specific variations are applied at publish time, not stored separately.

Scalable multi-location fulfillment

Orders from WooCommerce can be fulfilled from any warehouse, branch or dropship partner based on inventory and business rules. Returns and refunds route back through the same system that captured the order.

02 · When it's worth it

Where a WooCommerce integration earns its place.

If two or more of these are true, the integration usually pays for itself quickly.

Publish product catalogue, pricing and stock from PIM or ERP to WooCommerce alongside other channels
Ingest orders from WooCommerce into OMS and ERP with consistent order acknowledgement and status
Allocate inventory across WooCommerce, physical branches and other sales channels using OMS rules
Route despatch confirmations and tracking back to WooCommerce customers from fulfilment systems
Synchronise customer account data and order history between WooCommerce and CRM or trade platforms
03 · The limits

Where off-the-shelf connectors fall short.

Vendor connectors are fine for simple cases. Here's where the real ones need more.

Native stock sync gaps

WooCommerce's built-in inventory tools work best for single-channel retailers. Multi-channel stock allocation, backorder rules and channel-specific availability require custom logic outside WooCommerce to prevent oversell and manage channel priority.

Limited order routing

WooCommerce cannot natively route orders to different fulfillment locations or dropship suppliers based on inventory availability or business rules. OMS or custom middleware is needed to split orders and assign them to the right fulfillment node.

No native pricing by channel

WooCommerce stores prices locally; it cannot dynamically apply channel-specific pricing rules, margin adjustments or promotional pricing from a central price book without feed-based updates or a custom pricing layer.

Manual customer account linking

WooCommerce customer records exist only in the WordPress database. Syncing trade account details, credit limits or purchase history from ERP or CRM requires custom mapping and cannot be automated bidirectionally by default.

Weak exception visibility

Sync failures, stuck orders or inventory mismatches in WooCommerce often go unnoticed without external monitoring. The platform logs events but does not natively alert operational teams or queue exceptions for investigation.

04 · The real work

Retailers treat WooCommerce as a simple cart, then face inventory conflicts when orders collide with physical stores or other channels. The integration must allocate stock fairly and route orders through a unified operational system, not assume WooCommerce is the sole source of truth.

05 · Where it sits

Where this integration sits in your estate.

WooCommerce holds the commercial record. The iWeb integration layer manages the rules, mappings, monitoring and exceptions. The commerce platform presents the customer-facing experience. The estate map helps agree ownership before anything is built.

Platform-agnostic by design. WooCommerce sits at the centre of your estate, not at the edge of one platform.

System of record
Source / owner
WooCommerce
Sales channel for orders, product catalogue and customer interaction
  • Storefront display and checkout experience
  • Customer account profiles in WordPress
  • Local shopping-cart and checkout sessions
  • Initial order capture and customer communication
iWeb integration layer
Customer-facing commerce
Commerce platform
Magento Open SourceAdobe CommerceShopify PlusBigCommerceOther storefronts
  • Product catalogue (received from PIM)
  • Pricing and promotions (received from price book)
  • Inventory availability (received from OMS)
  • Order status and tracking (received from OMS/WMS)
  • Customer identity and history (shared with CRM/ERP)
Connected neighbours
Integration layer
PIM
Source of product attributes, descriptions, images and taxonomy. WooCommerce receives published snapshots.
Integration layer
ERP / Price book
Source of base and channel-specific pricing. WooCommerce displays prices; does not update the source.
Integration layer
OMS
Allocates inventory across channels and routes orders to fulfillment. WooCommerce receives available-to-sell stock; sends orders for processing.
Integration layer
WMS / 3PL
Executes fulfillment, generates tracking and processes returns. WooCommerce displays status updates for customer visibility.
Integration layer
CRM
Holds customer profiles, purchase history and preferences. WooCommerce syncs customer account events and order data.
Two-way sync where relevant
06 · Surrounding systems

Systems this integration usually sits next to.

Examples, not a closed list. iWeb is platform-agnostic on both sides: we wire this integration into whatever ecommerce platform and surrounding systems your estate already runs.

Ecommerce platforms (examples)
  • Magento Open Source
  • Adobe Commerce
  • Shopify Plus
  • BigCommerce
  • Other storefronts
Surrounding systems (examples)
  • Order management system (OMS)
  • Enterprise resource planning (ERP)
  • Product information management (PIM)
  • Warehouse management system (WMS)
  • 3PL / fulfillment provider
  • Customer relationship management (CRM)
  • Payment processor
Not sure?

Not sure if this works with your stack?

Tell us what you’re using and what needs to connect. We’ll give you a straight view on what’s possible, what might be awkward, and the safest way to approach it.

07 · Data flows

The data flows we wire.

Each flow has a direction and an owner. We agree both before a line of code is written.

→Into COMMERCE & SALES CHANNELS & ERP / OMS
←From FULFILMENT
↔BOTH WAYS
Catalogue and pricing sync: Product attributes, descriptions, images and channel-specific pricing from PIM or ERP feed into WooCommerce on a scheduled or event-driven cadence
Updates to variants, categories and media assets propagate without requiring manual intervention on the storefront.
Stock and allocation updates: Available-to-sell stock calculated in OMS or ERP pushes to WooCommerce to prevent oversell across channels and physical locations
Reserved stock for pending orders is held back from other channels in real time or near-real time.
Order capture and acknowledgement: Customer orders placed on WooCommerce are transmitted to the OMS or ERP with line detail, shipping address and any channel-specific attributes
Order acknowledgement and reservation are sent back to WooCommerce to display delivery windows or backorder status.
Dispatch and tracking: Despatch confirmations, carrier tracking numbers and proof-of-delivery events flow from the WMS or 3PL back through OMS to WooCommerce, updating customer order status and triggering shipping notifications.
Returns and refund coordination: Return authorisations initiated in WooCommerce or at the warehouse are tracked through OMS and ERP
Refund status and any associated credit notes flow back to WooCommerce to close the return cycle and manage customer expectations.
08 · How we build it

How iWeb configures the integration around your business.

Same method on every integration. The decisions come before the code.

  1. 01
    Multi-channel stock and allocation

    We design OMS and ERP integration patterns that treat WooCommerce inventory as part of a shared pool. Reserved stock, backorders and channel-priority rules are enforced consistently, preventing oversell and manual stock fixes.

  2. 02
    Order ingestion and routing

    We build connectors that pull orders from WooCommerce into OMS with full context and route them to the right fulfillment node. Order acknowledgement flows back to WooCommerce to show customers realistic delivery status.

  3. 03
    Catalogue and pricing feeds

    We create data pipelines from PIM or ERP to WooCommerce that keep products, variants, descriptions, images and pricing in sync. Channel-specific pricing, promotions and availability are applied at publish time without manual intervention.

  4. 04
    Despatch and tracking return

    We integrate WooCommerce with WMS and 3PL systems so that dispatch confirmations and carrier tracking flow back automatically. Customers receive shipment notifications and can track parcels without manual data entry at the warehouse.

  5. 05
    Exception handling and observability

    We deploy monitoring, alerting and dead-letter queues so that order, stock and sync failures are visible to the operations team. Fallback rules ensure that failures in WooCommerce do not break fulfilment or inventory control in other channels.

09 · Ownership

Who owns what.

The single most important table in any integration. One system owns each field; everything else reads it.

Data
Source / owner
Maintained by
Notes
DataChannel-specific listing data
Source / ownerPIM
Maintained byMerchandising team
NotesProduct attributes, descriptions and images originate in PIM; WooCommerce receives published snapshots on a cadence, not real-time bidirectional sync.
DataChannel pricing and promotions
Source / ownerERP or price book
Maintained byPricing team
NotesBase and channel-specific prices are calculated centrally and pushed to WooCommerce; WooCommerce does not update the source price book.
DataChannel stock and allocation
Source / ownerOMS or ERP
Maintained byInventory and OMS team
NotesAvailable-to-sell stock is calculated across all channels in OMS or ERP; WooCommerce receives allocated inventory, not absolute stock.
DataOrders from WooCommerce
Source / ownerOMS or ERP
Maintained byOperations team
NotesOrders are captured in WooCommerce and transmitted to OMS or ERP; the channel is the source, but the operational system is the record.
DataOrder status and tracking
Source / ownerOMS or WMS
Maintained byFulfillment team
NotesDispatch, tracking and returns events originate in WMS or 3PL and flow back to WooCommerce; WooCommerce is not the source of fulfillment truth.
DataDespatch and returns
Source / ownerWMS or OMS
Maintained byWarehouse and customer service
NotesReturn authorisations and despatch confirmations flow from WMS or OMS back to WooCommerce; WooCommerce queues the request but does not execute it.
10 · Experienced integrator

Built this before

iWeb has integrated WooCommerce into multi-channel estates alongside OMS, ERP and fulfillment systems. We understand how to keep WooCommerce stock and orders aligned with other sales channels without siloed data or manual handoffs.

We design stock-allocation logic so WooCommerce never oversells inventory reserved for stores or other channels.
We build order-routing patterns that send WooCommerce orders into OMS with full context and return acknowledgement and status without delay.
We connect WooCommerce to PIM for catalogue and image sync, and to price books for channel-specific pricing rules.
We integrate WMS and 3PL despatch events so tracking reaches WooCommerce customers automatically and returns flow back to the warehouse.
We deploy monitoring and exception handling so sync failures, stuck orders and inventory drift are visible and actioned by the right team.
11 · Before launch

What we test before launch.

Every one of these is rehearsed before a customer ever sees the integration.

Verify that stock reserved for one order on WooCommerce is not oversold to another channel by attempting simultaneous purchases across storefronts.
Confirm that a failed order ingestion from WooCommerce is queued and alerted to operations, not silently dropped.
Test that a product price change in PIM is published to WooCommerce within the SLA and matches the ERP invoice price.
Validate that a dispatch confirmation and tracking number from the warehouse appear in the WooCommerce customer account within 2 hours of shipment.
Ensure that a return authorisation created on WooCommerce generates an RMA and reaches the warehouse without manual intervention.
Confirm that if OMS is unavailable, WooCommerce shows a clear message to customers or queues orders for manual review, rather than overselling.
Run a reconciliation report comparing WooCommerce inventory to OMS allocation and confirm discrepancies are identified and flagged for investigation.
12 · Failure points

Common risks and where they bite.

We name these on day one. A risk written down is a risk you can plan around.

Oversell across channels

If stock is not allocated through OMS, the same inventory unit can be sold on WooCommerce and another channel simultaneously. Reconciliation after the fact causes fulfillment delays, oversold notifications and customer refunds.

Orders stuck between systems

WooCommerce orders may not be routed to OMS or ERP if the connector fails silently or the order status is not polled regularly. The customer sees no acknowledgement, and the warehouse does not know the order exists.

Stale catalogue and pricing

If PIM or ERP updates are batched or delayed, WooCommerce may show outdated product descriptions, images or prices. Customers see prices that do not match the invoice, or images that do not match the product shipped.

Tracking and returns go missing

If WMS despatch events do not flow back to WooCommerce, customers see no tracking number and assume the order is lost. Returns initiated on WooCommerce may not reach the warehouse if OMS does not have a reverse flow.

Silent sync failures

WooCommerce does not natively alert when inventory syncs fail, orders are rejected or customer account data cannot be reconciled. Days later, stock counts diverge or orders are lost without anyone noticing.

Channel-specific rules ignored

If the integration does not account for WooCommerce-specific tax rules, shipping zones or promotional rules, published prices and shipping costs will not match the customer's final invoice. Refunds become complex and operations teams spend time on manual corrections.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about WooCommerce integrations.

How do we prevent overselling the same product across WooCommerce and our physical stores?

An OMS or shared inventory system allocates available-to-sell stock across all channels based on defined rules, e.g. reserve 30% for stores, 70% for online, or allocate by location. WooCommerce receives only its allocation and cannot sell beyond it. Stock reservations for pending orders are held in the OMS until order is confirmed or cancelled.

What happens if an order is placed on WooCommerce but the order ingestion fails?

The integration should monitor inbound order flows and queue failed orders for investigation. Dead-letter handling, retry logic and alerting to operations ensure that missing orders are caught within minutes, not days. A fallback such as email notification to operations can prevent silent losses.

Can we publish WooCommerce-specific prices that differ from other sales channels?

Yes. If a PIM or price book supports channel-specific pricing rules, the integration can apply WooCommerce margin adjustments, promotional discounts or currency conversions at publish time. The source system holds the rules; WooCommerce receives the result and cannot override it.

How do we get tracking and despatch updates from the warehouse back to WooCommerce customers?

A WMS or 3PL integration feeds dispatch confirmations, tracking numbers and proof-of-delivery events into OMS, which routes them back to WooCommerce via API or webhook. WooCommerce updates the order status and automatically sends shipping notifications to the customer.

What happens if a customer initiates a return on WooCommerce but the warehouse never receives the RMA?

The integration should flow return authorisations from WooCommerce into OMS, which generates RMA numbers and alerts the warehouse. If the warehouse does not receive the RMA, alert monitoring will flag it. A fallback is email to customer service to manually follow up.

How often should product data sync from PIM to WooCommerce?

Depends on business need. High-velocity fashion may sync every hour; stable SKUs may sync daily. The integration should support scheduled batch syncs, event-driven updates (e.g. when a product is approved in PIM) and manual trigger. A delta-detection mechanism sends only changed products to minimize load.

Can WooCommerce customers see their order history and account details if they also shop in stores?

Only if customer identity is resolved across channels. The integration must link WooCommerce customer records to ERP or CRM accounts using email, phone or an explicit account link. Order history and trade-account pricing are then pulled from the central system.

What if WooCommerce pricing is out of step with the invoice that ERP generates?

A tax or currency calculation error between the PIM / price-book feed and WooCommerce will cause mismatches. The integration should validate that WooCommerce prices match the source before publish, and alert if rounding or tax treatment diverges. Post-launch, reconciliation reports flag price-mismatch refunds.

How do we handle WooCommerce orders that need to be split between a warehouse and a dropship supplier?

OMS applies routing rules to each line based on inventory availability, margin or business priority. One order generates two fulfillment instructions (one to the warehouse, one to the dropship supplier) and both are tracked back through OMS to WooCommerce. Customer sees a single order with multiple shipment events.

What monitoring tells us that WooCommerce inventory is drifting out of sync with ERP?

The integration should include scheduled reconciliation reports that compare WooCommerce stock levels against the OMS or ERP allocation. Discrepancies above a tolerance trigger alerts and a queue for investigation. Root causes include unacknowledged orders, manual WooCommerce stock edits, or failed syncs.

If ERP or OMS is down, can WooCommerce still accept orders?

Yes, WooCommerce can accept orders and queue them locally. However, stock checks may be stale, pricing may not reflect live promotions, and orders will not flow to fulfillment until the operational system is back up. A clear fallback policy (e.g. pause checkouts, show warning, or accept orders with manual review) prevents oversell or customer disappointment.

How do we know which team owns the data if WooCommerce, PIM, OMS and ERP all touch the same product or order?

A clear ownership map assigns responsibility: PIM owns product content and taxonomy; ERP or price book owns pricing; OMS owns order routing and status; WooCommerce owns storefront display and customer interaction. Each team knows what they maintain and what they consume from upstream. Handoff points are documented and monitored.

Can we test new products or promotions on WooCommerce without affecting other channels?

If the integration supports channel-specific test flags or draft status, products can be published to a WooCommerce staging environment without syncing to production channels. Once approved, the integration stages the product to all channels. Without staging support, testing must happen in an isolated WooCommerce instance.

What happens to WooCommerce refunds if the customer paid with a saved card or digital wallet?

The integration must route refund requests to the payment processor via OMS or ERP. Refund confirmation is sent back to WooCommerce to update order status and close the loop. If the payment processor is offline, the refund is queued and retried; WooCommerce shows 'pending refund' until it succeeds.

Next step

Have a WooCommerce integration brief?

Send the brief, or tell us what is breaking. You will get a written response from a senior expert: the integration boundary, the realistic shape, the risks worth naming, and what it takes to support after launch.
Talk to an expertOr browse all integrations →