Returns & Refunds

Handle return eligibility, item condition, shipping, refund method, exception status, and customer communication in one workflow. The screen connects Returns and Refunds so product teams can find the “Start return” action while checking open returns and refund pending.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as #10482 · Wrong size and #10471 · Damaged item, rather than an empty visual shell.

Use this template in Figr

Template facts

Screen

Workspace

Primary action

Start return

Pattern

Workspace

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Product teams need a clear “Start return” action without losing sight of open returns, refund pending and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

Primary action: Start return is clearly available where the task happens.
Main view: Returns keeps the starting point obvious.
Connected view: Refunds supplies nearby context.
Metric: Open returns is visible with a meaningful value.
Another signal: Refund pending helps people judge what to do next.
Representative record: #10482 · Wrong size makes the example specific.
Second record: #10471 · Damaged item 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 returns without changing the layout unexpectedly.
Unavailable or restricted panel; explain the problem and preserve work.
Permission denied for refunds; clarify who can continue.
Success after choosing Start return; 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

Returns → Refunds → Start return → Review outcome

Patterns used

Workspace, Returns, Refunds, Exceptions, 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 #10482 · Wrong size with #10471 · Damaged item. Make open returns clear, then use refund pending 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 “Start return” action. The happy path alone is not enough.

Related UI examples: Orders Admin, Inventory Management, Checkout.

Start from this in Figr

Design a returns & refunds screen for our existing software product. Use our real design-system tokens, components and product language. Show Returns and Refunds, include believable records such as #10482 · Wrong size, and make start return easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr