3PL buyer guide
A 3PL WMS must separate clients without fragmenting the floor.
The hard requirement is not another client filter. Inventory, orders, users, pricing, proof, and exports must stay client-scoped while people, docks, storage, automation, carriers, and finance remain operable as shared capacity.
Five buying tests
Test the boundary below the dashboard.
Direct identifier denial
Use a valid client A session against client B inventory, order, quote, wallet, user, invoice, and export identifiers. UI filtering is not sufficient.
Ownership at every movement
Receive, hold, reserve, count, move, pick, pack, return, and adjust without losing client, product, lot, handling-unit, or evidence context.
Share resources explicitly
Coordinate people, docks, bins, lanes, stations, robots, and carriers without blending inventory ownership or creating a second commander.
Trace work to bill
Retain service, quantity, tariff, source operation, review, invoice, payment, dispute, settlement, and margin rather than reconstructing month-end.
Portfolio operation
One console, explicit customer scope.
Operators work across the portfolio they are authorized to serve. Client users operate their own catalog, inbound, inventory, orders, shipping, funding, returns, and analytics without entering warehouse controls.
- Client-specific workflows, service plans, channels, packaging, rates, and notifications.
- Shared labour, docks, storage, equipment, and exception queues.
- Audited support, impersonation, role, module, and warehouse boundaries.
Implementation checklist
Price the operating model, not only warehouse users.
Client setup and migration
Entities, products, balances, open orders, rate cards, users, integrations, test evidence, cutover, and rollback.
SLA and exception ownership
Promise, measurement source, breach rule, work queue, notification, evidence, dispute, and commercial consequence.
Verifiable tenant takeout
Contracted datasets, schemas, row counts, checksums, audited download, import rehearsal, retention, and deletion.
Decision questions
Ask these before shortlisting a 3PL WMS.
Can clients have different workflows without separate deployments?
Require configuration and versioning evidence for client-specific service, channel, packaging, rate, notification, and approval rules.
Can shared resources be planned without exposing another client?
Inspect the resource model, reservation, operator authorization, work assignment, analytics aggregation, and drill-down denial.
Can every invoice line be traced to operational work?
Demand source entity, event, quantity, rate, reviewer, adjustment, document, and settlement evidence for representative charges.
Can one client leave without a platform-wide export?
Run a tenant takeout and independent import test before contract signature.