Business-owned records
Create shipments in the private console and keep each record tied to the signed-in account that owns it.
Customer tracking without a second operational world.
Give customers a clear shipment view while keeping the business record, access controls, and operational truth intact.
Stable customer links
Share a public shipment identifier that opens a limited tracking view without exposing the full private record.
Source-backed progress
Update status when your operation confirms a change instead of advancing a timeline because time passed.
A neutral tracking layer for the customer.
Shipment Lookup gives businesses a dedicated place to show delivery status without turning the public tracking page into an order-management portal. Customers get the information needed to follow the shipment, while purchase changes, refunds, returns, and account support stay with the merchant.
What a business record can contain
References
Order reference, carrier reference, and a stable public shipment identifier.
Status and history
The current shipment state plus recorded events that explain how it got there.
Operational context
Carrier, delivery estimate, and limited destination information when needed.
Separate public visibility from private operations.
The public result is intentionally narrower than the business record. Customer contact fields, payment information, private notes, and privileged credentials are not part of the public tracking response. This keeps the customer experience useful without turning a tracking link into a shortcut around account controls.
A workflow that stays understandable.
Create the shipment
Add the operational references and starting status your team actually knows.
Share the public link
Give the intended recipient a stable shipment page or tracking reference.
Publish real updates
Move the status forward when the source system or operation confirms a change.
Account ownership is part of the product.
Signed-in business users access their own shipment records through database policies. The public lookup path is separate and limited. Trusted integrations should use server-side credentials where privileged access is required and should never expose reusable secrets in browser code or tracking URLs.
Private by default
The business record can be richer than the public tracking response.
Clear responsibility
The merchant remains the place for delivery changes, returns, refunds, and product support.
Customer-ready links
Share only the shipment information needed to explain the delivery journey.