Skip to main content
web-development

Ecommerce Partial Shipments: A Store Brief

Plan split deliveries with accurate item quantities, shipment records, charges, tracking, customer messages and warehouse handoffs.

Mocky Digital
17 November 2026
7 min read

An ecommerce partial shipments brief defines how a store fulfils one order in more than one delivery without confusing the customer about what has arrived and what remains outstanding. A single order status can hide that distinction. The business needs item quantities, shipment records and communication that reflect the actual physical work.

For a shop planning ecommerce website development in Kenya, agree the split-delivery process before adding dispatch buttons. The examples here are illustrative requirements, not a universal delivery policy, a courier recommendation or a promise that splitting an order will reduce costs or improve sales.

Decide why an order may be split

List the genuine reasons the business needs separate shipments. Goods might leave different locations, one item may require different handling or the customer may approve sending available items first. Identify which reasons are supported at launch and who can authorise an exception.

Distinguish an operational split from a change to the purchase itself. Sending the same authorised goods in two parcels is different from substituting a product or cancelling an unavailable line. Keep those decisions in their approved workflows rather than using partial fulfilment to disguise an unresolved order change.

Write the customer-facing explanation before choosing the implementation. The shopper should understand whether separate deliveries are normal for the offer or require a later agreement. Staff should not introduce an unexpected arrangement during packing because the dashboard happens to allow multiple tracking numbers.

Track quantities at line and shipment level

For each order line, define the ordered, allocated, dispatched, cancelled and remaining quantities the system needs to represent. These values should have agreed meanings. An item appearing on a picking list is not necessarily evidence that it left the warehouse.

Each shipment needs a stable reference and an explicit list of goods. If two parcels contain different quantities of the same product, staff and the customer should be able to distinguish them. Avoid a structure where every tracking link appears to represent the complete order.

Ask the developer to show how repeated dispatch actions are prevented from exceeding the authorised quantity. The trusted system should validate the current record, including when two employees work on the same order. A disabled button on one screen is not enough to establish that duplicate dispatch records cannot be created.

Agree delivery charges before commitment

Decide how charges work for the supported split arrangements. The original checkout may cover one delivery model, while a later customer-requested change may require a reviewed adjustment. The business should approve those rules and explain them at the relevant decision point.

Do not assume that every additional parcel is free or that the same amount applies regardless of location and handling. Use the delivery zones planning guide to connect coverage and charge rules to actual fulfilment arrangements.

If an additional payment is required, keep it separate from approval to split the goods. The server must calculate the relevant amount and the payment must be verified through the agreed provider process. A support note or a customer screenshot should not mark a financial adjustment as settled.

Review the chosen platform's fulfilment model

Ask the developer to demonstrate the intended flow on the actual proposed setup. Multiple locations, third-party fulfilment services and local pickup can have different controls. Do not assume that a feature shown in another store is available through the same interface or plan.

Shopify's individual fulfilment documentation describes fulfilling part of an order, tracking and split fulfilments, with relevant restrictions. Use it as a starting point when reviewing a Shopify implementation, not a guarantee that every courier or platform behaves identically.

For a custom system, include the shipment relationships and allowed transitions in the specification. The business should understand how a shipment becomes prepared, dispatched and delivered, and which source can verify each state. Avoid one generic completed label that implies every stage has occurred together.

Keep the customer informed about the remaining goods

Prepare a message for each shipment that identifies its contents and explains what remains. A customer receiving a parcel should not have to compare the delivery with an old shopping basket screenshot to work out whether something is missing or simply coming later.

Use honest timing language for outstanding goods. An estimated replenishment date is different from a confirmed dispatch date. If the remainder depends on a preorder arrangement, refer to the approved preorder workflow rather than inventing a delivery commitment in a notification template.

Plan messages around verified events using the order notifications brief. Creating a shipping label, handing over a parcel and confirming delivery may happen separately. An outgoing message should describe the event its source actually establishes.

Make warehouse handoffs explicit

Define who assigns goods to shipments, who checks the packed quantities and who records handover. A packing slip should identify the specific shipment and its contents, while retaining the connection to the original order. Staff need to know whether another location is handling the remainder.

Decide how the system handles a last-minute shortage or damaged item during packing. The employee should be able to flag the exception without falsely confirming the original planned quantities. The business owner should approve whether the shipment is paused, revised or escalated.

If several locations fulfil the same line, test their shared quantity controls. One location's cancellation or correction should not make another location's record appear unfulfilled or invite a second dispatch. The project team should show these interactions with controlled records before the store relies on them operationally.

Handle delivery exceptions per shipment

A failed delivery for one parcel should not automatically label the entire order delivered or cancelled. Decide which states the customer sees and how support finds the affected shipment. Keep carrier evidence distinct from an employee's manual note where both are available.

Returns also need the shipment context. The customer may return only part of one parcel while another remains in transit. Financial decisions should follow the refund workflow brief, with quantities and original payment evidence checked separately from the logistics status.

Record corrections transparently. If staff entered the wrong tracking reference, the store needs an authorised amendment route and an accurate customer update. Do not silently attach another customer's tracking details or expose private delivery information through a public status screen.

Test the full order before handover

Prepare controlled scenarios for two shipments, a partially dispatched line, a cancelled remainder, a failed first parcel and a second parcel delivered first. Check what the customer, packing team and support staff each see. The order summary should remain understandable through every sequence.

Include a repeated dispatch request and an interrupted integration response. Ask how the system checks whether the first operation succeeded before retrying. Duplicate provider calls should not create another shipment or message merely because the initial response arrived slowly.

Run these tests without live customer messages, courier bookings, payments or invented production orders. An isolated environment should provide repeatable evidence without creating business activity. Label any part that cannot be verified before launch instead of treating a mock screen as proof of a working carrier integration.

At handover, retain the shipment state map, charge rules, permission boundaries and escalation owners. Request an ecommerce quotation with the actual locations and delivery services involved. The scope should explain how the complete order remains accurate across several parcels, rather than simply promise a field for extra tracking links.

Frequently asked questions

Is a partially shipped order fully completed?

Not necessarily. Track the remaining authorised goods and distinguish shipment progress from the overall order outcome.

Does every parcel need its own tracking number?

Use the identification the actual delivery arrangement supports. Keep each shipment and its contents distinguishable even when a provider offers limited tracking.

Can a split shipment change the total automatically?

Only under approved rules implemented by the trusted system. Explain and verify any required financial adjustment separately.

Should customers receive one or several messages?

Choose messages that explain actual shipments without duplication. The platform and provider capabilities must be reviewed for the intended process.

Share this article

Ready to Start Your Project?

Tell us what you need designed, built, or printed. We will reply with a clear price and timeline.

Book a Call

Preparing your booking calendar…

Having trouble? Open the booking calendar directly.

Mocky Digital

Let’s talk about your project

Choose a service and leave your details. We’ll follow up with you.

By submitting, I agree that Mocky Digital may save my details on its website and in Cal CRM and email me relevant service tips and offers. I can unsubscribe at any time.

Your details are used to respond to your enquiry. Privacy policy.