Leak 12 · Freight & Cost-to-Serve - Excessive customer-specific handling

Custom labels, kitting, special packaging, portal data entry, certs with every shipment. Real service, real labor, and usually free.

Diagnostic note. Symptoms, required records, an initial check, and possible fixes. This shorter note does not include a full worked example.

What is it?

Large customers accumulate requirements: barcode labels in their format, bagging and tagging, cut-to-length, certificates of conformance, packing lists in their layout, orders entered into their portal, invoices uploaded to their AP system. Each was agreed as a small favor. Together they can add an hour of labor to every order for that account, and the price was set before any of it existed.

Family
Freight & Cost-to-Serve
Primary owner
Operations Manager
Secondary owners
Sales Managers, CFO
Primary impact
EBITDA
Typical data source
Customer requirements, warehouse labor, order records
Detection difficulty
30-day measurability

Ask yourself

Can you name the five customers who require the most special handling, and do their prices reflect it?

Yes, partially, no, or don’t know. “Don’t know” is the most useful answer, because it points at the test below.

What does it look like?

Warning signs. None of these proves the leak exists. They tell you where to look.

  • Warehouse staff who know certain customers “take forever.”
  • Written or unwritten customer requirement sheets with no cost attached.
  • Accounts with average gross margin but visibly higher handling time.

What data do I need?

The minimum viable set. Most of it is already in your ERP.

Field
List of customer-specific requirements by account
Estimated labor minutes per order for each requirement
Orders per year and gross profit per account

The initial check

Start with a small sample. Gathering the exports, agreements, or observations is separate from running the check; agree that work with the person who owns the records.

  1. 1Ask the warehouse lead which five customers take the most extra work and what the extra work is.
  2. 2Estimate minutes per order for each and multiply by orders per year at a loaded labor rate.
  3. 3Compare the result to the account’s annual gross profit.
Handling cost per account = extra minutes per order ÷ 60 × loaded rate × orders per year

Then ask one question: For the account with the highest handling cost, is the margin still acceptable after subtracting it?

How much could it be costing us?

A conservative range, not a headline. The goal is a number management can trust enough to investigate.

Σ over accounts of unrecovered handling cost × share that could be priced, charged, or simplified

Common root causes

Fixes fall into three layers. Not every problem needs software, and almost none needs AI first.

Process
Requirements are agreed by sales without an operations review or a price adjustment.
Data
Requirements are not recorded against the account in the system, so they cannot be costed.
Technology
Labels, documents, and portal entry are done by hand because nothing generates them automatically.

What should we do?

Start with the simplest intervention that could solve it. Move down the list only if the one above is not enough.

  1. Level 1

    Visibility

    A requirements register by account with estimated cost, reviewed at each price negotiation.

  2. Level 2

    Policy

    New requirements go through an operations review and either a price adjustment or a handling fee.

  3. Level 3

    Automation

    Generate customer-format labels, documents, and portal submissions automatically from the order.

Where AI helps

  • Filling customer portals and producing customer-format documents from the order without re-keying.

Where AI probably doesn’t

Knowing what each account costs to serve starts with a list and a stopwatch, not a model.

Before you call it a leak

  • Handling requirements are often why a large account chose you. The goal is to price them, not to refuse them.
  • Labor estimates are rough. Use them to rank accounts, not to bill by the minute.

Think this might be happening in your business?

Turn the finding into a next step.

If the numbers say there is something there, send us what you found and we will help you decide whether it is worth a full investigation. No transaction files needed for that conversation.

Let’s start with one thing.

What would better performance look like?

Bring a result you want to improve, a symptom, or a workflow you already understand. You do not need to know the bottleneck yet. We’ll help choose what to investigate first.

No transaction files needed for the first conversation.