Vendor Management

Manage vendors by status, contract, spend, risk, owner, renewal date, and open actions without splitting context across systems. The screen connects Vendors and Contracts so growth teams can find the “Add vendor” action while checking active vendors and renewals 90d.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as AWS · Active and Figma · Renewal due, rather than an empty visual shell.

Vendor Management
Use this template in Figr

Template facts

Screen

Workspace

Primary action

Add vendor

Pattern

Workspace

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Growth teams need a clear “Add vendor” action without losing sight of active vendors, renewals 90d and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Add vendor is clearly available where the task happens.
  • Main view: Vendors keeps the starting point obvious.
  • Connected view: Contracts supplies nearby context.
  • Metric: Active vendors is visible with a meaningful value.
  • Another signal: Renewals 90d helps people judge what to do next.
  • Representative record: AWS · Active makes the example specific.
  • Second record: Figma · Renewal due shows the pattern works beyond one item.

States worth designing

  • First-use workspace; show what people can do instead of leaving a blank panel.
  • Loading vendors without changing the layout unexpectedly.
  • Unavailable or restricted panel; explain the problem and preserve work.
  • Permission denied for contracts; clarify who can continue.
  • Success after choosing Add vendor; 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

Vendors → Contracts → Add vendor → Review outcome

Patterns used

Workspace, Vendors, Contracts, Risk, accessible states, contextual actions

Why these choices work

Keep the main job visible above supporting panels. Group related controls and surface exceptions where people act.

In this design, people should be able to compare AWS · Active with Figma · Renewal due. Make active vendors clear, then use renewals 90d 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 vendor” action. The happy path alone is not enough.

Related UI examples: Marketplace Seller, Booking Admin, Audience Segmentation.

Start from this in Figr

Design a vendor management screen for our existing software product. Use our real design-system tokens, components and product language. Show Vendors and Contracts, include believable records such as AWS · Active, and make add vendor easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr