Order Tracking

Track one shipment from confirmation through delivery with carrier events, estimated arrival, address, package contents, and support actions. This example brings Status and Timeline together so shoppers can find the next task without losing context.

It includes representative records such as Order confirmed and Packed at Bengaluru hub. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Order Tracking
Use this template in Figr

Template facts

Screen

Detail

Primary action

Track package

Pattern

Detail

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Finance and operations teams need to track package while keeping status, eta and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Status gives users an obvious place to start.
  • Supporting view: Timeline keeps the related context close.
  • Primary action: Track package stays visible when people need it.
  • First signal: Status shows a useful value (In transit).
  • Second signal: ETA gives additional context (Sep 18).
  • Sample record: Order confirmed.
  • Next record: Packed at Bengaluru hub.

States worth designing

  • Record not available: say what changed, protect progress, and offer a clear next step.
  • Details refreshing: say what changed, protect progress, and offer a clear next step.
  • Incomplete evidence: say what changed, protect progress, and offer a clear next step.
  • Action complete: say what changed, protect progress, and offer a clear next step.
  • Record read-only: say what changed, protect progress, and offer a clear next step.
  • History not available: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Status → Timeline → Track package → Review outcome

Patterns used

Detail, Status, Timeline, contextual actions, error recovery

Why these choices work

Emphasize record status, next action and recent changes. Put secondary history nearby without competing with the primary task.

Pay attention to status and timeline. People need to distinguish Order confirmed from Packed at Bengaluru hub. Keep status visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Track package”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Delivery Options, Order Detail, Address Book.

Start from this in Figr

Design a order tracking screen inside our existing product. Use our current components, tokens and content language. Include Status and Timeline views, credible records like Order confirmed, and a clear “Track package” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr