Seller Onboarding

Onboard a marketplace seller through business details, identity, payout account, tax information, catalog readiness, and approval status. This example brings Business and Identity together so administrators and growth teams can find the next task without losing context.

It includes representative records such as Add business information and Verify seller identity. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Seller Onboarding
Use this template in Figr

Template facts

Screen

Onboarding

Primary action

Continue setup

Pattern

Onboarding

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product and growth teams need to continue setup while keeping setup, documents and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Business gives users an obvious place to start.
  • Supporting view: Identity keeps the related context close.
  • Primary action: Continue setup stays visible when people need it.
  • First signal: Setup shows a useful value (64%).
  • Second signal: Documents gives additional context (4 of 5).
  • Sample record: Add business information.
  • Next record: Verify seller identity.

States worth designing

  • No setup steps complete: say what changed, protect progress, and offer a clear next step.
  • Step in progress: say what changed, protect progress, and offer a clear next step.
  • Identity check failed: say what changed, protect progress, and offer a clear next step.
  • Invite sent: say what changed, protect progress, and offer a clear next step.
  • Access denied: say what changed, protect progress, and offer a clear next step.
  • Setup complete: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Business → Identity → Continue setup → Review outcome

Patterns used

Onboarding, Business, Identity, contextual actions, error recovery

Why these choices work

Make each setup step and completion state clear. Allow admins to resume without repeating the work they finished.

Pay attention to business and identity. People need to distinguish Add business information from Verify seller identity. Keep setup 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 “Continue setup”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Loyalty Program, Product Reviews Moderation, Referral Program.

Start from this in Figr

Design a seller onboarding screen inside our existing product. Use our current components, tokens and content language. Include Business and Identity views, credible records like Add business information, and a clear “Continue setup” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr