Inventory Management

Monitor stock, incoming inventory, sell-through, low-stock risk, and fulfillment locations before availability becomes a customer problem. The screen connects Inventory and Products so product teams can find the “Add stock” action while checking units on hand and low stock.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Studio Lamp · 84% sold and Linen Tote · 72% sold, rather than an empty visual shell.

Inventory Management

Template facts

Screen

Analytics

Primary action

Add stock

Pattern

Analytics

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Product teams need a clear “Add stock” action without losing sight of units on hand, low stock and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Add stock is clearly available where the task happens.
  • Main view: Inventory keeps the starting point obvious.
  • Connected view: Products supplies nearby context.
  • Metric: Units on hand is visible with a meaningful value.
  • Another signal: Low stock helps people judge what to do next.
  • Representative record: Studio Lamp · 84% sold makes the example specific.
  • Second record: Linen Tote · 72% sold shows the pattern works beyond one item.

States worth designing

  • No data for the chosen period; show what people can do instead of leaving a blank panel.
  • Loading inventory without changing the layout unexpectedly.
  • Partial or delayed metrics; explain the problem and preserve work.
  • Permission denied for products; clarify who can continue.
  • Success after choosing Add stock; confirm the result and the next step.
  • Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

Inventory → Products → Add stock → Review outcome

Patterns used

Analytics, Inventory, Products, Locations, accessible states, contextual actions

Why these choices work

Make time ranges, filters and metric units clear. Show the data behind each trend so readers can test what changed.

In this design, people should be able to compare Studio Lamp · 84% sold with Linen Tote · 72% sold. Make units on hand clear, then use low stock to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “Add stock” action. The happy path alone is not enough.

Related UI examples: Returns & Refunds, Payouts, Orders Admin.

Start from this in Figr

Design a inventory management screen for our existing software product. Use our real design-system tokens, components and product language. Show Inventory and Products, include believable records such as Studio Lamp · 84% sold, and make add stock easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr