The 3PL operations stack: every module a multi-client warehouse actually needs

A 3PL is a different shape of warehouse from a single-tenant brand operation.

Three clients in one bay, four billing models, six carriers, and one team trying to keep them straight.

Here is the module-by-module stack a 3PL actually runs on: what each one does and where to start.

Why 3PL is different

A brand warehouse runs one set of SKUs for one set of customers.

A 3PL runs many sets of SKUs, often in the same physical bays, for many clients with different SLAs, different carriers, different billing rules, and different visibility expectations.

Every module choice has to handle "whose stock is this" as a first-class concern, not an afterthought.

The minimum viable 3PL stack

Four modules. The smallest stack a real 3PL can run on.

Order Management

Multi-client order capture. Each client's orders flow into a shared queue but stay tagged with the client's storage account.

• Capture orders by client from EDI, API push, or manual entry
• Generate pick tasks that respect the client's SKU pool
• Customer (end-recipient) records sit under the client account for service

See /modules/order-management.

Inventory Management

Multi-tenant by design. Stock is owned by the client, not by the warehouse.

• Bin assignments can be mixed-client (with segregation rules) or dedicated-client (full bays per client)
• Available, allocated, and on-order tracked per client per SKU
• Bin-level, batch-level, and serial-level so a recall scope is "this client, this batch" not "all stock that looks similar"

See /modules/inventory-management.

Receiving/Inbound

Inbound by client. Every receipt knows whose stock it just took in.

• ASN per client; putaway suggestions respect dedicated vs shared bay rules
• Damage and short-receipt captured against the client so storage claims are clean
• Supplier records sit under the client account, not under the warehouse

See /modules/receiving-inbound.

Shipping/Outbound

Multi-carrier dispatch. The client's carrier rules decide rate selection, the rest happens in one queue.

• Client's contracted carrier and service tier carry through to label generation
• Mixed-client dispatch waves are fine; manifest per carrier per day
• Tracking events flow back to the client's order, not to the warehouse's order

See /modules/shipping-outbound.

The modules a real 3PL adds within six months

Past a few hundred outbound orders a day, the minimum stack starts breaking. Add these:

• Cycle Counting (/modules/cycle-counting): accuracy per client is now a contractual KPI, not a hope.
• Wave Picking (/modules/wave-picking): high-volume order arrival turns into a steady, plannable flow per carrier cut-off.
• Returns Management (/modules/returns-management): RMA, inspection, grading, and restock decisions by client.
• Business Rules Engine (/modules/business-rules-engine): encode the "client A wants double-pack confirmation, client B does not" rules without a developer.
• Dashboards & Reporting (/modules/dashboards-reporting): per-client KPI views you can hand the client a login to. This is how 3PLs win renewal conversations.

What a 3PL can defer (and what they cannot)

Honest gaps:

• Slotting Optimization helps but is not urgent until you have stable enough volume per client to justify the layout work.
• Production/Manufacturing module is irrelevant unless the 3PL does light value-added services (kitting, assembly) at scale.
• Finance & Accounting module is usually deferred. Most 3PLs invoice through Xero or MYOB and add the WMS-side financial tracking later.
• What you cannot defer: per-client billing rules. If your WMS cannot generate accurate per-client storage and handling invoices, you will lose margin on every contract within twelve months.

Where each kind of system wins

• Best 3PL platform for very high volume with deep WMS-only depth: a Tier-1 WMS like Manhattan or Blue Yonder. Six-figure setup, twelve-month implementations.
• Best 3PL platform for ANZ SMB volume with a modular stack: this kind of layered approach, start with four modules, add as the client list grows.
• Best 3PL approach for under three clients: a single inventory-led system like Cin7 might be enough. See /blog/3pl-software-anz for the wider buyer view.

The starting line

Pick four clients. Two with similar carrier profiles, two with very different ones.

Run them through Order, Inventory, Receiving, Shipping for one full peak month.

The gaps you find are the modules to add next: usually Cycle Counting, then Business Rules, then Dashboards.

The point of the modular stack is that the next module is a switch-on, not a re-platform.