A third-party logistics provider can measure almost anything. The warehouse system produces dozens of figures, the client asks for a dashboard, and the monthly report grows by a new measure every time a customer meets a competitor's version. After a year the report has thirty numbers, and the operations team can explain ten of them.
We suggest a stricter test for what goes into the 3PL KPIs you show clients. A measure is worth reporting only if it traces to a billable event or a contractual promise, has one source system, and carries a written definition that says where it starts and where it stops.
The failure is not in the formulas. Order accuracy is shipped lines that were right divided by shipped lines in total, and anyone can write that down. The failure is in everything the formula leaves open. Which lines count? Is a line right if the product is correct and the quantity is not? Is a shipment late if the carrier collected it on time and delivered it late?
When two parties compute the same measure from different readings of those questions, they get different answers, and each is correct by its own reading. The client's report says you were late on eleven percent of orders. Yours says four. Nobody has made an error, and a month's worth of goodwill goes into the argument.
That is why we say a definition dispute is a billing dispute in disguise. If service credits, penalties or renewals depend on a KPI, then the definition is part of the contract, whether or not anyone wrote it down.
A measure earns a place in the client report if it passes three checks.
It traces to a billable event or a promise. Receiving, putting away, storing, picking, packing, shipping and returning are the events a 3PL bills for or has promised. A measure that does not attach to one of them is interesting, and belongs in the internal report.
It has one source system. The number is computed from one place, with a stated timestamp, not assembled from three exports in a spreadsheet. If the figure cannot be reproduced by someone else from the same system, it cannot be defended.
It has a definition with a start and a stop. One page per measure, naming the event that starts the clock, the event that stops it, what is excluded and who agreed it.
We explain why the billing events matter so much in what a 3PL operator actually needs to buy: the warehouse system emits events, and the billing engine turns them into invoices. A KPI built from the same events means the report and the invoice cannot disagree about what happened.
Dock-to-stock time. From the receipt being recorded at the dock to the stock being available to pick. It traces to receiving and put-away. The definition has to say whether quality hold time counts.
Order accuracy. Shipped lines that matched the order in product and quantity, divided by shipped lines. It traces to pick and pack. The definition states how a substitution agreed with the client is treated.
On-time shipment. Orders shipped by the agreed cut-off, divided by orders received before that cut-off. It traces to the shipping promise. The definition fixes the clock: order received, or order released.
Inventory accuracy. Cycle counts matching the system, by location, divided by locations counted. It traces to storage. The definition says how a count within tolerance is treated.
Billing accuracy. Invoice lines accepted by the client without a dispute, divided by lines issued. It traces to every billed event. It is the measure a client feels most directly.
Space used against space contracted. Positions occupied against positions committed. It traces to storage billing and tells both sides whether the contract fits.
Six is not magic. It is the number a client can hold in their head, and each measure maps to a part of the work that a person can improve.
Everything else still has a use. Pick rate per hour, labor cost per order, dock door utilization and carrier claim rate help you run the building. They do not belong in the client report because the client did not buy them, no clause depends on them and a change in them cannot be traced to an invoice line. Keep them where the operations team looks, and promote one to the client report only when a contract term starts to depend on it.
Imagine a 3PL and a client who agreed that goods would be on the shelf within two days of arrival. The client's report shows an average dock-to-stock time of three days. The 3PL's shows one and a half.
Neither is wrong. The client starts the clock when the carrier's delivery appointment was booked, which is the date they know. The 3PL starts it when the receipt was entered in its system, which is the date it knows. The two dates are typically a day apart, and the 3PL also pauses the clock while an item is on a quality hold, which the client did not know about.
Written down, the definition says that the clock starts when the receipt is recorded at the dock, stops when the stock is available to pick, and pauses only for holds that the client requested. On that definition, both parties compute one and a half days, and a conversation that took an afternoon every month ends. The same sheet decides whether a service credit is owed, which is where the money was all along.
A definition sheet is worth little if only the 3PL has read it. Each sheet is agreed with the client's operations contact, filed with the contract and given a version number. When a definition changes, the version changes with it, and the report says which version it used. That small habit means that a figure from March can still be reproduced in September, when a renewal conversation turns on it.
Start with the three measures that have a clause attached, usually on-time shipment, order accuracy and inventory accuracy. The rest can follow as the client asks for them, one sheet at a time.
Take your current client report and, next to each measure, write the billable event it traces to, the system it comes from and the clock's start and stop. Mark every measure where any of the three is blank. Those are your disputes in waiting, and the blank that is easiest to fill is usually the stop point. Then pick the client who disputes most often and agree one written definition with them this month. For the billing side, how a 3PL stops leaking revenue covers where the money goes when events and invoices do not line up.
We start with a no-risk discovery: we take your client report, trace each measure to its event and system, write the missing definitions and show you which disputes are definitions, and you pay for the discovery only if you go on. A build comes with a guaranteed estimate, so if we estimate low, we absorb the difference. After go-live, Managed Technical Operations keeps the events, the report and the invoice reading from the same source.
A KPI the client can reproduce is a KPI you do not have to defend.
In a no-risk discovery we follow an order from sale to shipment to invoice across your systems and show where it breaks and what one connected system would change. You pay only if you proceed. Or see how we approach it.
More on the same problem:
"Something isn't working." "We're outgrowing our tools." "We're afraid to make the wrong move." No-Risk Discovery is a short, practical conversation that gets you clarity before you commit to anything big. We'll tell you if we're a fit. If we're not, we'll tell you that too.
Say who you are and ask. A person replies within one business day.
