Tracking number available, parcel in transit? Explain shipping statuses accurately
A tracking number alone does not prove that a carrier has processed the parcel. Distinguish shipment data being submitted, a recorded parcel event and delivery. The actual status, its source and its timestamp determine what you can reliably tell a customer.
This distinction is useful for a POD store because order acceptance, production and transport are separate stages. A store label may describe something different from a carrier's tracking message. Avoid calling every order “shipped” as soon as a number appears somewhere in the process.
What does an electronic announcement mean?
DHL explains an electronic announcement as shipment data being submitted for a created shipping label. A later processing event at a parcel centre describes a further step. Do not infer a specific parcel location or fixed delivery date from the announcement alone.
Check the meaning with the carrier actually handling the shipment. Wording and events can differ. An automatically generated tracking link in a store notification is initially a way to access tracking information; it is not additional evidence of transport progress.
For your own order workflow, check which tracking number belongs to each shipment and which message actually comes from the carrier. Record separately what your store displays, what is confirmed for the order at Shirtee.Cloud and which parcel event appears in the original tracking record. If a mapping or update is missing, clarify it before drawing a conclusion about transport progress.
Put three separate records side by side
A reliable answer needs the order stage, the mapping between parcels and items, and the latest relevant tracking event. Record each with its source. This keeps it clear whether you are explaining a store notification, a fulfilment status or a carrier event.
| Record | Question to check | What it does not prove alone |
|---|---|---|
| Order | Which item is at which processing stage? | That every item is already in transit |
| Shipment | Which tracking number belongs to which items? | That one parcel contains the whole order |
| Tracking event | What did the carrier record, and when? | A location or delivery date beyond the stated event |
Keep the event wording and timestamp with the stated time zone. If you convert times for a shared overview, retain the original timestamp alongside the conversion. Do not confuse the time you checked the page with the time the parcel event occurred.
A worked example with two parcels
Suppose a fictional order contains two items that are shipping separately according to the confirmed shipment mapping. Parcel A has a visible carrier processing event. Parcel B has only shipment data. Saying “Your whole order is on its way” would be too broad.
One original example response is: “A carrier processing event is already visible for part of your order. The second parcel currently shows only an electronic announcement. I am checking the handover of that parcel. The two tracking links relate to different parts of your order.”
This wording is a template for that particular assumed scenario. Use it only when the facts and the stated checking action are true. Do not add an alleged reply from the warehouse or carrier that you have not actually received.
Shipment mapping also matters when a customer has received a delivery but reports a missing item. First check which items were assigned to that parcel. With multiple shipments, one delivered parcel does not automatically mean that the complete order has arrived.
Keep the remaining item and its shipment visible in the case record. Otherwise, a support conversation can be closed because one tracking number says “delivered”, while the customer's actual question concerns the other parcel.
How should you respond when a status has not changed?
An unchanged tracking status does not explain its own cause. It proves neither loss nor a particular internal process. First check that the number is complete, belongs to the correct carrier and still maps to the same shipment. Then open the current original tracking page rather than relying on an old screenshot.
Record the latest evidenced step and the information still missing. If only shipment data is visible, check handover. If a parcel event exists, investigate the subsequent route using the relevant shipping terms and contact process. Avoid inventing a single waiting period that supposedly applies to every carrier and destination.
Agree internally who owns the enquiry and when the case will next be checked. A planned review time is different from a promised delivery time. Keeping them separate makes your response more specific without inventing the transport process.
Build customer updates from verified facts
A useful status response has four parts: the confirmed position, what it means, the next actual check and the planned next contact. Include a specific contact time only if your operation can honour it.
For example: “Tracking currently shows that the shipment data has been submitted. I cannot yet see a later processing event there. I am having the handover checked and will update you after receiving a response.” This original wording describes an open enquiry. It claims neither that the parcel is lost nor that it will definitely arrive tomorrow.
The guide to support and order exceptions helps you organise these cases within your team. Also use your order-journey test to establish which messages your connection actually transfers. You can then align notifications with evidenced events before launch and answer later questions from a consistent set of facts.
AI-generated illustration of shipping stages; not a particular carrier or a documented Shirtee.Cloud workflow.