Understand information received, in transit, out for delivery, hold and delivered statuses. Identify the next action and verify the actual warehouse receipt.

OUR RECOMMENDATION

Decide what to do from the tracking evidence

Read the event, location and time before deciding whether to wait, send information or check receipt. Follow up against the next agreed milestone. Departure, arrival and delivery scans describe different stages; none alone confirms when the customer can use the stock.

Compare your options ↓

Choose the option that fits

  1. Tracking shows information created but no confirmed physical receipt

    Ask the origin dispatch team for the collection or warehouse receipt and match it to the shipment reference before telling the buyer that goods are moving.

    Before choosing: Electronic shipment information alone does not demonstrate handover; check whether collection happened before reporting a delay in transit.

  2. A hold or exception message requests documents or details

    Obtain the exact request and verified submission channel, assign one response owner, provide consistent information and record acknowledgement plus the provider's next expected update.

    Before choosing: A hold label does not identify its cause by itself, and submitting information is not the same as obtaining release.

  3. A delivered scan appears before the warehouse confirms stock

    Compare the delivery location and proof of receipt with warehouse records, then ask receiving staff to check package IDs, counts and visible condition against the list.

    Before choosing: Transport handover can precede internal receiving or stock release; check the remaining warehouse steps before promising immediate stock availability.

Read the event, location and time together

Start with the detailed tracking event rather than only the progress bar. Information created, cargo received and departure from origin describe different stages. Check the carrier’s official definitions; similar labels can mean different things across services.

Arrival at an airport or port also does not mean delivery to the consignee. Destination handling, import cooperation, release and final transport may remain. Tell the customer which stage is complete so an arrival update does not imply the goods are ready to use that day.

Separate information from requests for action

If the status mentions address confirmation, consignee details, additional documents or charges, read the specific action requested by the carrier. A general exception or hold label does not identify the cause on its own. Avoid describing every pause as a customs inspection without confirmation.

Assign one person to contact the provider with the tracking reference, latest event and relevant order information. Ask what action is needed and who must take it. If documents are requested, verify the official channel and required scope, submit information consistent with the existing record, and keep an acknowledgement where available.

Follow up against the next expected milestone

For each shipment, record the next confirmed milestone and its expected window, such as availability for collection or a delivery appointment. If that window passes without a useful update, contact the agreed person to confirm what changed and the revised timing.

Update frequency can vary across a longer journey. Agreeing which milestones require a notification is more useful than expecting continuous movement on a screen. Share changes affecting the customer's plan, and distinguish confirmed facts from items still awaiting the provider's response.

Verify the outcome after a delivery scan

Check whether the recorded delivery location and receipt match the transport instructions. A fulfilment centre, third-party warehouse or large company may perform internal receiving checks after the vehicle handover. Transport delivery and stock available for use are therefore not necessarily the same milestone.

Ask the recipient to check package references, counts and visible condition against the packing list, retaining any discrepancy record. Save the confirmed delivery details and unresolved issues with the order before closing the tracking task.

Use a status-to-action record

These examples use common express-shipment wording; they are not a universal translation of every carrier's events. Keep the exact original text, timestamp and location beside your operational summary. The action owner below is a suggested internal assignment, not a statement of carrier liability.

For example, UPS describes On the Way as movement through its network and Out for Delivery as the package being loaded for final delivery. Neither status confirms receipt by your warehouse. Use the selected carrier's own wording and confirm the delivery outcome before changing stock availability.

Interpret the evidence before promising the next milestone
Observed eventStill unconfirmedNext actionInternal owner
Shipment information receivedPhysical handover to the carrierCheck dispatch receipt and collection recordOrigin dispatch team
Picked up / receivedDeparture on the planned international serviceMatch piece count; monitor the agreed next eventShipment coordinator
In transit / on the wayArrival at the destination or a completed final deliveryRead the last location and next expected milestone; follow up when its agreed window passesShipment coordinator
Clearance information requestedRelease and revised delivery dateIdentify the exact document request and confirm receipt after submissionImport contact
On hold / exceptionCause, corrective action and durationAsk the provider for cause, action owner and next update timeShipment coordinator
Out for deliverySuccessful handover at the correct receiving pointKeep the receiving contact available and check any delivery instructions or access restrictionReceiving team
DeliveredCorrect receiving location, complete count and saleable stockCheck proof of delivery against warehouse receiptReceiving team

Worked update: report what is known and what comes next

Illustrative record: at 09:20 destination local time on 12 November, tracking requests an invoice clarification. The import contact sends the corrected description through the verified provider channel at 10:05 and records the case reference. That proves submission; it does not yet prove customs release.

A useful customer update is: 'The provider requested an invoice clarification. We submitted the requested information at 10:05 and are awaiting acknowledgement and the revised delivery estimate. Our shipment coordinator will follow up at the agreed next-update time.' Replace the example with actual evidence before sending.

Keep four fields open until resolved: requested action, person responsible, acknowledgement received and next follow-up time. If no update window has been agreed, ask for one rather than inventing a universal 24-hour escalation rule. After delivery, close the transport record only when the receiving team has checked the relevant package count and location.

Reconcile individual pieces and put events on one time basis

A shipment summary is only useful if you know which pieces it covers. In an original twelve-carton example, the receiver signs for eleven cartons, C01–C11, while C12 remains unresolved. Do not close the whole order because one tracking reference shows “delivered.” Compare the booking’s piece list with the delivery evidence and record the missing identifier.

Keep each original timestamp and its time zone. For example, on the same date, 16:00 at UTC+08:00 equals 08:00 UTC, while 10:00 at UTC+01:00 equals 09:00 UTC. The second event occurred one hour later despite its smaller local clock reading. Use the actual offset on that date rather than assuming a city has one offset all year.

UPS’s US definitions distinguish a created label, movement through its network, dispatch to a delivery driver and delivery. Use the provider’s exact event wording in your record; the internal worksheet below does not add a carrier status or promise a next scan.

  • Save the event text, source, package reference, local timestamp and offset; keep customer-facing updates separate from raw scans.
  • If the next agreed milestone passes, send the specific unresolved reference and evidence rather than a general request for a shipment update.
  • Update the receiver with the confirmed change, responsible contact and next review point; do not turn an estimated milestone into an actual event.
Original piece-level tracking and receiving control
Recorded factScope and evidenceOwner / next actionClose the item when
Label existsList of assigned tracking referencesShipping coordinator obtains handover evidenceReceipt of the actual goods is evidenced
Eleven cartons receivedSigned receiving record listing C01–C11Receiver checks count and condition before closing receiptPhysical count and package references are reconciled
C12 unresolvedExpected piece list, latest C12 event and exception reference if availableCoordinator asks the provider to locate C12 and sets the next review timeC12 is received or the exception is formally resolved
Whole order completeAll twelve piece records plus any damage or shortage exceptionsOrder owner reconciles the shipment and receiving systemsNo unaddressed piece or condition discrepancy remains

What to prepare

  1. Keep the original event text, timestamp and location beside your summary, with the shipment reference and latest confirmed physical handover.
  2. Ask for the next expected milestone or update window and name the person responsible for acting if that window passes.
  3. Tell the customer what is confirmed, what remains open and the next action, then reconcile delivery with the recipient before closing tracking.

Adds this checklist to your editable brief. You decide how to share it.

This is a planning guide. Requirements vary by service and destination. Confirm cargo acceptance, charges, customs requirements and delivery arrangements with your provider before shipping.

Create your shipment brief