Wishlist

Save products for later with price movement, stock status, selected variant, and quick move-to-cart actions. This example brings Wishlist and Price drops 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.

Wishlist
Use this template in Figr

Template facts

Screen

Table

Primary action

Move to cart

Pattern

Table

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 move to cart while keeping saved, price drops and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Wishlist gives users an obvious place to start.
  • Supporting view: Price drops keeps the related context close.
  • Primary action: Move to cart stays visible when people need it.
  • First signal: Saved shows a useful value (17).
  • Second signal: Price drops gives additional context (4).
  • Sample record: Cloud Runner Sneakers.
  • Next record: Studio Backpack.

States worth designing

  • No rows in current filters: say what changed, protect progress, and offer a clear next step.
  • Sorting or bulk action in progress: say what changed, protect progress, and offer a clear next step.
  • Row update conflict: say what changed, protect progress, and offer a clear next step.
  • Bulk update partly failed: say what changed, protect progress, and offer a clear next step.
  • Restricted columns: say what changed, protect progress, and offer a clear next step.
  • Export complete: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Wishlist → Price drops → Move to cart → Review outcome

Patterns used

Table, Wishlist, Price drops, contextual actions, error recovery

Why these choices work

Prioritize columns that help people act. Keep filters when readers drill into details and return; show who owns each unresolved exception.

Pay attention to wishlist and price drops. People need to distinguish Cloud Runner Sneakers from Studio Backpack. Keep saved 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 “Move to cart”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Shopping Cart, Address Book, Product Detail.

Start from this in Figr

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

Open Figr