Ecommerce fulfilment: orders, stock and dispatch

Understand ecommerce fulfilment from stock reservation to carrier handover. Assign order responsibilities and resolve split or failed dispatch.

Ecommerce fulfilment is the process of completing an accepted customer order, from allocating stock to preparing the goods and handing them to a carrier. Each step needs its own record. A tracking number alone doesn’t show that a parcel has left the warehouse.

When stock, warehouse and carrier records disagree, establish the last confirmed event for each order line before promising the next step.

What fulfilment means for an online order

Retail fulfilment turns an accepted order into goods ready for the customer, with recorded responsibility at each handover. This is different from fulfilment meaning personal satisfaction. Fulfilment is the Australian and British spelling. Fulfillment is the US spelling of the same process.

Receiving an order records what the customer bought. Stock allocation reserves units for that order. Preparation confirms which goods are packed, while carrier acceptance establishes that the transport provider has taken possession. Delivery records the later arrival with the customer.

A fulfilment centre is a facility that receives and stores inventory, then picks, packs and hands goods to carriers. It sits within the wider order and exception workflow. It isn’t the carrier’s transport network, and printing a label there doesn’t establish dispatch.

Self-fulfilment means your own team manages this work. Third-party logistics (3PL) fulfilment assigns it to an outside provider. In either arrangement, keep a retailer-side owner for the customer promise. For choosing that operating partner, compare ecommerce fulfilment providers against your order and stock requirements.

Ecommerce shipping covers carrier handover and transport. Fulfilment also includes inventory receipt, storage, allocation and preparation, plus resolving failures. Wider logistics connects incoming supply, stock locations and outbound movement. A shipment record covers its assigned goods. It doesn’t establish that every line of an order is complete.

Assign each order and stock event

Assign one accountable role and one source record to every event before connecting your store to a warehouse or fulfilment partner. These are suggested responsibilities for a retailer to adopt, not universal software status names.

EventSource record to retainAccountable role
Order acceptedOrder ID, line quantities, accepted terms and acceptance timeStore operations lead
Payment cleared for releasePayment reference and captured, authorised or approved credit status under your release rulesPayments lead
Stock reservedReservation ID, location, variant, quantity and resultInventory controller
Released to fulfilmentAccepted fulfilment request tied to the order and reservationOrder operations lead
Preparation confirmedPick and pack confirmation with exact line quantities and exceptionsFulfilment supervisor
Dispatch recordedShipment ID, parcel contents and warehouse handover recordDispatch supervisor
Carrier acceptance confirmedCarrier receipt or acceptance event matched to that shipmentShipping coordinator

Decide what payment state permits release for your business. An order confirmation and a payment authorisation are separate records. Neither alone proves the warehouse can prepare it.

Count sellable stock separately

On-hand stock is the physical quantity recorded at a location. Reserved stock is assigned to orders and unavailable to other buyers. Available-to-sell stock excludes those reservations and other holds, such as damaged goods or safety stock.

For example, Shopify’s inventory-state definitions separate on-hand stock into available, committed and unavailable quantities. Incoming stock is separate. Use the equivalent states in your own inventory system.

With five units on hand, two reserved and one damaged, two units remain available to sell. Across several sales channels, use one reservation authority for that stock pool. The first successful reservation consumes the last available unit. A second request must receive an unavailable result instead of a second promise.

A catalogue cache can display an older quantity. Refreshing it helps shoppers, but the reservation decision must use the stock authority’s current record.

Keep the exact order line identifiable

Retain the order ID, stable line ID, stock keeping unit (SKU), variant ID, quantity and event time across every handover. Map partner and carrier identifiers back to those records. The event time establishes when something happened. The received time shows when your system learnt about it.

For a skincare order, a 150 ml cleanser and its 50 ml version need different variant mappings. Pass only the storage and handling instructions documented for that exact product. If a unit is damaged, the inventory controller records its hold and adjusts sellable stock. For a restricted item, the product compliance owner establishes the applicable restriction from the product record and carrier rules before release.

Software-specific source mapping belongs in a Shopify WMS integration, where WMS means warehouse management system. Native rates and fulfilment settings belong in the Shopify shipping guide.

Trace a normal order to carrier acceptance

A normal order advances only when the next responsible party confirms its part. The following fictional order, F-104, illustrates the required evidence. The later shortage and dispatch cases are alternative branches of this same order.

Line IDProduct and variant IDSKUOrdered quantity
L1Cleanser 150 ml, V-150CL-1501
L2Moisturiser 50 ml, V-050MO-0502
  1. Accept F-104 with L1 quantity 1 and L2 quantity 2. Retain the accepted order and payment reference PAY-104. Confirm that PAY-104 meets the release rule.
  2. Reserve those exact quantities at location WH-A under reservation R-104. Both lines need successful results before the normal whole-order release.
  3. Send release REL-104 to the fulfilment team. Its acknowledgement must identify F-104 and the accepted line quantities. A sent request without acknowledgement remains unresolved.
  4. Record preparation against shipment S-104-A. Confirm one L1 unit and two L2 units in its contents record, with any product-specific handling instructions carried through.
  5. Create fictional tracking reference TRK-104-A for S-104-A. This establishes a labelled parcel. Keep the warehouse handover evidence separate from the carrier’s acceptance confirmation.
  6. Match the carrier acceptance event to S-104-A and TRK-104-A. All three ordered units now have dispatch evidence. Customer receipt still requires a delivery event.

Under this evidence convention, “awaiting fulfilment” means preparation or dispatch remains outstanding. “Partially fulfilled” means only some required quantities have confirmed dispatch. “Dispatched” applies to the quantities covered by the handover evidence. Map your platform’s labels to these meanings explicitly.

Read vendor events by their definitions

ShipBob’s order-integration guide distinguishes the first tracking details from subsequent carrier tracking updates. Its webhook definitions say order.shipped fires after label purchase and printing. For a split order, it fires after all shipment labels are printed.

That ShipBob event doesn’t establish carrier possession. order.shipment.tracking.updated records a shipment tracking-status change. order.shipment.delivered applies to one shipment, while order.delivered means all shipments have been delivered. Keep these documented meanings beside the event names in your mapping.

Automated order fulfilment passes these confirmations between systems. Staff and carriers still handle the goods. Deduplicate repeat messages by their stable message identifier. ShipBob documents that retried messages retain their webhook-id, and its integration guide warns that events can arrive out of sequence.

Retain event times and prevent an older message from overwriting a later confirmed state. Assign an integration owner to investigate a missing acknowledgement or contradictory update. Before replaying a failed request, check whether the recipient already accepted it so the retry cannot create another shipment.

Resolve an unavailable line before promising dispatch

When F-104 cannot reserve both L2 units, pause the affected release and establish the actual available quantity. An unavailable response has several possible causes.

SignalEvidence that distinguishes itCorrection and owner
Catalogue shows two, reservation authority shows oneCompare location, variant and update timesInventory controller corrects the availability feed
Reservation request fails without a quantity resultRead the request response and existing R-104 recordIntegration owner resolves the request without making a second reservation
Stock authority records a shortageReconcile the stock ledger with a physical count and active holds at WH-AInventory controller confirms the sellable quantity and records the adjustment

Suppose that reconciliation confirms only one sellable L2 unit. Keep F-104’s original L2 quantity of two visible in its history. Record the missing unit and the decision separately.

Ask the customer to agree to a revised wait or a substitute before changing the promise. A substitute needs its own exact product and variant mapping. Permission to propose an alternative doesn’t mean permission to send it. Record the customer’s acceptance and any price adjustment against F-104.

If the missing unit is cancelled, record cancellation of one L2 unit and reduce the remaining fulfilment quantity accordingly. Match any refund to PAY-104 and that cancelled quantity. A refund request is still pending until the payment record confirms its outcome. Don’t make the customer’s applicable refund rights depend on accepting a substitute or a delay.

Before support closes the shortage, confirm the agreed remedy, payment outcome and remaining dispatch plan. For a one-unit L2 cancellation, the revised order must account for one L1 unit, one L2 unit to dispatch and one cancelled L2 unit.

Reconcile split orders and failed dispatch

A split order needs a quantity-to-shipment mapping before any parcel can close an order line. In this alternative F-104 branch, all original units are available, but L2 travels separately.

Shipment and trackingContents from F-104Confirmed evidenceOrder consequence
S-104-A, TRK-104-AL1 quantity 1Carrier acceptance recordedL1 dispatched
S-104-B, TRK-104-BL2 quantity 2Label created, acceptance unresolvedL2 still needs handover confirmation

F-104 is partially fulfilled under the stated evidence convention. The label for S-104-B cannot close L2. Once its carrier acceptance is confirmed, both shipments account for all original units. Delivery remains a separate check for each parcel.

A missing scan alone doesn’t prove the parcel stayed in the warehouse. Australia Post explains Pending tracking as an item not yet scanned into its system. It can include an item already posted. The shipping coordinator must compare the handover record with carrier evidence before deciding what failed.

Use these checks for S-104-B before creating any replacement:

  • For a printed label with no acceptance, the dispatch supervisor checks whether the parcel is still at WH-A. The shipping coordinator investigates any recorded handover.
  • For a rejected handover, retain the rejection reason. The dispatch supervisor corrects the documented parcel, address or service problem, then obtains evidence of the next accepted handover.
  • For a failed dispatch update, the integration owner compares S-104-B in both systems. If the carrier already accepted it, repair the missing record against the original shipment.
  • If a replacement is required, resolve the original parcel’s location and shipment status first. Record the replacement’s relationship to S-104-B and prevent both parcels from being released accidentally.

Close the exception when the corrected shipment record, line quantities and carrier evidence agree, or when a confirmed cancellation and payment remedy account for the undelivered goods. Sending an apology doesn’t perform that reconciliation. Customer wording for split shipments is the next task after the dispatch plan is established.

Give customers promises the records can support

Customer support can promise only the state and next action established by the relevant records. Keep a person responsible for the next unresolved event.

CaseConfirmed factsPermissible customer statementNext actionHuman owner
Normal F-104S-104-A contains L1 × 1 and L2 × 2, with carrier acceptanceYour full order has been handed to the carrierFollow carrier progress without inventing an arrival guaranteeShipping coordinator
Unavailable L2 unitOne unit missing, remedy not yet agreedOne moisturiser is unavailable. We need your decision on the offered remedyAgree the remedy and reconcile PAY-104Order operations lead
Split F-104S-104-A accepted, S-104-B only labelledYour cleanser has dispatched. The two moisturisers await confirmed handoverEstablish S-104-B’s handoverDispatch supervisor
Failed S-104-B updateCarrier acceptance confirmed, store record missingThe carrier has your moisturisers. We’re correcting the order statusRepair the original shipment recordIntegration owner

Catalogue availability comes from the inventory authority. Checkout delivery wording combines the store’s processing policy with the selected shipping service and its applicable estimates. Order support needs the customer’s authorised order record, line quantities and shipment events. These sources answer different questions.

A shopping assistant can consume authorised catalogue, policy and order facts. It must preserve their distinctions when answering a customer. An in-stock catalogue entry doesn’t establish that this order has a reservation, and a label doesn’t establish an arrival time.

Use this acceptance checklist on your own order handover:

  • Confirm that every accepted line retains its SKU, variant and quantity across store and fulfilment records.
  • Check that reservations exclude the same units from other sales channels.
  • Identify the record that permits payment release and the acknowledgement that permits preparation.
  • Match each dispatched quantity to a shipment and carrier acceptance evidence.
  • Compare event times when sources disagree, and assign stale or missing updates to a named owner.
  • Account for every unresolved unit through a dispatch plan, agreed wait, accepted substitute or recorded cancellation and payment remedy.
  • Reopen one stalled order and confirm that support’s promised next step matches the last established event.

Keep the order open while a required quantity or remedy remains unresolved. The next customer response must name the confirmed state and the person’s next action.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup