Task alerts
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
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 patterns
Anchor 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 |
|---|---|---|---|
| Banner | Page-level alerts, often system related or 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 |
Information
Anchor link to section titled "Information"When you use alerts to communicate important information to merchants, you can choose from a few standard patterns.
Informational banner
Anchor to section titled "Informational banner"
Must Do
Informational banners must have a blue header and contain only lower priority information that’s always dismissible.
Must Do
Banners 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 Do
Display toasts in the bottom center of your app screen.
Must Do
Use toasts for only short messages that confirm an action.
Must Do
Make toast messages three words or fewer.
Must Do
Toasts are only for non-critical messages that are relevant at the moment.
Do Not
Don't use toasts for error messages, except for persistent errors such as connection errors. Refer to Polaris toast best practices for more information.Success banners
Anchor link to section titled "Success banner">/span>
Must Do
Make success banners green and include next steps, if applicable.
Do Not
Don’t use banners to show success messages for actions that merchants have completed. For user-initiated feedback, use success toasts instead.
Do Not
Don’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 banners
Anchor link to section titled "Warning banners"Use warning banners to display information that needs attention or that merchants need to take action on.
Must Do
Make warning banners yellow. Seeing these banners can be stressful for merchants, so use them intentionally.Inline warning in a list
Anchor to section titled "Inline warning in a list"
Must Do
Use inline warnings to draw attention to exceptions in a list, and encourage action when possible.
Do Not
Don’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 Do
Make error banners red. Always tell merchants what happened and offer a path forward.
Do Not
Don't use scary language, technical terms, and jargon.
Do Not
Don't use humor, idioms, or other words and phrases that might not translate correctly.Critical banners
Anchor to section titled "Critical banners"
Must Do
Make critical banners red and use them sparingly.
Must Do
Provide troubleshooting steps and a clear way to get support.Inline errors in forms
Anchor 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.
Must Do
Place error messages directly below the affected field.
Do Not
Don’t show an error while merchants are typing, because it can cause confusion. Wait until the keyboard focus moves away from the field, and then display the error.Inline errors in lists
Anchor link to section titled "Inline errors in lists"
Must Do
Highlight an exceptional state that encourages merchants to click on a list item. Lead with what went wrong.
Do Not
Don’t use only color to convey an error. Instead, pair the error message with an error icon. This increases accessibility by providing additional identifiers.Errors in cards, sections, or modals
Anchor link to section titled "Errors in cards, sections, or modals"
Do Not
Don’t nest error messages too deeply within your app’s hierarchy. If the error applies more broadly, then place it at the top of the affected element.
