Checkout Success

Confirm a successful order with order number, payment status, delivery promise, next actions, receipt access, and recommended follow-up. This example brings Confirmation and Delivery together so shoppers can find the next task without losing context.

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

Checkout Success
Use this template in Figr

Template facts

Screen

Onboarding

Primary action

View order

Pattern

Onboarding

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

Key elements

  • Main workspace: Confirmation gives users an obvious place to start.
  • Supporting view: Delivery keeps the related context close.
  • Primary action: View order stays visible when people need it.
  • First signal: Order shows a useful value (NS-48291).
  • Second signal: Total gives additional context (286).
  • Sample record: Payment confirmed.
  • Next record: Order created.

States worth designing

  • No setup steps complete: say what changed, protect progress, and offer a clear next step.
  • Step in progress: say what changed, protect progress, and offer a clear next step.
  • Identity check failed: say what changed, protect progress, and offer a clear next step.
  • Invite sent: say what changed, protect progress, and offer a clear next step.
  • Access denied: say what changed, protect progress, and offer a clear next step.
  • Setup complete: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Confirmation → Delivery → View order → Review outcome

Patterns used

Onboarding, Confirmation, Delivery, contextual actions, error recovery

Why these choices work

Make each setup step and completion state clear. Allow admins to resume without repeating the work they finished.

Pay attention to confirmation and delivery. People need to distinguish Payment confirmed from Order created. Keep order 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 “View order”. Make error recovery as clear as the happy path.

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

Start from this in Figr

Design a checkout success screen inside our existing product. Use our current components, tokens and content language. Include Confirmation and Delivery views, credible records like Payment confirmed, and a clear “View order” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr