Supplier Portal

Give suppliers a shared view of purchase orders, delivery commitments, invoices, documents, disputes, and account actions. This example brings Overview and Orders together so operations managers can find the next task without losing context.

It includes representative records such as PO-4821 hardware shipment and Invoice INV-884 due. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Supplier Portal
Use this template in Figr

Template facts

Screen

Workspace

Primary action

Upload document

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 upload document while keeping open orders, due this week 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: Orders keeps the related context close.
  • Primary action: Upload document stays visible when people need it.
  • First signal: Open orders shows a useful value (12).
  • Second signal: Due this week gives additional context (5).
  • Sample record: PO-4821 hardware shipment.
  • Next record: Invoice INV-884 due.

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 → Orders → Upload document → Review outcome

Patterns used

Workspace, Overview, Orders, 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 orders. People need to distinguish PO-4821 hardware shipment from Invoice INV-884 due. Keep open orders 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 “Upload document”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Receiving Inventory, Quality Inspection, Purchase Orders.

Start from this in Figr

Design a supplier portal screen inside our existing product. Use our current components, tokens and content language. Include Overview and Orders views, credible records like PO-4821 hardware shipment, and a clear “Upload document” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr