A tracking page sits between purchase confirmation and delivery. It should help a customer answer three questions quickly: which order is this, what changed, and what should I do next?
Keep the page under the store identity
Use the store domain, logo and support path so a customer does not have to decide whether a separate tracking site is trustworthy. The page should still make the carrier and tracking reference visible.
Start with lookup, then show the timeline
Support the lookup methods your store can verify. After a match, show package, item and carrier context before listing events. Multiple packages need separate labels so one delayed shipment does not make the whole order look missing.
Write status explanations for customers
Carrier events are operational data. Add a short explanation when the event name is hard to interpret, and link to support when the timeline stops changing. Avoid turning a display-only milestone into a claim about a real carrier scan.
Test the page with real routes
Use development orders that cover more than one carrier and more than one package. Check the no-result state, delayed scans, mobile width and the support link. BestTrack provides a store-domain customer tracking page. The existing branded tracking article covers the same topic from the customer journey angle.