Product Detail

Inspect one product with price, variants, stock, reviews, delivery promise, returns, and related recommendations before purchase. This example brings Overview and Details together so shoppers can find the next task without losing context.

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

Product Detail
Use this template in Figr

Template facts

Screen

Detail

Primary action

Add to cart

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 add to cart while keeping price, rating 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: Details keeps the related context close.
  • Primary action: Add to cart stays visible when people need it.
  • First signal: Price shows a useful value (128).
  • Second signal: Rating gives additional context (4.8).
  • Sample record: Cloud Runner Sneakers.
  • Next record: Size 9 · Black.

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 → Details → Add to cart → Review outcome

Patterns used

Detail, Overview, Details, 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 details. People need to distinguish Cloud Runner Sneakers from Size 9 · Black. Keep price 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 “Add to cart”. Make error recovery as clear as the happy path.

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

Start from this in Figr

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

Open Figr