WMS Requirements Checklist for Ecommerce Sellers

In 2026, the hardest part of choosing an ecommerce WMS is not finding software. It is separating warehouse tools that look impressive in a demo from systems that can survive real marketplace operations. Capterra lists 844 warehouse management products in its 2026 category, while Sendcloud’s WMS guide says sellers often start evaluating WMS Lite once they pass roughly 50 orders per day or run more than one fulfillment location.

That creates a practical problem for online sellers: the shortlist is too broad, and most articles describe WMS features as if every warehouse behaves like a distributor. Ecommerce warehouses behave differently. They need to import orders continuously, reserve stock across channels, support barcode-driven pick and pack, print labels fast, handle returns, and update marketplaces before customer-service tickets start.

This checklist is written for sellers that ship from their own warehouse, use a 3PL for part of the flow, or are moving from Shopify, WooCommerce, bol.com, Amazon, Zalando, OTTO, Kaufland, Temu or TikTok Shop into a more controlled warehouse setup. Use it before you sign a WMS contract, before you migrate SKU data and before you train pickers on a workflow that may not match your actual order mix.

1. Start with ecommerce order reality, not warehouse theory

Generic WMS requirements usually begin with receiving, storage, picking, packing and shipping. Those are correct, but online sellers should start one layer earlier: where do orders originate and what promise has each channel already made to the customer?

A bol.com order, Amazon order, Shopify order and B2B order can all land in the warehouse as “pick one unit”, but they carry different stock rules, cut-off times, label expectations and customer-message requirements. If your WMS treats them as identical, the warehouse may look efficient while marketplace performance suffers.

Build the first requirement table around order sources: webshops, marketplaces, manual orders, POS, B2B portal, backorders, pre-orders and 3PL-routed orders. Then mark which system is allowed to change stock. For many sellers, ChannelDock integrations become the control layer between sales channels, carriers and the WMS, so the warehouse tool can focus on execution instead of custom channel plumbing.

2. Require one inventory truth across WMS and sales channels

Real-time inventory tracking is listed in almost every WMS buyer guide. Ecommerce sellers need a stricter version: the WMS count, the sellable count and the marketplace-published count must be explainable from the same stock ledger. Otherwise a warehouse can be physically accurate and commercially wrong.

The requirement should cover available stock, reserved stock, damaged stock, returned-but-not-inspected stock, inbound stock, bundle components and location-specific stock. If Amazon receives 8 units, bol.com receives 6 and Shopify receives 10, your team must know which buffer or reservation rule created the difference.

ChannelDock’s inventory feature overview is useful here because stock sync is not just a product count. It is a policy layer: which channel receives which quantity, how quickly updates are sent, how oversell risk is reduced and how exceptions are surfaced before they become penalties.

3. Test barcode picking with imperfect SKUs

Barcode support is not a checkbox. A WMS can “support barcode scanning” and still fail in the workflows that matter: duplicate barcodes, supplier EANs that differ from marketplace identifiers, FNSKU labels for Amazon stock, bundles, missing barcodes, size variants, refurbished items and products that return without their original packaging.

The test is simple: pick 20 awkward orders from the last 30 days and ask each WMS vendor to process them in a demo or pilot. Include a single-line order, a multi-line order, a bundle, a return, a product with a supplier barcode, a product without a barcode and an order that needs a different carrier than usual. The outcome should show whether the picker receives clear instructions and whether the packer can verify the shipment before the label prints.

1. 1
   Map the order sources before the warehouse tour

   List every webshop, marketplace, manual order source, POS and B2B flow. A WMS demo that only shows Shopify is incomplete if your warehouse also ships bol.com, Amazon, Kaufland or wholesale orders.
2. 2
   Define the inventory promise per channel

   Document whether each channel receives available stock, buffered stock, reserved stock or warehouse-specific stock. This prevents the WMS from becoming accurate internally while marketplaces still oversell externally.
3. 3
   Run a barcode pick-pack scenario with awkward SKUs

   Include bundles, duplicate EANs, missing barcodes, size variants, fragile items and returned products. Clean demo SKUs hide the exceptions that create warehouse errors.
4. 4
   Test labels, tracking and marketplace updates in one flow

   The order is not finished when it is packed. The WMS must hand shipping data to carriers and send the correct tracking status back to every sales channel.
5. 5
   Score go-live work, not only monthly price

   Include data cleanup, bin labels, scanner setup, staff training, integration mapping and rollback planning. A cheap subscription can become expensive if implementation depends on custom work.

For sellers that are still formalising warehouse work, ChannelDock’s pick & pack workflow page shows the operational pattern to look for: order queue, barcode validation, packing confirmation, shipping handoff and audit trail.

4. Put shipping labels and tracking inside the WMS test

Many WMS evaluations stop at “order packed”. Ecommerce operations stop later: label printed, tracking created, marketplace updated, customer notified, carrier manifest closed and exception visible if any of those steps fails. This is where warehouse software, carrier software and marketplace connectors often overlap.

Require a live label scenario in the pilot. Test at least two carriers, one international shipment, one order above a weight threshold, one parcel-shop flow and one order that should be held because the address or stock is wrong. The WMS does not need to own every carrier contract, but it does need to pass clean shipment data into the label system and receive enough status back to keep the order queue honest.

If the WMS is strong in scanning but weak in carrier routing, connect it to ChannelDock’s orders workflow and shipping integrations rather than forcing warehouse users to copy tracking numbers manually.

5. Score implementation work before you score price

WMS price pages rarely show the full cost of adoption. Capterra’s buying guidance calls out often-overlooked costs such as data migration, training, hardware, IT, maintenance and upgrades. For ecommerce sellers, add SKU cleanup, marketplace mapping, bin labels, scanner configuration, packing station layout, carrier templates, return reasons and staff training during peak order hours.

A good WMS requirements checklist therefore has two scores: monthly software cost and go-live workload. A “cheaper” WMS that needs custom marketplace connectors, consultant-only configuration and a three-month migration may be more expensive than a cloud WMS with fewer knobs but a clean integration path.

Do not let the pilot become a software tour. Set the success criteria before the first demo and reuse the same scenarios for every vendor. That is the only way to compare a WMS built for enterprise distribution, a Shopify-focused WMS, an ERP/Warenwirtschaft add-on and an ecommerce operations platform fairly.

6. Decide where ChannelDock fits in the architecture

The right WMS architecture is rarely “one tool does everything”. Online sellers usually need a warehouse execution layer, a channel integration layer, carrier handoffs, inventory policy and reporting. ChannelDock is strongest when the WMS or ERP should not be burdened with every marketplace and carrier edge case.

For example, a seller might keep a warehouse-focused WMS for bin locations, scanners and pick paths, while ChannelDock handles marketplace order intake, stock synchronisation, carrier labels, tracking updates and operational dashboards. Another seller might use ChannelDock as the first WMS until order volume justifies a specialised warehouse system. The requirement is the same in both cases: no manual re-keying between systems.

FAQ

Conclusion

An ecommerce WMS requirements checklist should not be a generic feature inventory. It should be a proof script for the exact warehouse promises your channels make every day: available stock, accurate picking, fast labels, clean tracking, visible exceptions and controlled returns.

If a WMS passes those tests, price and interface become easier to compare. If it fails them, more dashboards will not fix the operational gap. Start with real orders, test the messy SKU cases and make sure every system in the stack — WMS, ChannelDock, carriers, marketplaces and ERP — agrees on what happened to the order.