Purchase Orders

Track purchase orders with supplier, amount, requester, delivery date, approval, receiving, and payment status in one operations table. This example brings Open and Approved together so operations managers can find the next task without losing context.

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

Purchase Orders
Use this template in Figr

Template facts

Screen

Table

Primary action

Create PO

Pattern

Table

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Operations managers need to create po while keeping open pos, value and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Open gives users an obvious place to start.
  • Supporting view: Approved keeps the related context close.
  • Primary action: Create PO stays visible when people need it.
  • First signal: Open POs shows a useful value (48).
  • Second signal: Value gives additional context (1.84M).
  • Sample record: PO-4821 · Cloud hardware.
  • Next record: PO-4819 · Research software.

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

Open → Approved → Create PO → Review outcome

Patterns used

Table, Open, Approved, 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 open and approved. People need to distinguish PO-4821 · Cloud hardware from PO-4819 · Research software. Keep open pos 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 PO”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Procurement Requests, Receiving Inventory, Delivery Dispatch.

Start from this in Figr

Design a purchase orders screen inside our existing product. Use our current components, tokens and content language. Include Open and Approved views, credible records like PO-4821 · Cloud hardware, and a clear “Create PO” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr