Public tracking
Stable tracking pages put the latest recorded state, estimate, and event history in one place.
One record. Every handoff.
A neutral shipment experience for customers, backed by the records a business already creates and updates.
Customer experience
Make shipment information easier to find and easier to trust.
Shipment Lookup brings references, delivery estimates, current status, and recorded shipment events into a consistent public view. Customers can open a shared link, enter a tracking number, or use supported order details when that lookup method is available.
Operational records
Businesses can create shipment records and update status when a real operational change is confirmed.
Data boundaries
Public responses exclude customer contact, payment, and internal operational fields.
Different entry points, one shipment view.
A customer may arrive with a tracking number, a shareable shipment link, or supported order details. The lookup method can vary, but the result is designed around the same core record: current status, shipment references, relevant route information, the delivery estimate when supplied, and a chronological history of recorded events.
Keep estimates and events distinct.
A delivery estimate describes an expected date. A recorded event describes an update supplied by the source system, business, or carrier integration. Shipment Lookup keeps those concepts separate. Time passing alone never creates a delivery scan, changes a shipment to delivered, or fills a missing gap in the timeline.
Recorded events
Shown when a source has committed an actual update.
Delivery estimates
Shown as expected timing, not proof that movement occurred.
Source failures
Shown as service problems instead of being disguised as “no shipment found.”
A private side for the business.
The business console is separate from the public tracking experience. Signed-in users can create shipment records owned by their account, add operational references and destination context, and update statuses. Account ownership and database policies limit which private records each signed-in user can access.
A public side designed for the customer.
Public shipment pages return only the information needed to understand the delivery. They do not expose customer email addresses, phone numbers, street addresses, payment details, or private notes. Tracking links are shareable, so businesses should distribute them only to intended recipients.
Designed for connected systems.
Shipment Lookup supports records created in its own console and records resolved through connected source adapters. Integrations should keep privileged credentials on the server, preserve the source system as authoritative, and publish only shipment changes that have actually been confirmed.
Stable links
Use a durable public shipment identifier so customers can return to the same page.
Private credentials
Keep privileged integration credentials off the browser and out of public tracking links.
Limited responses
Expose only the customer-facing fields required to explain shipment progress.
Built for operational truth.
Tracking software becomes less useful when it guesses. Shipment Lookup favors a smaller, clearer set of states backed by recorded information. If the source has not reported a new event, the timeline stays unchanged. If an estimate passes, it remains an estimate until a source publishes something new.