How does parcel delivery work? 7 stages behind a shop order

You leave a stack of webshop orders at a parcel point. Your customer sees a tracking link and expects the next update to explain everything. Between that counter and the doorstep, however, the box travels with other parcels whose destinations are different. Sorting repeatedly separates those flows. Understanding that shared journey helps you answer customers without guessing where a particular vehicle is.

This guide concerns UK shop dispatches and the work after drop-off. Carrier examples were checked on 19 October 2026. They explain how a network is organised, rather than promising that your booked service follows one fixed route. Keep the carrier, service and actual tracking history attached to the order throughout.

What happens between the parcel counter and the delivery van? #

The acceptance point and the delivery address are the visible ends of a shared transport system. A parcel point can accept goods while the next collection is still ahead. Later, a destination facility can receive parcels before they are assigned to a local round. Avoid describing either location as the driver already being on the way to your customer.

Use the table to locate your next question. If only booking details exist, check whether the box actually left the packing location. If network processing is visible, check the carrier’s latest event. If an alternative collection location is shown, establish whether the customer has the collection notification. Each question belongs to a different stage.

Why can a parcel travel through a hub instead of going straight to the customer? #

A direct trip would carry your individual order to its destination. A shared parcel network combines orders, moves them together and then separates them towards delivery areas. A hub provides that separation at scale. The route that looks indirect on a map can therefore be part of the booked network rather than evidence of a mistake.

The physical scale is useful context. In its November 2021 announcement, La Poste Groupe described DPD’s Hinckley Hub 5 with 3,000 metres of conveyor and a sorting design capacity of 72,000 parcels per hour. The same announcement describes optical character recognition and video coding for address information. These are published facility specifications, not current measurements of your parcel’s processing time.

A second example uses a different unit. Evri’s September 2022 Barnsley announcement gives capacity of up to 1.1 million parcels a day for that facility. You cannot rank those networks by putting a daily figure next to an hourly one. Nor can you infer that any particular UK parcel must pass through Barnsley or Hinckley.

For your shop, the practical consequence is to preserve a readable destination and an intact package through shared handling. The hub sorts the packaged order you supplied. It does not check that the correct size of shirt went into the box. Product accuracy remains a packing task, while route allocation is a carrier task.

Does every movement create a new tracking update? #

No. A tracking page is a record of reported events, not a continuous location feed. UPS explains its UK tracking statuses: label creation records shipment details and billing information; the status changes when UPS possesses the shipment and it moves in the network. On long journeys, another scan may not occur until the destination hub.

That distinction gives you two separate checks. First establish the latest event that actually exists. Then establish whether it fits the purchased service and current estimate. An unchanged status alone cannot tell you that the box is lost, and a newly created label alone cannot tell you that the carrier has it. Neither conclusion follows from the available evidence.

Keep the wording of an exception rather than flattening everything into delayed. UPS describes an exception as an unexpected issue that may change the scheduled date. Your customer needs the revised information applicable to that shipment. They do not need an imagined explanation about a missed truck or a broken sorting belt.

Which clock should you use when a buyer asks when the order left? #

Separate the order clock, the preparation clock and the carrier clock. The first begins with the order you accepted. The second concerns picking, packing and handover. The third concerns the transport service after the relevant acceptance step. Writing a shipping email when a label is booked can make these clocks look identical to the customer even when the box is still beside your printer.

Choose customer wording that matches the event you know. If the order is packed, say so. Once handed over, record that event with its evidence. When the carrier reports a delivery round, use that carrier information. An internal workflow label should not silently turn a preparation event into a confirmed delivery date.

If someone else packs your orders, agree who records the handover and who checks exceptions. A message that merely says done leaves you asking whether it means packed, labelled or accepted. One agreed handover record is more useful than several informal messages that refer to different moments. For the earlier part of the process, see your first outsourced order step by step.

What can a local fulfilment sender actually change? #

With AirPost’s local fulfilment model, you send products and packaging to a sender. That person packs orders, prints the labels and takes the parcels to a parcel point. The published workflow keeps stock, orders and tracking in a shared conversation. It moves execution away from your own packing bench, while carrier transport still follows the chosen service.

Putting stock nearer the customers can change the origin from which an order enters a network. It does not establish a direct doorstep journey or grant access to a sorting belt. Compare the actual available service from that origin before setting a checkout promise. The network examples above do not establish which carriers are offered for an AirPost route.

Here is a hypothetical batch of 24 small parcels, using AirPost constants checked on 19 October 2026. The recommended sender fee is €2.25 per parcel and the platform component is €0.85. Together they are €3.10, or €74.40 for the batch, before carrier transport, packaging and stock replenishment. The sender fee is agreed with the sender; the recommendation is not a measured average.

This example is expressed in euros because it isolates those AirPost components. It is not a sterling postage quote or an exchange-rate calculation. Compare those execution costs with the picking, printing and parcel-point work you actually want to transfer. Buying a more expensive label by itself does not transfer those tasks.

How should you investigate a gap without creating a second shipment? #

Open the order record before purchasing replacement transport. Match its parcel reference to the actual carrier page, then look for handover evidence. Ask the person who packed it whether the physical box remains at the stock location. These checks distinguish a preparation problem from a shipment already travelling through the network.

If the parcel is in the network, use the booked service’s support route and retain the enquiry reference. Assign one person to update the customer and decide on any replacement. Keep the original tracking record open if you dispatch another item. A replacement order does not cancel a parcel already travelling towards the buyer, and duplicate arrival needs its own arrangement.

For a genuine loss or damage case, move from route explanation to the appropriate evidence process. The records you retained at each stage then become useful rather than having to be reconstructed. Our shop guide to lost or damaged parcels covers that next decision separately.