Orders Admin

Run order operations with payment, fulfillment, delivery, exception, and customer status visible without opening every order. The screen connects Orders and Fulfillment so product teams can find the “Create order” action while checking orders and unfulfilled.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Processing · 18% and Packed · 22%, rather than an empty visual shell.

Orders Admin
Use this template in Figr

Template facts

Screen

Analytics

Primary action

Create order

Pattern

Analytics

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Product teams need a clear “Create order” action without losing sight of orders, unfulfilled and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Create order is clearly available where the task happens.
  • Main view: Orders keeps the starting point obvious.
  • Connected view: Fulfillment supplies nearby context.
  • Metric: Orders is visible with a meaningful value.
  • Another signal: Unfulfilled helps people judge what to do next.
  • Representative record: Processing · 18% makes the example specific.
  • Second record: Packed · 22% shows the pattern works beyond one item.

States worth designing

  • No data for the chosen period; show what people can do instead of leaving a blank panel.
  • Loading orders without changing the layout unexpectedly.
  • Partial or delayed metrics; explain the problem and preserve work.
  • Permission denied for fulfillment; clarify who can continue.
  • Success after choosing Create order; 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

Orders → Fulfillment → Create order → Review outcome

Patterns used

Analytics, Orders, Fulfillment, Returns, accessible states, contextual actions

Why these choices work

Make time ranges, filters and metric units clear. Show the data behind each trend so readers can test what changed.

In this design, people should be able to compare Processing · 18% with Packed · 22%. Make orders clear, then use unfulfilled 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 “Create order” action. The happy path alone is not enough.

Related UI examples: Checkout, Returns & Refunds, Budget Planning.

Start from this in Figr

Design a orders admin screen for our existing software product. Use our real design-system tokens, components and product language. Show Orders and Fulfillment, include believable records such as Processing · 18%, and make create order easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr