A split shipment can protect a delivery promise when one location cannot fulfill an entire order. It can also add transportation cost, packaging, customer confusion and more opportunities for exception. The decision should compare complete options, not assume that fewer packages or faster release is always best.
Define what may be split
Decide whether the OMS may split by line, quantity, location, availability date or shipment method. Preserve constraints such as kits that must travel together, regulated items, gift sets, channel rules and customer-selected delivery options.
Some lines may be independently fulfillable while others form an inseparable group. Model those groups explicitly. Do not infer them only from a shared product title.
Compare eligible plans
First apply the same eligibility gates used for normal routing: stock, capability, authorization, promise and operational status. Then compare complete plans using:
- expected delivery by line and package;
- shipping, handling and packaging cost;
- number of fulfillment handoffs;
- capacity and cutoff risk;
- inventory fragmentation;
- channel and customer communication requirements.
Use eligibility-first routing to build candidates, and use the order lifecycle model to preserve partial fulfillment states.
Work through a hypothetical decision
An order has a jacket and belt. Location A has both, but ground delivery is one day later than the customer’s requested date. Location B has the jacket and Location C has the belt; each can meet the date.
The OMS can compare a one-package late option with a two-package on-time option. If the requested date is a hard commitment, the split may be appropriate. If it is an estimate and the incremental shipping cost is high, the one-package plan may be preferable under approved policy. The system should store which service rule decided the outcome.
Now change the example: the “belt” is a component of a bundled gift set. Splitting it would break the sold product. That plan is ineligible before cost comparison.
Reserve atomically where possible
A split plan depends on multiple reservations. If one succeeds and another fails, the OMS needs a compensation path: release successful holds, select a revised plan or send the order to exception. Do not mark the plan committed while one location remains unconfirmed.
Record each fulfillment’s source lines and quantities. Tracking, cancellation, refund and customer messages must reflect partial shipments without making the whole order look complete.
Handle cancellation and short picks
Define the cutoff independently for each fulfillment. A customer may be able to cancel the unreleased package after another has shipped. Financial and channel updates must preserve what was actually fulfilled.
If one site shorts a line, do not automatically duplicate already released work elsewhere. Confirm the short, remaining eligible stock and other fulfillment states. Create a replacement shipment only through a controlled transition with a unique identity.
Recover from duplicate or missing shipments
When package evidence conflicts, correlate order, fulfillment, carton and tracking identifiers. Determine whether the error is a missing acknowledgment or an actual missing shipment. Replaying a create-shipment action before checking the destination can produce a duplicate.
For a duplicate shipment, stop further release if possible, preserve the audit trail and follow the agreed customer and carrier recovery path. For a missing acknowledgment, reconcile the existing fulfillment instead of creating another.
Accept the operating tradeoff
Strict no-split policies lower package count but can increase delays and cancellations. Aggressive splitting protects individual-line speed but can consume margin and capacity. Set thresholds by channel promise, order value, product constraints and tested cost inputs; review outcomes rather than hard-coding one universal answer.
A useful next step
Analyze a sample of split orders by reason, incremental package count, promise result and exception rate. Separate planned splits from warehouse shorts so policy performance is not confused with execution failures.
Include customer-contact evidence where available. Two packages that both arrive on time may still create “where is the rest?” contacts if channel messaging shows the whole order as fulfilled after the first shipment. Test email, account-page and service-console presentation as part of the policy, not as a downstream cosmetic concern.
1Commerce can help teams connect OMS decisions with configured channel and fulfillment workflows. Explore fulfillment capabilities or contact 1Commerce to review split-shipment policy.