Brands searching for warehouse management software in Canada usually fall into one of two groups, and the two need opposite answers. If you operate your own warehouse, you are shopping for a WMS and the question is which one to license. If you use a third-party logistics provider, you are not shopping for anything. Your 3PL already owns that decision, made it before you arrived, and their choice quietly sets your inventory accuracy, your order sync latency, your ability to ship retail purchase orders, and whether your invoice can be audited.
This guide is for the second group. It covers what Canadian 3PLs actually run, what each tier can and cannot do, and the specific questions that reveal a system’s real capability during a site visit. If you are earlier in the process, the guide to choosing a 3PL in Canada covers the broader evaluation and this post covers the systems half of it.
The Software Layers, and Which One Is Yours
“Fulfillment software” is not one thing, and confusing the layers is why these conversations go sideways. Four distinct systems are usually in play.
The WMS runs the building. Receiving, put-away, bin locations, wave and batch picking, packing, cycle counting, and the activity capture that produces your bill. This is the 3PL’s system, on the 3PL’s licence, configured for their operation. You will never log into it as an administrator, though most modern platforms give clients a read-only portal.
The OMS runs your orders. Order management sits on your side and consolidates demand from every channel before it reaches the warehouse. If you sell on one storefront, your e-commerce platform is your OMS and you do not need another. Once you have a website, two marketplaces and wholesale POs, the consolidation problem becomes real. This is the layer most brands are actually shopping for when they search for fulfillment software.
The inventory record is a question of authority, not a product. Somewhere there has to be one system whose count is the truth. Usually it is the 3PL’s WMS, because that is where physical reality is measured. Problems start when a brand also treats its own platform as authoritative and the two drift.
The integration layer connects them. Native connectors, a middleware service, or a custom API build. This is where most day-to-day pain lives, and it is worth more attention than the WMS brand name.
The practical consequence: a brand on a 3PL should spend its software budget on the OMS and integration layers, and spend its diligence on the 3PL’s WMS rather than trying to influence it.
What Canadian 3PLs Run, by Tier
Operator size predicts capability better than geography does. Canadian 3PLs sit in roughly four bands.
Tier-one enterprise platforms. Manhattan Associates, Blue Yonder, Korber. These run at national and multinational operators handling high-volume, high-complexity work: large retail DC flows, deep labour management, sophisticated slotting and wave optimization. If your operator runs one of these, capability is not your risk. Configuration cost and change-request lead times are. Getting a custom workflow built into a tier-one deployment is a project, not a favour.
Cloud multi-client platforms built for 3PLs. This is where most Canadian mid-market operators sit. Extensiv, formerly 3PL Central, is the platform you will encounter most often, alongside Deposco, Da Vinci, Infoplus, Logiwa, ShipHero and Snapfulfil. These are purpose-built for the third-party model, which matters more than it sounds: multi-client architecture, per-client rate cards, activity-based billing, and a library of pre-built e-commerce and marketplace connectors. For a brand shipping DTC and marketplace volume in Canada, this tier is usually the sweet spot.
Proprietary in-house systems. Some established operators, particularly on the B2B and contract-logistics side, run software they wrote themselves. This is not automatically a warning sign. A twenty-year-old in-house system at an operator who ships the same freight profile every day can be excellent, tuned precisely to their work. The risk is narrower: integration options are whatever they have built, new connectors take real development time, and if the person who wrote it retires you inherit that problem. Ask what their integration roadmap looks like and how long the last new connector took.
ERP modules and spreadsheets. At the small end, some operators run a warehouse module inside an accounting or ERP package, with spreadsheets covering what it does not do. Occasionally this is fine for straight pallet-in, pallet-out storage where nothing needs to sync anywhere. For e-commerce fulfillment it is not, because there is no reliable path to real-time inventory sync, and you will find out during your first peak.
None of this makes a platform name a proxy for service quality. A disciplined operator on a mid-tier platform will outperform a sloppy one on Manhattan every time. The tier tells you what is possible, and the operator tells you what actually happens.
What the WMS Decides for You
Five things, concretely.
Inventory accuracy. Scan enforcement is the single biggest factor. A system that requires a barcode scan on every movement and refuses keyboard overrides on put-away and replenishment will hold accuracy. One that allows a keyed override will drift, because someone will always be in a hurry. Count-by-exception, where any bin that hits zero is counted immediately, is close to free and self-scheduling, and its presence tells you the operator thinks about this properly.
Sync latency. Real-time API push versus scheduled batch. Modern cloud platforms push inventory and order status within seconds to a few minutes. Batch integrations run every 15 to 60 minutes, and older setups sync a handful of times a day. During normal trading the difference is invisible. During a promotion or at low stock it is the difference between a clean sell-through and a queue of oversell cancellations.
Order edit behaviour. An underrated question. A customer changes their address or adds an item after the order has imported to the WMS. Does the change flow through, does it fail silently, or does the order have to be cancelled and rebuilt? Ask this specifically. The answer varies enormously between platforms and it is a daily occurrence, not an edge case.
Lot, serial, and expiry control. Mandatory for food, beverage, supplements, cosmetics and anything regulated. FEFO picking, lot-level traceability, and the ability to run a recall query and get a customer list are WMS capabilities, and not every platform has them configured even when it supports them. If you have expiry-dated stock, ask them to run a mock recall in front of you. The food and beverage fulfillment guide covers what else changes for regulated product.
Billing detail. Activity-based billing is a WMS function. A system capturing every receipt, pick, pack, storage position and value-added touch can produce an invoice you can reconcile line by line against your rate card. A system that cannot will give you summary charges nobody can audit. The most common billing disputes are not overcharging, they are definitional: additional-unit picks billed at first-unit rates, storage billed on peak positions rather than average, receiving billed hourly against a per-pallet quote. An itemized invoice from a capable system makes those visible in month one instead of month nine.
EDI and Retail Orders
If you ship to Canadian retailers, this is the capability that separates operators, and it is frequently oversold. Shipping a compliant purchase order requires EDI transaction sets including the 856 advance ship notice, GS1-128 carton and pallet labelling, and adherence to each retailer’s routing guide and appointment windows. Miss any of it and the chargeback lands on someone.
Three questions settle it. Is EDI native to your WMS or brokered through a third-party provider, and if brokered, who owns that relationship? Which Canadian retailers are you currently trading with, by name? What was your chargeback rate last year, and who absorbed it? An operator who ships retail volume answers all three immediately. One who says the system “supports EDI” and cannot name a trading partner is describing a capability they have not used. The retail compliance and chargebacks guide covers how that liability gets allocated in the contract, which is the part worth settling before your first PO rather than after.
The Questions to Ask on a Site Visit
Software demos are designed to look good. These questions are harder to stage.
- What percentage of inventory movements are barcode-scanned rather than keyed, and can the system be overridden on put-away?
- What is the actual inventory sync interval to my platform, in minutes, and is it push or scheduled?
- What happens to an order that is edited after it imports?
- Show me a sample itemized invoice for a client with a similar profile, with the client details removed.
- What is your storage billing basis: average positions held, peak positions, or a month-end snapshot?
- Run a mock recall on a lot number and show me the output. (Only if you have lot-controlled stock.)
- What was your last cycle-count variance, and how do you review negative adjustments?
- Which integrations are native versus custom-built, and how long did the last new one take?
Ask to watch a pick on the floor rather than on a screen. Whether the picker scans every location or keys past the prompts tells you more in thirty seconds than the demo will in an hour.
When the WMS Should Change Your Decision
Rarely on its own. Systems capability is a filter, not a ranking. Use it to eliminate operators who cannot do what you need, then choose among the survivors on service, location, rates and cultural fit.
The cases where it genuinely decides:
- You need real-time sync and they run batch. If you sell on marketplaces where account health depends on shipment timing, or you run frequent promotions on limited stock, a multi-hour sync gap is a structural problem you cannot manage around.
- You have lot or expiry control and they do not. Not negotiable for regulated product. There is no workaround.
- You are shipping retail POs and their EDI is theoretical. Learning on your account is expensive, and you pay the chargebacks during the learning.
- Their billing cannot itemize. You will not be able to verify you are being charged what you agreed to, for the life of the contract.
Everything else is a preference. A brand shipping straightforward DTC parcel volume from a single Canadian facility has more good options than it thinks, and the operator’s discipline will matter more than the logo on their login screen. If you are already with a 3PL and the systems side is what is failing, the guide to switching 3PL providers covers how to run a migration without losing inventory accuracy in the handover.
Getting a Straight Answer
Most brands never ask these questions, which is why operators are rarely ready for them. The eight above take about twenty minutes and will tell you more about a 3PL than a rate card will.
Warehouse Bridge maintains systems detail on the operators in our Canadian network, including WMS platform, integration capability and EDI trading history, because it is one of the first filters that matters and one of the hardest to research from outside. If you want a shortlist filtered on systems capability rather than rate alone, tell us what you need and we will come back with operators that actually clear the bar.