Logistics and third-party warehousing

How work moves in logistics and third-party warehousing

The work belongs to someone else. A client sends inbound shipments with an advance notice, or without one. The dock receives, counts, inspects and puts away, and reports what arrived back to the client. Orders come in through EDI, a client portal, an integration with the client's store or a spreadsheet by email. The floor picks, packs, labels to each client's rules and stages for the carrier. Trucks are booked, loaded, tracked and delivered, and proof of delivery comes back.

On the transportation side, a broker or carrier takes a load, books a truck, tracks it, and handles the appointment changes, detention and claims that come with it. Throughout, the client wants to know where their goods are.

Billing runs on rates per pallet, per order, per pick and per day in storage, plus accessorial charges for everything outside the standard: relabeling, special handling, rush orders, detention. The roles are account managers or client service reps, receiving and shipping leads, pickers and forklift operators, inventory control, dispatchers or brokers, and a billing team that reconciles the floor to each client's rate sheet.

Where it usually breaks

Each client's orders arrive a different way

One client integrates, another emails a spreadsheet, a third calls in rush orders. Client service retypes the stragglers into the WMS. Errors show up as wrong shipments charged to the warehouse. That is the re-entry trap.

Dock exceptions are settled by email

A shipment arrives short, damaged or without paperwork. The dock lead takes a photo, holds the pallet and emails the account manager, who emails the client. The pallet sits until someone answers. That is the exception swamp. See billing disputes take weeks, which is where these end up.

Extra work never reaches the invoice

The client asks for a relabel or a rush. The floor does it. Whether it was recorded, by whom and at what rate decides whether it is billed, and often it is not. That is the field-to-office split. The guide on extra work that never gets billed shows how to measure it.

The client cannot see what is happening

Inventory in the WMS and the client's own count disagree. Where a load is lives in a dispatcher's phone. Client service spends its day answering status questions. That is the invisible queue. See nobody knows what's in the warehouse.

The first workflow we usually look at

Usually the path from work done on the floor to a billed charge: the receipts, orders, storage days and accessorial work for one client's month, traced from the dock to the invoice and compared to the client's rate sheet. It is where finished work turns into money or does not, and the gap is countable. If inbound exceptions or order intake cost the business more, the Spec says so and focuses there.

We stand on the dock through receiving and shipping, sit with client service and billing, and follow a set of recent orders and exceptions from arrival to invoice.

The systems in the picture

A logistics or third-party warehousing company usually runs some mix of these:

• A warehouse management system and handheld scanners
• A transportation management system or load board, for those that move freight
• EDI and integrations with clients' stores and ERPs
• Client portals and carrier portals
• An accounting system and a billing spreadsheet per client
• Email and phones for exceptions, appointments and status

What a Workflow Spec looks like here

A Workflow Spec for a logistics or third-party warehousing company is priced by deployment, and takes up to five business days on site. We work the dock with receiving and shipping leads, sit with client service, dispatch and billing, and interview the people who touch a client's goods from arrival to invoice. You get the workflow map, the business case, an adoption design built for the floor leads and staff who would use the tool, and a fixed proposal for the build. The answer can be not to build. Details are on how we work.