Order tracking
The customer-facing timeline that answers where an order is, what shipped, and when each package should arrive.
See it
What it is
Order tracking is the customer-facing record of a shipment moving from label created to delivered. It combines the carrier's tracking number and scan events with the store's own fulfillment context, then presents plain updates on an order status page, in email, or by text. Domino's Pizza Tracker set the expectation for what that progress bar should feel like.
Reach for it as soon as orders leave your operation and enter a carrier network. Show each shipment separately when an order splits, include the items inside it, and link to the carrier for the raw detail without forcing the shopper to decode carrier status codes.
Gotcha: carrier events arrive late, repeat, disappear, and sometimes land out of order. Keep the raw events, deduplicate them, and derive the visible state from event timestamps instead of webhook arrival order. Do not label a package delivered because its estimated date passed; only a real delivery event should do that.
Ask AI for it
Build an order-tracking page backed by EasyPost tracker webhooks, with the signature verified before processing. Store every event with the carrier event ID, tracking number, raw status, location, and an RFC 3339 occurrence timestamp; make ingestion idempotent on carrier plus event ID. Normalize raw statuses into label_created, in_transit, out_for_delivery, delivered, and exception, but retain the original payload for support. Render one card per shipment with its line items, carrier link, estimated arrival window, latest plain-language status, and a chronological timeline. Sort by the occurrence timestamp, not webhook receipt time, and announce new events through a polite ARIA live region. Show a specific recovery message for exceptions and never infer delivered from an expired estimate.