A customer opens your order tracking page because they want an answer: Where is my order, and do I need to do anything? A carrier code such as “exception” or “label created” rarely answers either question. If the page simply sends shoppers to a carrier website, you also lose the chance to explain what is happening in your store’s own terms.
An effective ecommerce order tracking page pairs the latest reliable shipment update with a plain-English explanation, a realistic expectation, and a clear next step. Here’s how to design one that works for routine deliveries and the moments when a package is delayed, missed, or marked delivered but cannot be found.
Start with the questions customers actually have
Before choosing a layout, list the questions your page needs to answer. For most orders, customers want to know:
- Has my order been prepared and handed to the carrier?
- Where is the shipment in its journey?
- When might it arrive, and how certain is that date?
- Is there a problem or something I need to do?
- Where can I get help if the update looks wrong?
Put the answers in that order. Show the current status prominently, followed by a short explanation and the next expected event. Keep the order number, items, delivery address summary, and support option easy to find without making customers read them before they see the shipment update.
Translate shipment statuses into clear next steps
Carrier events describe what a shipping network has recorded. Your tracking page should explain what those events mean to a shopper. Keep the original carrier wording available when useful, but do not rely on it as the main message.
| Status | What to explain | Useful next step |
|---|---|---|
| Order confirmed | You received the order, but it has not shipped yet. | Show the expected dispatch window if you have one. |
| Label created | A shipping label exists; the carrier may not have the package yet. | Tell the customer when to check back or when to contact you if no scan appears. |
| In transit | The carrier has the package and is moving it through its network. | Show the latest scan and a delivery estimate only if one is available. |
| Out for delivery | The carrier expects to attempt delivery today. | Share any verified delivery instructions or carrier options. |
| Delivery exception | Something may affect delivery; the reason depends on the carrier event. | Explain the specific issue and whether the customer or your team needs to act. |
| Delivered | The carrier reports delivery, including the recorded time or location if available. | Offer clear guidance for a package the customer cannot find. |
Avoid turning every possible carrier scan into a new stage on a progress bar. A few understandable milestones help customers orient themselves; the event history can provide detail underneath. If an order ships in multiple packages, give each shipment its own status, items, and tracking information so “delivered” does not appear to describe items still in transit.
Write status messages that answer “what now?”
A useful message combines what happened, what it means, and what to do next. For example: “Your shipping label was created on Tuesday. The carrier has not recorded a pickup scan yet. We’ll show an update here when a scan becomes available.” If your dispatch process gives you a dependable handoff timeframe, add it; if not, do not invent one.
For an exception, be more specific than “There’s a delay.” If the carrier reports an unsuccessful delivery attempt, explain whether the customer should check a notice, arrange redelivery, collect the package, or wait for another attempt. Only display instructions supported by the actual carrier event and available options.
Make delivery estimates helpful without overstating certainty
An estimated delivery date is useful, but a confident-looking date based on stale information can create more confusion than no date at all. Identify where your estimate comes from—your dispatch promise, the carrier’s estimate, or your own shipping rules—and update the wording as the order progresses.
- Before carrier pickup: Separate the expected dispatch date from the estimated delivery date. They are not the same promise.
- After pickup: Show the carrier’s current estimate when available, alongside the latest recorded event.
- When the estimate passes: Do not leave an overdue date displayed as if it were still valid. Acknowledge the missed estimate and explain the next action your team will take or the point at which the customer should contact you.
Display when tracking was last updated, including the time zone if it could be ambiguous. If there is no new scan, say so plainly rather than implying the package has stopped moving. Tracking events can arrive late or skip intermediate scans.
Design the page for quick scanning on a phone
Many customers will open a tracking link from an email or message while on the move. Your page should make the essential information visible before a long event log or promotional content.
- Lead with a plain-language status. Use a short heading such as “Your package is in transit,” not only an icon or carrier code.
- Show the next expected milestone. For example, “Next update: out for delivery,” if that is a meaningful next stage. Do not imply that every intermediate scan is guaranteed.
- Keep dates and actions together. A customer should not need to scroll past the order history to find an estimated arrival or redelivery instruction.
- Make help easy to reach. Link to your contact or help page with wording that reflects the issue, such as “Get help with this delivery.”
- Use text as well as visual cues. Colors and progress icons can support the message, but status and instructions should remain understandable without them.
Place the carrier name and tracking number near the status, with a carrier tracking link if you have a valid one. Your own page should still provide enough context that customers do not have to leave it to understand the basics. On a small screen, use a simple chronological event list rather than a wide table that requires horizontal scrolling.
Plan the difficult states before you publish
The routine “in transit” view is the easiest version to design. The more valuable test is whether your order tracking page stays useful when information is incomplete or something goes wrong.
When tracking has not started
Distinguish “we are preparing your order” from “the carrier has your package.” A label-created event alone does not confirm pickup. If scans typically take time to appear in your workflow, explain that possibility without promising a precise update you cannot control.
When a shipment is delayed or needs attention
Do not treat every exception as the customer’s problem to solve. Route events based on who can act. A missing address detail may require customer input; a carrier investigation may require your support team. State the owner of the next action and provide a relevant contact path. Review exception messages regularly so they still match the carrier services you use.
When the carrier says “delivered” but the customer disagrees
Offer a short, considerate checklist: review the delivery details, check the location recorded by the carrier and any safe places the customer has authorized, and contact your team if the package is still missing. Do not make customers work through an extensive checklist before they can report a problem. Your support process should account for the possibility of an incorrect delivery scan or a genuinely missing parcel.
Connect the page to a support workflow you can maintain
A tracking page cannot explain an order accurately if its data or ownership is unclear. Map the status events your store receives from each carrier to a smaller set of customer-facing messages. Decide which events trigger a support review, which require customer action, and how your team will handle events you cannot confidently classify.
Then test real scenarios: a split shipment, a label without a pickup scan, an expired delivery estimate, an exception, and a delivered-but-missing report. Check that order emails and the tracking page use consistent wording. If a customer contacts support, your team should be able to see the same status and event history the customer sees.
Protect customer information, too. If someone can open the page without signing in, consider what order details are visible to anyone who has the link. Show only what is needed to identify the order and understand the delivery; use an appropriate verification step before allowing sensitive changes.
Measure whether the page resolves questions
Page views alone cannot tell you whether shoppers found an answer. Review the support requests that follow tracking-page visits, especially messages about missing scans, late orders, exceptions, and delivered-but-missing packages. Look for wording customers repeat: it often reveals a status that your page has not explained well enough.
You can also check whether visitors use the relevant help option, whether common carrier events map to the right message, and whether outdated estimates remain on live pages. Make one improvement at a time, then review the resulting customer questions. The aim is not to hide your contact details or eliminate support requests; it is to let customers understand their order and reach the right help when they need it.
Give customers an answer, not just a tracking number
A strong ecommerce order tracking page makes the current shipment status understandable, sets an honest expectation, and shows who should act next. Start by rewriting your most common status messages, then test the page against the exceptions that generate the most customer questions. That small exercise can reveal where your delivery communication needs more than a design change—and give you a practical plan to fix it.
Frequently Asked Questions
What should an ecommerce order tracking page include?
Include a plain-language status, the latest available update, a realistic delivery estimate when one exists, the carrier and tracking details, shipment-specific items for split orders, and a clear route to help. Add next-step guidance for delays and delivery exceptions.
What is the difference between “label created” and “in transit”?
“Label created” means shipping information has been prepared; it does not necessarily mean the carrier has received the package. “In transit” generally means the carrier has recorded the shipment moving through its network. Your page should preserve that distinction.
Should you display a delivery date if tracking has not updated?
Only if you can still support the estimate. Show when the tracking information was last updated and distinguish an estimate from a confirmed delivery appointment. If the date has passed, acknowledge it instead of continuing to display it as current.
How should a tracking page handle multiple packages?
Show a separate status, tracking number, delivery estimate, and item list for each shipment. This prevents a delivered package from making the entire order appear complete when other items are still on the way.