On this page
Quick Overview
A control for telling customers which lines shipped, which remain open, and when the balance will arrive before a partial delivery becomes a chargeback.
A split shipment is often the right operational answer. One location has eight of ten cases, the other has the balance, and waiting for a single full truck would miss the customer's window. The problem starts when the customer learns about the split from a delivery receipt instead of from the company.
Decide the split before the pick is released
A split should be a deliberate decision with a reason, not a surprise created by allocation. Record why the order is splitting: insufficient stock at one location, a customer delivery window, a carrier capacity limit, or a warehouse cutoff. The reason determines who approves the extra freight and who tells the customer.
If the split is caused by a data error, such as inventory that is physically present but not available, fix the data before releasing a second shipment. Otherwise the company pays twice to solve a record problem.
Show the customer the line-level plan
A message that says your order has shipped is not enough when only part of it shipped. The customer needs the lines and quantities in the first shipment, the lines and quantities still open, the expected date for the balance, and a contact for changes. Use the same order and PO references the customer already has.
When the balance date is uncertain, say so and give the next update date. A vague promise invites a call; a dated update plan gives the customer a reason to wait.
Keep the notification tied to the shipment record
The notification should be generated from the same data that creates the packing list and the advance ship notice, not typed from memory. That linkage keeps the quantities consistent and gives the team a record of what the customer was told.
Align invoicing with the physical split
Customers dispute invoices when the billing does not match what arrived. If the first shipment is invoiced separately, the invoice should reference the shipment and the lines it covers. If the order is invoiced once at the end, the customer should know that before the first carton arrives.
Freight charges need the same treatment. A split can create two shipments, two accessorial charges, or a minimum charge on each. Decide who pays before the second shipment leaves, and state it in the customer notification. A charge that appears for the first time on the invoice is a collection problem waiting to happen.
Give the exception a named owner
The customer service owner should own the communication, while the warehouse or transportation owner owns the physical plan. The two need a shared record. If the customer calls to change the balance, the change should flow back to the open order and the shipment plan, not stay in a phone note.
Set a rule for when a split becomes a backorder. If the balance cannot be dated within the customer's window, the order may need a new promise date, a substitute, or a cancellation conversation. Leaving the balance in an open shipment state hides the customer impact.
Review splits for cost and cause
Review split orders weekly by reason, customer, and cost. A high volume of splits caused by one location's inventory record is a different problem from a high volume caused by customers ordering beyond a single truck. The first calls for a data fix; the second may call for a commercial conversation.
Track customer contacts after the split notice, chargebacks tied to partial delivery, and second-shipment freight cost. These measures show whether the notification is actually preventing surprises or merely documenting them.
Control table
| Control point | What to capture | Customer outcome |
|---|---|---|
| Split reason | Stock, window, capacity, cutoff | The customer hears a reason, not an excuse |
| First shipment | Lines, quantities, carrier, tracking | The customer knows what is arriving |
| Open balance | Lines, quantities, promised date | The customer knows what remains |
| Freight responsibility | Who pays, which shipment | No surprise charge later |
| Invoice plan | Per shipment or at completion | Billing matches the delivery |
| Next update | Owner and date | The customer has a follow-up path |
Frequently asked questions
Should the customer approve every split?
Not always. A split inside the agreed window may only need notice. A split that changes the delivery date, freight cost, or order completeness should follow the customer agreement.
Can the ASN carry the split information?
Yes, when the trading partner supports it. The ASN and the customer message should tell the same story, with the same order, lines, and quantities.
What if the balance never ships?
Convert the open balance into a backorder or cancellation with a new promise date. An open shipment that never closes distorts the order report and frustrates the customer.
Where to begin
The split shipment invoice readiness shows how the surrounding record can stay reviewable, and the order workflow support describes the kind of administrative support that can keep the queue current without taking over the decision. The GS1, EDI Standards (opens in a new tab) provides public context for the operating risk described here.
On October 22, 2026, take one open item from this workflow and test the record against the fields above. If a reviewer cannot identify the owner, the deadline, the evidence, and the next action, fix the record before adding volume.
Tags: split shipment customer notification control, distribution operations, workflow controls
