The modules of a 3PL WMS and what each one hands over

A 3PL WMS is a set of modules that work like a relay: client accounts, inbound, putaway and locations, inventory, order management, picking, packing and shipping, returns, billing events and client access. When a vendor says their system has "modules", they might mean a clearly separate set of screens and rules, or a menu item. This page gives you a way to tell the difference. For each module we list what it takes in, what it hands to the next one, and the one question that exposes a weak version.

Module names vary between products. The jobs do not.

The map at a glance

Read the table left to right as a relay. If one runner drops the baton, the next cannot run.

Client accounts: the 3PL-specific base

In a single-owner warehouse, there is one owner. In a 3PL, every record belongs to a client, and the rules differ per client. This module holds each client's details, their special instructions, their rate card and their login.

It hands over one thing: a client identity that rides along on every later record.

Weak version: the client is just a text field on the item. Question to ask: can I give two clients the same item code and keep their stock apart?

Inbound

This module expects shipments, checks them in, compares counts to the notice and records exceptions. It hands over stock waiting for a location, with a client, a time stamp and any notes.

Weak version: receiving is just "add stock". Question: show me a delivery that does not match its notice.

Putaway and locations

Locations are the map of your building: aisles, racks, bins, floor spots, dock areas. Putaway decides where received stock goes, by rule or by choice, and confirms it by scan.

It hands over a known place for every unit.

Weak version: locations are a plain text note. Question: what happens if two people put different items in the same bin?

Inventory

This is the ledger. Every movement (receive, move, pick, adjust, ship, return) writes a line. On hand, allocated and available quantities are derived from those lines.

It hands over a figure everyone can trust. Counting routines such as cycle counts live here too.

Weak version: you can edit the quantity directly. Question: can I see the history of every change to this number, with who and why?

Order management

Orders arrive from stores, files or typed entries. The module checks stock, reserves it, applies the client's rules (carrier, packing instructions, ship by date) and releases work to the floor.

Hands over reserved stock and a list of tasks.

Weak version: orders are only a pick list printout. Question: what happens to an order for stock we do not have?

Picking

Tasks go to people with handhelds or lists. The module can run single-order picks, batches or zones. It confirms by scan and captures short picks.

Hands over picked items tied to the right orders.

Weak version: the picker confirms a whole list at once. Question: show me a short pick and where the shortage is recorded.

Packing and shipping

At the pack station, items are verified against the order, a carton is chosen, and a label is made. Shipping closes out the day's loads and sends tracking back.

Hands over parcels or pallets that have left, tracking numbers and a closed order.

Weak version: labels are made in a separate carrier tool and keyed in later. Question: where does the tracking number get recorded, and how does it reach the client?

Returns

Returned goods are authorised, received, inspected and sent to stock, rework or disposal.

Hands over restocked units, or a record of what happened to them.

Weak version: a return is treated like a new receipt with no link to the original order. Question: can I trace this return to the order it came from?

Billing events

This module watches the others and writes a line each time something billable happens. It then applies the client's rate card. In some systems it also produces the invoice; in others it exports data to accounting.

Hands over charges per client for a period.

Weak version: billing is a monthly spreadsheet export. Question: which events are captured automatically and which must I add by hand?

Client access

A secure view for the client: their stock, inbound and outbound orders, documents and invoices. It should only show what that client owns.

Hands over fewer emails and phone calls.

Weak version: one shared login. Question: show me what a second client sees when logged in.

What you can skip at the start

You do not need every module on day one. A small 3PL might begin with client accounts, inbound, locations, inventory, orders, picking, packing and basic billing events, and add client access and returns later. What you cannot skip is the client identity, because it is very hard to add after the fact.

Checking a vendor's module claims

Ask for the same demonstration for each module: take one item through that module and show me what it wrote to the ledger. If the answer is "that happens in another tool", ask what you need to key in by hand.

Also ask what a module costs. Some products price by module, some by volume or users, and a custom build is scoped by what you ask for. A one-time custom build, no per-seat, per-truck or per-client fees is one structure to put next to subscription plans, because you choose the modules you need up front.

Questions people ask

What modules does a 3PL WMS have?

Client accounts, inbound, putaway and locations, inventory, order management, picking, packing and shipping, returns, billing events and client access. Names vary between products, but the jobs do not.

Which module matters most in a 3PL WMS?

Inventory by client. Every other module rests on it.

What can a small 3PL skip at the start?

It might begin with client accounts, inbound, locations, inventory, orders, picking, packing and basic billing events, and add client access and returns later. The client identity cannot be skipped because it is very hard to add after the fact.

How do I check a vendor's WMS module claims?

Ask for the same demonstration for each module: take one item through it and show what it wrote to the ledger. If the answer is that it happens in another tool, ask what you would need to key in by hand.

Can I mix WMS modules from different vendors?

You can, but each join needs an integration, and more joins mean more places where data gets out of step.

Is a WMS module the same as an add-on?

Sometimes. Find out whether a module is included, extra or built by a partner.