Product Listing

Browse a catalog with category, price, availability, rating, filters, sorting, and quick actions without losing shopping context. This example brings All products and New arrivals 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.

Product Listing
Use this template in Figr

Template facts

Screen

Table

Primary action

View 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 view cart while keeping products, in stock and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: All products gives users an obvious place to start.
  • Supporting view: New arrivals keeps the related context close.
  • Primary action: View cart stays visible when people need it.
  • First signal: Products shows a useful value (248).
  • Second signal: In stock gives additional context (231).
  • 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

All products → New arrivals → View cart → Review outcome

Patterns used

Table, All products, New arrivals, 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 all products and new arrivals. People need to distinguish Cloud Runner Sneakers from Studio Backpack. Keep products 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 cart”. Make error recovery as clear as the happy path.

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

Start from this in Figr

Design a product listing screen inside our existing product. Use our current components, tokens and content language. Include All products and New arrivals views, credible records like Cloud Runner Sneakers, and a clear “View cart” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr