3PL WMS vs Generic Warehouse Software

A 3PL needs a WMS built for 3PL work because generic warehouse software assumes one owner of the stock, and a 3PL holds goods for many. We keep the argument to things you can test yourself.

Most warehouse software began in a warehouse that owned its stock: a manufacturer, a retailer, a distributor. One company, one set of goods, one set of books.

A 3PL is different. You hold other people's goods, do work on them and send a bill. Software that treats the owner as a single unknown makes you build the "many clients" part yourself, out of spreadsheets and habit.

Where the workarounds begin

The first sign is small. Someone adds a prefix to each client's SKUs so two clients with the same product code do not collide. Someone else keeps a tab per client for rates. A third person types the monthly storage figure by hand from a pallet count taken on the last day.

None of that is a disaster. Added together, it is a second system that lives in people's heads and in files, and the real system knows nothing about it.

One question exposes the pattern: what do we do outside the system every month to get the invoice out? That list is the cost of the mismatch.

Client-level inventory

In a generic system, "how many of these do we have?" has one answer. In a 3PL it has one answer per client, per location and per status.

Without that structure you lean on labels and discipline. With it, the system carries the discipline for you. Cargohold's inventory page, for example, describes balances kept per client, warehouse, location, lot and serial, behind a ledger where each quantity traces back to the movement that produced it. Whatever you buy, that is the shape to look for: not a single total, but a total broken down by owner, with a reason behind every change.

A hypothetical example: a client disputes a count after a quarter-end audit. You need the stock history for one item, one client and one quarter. In a client-aware system that is a single screen. In a generic one it is an afternoon of exports.

Billing: the charges that get missed

This is where the money is. A 3PL earns on work, and work that is not recorded is not billed.

Think of the small jobs. Relabelling a carton. Holding a pallet an extra week because the client asked. Opening a case to count it. Staff do these as favours, the moment passes, and at month end nobody remembers.

A hypothetical example: a 3PL does about 40 small extras a month that are never recorded. Even at a modest fee each, a year of them adds up to real money, and nobody sees it because there is no line to look at.

Better memory is not the fix. The fix is a system where the work itself raises the charge. Cargohold's 3PL billing page describes that design: billable events raised from the ledger and task records, each traceable to the event that created it, and a check that lists work done with no matching charge before a billing run is approved. Other designs exist. The principle is what matters: if a person has to remember to add a charge, some will be forgotten.

When you evaluate any system, ask to see a receiving charge appear without anyone typing it.

The client portal question

Clients keep asking the same things. What is my stock? Did my order ship? Why is the invoice this amount?

Each question becomes an email, a call, or a spreadsheet someone on your team has to send. A client-facing view answers them without a person in the middle. Cargohold's portal page describes a dashboard of stock on hand, open orders and shipments, plus invoices that open to the charges behind them, all limited to that client's own data.

A portal also changes how billing disputes go. When a client can click from an invoice line to the event behind it, many arguments never start.

Ask two things about any portal. Can a client only ever see their own data? And can a client open an invoice line and see why it exists?

Why generic software forces workarounds

Generic software is not badly made. It was made for a different customer, and the assumptions show:

• The owner of the stock is the company running the software, so "client" is an afterthought or a plugin.
• Charges are internal costs, not revenue lines with client-specific rates.
• Nobody outside the company needs a login to see stock.
• Seat-based pricing, where it applies, can sit oddly with a business in which a new client may add pallets without adding staff.

You can sometimes bend a system to fit. But every bend is a rule that only a few people understand, and when they leave, the rule leaves with them.

Questions to ask before you commit

Take these to any vendor, including us.

1. Show me two clients with the same SKU code. How does the system keep them apart?
2. Show me a charge raised from work on the floor, without anyone typing it.
3. How does the system catch work that was done and not billed?
4. Show me what a client sees. Prove they cannot see another client.
5. Show me how I explain a storage charge to a client, line by line.
6. What do I pay when I add a client, a user, an order or a site?
7. Who owns my data and my configuration, and what do I get if I leave?
8. Who runs the system after launch, and what happens when that person is away?
9. What do I still have to do in a spreadsheet after all of this?

Question nine matters most. A system that answers the other eight well and still leaves your monthly invoice in a spreadsheet has not solved your problem.

Where this leaves you

You do not need the most complicated system. You need one that treats the client as part of the record, raises charges from work, and lets clients look things up for themselves.

For the broader choice, start with what kind of warehouse management system a 3PL should get. To find out whether our own approach suits you, read is Cargohold the right system for your 3PL, which includes the cases where we would tell you to buy something else.

Questions people ask

Why doesn't generic warehouse software work for a 3PL?

It was made for a different customer. It assumes the stock owner is the company running the software, treats charges as internal costs instead of revenue with client rates, assumes nobody outside needs a login, and often prices by seat, which sits oddly with a business where a new client adds pallets without adding staff.

How do 3PLs lose money on unbilled work?

On small jobs that are never recorded, such as relabelling a carton, holding a pallet an extra week or opening a case to count it. Work that is not recorded is not billed. The fix is a system where the work itself raises the charge, so nobody has to remember.

What should a 3PL client portal do?

Let clients look up their stock, open orders, shipments and invoices without emailing your team. A client should only see their own data, and should be able to open an invoice line and see why it exists.

How do I find the workarounds my 3PL team uses today?

Ask what you do outside the system every month to get the invoice out. That list is the cost of the mismatch between your software and your work.

What questions should I ask a 3PL WMS vendor before I commit?

The page lists nine questions. They include how two clients with the same SKU stay apart, how a charge is raised without anyone typing it, what a client sees, what you pay when you add a client or user, who owns your data, and what you still have to do in a spreadsheet. The last one matters most.