Client EDI, visibility and billing data for 3PLs
A 3PL runs one building for many owners. The stock is in the WMS. The time goes into everything around it, from each client's interface to each month-end invoice.
Scope a client integration kit
A third-party logistics warehouse runs one operation for many owners. Each client brings its own items, its own ERP, its own idea of what “received” means and its own reporting expectations. Your WMS keeps the stock. The time goes into everything around it: building each client’s interface, answering status questions by email, and turning a month of activity into an invoice the client does not dispute. We build those surrounding pieces around the WMS you run.
Multi-client inventory
Every unit in the building belongs to someone, and that ownership has to be on every record: item, lot, location, receipt, order and adjustment. Two clients can use the same item number for different products. Requirements we settle early:
- Client as part of the item key, with client-specific units of measure, case packs, and lot and expiry rules.
- Dedicated or shared locations by client, and what happens when stock of two owners sits in one bin.
- Per-client cycle counting and accuracy reporting, because each client asks how accurate its own stock is, not the building’s. The cycle count planner helps size the count workload.
The warehouse EDI messages
| Set | X12 name | Direction and purpose |
|---|---|---|
| 943 | Warehouse Stock Transfer Shipment Advice | Client to 3PL: stock is on its way |
| 944 | Warehouse Stock Transfer Receipt Advice | 3PL to client: what was received |
| 940 | Warehouse Shipping Order | Client to 3PL: ship this order |
| 945 | Warehouse Shipping Advice | 3PL to client: what shipped |
| 947 | Warehouse Inventory Adjustment Advice | 3PL to client: adjustments such as damage or count variances |
| 846 | Inventory Inquiry/Advice | 3PL to client: inventory balances |
| 997 | Functional Acknowledgment | Both ways: the document arrived |
Each client implements these differently: which version, which segments are required, how lots and units are sent, whether a 945 goes per order or per shipment. Some clients cannot send EDI at all and send files or call an API instead. We build the interface for each client, and the reconciliations that catch silent failures: every 940 should have a 945, every 943 a 944, and any gap older than an agreed time goes to a named person. The integration work is described under ERP and WMS integration.
Client-facing visibility
Clients want to see their stock, orders and shipments without emailing your customer service team. We build a client view, or scheduled reports where that is enough, scoped strictly to each client’s data:
- On-hand by item, lot and status, including held and damaged stock.
- Open orders with their current step: received, released, picked, packed, shipped.
- Shipped orders with carrier and tracking number.
- Receipts with any discrepancies against the 943.
Access is set by client and by role, as described on our security page.
Billing data capture
A 3PL invoice is built from activity: storage, handling, and value-added services such as kitting, relabeling or special packaging. The usual problem is not the rate card. It is that the activity was never captured as data when it happened, so someone rebuilds it from paper at month end.
We record billable events from scans that already happen: a pallet received, an order line picked, a kit assembled, a carton relabeled. Storage is captured as snapshots on the schedule your contracts use, such as pallets or bins occupied per period. Each client’s activity is exported to your billing or accounting system, where your rates stay. The quantities are ours to capture; the prices are yours.
The dimensions captured at receiving help with freight as well. Under the NMFC changes that took effect July 19, 2025, which NMFTA calls Phase 1 of a larger overhaul, the density scale grew to 13 subprovisions, with the top one at 50 pounds per cubic foot or more. Whether an item uses the density scale depends on its NMFC entry. The freight density calculator shows the arithmetic.
Onboarding new clients with an integration kit
Without a kit, each new client restarts the same conversations about formats, units and test cases. A documented integration kit lets you start from a package instead:
- Your implementation guide for each message you support, with sample files.
- An item master template with units of measure, case packs and lot rules.
- A test plan with standard scenarios: partial shipment, lot-controlled receipt, backorder, adjustment, cancelled order. Our UAT test plan template is a starting point.
- A cutover checklist and a runbook for your support team.
We write the kit with your team, test it on the next client, and hand it over through our documentation service so your staff can maintain it.
Example (fictional). A 3PL takes on a pet-supply client whose ERP sends every 940 line in eaches, while the warehouse stores treats such as item EX-20118 by the case of 12. In the first test, an order for 24 eaches is picked as two cases, and the 945 reports a quantity of 2 against a unit of “each”. The kit’s test plan catches it because it includes a “case-pack item ordered in eaches” scenario. The fix is a unit-of-measure conversion table in the client setup, and the runbook now tells the next onboarding team to check it first.
Where to start
A Scope and plan engagement for a 3PL can center on one upcoming client onboarding. We walk the process, list every interface in an integration inventory, and write requirements for the kit, the client view and billing capture. The build then uses that client as its first test, and every later client starts from the kit.
Scope your project.
Tell us what you need to track, which systems you run and when it has to work. We reply with questions or a time to talk.