Shopping Cart

Review selected products, quantities, discounts, delivery estimates, saved items, and order total before checkout. This example brings Cart and Saved for later 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.

Shopping Cart
Use this template in Figr

Template facts

Screen

Workspace

Primary action

Go to checkout

Pattern

Workspace

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

Key elements

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

States worth designing

  • First-use empty state: say what changed, protect progress, and offer a clear next step.
  • Data panel loading: say what changed, protect progress, and offer a clear next step.
  • Stale status or conflict: say what changed, protect progress, and offer a clear next step.
  • Action completed: say what changed, protect progress, and offer a clear next step.
  • Insufficient permission: say what changed, protect progress, and offer a clear next step.
  • Network retry: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Cart → Saved for later → Go to checkout → Review outcome

Patterns used

Workspace, Cart, Saved for later, contextual actions, error recovery

Why these choices work

Give the main job visual priority, keep supporting signals nearby and surface exceptions where people must act.

Pay attention to cart and saved for later. People need to distinguish Cloud Runner Sneakers from Studio Backpack. Keep items 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 “Go to checkout”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Product Detail, Wishlist, Product Listing.

Start from this in Figr

Design a shopping cart screen inside our existing product. Use our current components, tokens and content language. Include Cart and Saved for later views, credible records like Cloud Runner Sneakers, and a clear “Go to checkout” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr