FIGR / UI TEMPLATE

Receiving Inventory

Receive inbound inventory against purchase orders with quantity checks, damage notes, lot details, storage location, and discrepancy handling. This example brings Expected and Receiving together so operations managers can find the next task without losing context.

It includes representative records such as PO-4821 · 240 units and PO-4819 · 60 units. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Receiving Inventory

BUILD ON THIS

Make it yours in Figr.

Explore this screen, then bring in your own product and design system to shape the next version.

Use this template ↗

At a glance

Screen

Table

Primary action

Receive shipment

Pattern

Table

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps with

Operations managers need to receive shipment while keeping expected today, receiving and exceptions visible. The interface should show what changed and who should act next.

What to look for

  • Main workspace: Expected gives users an obvious place to start.
  • Supporting view: Receiving keeps the related context close.
  • Primary action: Receive shipment stays visible when people need it.
  • First signal: Expected today shows a useful value (18).
  • Second signal: Receiving gives additional context (6).
  • Sample record: PO-4821 · 240 units.
  • Next record: PO-4819 · 60 units.

States to consider

  • 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 it fits

Expected → Receiving → Receive shipment → Review outcome

Patterns in this screen

Table, Expected, Receiving, contextual actions, error recovery

UX choices to review

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

Pay attention to expected and receiving. People need to distinguish PO-4821 · 240 units from PO-4819 · 60 units. Keep expected today 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 “Receive shipment”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Purchase Orders, Supplier Portal, Procurement Requests.

Try a similar screen in Figr

Design a receiving inventory screen inside our existing product. Use our current components, tokens and content language. Include Expected and Receiving views, credible records like PO-4821 · 240 units, and a clear “Receive shipment” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr

KEEP EXPLORING

More ways to approach your next screen.

Browse other product UI examples, compare patterns, and pick the direction that suits your product.

Explore all 500 templates ↗