Alerts notify merchants of important system information, and provide feedback on merchant actions.
Task alerts are initiated in response to merchant actions during a specific task. Task alerts give merchants direct and immediate feedback.
The following are examples of task alerts:
- A form is successfully submitted.
- There's problem uploading something.
- The information provided is incorrect or doesn’t match the requested format.
System alerts are initiated by the application or system, independent of merchant actions. System alerts provide updates on background system status or out-of-context events that have finished.
The following are examples of system alerts:
- Lost network connection.
- A planned upgrade.
- The app subscription is expiring soon.
Alert patternsAnchor link to section titled "Alert patterns"
- Banner (system alert)
- Inline (task alert)
- Toast (task alert)
The following are common patterns available for merchant alerts:
|Pattern||Definition||Duration and interaction||Used to communicate|
Page-level alerts, often system related
Contextual alerts that are specific to a card, section, or modal
|Banners persist until merchants dismiss them, and can include an action button or link.|
|Inline||Provides merchants with feedback that’s as close to the source as possible||Inline alerts persist until merchants resolve the message.|
|Toast||Short, temporary messages that slide in and out of a page and provide succinct information.||Toast alerts without actions can disappear automatically or merchants can dismiss them.||Success|
InformationAnchor link to section titled "Information"
When you use alerts to communicate important information to merchants, you can choose from a few standard patterns.
Informational bannerAnchor to section titled "Informational banner"
Must DoInformational banners must have a blue header and contain only lower priority information that’s always dismissible.
Must Do NewBanners must be dismissible unless they contain critical information that merchants need to resolve to move forward. Dismissed banners shouldn't display again within the same user session.
When you’re communicating success, it’s important to provide feedback. That means using patterns that inform merchants when a task has been completed successfully.
Toasts inform merchants of a process that the app has performed or will perform. Toasts display temporarily, at the bottom of the interface. Toasts don’t require any merchant input to disappear, and they shouldn’t interrupt the merchant experience.
Must DoDisplay toasts in the bottom center of your app screen.
Must DoUse toasts for only short messages that confirm an action.
Must DoMake toast messages three words or fewer.
Must DoToasts are only for non-critical messages that are relevant at the moment.
Do NotDon't use toasts for error messages, except for persistent errors such as connection errors. Refer to Polaris toast best practices for more information.
Success bannersAnchor link to section titled "Success banner">/span>
Must DoMake success banners green and include next steps, if applicable.
Do NotDon’t use banners to show success messages for actions that merchants have completed. For user-initiated feedback, use success toasts instead.
Do NotDon’t use success banners if there isn’t a CTA.
When you’re communicating warnings to merchants, you have different options based on what’s causing the warning.
Warning bannersAnchor link to section titled "Warning banners"
Use warning banners to display information that needs attention or that merchants need to take action on.
Must DoMake warning banners yellow. Seeing these banners can be stressful for merchants, so use them intentionally.
Inline warning in a listAnchor to section titled "Inline warning in a list"
Must DoUse inline warnings to draw attention to exceptions in a list, and encourage action when possible.
Do NotDon’t use only color to convey a warning. Pair warning messages with a warning icon. This increases accessibility by providing additional identifiers.
When you’re communicating problems and errors, use recognizable patterns that inform merchants of the alert’s significance. Put error messages as close to the problem as possible.
Error messages are necessary when something isn’t working as expected, or when merchants should be alerted to critical disruptions.
When errors happen, they can be frustrating or even scary. Guide merchants to a solution clearly and quickly.
Must DoMake error banners red. Always tell merchants what happened and offer a path forward.
Do NotDon't use scary language, technical terms, and jargon.
Do NotDon't use humor, idioms, or other words and phrases that might not translate correctly.
Critical bannersAnchor to section titled "Critical banners"
Must DoMake critical banners red and use them sparingly.
Must DoProvide troubleshooting steps and a clear way to get support.
Inline errors in formsAnchor link to section titled "Inline errors in forms"
When you’re validating form fields like text fields, place the error message directly below the affected field.
Use red for error message text, because it’s a common convention outside of Shopify.