Marketplace Seller

Give sellers one operating view for listings, orders, ratings, stock, payouts, and marketplace policy issues. The screen connects Overview and Listings so growth teams can find the “Add listing” action while checking active listings and orders 30d.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Studio Lamp · Active and Linen Tote · Low stock, rather than an empty visual shell.

Use this template in Figr

Template facts

Screen

Workspace

Primary action

Add listing

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 listing” action without losing sight of active listings, orders 30d and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

Primary action: Add listing is clearly available where the task happens.
Main view: Overview keeps the starting point obvious.
Connected view: Listings supplies nearby context.
Metric: Active listings is visible with a meaningful value.
Another signal: Orders 30d helps people judge what to do next.
Representative record: Studio Lamp · Active makes the example specific.
Second record: Linen Tote · Low stock 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 overview without changing the layout unexpectedly.
Unavailable or restricted panel; explain the problem and preserve work.
Permission denied for listings; clarify who can continue.
Success after choosing Add listing; 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

Overview → Listings → Add listing → Review outcome

Patterns used

Workspace, Overview, Listings, Orders, 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 Studio Lamp · Active with Linen Tote · Low stock. Make active listings clear, then use orders 30d 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 listing” action. The happy path alone is not enough.

Related UI examples: Audience Segmentation, Vendor Management, Campaign Builder.

Start from this in Figr

Design a marketplace seller screen for our existing software product. Use our real design-system tokens, components and product language. Show Overview and Listings, include believable records such as Studio Lamp · Active, and make add listing easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr