Page actions

Page actions let merchants take key actions at the bottom of specific pages in the interface. This is important because sometimes the primary call to action is hard to access when merchants are at the bottom of a page.


Used on a resource page (e.g. individual order or product page) to let merchants take key actions at the bottom of the page. Usually, the primary action is Save and the secondary action is Delete.

Drag to resize example
    content: 'Save',
    content: 'Delete',
The primary action for the page
The secondary actions for the page


Put the merchant first by identifying the problem they face and the component that helps them solve it.


Merchants need to be able to take important page actions, even after they’ve scrolled to the bottom of the page.


Page actions show at the bottom of pages so that merchants don’t need to scroll up to take important actions.

Best practices

Page actions should:

  • Include a single primary action on the right. It should be the same as the primary action that shows in the title bar at the top of the page.
  • Include a maximum of two secondary actions, but doesn’t have to include any secondary actions.

Content guidelines

Call to action buttons

Buttons should be:

  • Clear and predictable: merchants should be able to anticipate what will happen when they click a button. Never deceive a merchant by mislabeling a button.
  • 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