Feature lists do not separate warehouse systems. Client segregation, an exportable traceability record and honest billing do.
Key takeaways
For a small third-party logistics operation the decision is not made on the feature list, because every vendor has one. It is made on three questions: can the system keep each client’s inventory, records and paperwork properly separate; can it produce a lot-level traceability extract on demand in a form a regulator will accept; and does it capture everything you should be billing for. A system that does those three things well and nothing clever is worth more than a system with a long brochure.
The reason to lead with the regulator is that the regulator sets a deadline you cannot negotiate, and your export format is the thing that meets it or does not.
A general inventory package assumes one owner of the stock. A 3PL never has one. You need per-client stock ownership, per-client locations or logical segregation, per-client document templates, per-client user access, and reporting that a client can be given without exposing anyone else’s volumes.
Test it in the demo with a specific scenario rather than a question. Ask to see two clients’ identical SKUs in adjacent racking, a receipt posted to the wrong client and corrected, and the audit trail that correction leaves. How a system handles a mis-posted receipt tells you more than an hour of feature walkthrough.
If any of your clients store food, the Safe Food for Canadians Regulations apply to you as the storage operator, not only to them. Section 90 requires the persons it covers — including the holder of a licence to store a food and anyone sending food from one province to another, importing or exporting it — to prepare and keep documents setting out the common name of the food, a lot code or other unique identifier that enables the food to be traced, and the name and principal place of business of the person by or for whom it was manufactured, prepared, produced, stored, packaged or labelled, together with who they provided it to and when, who provided it to them and when, and the food commodities incorporated into it.
Retention is fixed: those documents must be kept for two years after the day the food was provided to another person or sold at retail, and must be accessible in Canada. “Accessible in Canada” is a live question for a cloud system whose data sits elsewhere; make it a contractual answer, not an assumption.
Then the clock. On a request from the Minister, the documents must be provided within 24 hours after receipt of the request, or a shorter period the Minister specifies if it is necessary to identify or respond to a risk of injury to human health, and if provided electronically, in a single file and in plain text that is capable of being imported into and manipulated by standard commercial software.
Read that as a system requirement, because it is one. A WMS that can only show traceability on screen, or that exports one PDF per movement, fails a recall at the point it matters. Ask every vendor to demonstrate a single-file plain-text export of one lot’s full upstream and downstream history, and time it.
If you hold imported goods before release, a different records regime attaches. Section 24 of the Customs Act is the licensing provision for operating a place as a sufferance warehouse for the examination of imported goods that have not been released, and section 40 requires licensees to keep prescribed records. The Imported Goods Records Regulations set the periods: a sufferance warehouse licensee keeps records of receipt and removal for six years after receipt into the warehouse, and a bonded warehouse licensee keeps records of goods received and removed for six years after their removal.
Six years is longer than most WMS retention defaults and longer than many contracts. If your archive policy is “two years then purge”, you have a gap. The CBSA’s carrier and warehouse programme pages are the reference point for the licensing side.
Storage by pallet or by square metre, receiving by pallet or by carton, pick and pack by line, special handling, pallet wrapping, disposal, rework, container destuffing, after-hours receiving — every one of those is a real cost, and every one of them is invisible unless the system records the event when it happens.
The test to run before signing: take last month’s invoices for your three largest clients and ask whether the candidate system would have captured each line automatically from a warehouse event, or whether someone would still be typing it from a notebook. Anything in the second category will eventually stop being billed.
Worked example: a three-client operation in Brampton
One client is a food importer, one is a consumer electronics brand, one is an industrial distributor whose goods sometimes sit before customs release. The operator is choosing between a low-cost inventory app and a mid-market WMS.
The food client alone decides it. The operation is storing food, so the section 90 documents have to exist, be kept two years, be accessible in Canada, and be producible in a single plain-text file within 24 hours of a request. The inventory app can report on hand quantities by SKU but has no lot-level chain of custody and exports one spreadsheet per report.
The electronics client adds serial-number capture at pick, which the app can fake with a note field and the WMS handles natively. The industrial client adds a six-year retention obligation on any goods held before release. The mid-market system wins not because it is better software but because two of the three clients bring an external record standard the cheaper tool cannot meet.
Three uses hold up in a small operation. Document extraction: reading inbound packing slips, bills of lading and supplier invoices into structured receipt lines, so the receiving clerk confirms rather than types. Exception detection: flagging a lot with no downstream record, a client SKU with an unexplained adjustment, or a receipt whose quantity does not match the advance notice. And drafting: assembling a client’s monthly activity summary or a first-pass recall notification from records that already exist.
The boundary is worth stating in your own procedures. These tools extract, flag and draft. A person confirms the count, approves the adjustment, decides whether a lot is affected, and signs the notice. Nothing about a recall decision, a customs declaration or a food safety determination should rest on an unreviewed model output.
First, per-client segregation with a clean audit trail. Second, lot and serial capture at receipt and at pick, with a single-file export. Third, billing events generated from warehouse activity. Fourth, integration — how your clients’ systems will send orders and receive confirmations, and whether that is an included connector or a project. Fifth, retention and data location terms in the contract, matched to the six-year and two-year obligations above. Everything else, including the mobile interface everyone demos first, ranks below those.
If you are buying or selling a warehousing or 3PL business, the same records are the diligence file. Treadstone’s sister law firm covers that transaction in its guide to buying or selling a warehousing or 3PL business, and the wider sector in its transportation and logistics business guide.
Yes, in the dimension that matters here. An accounting inventory module tracks what you own; a WMS tracks what you hold for others, where it is, in which lot, and what you did to it. A 3PL needs the second.
Section 90 reaches the holder of a licence to store a food and persons who provide food to another person, which is what a storage operator does when it ships on a client’s instruction. Take advice on your specific licence position rather than assuming ownership is the test.
The traceability documents must be accessible in Canada. Confirm with the vendor how that is satisfied and get it in the contract.
A wrong-client receipt and its correction trail; a single-lot traceability export as one plain-text file; and an invoice line generated automatically from a warehouse event.
A 30-minute call is enough to tell you whether AI pays for itself in your back office.
