Connecting your webshop to a 3PL: how Shopify and WooCommerce integrations work

Why the integration matters

In ecommerce the pace is high and many small steps must work together. If orders have to be moved manually between systems, or information gets lost, the flow becomes vulnerable. A good integration gives:

• less manual work and fewer errors in order handling
• a faster path from purchase to delivery
• better control of stock and order status
• a scalable foundation – what is manageable by hand at low volumes quickly becomes a brake as you grow

The integration is not only about getting the order into the warehouse, but also about following what happens afterwards.

What the integration does

It connects your sales channel to the logistics partner's WMS. Ongoing WMS, which we use, has documented integrations for Shopify and WooCommerce: it can fetch or receive information from the webshop and report relevant stock and delivery events back. Exactly what works depends on the integration version, your store configuration and which add-ons you use – so map data objects and responsibilities rather than just asking whether the platform is "supported".

Which information needs to flow

The order flow, step by step

1. The product is set up in the agreed master source and transferred to the other systems. SKUs must be unique and stable – reusing a SKU for a new product links stock and orders wrongly.
2. The customer buys. Shopify or WooCommerce records the order, payment status and delivery choice. A rule decides when the order is released to the warehouse: immediately, after payment approval or after another check.
3. The order arrives in the WMS, which validates the data and places it in the right flow. A missing address, unknown SKU or wrong shipping method must produce a clear error that someone owns.
4. The warehouse picks and packs, with scanning to confirm the right item is handled and to register status.
5. Delivery is booked. Shipping information goes to the transport solution and a label is created; tracking and delivery status are stored.
6. The webshop is updated with order status and tracking, so customer communication can start, and stock is updated according to the chosen sync logic.

Shopify and Ongoing WMS

Ongoing's documentation describes a ready-made Shopify integration that can transfer orders and synchronise items, stock and fulfillment status. Check which store settings, markets, locations and apps affect your configuration:

• decide which Shopify location corresponds to the 3PL warehouse
• map how orders across several locations are split or prioritised
• check markets, currencies and shipping codes
• test cancellation before and after picking has started
• verify how fulfillment status and tracking are shown to the customer

WooCommerce and Ongoing WMS

There is also a documented WooCommerce integration. WooCommerce stores vary more because of themes, plugins and custom fields, so a standard connector must be tested against your actual WordPress environment:

• list plugins that change orders, products, stock or checkout
• check variations and SKUs for every product variant
• decide how WooCommerce order statuses map to the WMS
• test discounts, gift cards, bundles and backorders if you use them
• plan how WordPress, WooCommerce and plugin updates are tested

Other platforms, ERPs and shipping tools are listed on our integrations page.

Common integration problems

• SKUs do not match. Different or missing SKUs mean an order line cannot be linked to the right stock item. Introduce a fixed routine for item setup and never change keys without a controlled migration.
• Shipping methods are not mapped. The name the customer sees at checkout is not always the code the warehouse or carrier needs. Keep a clear table mapping each delivery option to a warehouse and transport service.
• Orders change too late. An address change or cancellation after picking has started causes errors. Decide the status after which changes need manual contact.
• Stock differs between systems because of reservations, blocked stock, returns or several channels. Define exactly which balance is published and how often.
• Errors have no owner. An integration can work for most orders but still stop individual ones. Alerts, logs and ownership of troubleshooting must be part of operations.

Test plan before go-live

• a normal order with one item
• an order with several lines and quantities
• product variants and bundles, if used
• different shipping methods, countries and address formats
• cancellation and address change in permitted statuses
• partial delivery, backorder or out of stock, according to your setup
• delivery status and tracking back to the store
• return, restocking and updated stock
• a temporary integration error and the documented fallback routine

Responsibility after launch

Document who owns the platform, the integration, the item data and the warehouse process, and how changes are requested and tested. A new checkout app or shipping method can affect order data even if nothing has changed in the warehouse. Agree named contacts on both sides, a routine for new SKUs, shipping methods and markets, monitoring and alerts for stopped orders, testing before major platform or plugin updates, and regular checks of stock and status deviations. See onboarding for the full go-live process.