Empty state

Empty states are used when a list, table, or chart has no items or data to show. This is an opportunity to provide explanation or guidance to help merchants progress. The empty state component is intended for use when a full page in the admin is empty, and not for individual elements or areas in the interface.

Examples

Use to explain a single feature before merchants have used it.

Drag to resize example

Props

action
Action
Primary action for empty state
children
React.ReactNode
Elements to display inside empty state
footerContent
React.ReactNode
Secondary elements to display below empty state actions
heading
string
The empty state heading
imageRequired
string
The path to the image to display
imageContained
boolean
Whether or not to limit the image to the size of its container on large screens.
largeImage
string
The path to the image to display on large screens
secondaryAction
Action
Secondary action for empty state

Accessibility

Empty state illustrations are implemented as decorative images, so they use an empty alt attribute and are skipped by technologies like screen readers.

Default empty state

Use to explain a single feature before merchants have used it.

Default empty state

Accessibility

See Material Design and development documentation about accessibility for Android:

Default empty state

Use to explain a single feature before merchants have used it.

Default empty state

Accessibility

See Apple’s Human Interface Guidelines and API documentation about accessibility for iOS:

Best practices

Empty states should:

  • Orient merchants by clearly explaining the benefit and utility of a product or feature
  • Simplify a complicated experience by focusing on a few key features and benefits
  • Use simple and clear language that empowers merchants to move their business forward
  • Be encouraging and never make merchants feel unsuccessful or guilty because they haven’t used a product or feature
  • Explain the steps merchants need to take to activate a product or feature
  • Use illustrations thoughtfully as outlined in our illustration guidelines
  • Use only one primary call-to-action button

Content guidelines

Title

Empty state titles should:

  • Be action-oriented: encourage merchants to take the step required to activate the product or feature
  • Create orders and send invoices

  • Orders and invoices

Subtitle

Empty state subtitles act like body content. They should:

  • Describe or explain what’s in the empty state title or item title
  • Be conversational: include articles such as the, a, and an

Primary action

Buttons are used for the most important actions you want merchants to take. They should be:

  • Clear and predictable: merchants should be able to anticipate what will happen when they click a button. Never deceive merchants by using misleading titles.
  • Create order

  • Buy shipping label

  • New order

  • Buy

  • Action-led: buttons should always lead with a strong verb that encourages action. To provide enough context to merchants use the {verb}+{noun} format on buttons except in the case of common actions like Save, Close, Cancel, or OK.
  • Activate Apple Pay

  • View shipping settings

  • Try Apple Pay

  • View your settings

  • Scannable: avoid unnecessary words and articles such as the, an, or a.
  • Add menu item

  • Add a menu item

Secondary action

Secondary actions are used for less important actions such as “Learn more” or “Close” buttons. They should follow all the other content rules outlined for primary buttons.