Skip to content
← Insights

Partial Deliveries: How to Split Shipments Without Losing Control

Learn when to split an order, how to link its shipments, and how to communicate each update clearly without confusing inventory, operations, or customers.

An ecommerce order divided into several shipments, with products, statuses, and delivery dates shown separately.

An order may include products shipping from different warehouses, items available on different dates, or units that require separate preparation processes. In these cases, shipping everything together can delay products that are ready. Shipping in parts, however, requires more coordination and can raise questions about the actual status of the purchase.

The solution is not simply to create several shipping labels. You need to maintain a clear relationship between the original order, its line items, and each shipment, as well as define which statuses each team sees and what information the customer receives. This guide outlines practical criteria for designing that process.

What a partial delivery is and why it happens

What a partial delivery is and why it happens

A partial delivery occurs when a customer receives only some of the items or units in an order, while the rest arrive in another shipment or at a later date. An order can have several shipments while still representing a single purchase from a commercial perspective.

Common causes include inventory distributed across locations, staggered availability, preparation by different suppliers, or an issue affecting only some line items. It is worth distinguishing between these causes: a planned split does not require the same response as a separate shipment caused by an unexpected stock shortage.

A simple rule should guide the design: the order expresses the commercial commitment; shipments represent how it is fulfilled, in full or in part. If these concepts are confused, a delivered shipment could incorrectly mark an order as complete even though some items are still outstanding.

When to split an order and when to wait

Splitting an order may make sense if the products available now are useful on their own, if waiting longer would inconvenience the customer, or if a delivery date has been communicated for each part. It may also be necessary when each warehouse or supplier prepares its units independently.

Waiting until the order is complete may be preferable when the items are used together, the customer expects a single delivery, or the additional shipments involve costs and work that do not provide enough value. The decision should not depend solely on whether stock is available somewhere. It should take into account the delivery promise, the customer’s preferences, and the operational cost of splitting the order.

Before setting a rule, product and operations teams should answer specific questions:

  • Can the customer receive the items separately without losing practical value?
  • How much delay does the first shipment avoid, and what additional cost does the split create?
  • Is there a deadline or delivery preference recorded for the order?
  • Can the team handle questions about multiple packages and delivery dates?

If the answer depends on the product type, sales channel, or commercial promise, establish explicit rules for each situation. Do not leave the decision to the individual interpretation of warehouse or customer service staff.

Linking the order, its line items, and its shipments

The operational model must show how many units from each line item are assigned to each shipment. A list of packages linked to the order is not enough: if a line item contains several units, some may ship today and others later.

At a minimum, each shipment should have its own identifier and be linked to the original order and the specific quantities it contains. It should also be possible to check its operational origin, estimated date when known, and tracking identifier when available. This allows an agent to explain which items have shipped, which are still outstanding, and why.

For example, if an order contains three units of an item and only two are ready, the records must preserve that difference. The shipment should not show the entire line item as dispatched. The outstanding unit remains linked to the order, but not to the package that has already left.

The quantity assigned to shipments must not exceed the quantity ordered. Canceled or unfulfilled units must also be distinguished from outstanding units. This prevents the system from treating a permanent shortage as a temporary delay or preparing units that have already been assigned a second time.

Separate statuses for orders, preparation, and delivery

A single overall status is usually too limited. It is clearer to maintain separate statuses for the order, the preparation of each part, and the transportation of each shipment. For example, an order may be partially shipped while one package is in transit and another is still awaiting preparation.

Specific status names will vary by operation, but every status needs a definition and an authorized transition. “Pending” should not mean a stock shortage, waiting for preparation, or missing tracking information interchangeably. When these reasons are mixed together, it becomes difficult to prioritize issues.

  • Order: summarizes commercial fulfillment, such as confirmed, partially fulfilled, or complete.
  • Preparation: describes the work for each part, from allocating units through dispatch.
  • Shipment: reflects the logistical progress of a package and its delivery, based on the information available.

Show operations teams outstanding quantities and their reasons. For customer service, provide a clear view by product, package, and estimated date, without requiring agents to interpret internal statuses. Do not display “order delivered” if units covered by the commitment are still unresolved.

Assigning stock, costs, and tracking by shipment

Inventory reservations should be tied to identifiable quantities. When a unit is assigned to a shipment, the operation must prevent that same unit from being reserved for another order or package. If an allocation changes, release or reassign the stock in a controlled way and make the outcome visible.

Costs require a separate rule. Define how preparation and shipping expenses are recorded when there are several shipments, and who decides whether they are passed on, absorbed, or require approval. Do not assume that every package results in an additional charge: the answer depends on the applicable commercial terms and what has been communicated to the customer.

Tracking information also belongs to each shipment, not just to the order. Save the link or identifier associated with the relevant package, and avoid reusing a tracking number for multiple shipments unless you have verified that it accurately represents their journeys. If tracking information is not yet available, say that it is pending; do not present unconfirmed information as fact.

Communicating each delivery without confusing the customer

Communication should explain that the order will arrive in parts, which items are included in each shipment, and what is known about the dates. A useful message distinguishes confirmed details from estimates and makes it easy to track each package. If a date changes, communicate the change for the affected part and clarify whether the rest of the order is still expected on schedule.

On the order page, show an overall summary and details for each shipment. Avoid repeating the complete order in every notification: this could lead the customer to think they will receive each product more than once. Messages should share a common order reference while clearly distinguishing between packages.

It is also important not to promise more accuracy than the operation can deliver. If only an estimated window is known, present it as an estimate. If one part has no date, explain when the information will be updated or what alternative the customer can check, in line with current policies.

Exceptions and indicators for improving the process

Exceptions and indicators for improving the process

A stock shortage, a canceled line item, and a delay require different responses. If there is an inventory discrepancy, block the allocation for the affected quantity and check which other line items can still proceed. If part of an order is canceled, update the outstanding units and communicate the effect on the rest of the order. In the event of a delay, check whether there is a reliable new estimate before changing the message to the customer.

Define when an exception requires human intervention. This might be when a date cannot be confirmed, when reserved and prepared quantities do not match, or when a shipment is marked as delivered but the customer says it never arrived. Each case should have an owner and a record of the decision to prevent conflicting responses.

To review the process, track signals that help identify friction, not just the number of packages:

  • The proportion of orders that are split and the recorded reasons.
  • The time between the first shipment and resolution of the remaining units.
  • Issues caused by duplicate allocations or incorrect outstanding quantities.
  • Questions and complaints related to partial deliveries.
  • Differences between communicated dates and the dates ultimately observed.

Before launching the workflow, check that the order retains a unique reference, each shipment identifies its line items and quantities, statuses do not conflict, and a cancellation or reassignment does not leave any units unlinked. Also test a standard case, one with partial stock, and one involving a delay. The process is well designed when any team can explain what was ordered, what has shipped, what is outstanding, and what happens next without having to reconstruct the history manually.

Fuentes y referencias

  1. Web standardsW3C
  2. OWASP Cheat Sheet SeriesOWASP Foundation
  3. Web performanceweb.dev