Findability
Start from the reference a customer actually has and make the shipment record easy to reach again.
Tracking should feel simpler than the shipment itself.
Shipment Lookup is a neutral visibility layer built to make delivery information easier to find, read, and trust.
Why it exists
Customers should not need to decode an operations system.
A delivery page should answer a few basic questions well: Is there a shipment record? What is the latest confirmed status? What does the timeline show? Is the date an estimate or an event? Who should I contact if the delivery needs action?
Context
Put the current state, estimate, and event history together so a status label is not left unexplained.
Restraint
Show useful shipment information without turning a public tracking page into a customer data page.
Neutral by design.
Shipment Lookup does not need to be the merchant, the carrier, or the checkout system to be useful. Its role is narrower: present the shipment information supplied by connected records in a consistent customer-facing experience.
Recorded information over manufactured certainty.
Delivery systems are messy. Updates can arrive late, estimates can change, and physical movement can happen before a new scan appears. Shipment Lookup does not smooth those gaps by pretending events happened. If the source has not recorded a new event, the timeline remains unchanged.
Clarity before decoration
Status, history, timing, and next actions should be understandable at a glance.
Privacy before convenience
The public view should contain enough to explain a delivery, not enough to expose a customer record.
Source truth before prediction
Estimates are useful, but they are not rewritten as confirmed events.
Built for both sides of the handoff.
Customers get a focused tracking experience. Businesses get a private place to maintain shipment records and a public link they can share. Developers get a small set of explicit behaviors for lookup, authenticated writes, and status handling.