Warehouse Operations

Run daily warehouse work across inbound, picking, packing, exceptions, capacity, and staffing from one operations view. This example brings Overview and Inbound together so operations managers can find the next task without losing context.

It includes representative records such as Inbound pallet 8A delayed and Zone C pick wave ready. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Warehouse Operations
Use this template in Figr

Template facts

Screen

Workspace

Primary action

Create task

Pattern

Workspace

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Operations managers need to create task while keeping orders waiting, pick rate 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: Inbound keeps the related context close.
  • Primary action: Create task stays visible when people need it.
  • First signal: Orders waiting shows a useful value (184).
  • Second signal: Pick rate gives additional context (126/hr).
  • Sample record: Inbound pallet 8A delayed.
  • Next record: Zone C pick wave ready.

States worth designing

  • First-use empty state: say what changed, protect progress, and offer a clear next step.
  • Data panel loading: say what changed, protect progress, and offer a clear next step.
  • Stale status or conflict: say what changed, protect progress, and offer a clear next step.
  • Action completed: say what changed, protect progress, and offer a clear next step.
  • Insufficient permission: say what changed, protect progress, and offer a clear next step.
  • Network retry: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Overview → Inbound → Create task → Review outcome

Patterns used

Workspace, Overview, Inbound, contextual actions, error recovery

Why these choices work

Give the main job visual priority, keep supporting signals nearby and surface exceptions where people must act.

Pay attention to overview and inbound. People need to distinguish Inbound pallet 8A delayed from Zone C pick wave ready. Keep orders waiting 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 “Create task”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Shipment Planning, Fleet Tracking, Delivery Dispatch.

Start from this in Figr

Design a warehouse operations screen inside our existing product. Use our current components, tokens and content language. Include Overview and Inbound views, credible records like Inbound pallet 8A delayed, and a clear “Create task” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr