Account Management

A Channel should ideally be an Embedded App. If you are using our Polaris React library for your embedded app experience, we've provided code snippets that powers this. We've provided some mock-ups here of how your application could look - these are subject to change! 

Empty State

  1. When a merchant arrives at your Channel for the first time, ask them to connect their account.
  2. Get merchants excited about your Channel by showing a value statement and illustration.

Account Connection

The popup that triggers when you hit Connect Account should be clearly branded to you. This is to inform the merchant which account credentials to use and who to contact with questions over onboarding. 

Account Qualifying

If you have special requirements for your channel, you can take merchants through a brief setup flow. We recommend a maximum of 3-4 steps to keep friction to a minimum. Typically, these might be only selling in particular categories, methods of fulfillment or geographies you serve.

  1. We advise you provide a link to your support to field questions, especially with a more complicated clarifying flow
  2. The language "Complete Setup" makes it clear they are completing the setup portion only, especially if you have a review period.

Polaris is fully responsive to support the growing number of merchants who complete tasks on mobile. It's important that any dialogs in your app also work well on mobile devices.

Account Review

Once a merchant has completed setup, if required they will see a banner telling them you are reviewing their application.  Always try to include a timeframe in the banner, so merchant know how long they may have to wait. We recommend a max of 48 hours. Less is better.

If the account connection fails for any reason, we show a red alert banner with clear reasoning and path to resolution.  An appeals process is important because it gives merchants an avenue to leave feedback, deterring them from leaving a low app rating on the app store. 

Connection Success 

 

After the merchant successfully connects their account, they should see a success banner with clear next steps that a merchant should take to start using the channel. 

Your embedded app should become a place to set preferences and communicate important information to the merchant. 

You should then prompt them what to do next. If there's particular configuration that needs to happen, you should use a card for each configuration item 

If the merchant has to take an action that is irreversible, confirm with a modal and large red button to give them a loud warning. For example, disconnecting their account and thereby removing your ability to accept orders from your channel is a case where we'd use a confirmation.