Skip to main content

3PL software

3PL software, explained

Third-party logistics software is two products wearing one name: the warehouse system a 3PL runs, and the order and stock layer a brand uses when its stock sits in someone else's building. This page covers both - what the modules do, how a 3PL invoice is built, what the words mean, and how to choose and onboard without the surprises that turn up in month three.

Two buyers, one phrase

Ask a 3PL what software it runs and it will describe a warehouse management system with a billing engine attached: locations, licence plates, putaway, pick, pack, despatch, and an invoice per client produced from the same activity data.

Ask a brand that outsources fulfilment and it will describe something else: an order management and inventory tool that watches stock inside someone else's warehouse, routes each order to the right one, and tells the customer what happened to it.

Both get called 3PL software. If you are buying, decide which of the two you are before you look at a demo, because the questions, the price and the timescale are different.

You run the warehouse

You need a WMS built for several clients in one building: stock and permissions kept apart per client, a billing engine that can price each account differently, receiving against an ASN, and a portal so clients stop emailing for stock levels.

Your stock is with a 3PL

You need order management over someone else's floor: orders in from every channel, stock levels synced back, receipts and ASNs visible, and invoices you can check against the rate card line by line.

You are both

Some operators run their own first-party warehouse and take 3PL work in the same building. Then the honest answer is one system with multi-client isolation and a first-party mode, not two systems stitched together with spreadsheets.

The directory keeps two separate things: what a system is, and who it is for. The 3PL WMS category holds the systems built around multi-client operation, with client billing at the centre; the 3PL and fulfilment filter holds every system recorded as suitable for third-party work, which is a wider list. The 3PL WMS category (15) → · every system recorded as suitable for 3PLs (30) →

What the system actually does, module by module

A 3PL platform is a warehouse system plus five things a first-party warehouse never needs. Judge a vendor on the six separately, because a strong WMS with a weak billing engine is a bad 3PL system.

1

Warehouse management

The physical layer: locations and zones, licence plate numbers on every pallet and carton, directed putaway, replenishment, wave or batch picking, pack and despatch, and a stock balance per client that never mixes two accounts.

Check: Ask to see two clients' stock in one aisle, and prove neither can see the other's.

2

Client billing

The rate card multiplied by what actually happened: storage by pallet, bin or shelf, receipts by pallet or carton, outbound by order, package or line, plus value-added services. It is the module that decides whether the operation makes money, and the one most 3PLs under-invest in.

Check: Ask for a sample invoice built from a month of your own data, not a screenshot.

3

Client portal

The brand's window into the warehouse: stock on hand, orders and their status, receipts, returns and invoices, without a phone call. Weak portals are the most common reason a client starts quietly looking elsewhere.

Check: Log in as a client, not as an administrator, and try to answer three questions from it.

4

Order intake and integrations

Where orders arrive: native channel connections, an integration layer, or EDI. Most 3PLs run an integration manager alongside the WMS rather than relying on the WMS alone, which means two systems to keep and two places a failure can happen.

Check: Ask who owns each connection when a channel changes its API - the 3PL, the vendor, or the brand.

5

Shipping and labels

Carrier accounts, rate shopping, label printing, manifests and tracking. In a 3PL the carrier account usually belongs to the client or to the 3PL, and that choice decides who pays for the label and who reconciles the invoice.

Check: Ask whose carrier account a label is bought on, and who checks the surcharges.

6

Returns and value-added services

Receiving returns per client, grading, re-kitting, relabelling, assembly, gift wrapping. It is also where most billing disputes begin, because the work is manual and the unit ("per unit", "per hour") is fuzzy until someone defines it.

Check: Ask how a VAS is priced and how the work is captured - scan, spreadsheet or memory.

7

Reporting, SLAs and AI

Per-client performance: on-time despatch, order accuracy, receipts turned around, stock accuracy, cost per order. Newer systems put an AI layer over the same data to explain a drop rather than only plot it.

Check: Ask for the report a 3PL would send to a client, not the operator dashboard.

How a 3PL invoice is built, and why the software decides it

Almost every 3PL invoice is a rate card multiplied by activity the warehouse system recorded. That is why a billing engine reading the same events as the floor is worth more than one that imports a spreadsheet at month end: an invoice a client cannot reconcile becomes a credit note, and then a conversation about leaving.

These are the charge types on most rate cards. The definitions matter more than the numbers, because two 3PLs quoting "per order" can mean very different things.

Charge Normally measured by What to pin down
Storage Pallet, bin, shelf, cubic foot or square foot, per week or per month When the clock starts (receipt or putaway), and whether a part month is charged in full
Receiving Per pallet, carton, unit or hour, plus unloading Whether it is measured on the ASN, the carton scan, or the count at goods-in
Outbound Per order, per package, per line or per unit The difference between an order with one item and an order with six
Value-added services Per unit, per hour, or a project fee How the units are captured, and who signs off unusual work
Returns Per unit received, per inspection, or included Whether the returns handling is billed to the brand or absorbed, and who scraps
Minimums and surcharges Monthly minimum, peak surcharge, fuel, oversize, packaging What triggers each one, and how much notice the 3PL must give before it applies

A more expensive system that can produce a client-ready invoice is often cheaper than a cheap one that cannot, because the cost of a disputed invoice is not the invoice. It is the account manager's month.

How to choose, from either side

The two buyers need different proofs. Take the list for your side into the first call, and do not accept a demonstration that uses the vendor's data.

If you run the 3PL, ask

  • Can each client have their own rate card, and can two clients be on different units for the same work?
  • Does the billing engine read the same events as the floor, or does someone rebuild the month from a spreadsheet?
  • How does a new client come on board: item master, dimensions and weights, ASN format, carrier accounts, portal setup?
  • What does a client see in the portal, and can they run their own reports without asking us?
  • Which integrations are native, which go through the integration manager, and who supports each when it breaks?
  • Can I run two warehouses, and a first-party location for my own stock, on the same licence?
  • What happens at the end of a contract: how do I export a client's stock, order history and billing, and in what format?

If your stock sits in one, ask

  • Which 3PLs is it already connected to, and how long does a new connection take?
  • Do I see receipts and ASNs, or only outbound orders?
  • Can I check an invoice against the rate card myself, line by line?
  • What happens when I add a channel, a marketplace, or a second 3PL?
  • Can it route an order to whichever warehouse actually has the stock, or is routing manual?
  • Who owns the integration: the vendor, the 3PL, or me?
  • What does it cost at 500 orders a month and at 20,000, and where is the step change?

Whichever side you are on, insist on a demonstration with your own data: your item master, your rate card, and your worst SKU - the one with six dimensions and two barcodes. A scripted demo tells you what the software does with clean data. Your data tells you what it will do with yours.

The first 90 days

Most 3PL software failures are onboarding failures. This is the sequence that keeps appearing in the ones that work.

Weeks 1-2: the data

  • Locations, zones and pick faces, mapped to the way the floor actually works rather than the old spreadsheet
  • Item master with dimensions, weights and barcodes - the data that decides your shipping cost
  • Licence plate and label rules, including the client prefix that keeps accounts apart
  • Per-client permissions, carrier accounts and the first rate cards

Weeks 3-4: the connection

  • Order intake for each channel, and a named owner for each connection
  • ASN and receipt format agreed with the first client
  • Test orders end to end: a normal order, a cancellation, a backorder, a partial despatch and a return
  • Stock sync back to the client's system, and the portal switched on for them

Go-live: one client first

  • Put a single client, or a single product range, through the system properly before the rest
  • Keep a manual reconciliation of stock for the first month, and compare it weekly
  • Have someone on the floor whose only job that week is fixing what the system gets wrong

First month: prove the meter

  • Run the first invoice by hand against the rate card and compare it with what the system produced
  • Do the first cycle count and compare the system's accuracy with the physical count
  • Fix the item master wherever the two disagree, before the errors reach a carrier invoice

Day 60-90: hand it over

  • Document who owns each integration, and what happens when a channel changes its API
  • Write down how a VAS is captured and priced, because the next dispute will be about one
  • Agree the client-facing SLA report and send the first one before the client asks for it

Where it goes wrong

The same six problems account for most of the unhappy 3PL system stories.

The item master

Wrong dimensions, weights and barcodes are the biggest single cause of wrong labels, wrong shipping charges and stock that cannot be counted. Treat it as a data project with an owner, not an admin task that gets done at go-live.

Unit definitions on the rate card

Two people can sign a contract both believing "per order" means the same thing. Define every unit in the contract with an example, and attach one worked invoice to it.

The integration nobody owns

When a channel changes its API, the 3PL blames the vendor, the vendor blames the 3PL, and the brand loses orders. Name an owner per connection in writing, and a response time when it breaks.

Returns as an afterthought

Returns cost more per unit than outbound and are billed the least clearly. Design the return path before go-live: who grades, who scraps, who credits, and how it is recorded against the client.

Peak discovered in November

Volume spikes break packing stations and carrier capacity before they break the software. Rehearse a peak day with real volumes, and agree what the 3PL will refuse when the floor is full.

No exit plan

Ask what exporting a client's stock, order history and billing looks like before signing, and test the export once while everyone is still friendly. A system you cannot leave is a system you are stuck in.

The words, in plain English

The terms that come up in a 3PL conversation. The rest of the site's glossary - the acronyms for systems, product data and connections - is on the glossary page.

Rate card The schedule of charges
The 3PL's price list: storage, receiving, outbound, returns and value-added services, each with a unit. The unit matters more than the price - "per order" and "per package" are different businesses at Christmas.
Storage billing Charging for space
Rent measured by the space the stock occupies: per pallet, bin, shelf, cubic foot or square foot, usually per week or per month. Ask when the clock starts - receipt or putaway - and whether a part month is charged in full.
Per order / per package The two outbound units
Per order bills the shipment however many parcels it took; per package bills each parcel. An order split across three boxes costs a 3PL three times as much to ship but is often billed once, which is why the definition belongs in the contract.
VAS Value-added services
Work beyond pick, pack and despatch: kitting, relabelling, gift wrapping, assembly, quality checks, photography. Usually manual, usually billed per unit or per hour, and usually where an invoice starts to drift.
Kitting Building a saleable item from parts
Assembling components into one sellable product - a gift set, a hamper, a bundle - either ahead of orders or at the pack bench. It changes stock: the components go down and the kit goes up, and the system has to know both.
Co-mingled stock Shared locations
Different clients' stock sharing the same bins, separated by licence plates and system records rather than walls. Efficient in space and unforgiving of process: one wrong scan puts someone else's stock into the wrong order.
Dedicated stock Reserved locations
A client's stock kept in its own area or its own bins. Easier to count, audit and photograph, and more expensive because the space is bought whether it is full or not.
Cross-dock Receive and despatch without storage
Stock arrives and goes straight back out, usually against a known order. It saves putaway and storage, and it needs the order in the system before the lorry arrives.
Slotting Where each SKU lives
Deciding which products go in which bins so the fastest movers travel least and the heaviest stay low. A better layout beats a faster picker, and it is skipped more often than it should be.
Cycle count Counting stock without shutting down
Counting a slice of the stock on a rota rather than closing the warehouse for a stocktake. The system picks what to count - often what has moved least, or been picked most - so accuracy is maintained instead of measured once a year.
Wave picking Releasing orders in batches
Freeing a group of orders to the floor at once so pickers can work a route and the packing stations stay fed. The warehouse equivalent of batch cooking: less walking, more coordination.
Client portal The brand's view of the warehouse
The login where a brand sees its own stock, orders, receipts, returns and invoices. A good portal removes the weekly email; a weak one is the most common reason a client starts looking at another 3PL.
Integration manager The connector layer
Middleware that joins a 3PL's warehouse system to many channels and customer systems, so the warehouse does not need a native connection for every one of them. Ask who maintains each connection when a channel changes its API.
Dimensional weight Charging for space, not weight
A carrier charge based on the volume a parcel takes rather than what it weighs. It is why the dimensions in an item master have to be right, and why a wrong carton choice arrives as a shipping surcharge.
Minimum monthly charge The floor on the invoice
An agreed monthly minimum whatever the activity, so the 3PL is paid for reserving space and people. It is normal in a first year, and worth comparing with the projected invoice rather than with the rate card.

The full list, including the acronyms for systems, product data and connections, is on the glossary page.