Order Detail

Inspect a completed order with products, totals, payment, delivery address, shipment status, invoices, and return eligibility. This example brings Overview and Items together so shoppers can find the next task without losing context.

It includes representative records such as Cloud Runner Sneakers and Studio Backpack. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Order Detail
Use this template in Figr

Template facts

Screen

Detail

Primary action

Track order

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 order while keeping order total, items and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Overview gives users an obvious place to start.
  • Supporting view: Items keeps the related context close.
  • Primary action: Track order stays visible when people need it.
  • First signal: Order total shows a useful value (286).
  • Second signal: Items gives additional context (4).
  • Sample record: Cloud Runner Sneakers.
  • Next record: Studio Backpack.

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

Overview → Items → Track order → Review outcome

Patterns used

Detail, Overview, Items, 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 overview and items. People need to distinguish Cloud Runner Sneakers from Studio Backpack. Keep order total 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 order”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Order Tracking, Return Request, Delivery Options.

Start from this in Figr

Design a order detail screen inside our existing product. Use our current components, tokens and content language. Include Overview and Items views, credible records like Cloud Runner Sneakers, and a clear “Track order” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr