A Warehouse Management System (WMS) controls what happens inside the warehouse. It tracks where every product is stored, manages pick routes and packing, and updates stock levels in real time as items move. For ecommerce businesses that have outgrown manual processes, a WMS is the prerequisite for delivering at scale without headcount and error rates growing in proportion to volume.
When you need a WMS
Not every ecommerce business needs a standalone WMS. The tipping point varies, but many reach it somewhere between 50 and 200 orders per day. At that point, manual processes start producing too many errors and take too long during peaks. Clear signals are recurring pick errors, stock discrepancies that do not match the ERP, and an inability to scale during peak season without proportional staff increases. If you also need 3PL management with location-level tracking, a dedicated WMS is almost always the right path.
The need is determined by whether your operation knows where every item is in the warehouse at any given moment, and whether that information reaches the ecommerce platform and the customer in real time.
WMS, ERP, and OMS: who does what
The boundaries between WMS, ERP, and OMS cause frequent confusion. Your ERP owns the financial record and handles stock valuation, invoicing, and accounting. The OMS owns order orchestration and determines which warehouse should fulfil, in what order, based on defined rules. The WMS owns the physical warehouse and tracks where every pallet, shelf, and item is located, optimising pick routes to minimise time and errors.
The three systems do not need to be separate products. Norce handles parts of order orchestration natively. Shopify’s built-in inventory management covers basic scenarios. But when complexity grows with multiple warehouses, 3PL providers, or ship-from-store, a dedicated WMS justifies itself quickly.
How WMS connects to your ecommerce platform
- Shopify — integrates through the Fulfillment API, which exposes inventory and order events to external systems
- Shopware — connects via API and the plugin ecosystem. Shopware’s modular architecture makes it relatively straightforward to swap or add warehouse systems
- Norce — the WMS sits downstream from the commerce engine, which handles order routing while the WMS takes over for physical picking
- Magento / Hyvä — the WMS integration pushes data into the multi-source inventory framework, which manages stock sources and allocation
The WMS and the ecommerce platform must share a real-time view of stock status. A sync every fifteen minutes via batch job is not sufficient. Delayed inventory data leads to overselling, cancelled orders, and customer contact that costs more than the integration investment.
Cloud WMS vs. on-premise
The WMS market has shifted strongly towards cloud-based SaaS. Cloud WMS solutions like Ongoing WMS offer a lower initial investment and faster implementation. Pricing is per user and updates happen continuously without upgrade projects. On-premise WMS gives more control and may be the right choice for operations with specific security or integration requirements, but it requires more internal technical responsibility.
For most Nordic ecommerce businesses in a growth phase, cloud WMS is the starting point. The barrier to getting started is lower and the integration work against platforms and ERPs is typically better documented.
WMS and 3PL
If you use a third-party warehouse (3PL), the WMS picture changes. Many 3PL providers run their own WMS platforms and expose inventory and order data via API to your ecommerce platform. In practice, you are integrating against the 3PL’s system rather than a WMS you own.
The data flow must work the same way regardless of who owns the warehouse. The ecommerce platform needs real-time inventory from the 3PL, orders need to flow in without manual handling, and tracking information needs to reach the customer automatically. Junipeer acts as middleware and abstracts the 3PL integration from the ecommerce platform’s perspective. That makes it possible to switch 3PL providers without rebuilding the platform integration.
WMS as part of the delivery
Setting up a WMS is not a standalone project. It touches warehouse processes and layout, requires integration points against the ERP, ecommerce platform, and shipping providers like nShift or Ingrid, and requires training the warehouse team on new workflows.
The critical path in an implementation is almost always the integration, not the WMS configuration itself. Mapping data flows, defining error handling logic, and testing with real orders takes time. Expect 4–12 weeks for a cloud-based WMS implementation with standard integrations. More complex setups involving 3PL, multiple warehouses, or legacy systems take longer.
The businesses that get the most value from WMS treat it as the operational backbone of the entire fulfilment chain. It is integrated with the omnichannel strategy, fed with clean product data from PIM, and keeps stock and financial data in sync with the ERP.
