> This page is for Developer.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.bigcommerce.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.bigcommerce.com/_mcp/server.

# Status Messages

Status messages help the user to understand what is happening in the application. Their common instances are success, warning and error messages.

## Basic guidelines

### Keep it simple

Messages should be short and to the point. Focus on what happened and what the user needs to do to move forward. When applicable, include a link to the place where the user can act upon what's being announced.

### Avoid vague language

Don't start status messages with "It seems like…" or "It looks like…." It sounds like we don't know what went wrong. There's no room for ambiguity — especially when we're trying to confirm a potentially destructive action.

> **Error**
>
> ![Don't write vague error messages](/_fern-img/c65076cf25af2a72a55cef2236b4e8db89264a3c45ae9b7964e70296f6995ba3.webp)

### Use positive language

Don't use scary or dramatic words like "bad," "forbidden," "fatal," "failed," "unresolved," "invalid" etc.

### Don't mention error codes

Error codes mean nothing to the average user.

### Avoid using "please"

Only use "please" when asking the user to go out of their way to do something they might find inconvenient.

### Avoid humor

Words and phrases like "Whoops" or "Oh no!" could be taken as inconsiderate, even insulting.

> **Error**
>
> ![Avoid humor in error messages](/_fern-img/c08d48703b633bf252a2676f6a301da621257d005a1eb5e69f6613070fede8e0.webp)

### Follow the \{verb} + \{noun} formula

Use supporting copy to provide additional context as needed.

> **Success**
>
> ![Confirmation example](/_fern-img/9dc976eca2ae495f4d283942407ef1774c292a012b32378fc5d8b47d009136c8.webp)

### Don't ask vague questions

"Are you sure?" About what? It's not clear to the user what we're trying to confirm.

> **Error**
>
> ![Don't ask vague questions](/_fern-img/d1e963428602bd79b48c7e1d01a71924243800586bed00da2b5ea04d2115dade.webp)

### Always use "Cancel"

For modal alerts, always use "cancel" when giving the user the option to back out. Never use "stop," "pause," "terminate," "never mind" or "back"

### Write descriptive buttons

When a user clicks a button, whether it's to confirm an action or cancel one, it should be clear what will happen when they click.

> **Success**
>
> ![Don't use vague CTAs](/_fern-img/9dc976eca2ae495f4d283942407ef1774c292a012b32378fc5d8b47d009136c8.webp)

### Include applicable links

Whenever possible, save the user some trouble and provide a link to the place where the user can fix the error. It's okay to include "Learn more" links to Knowledge Base articles.

> **Success**
>
> ![Banner error, with header](/_fern-img/20d6d25d53c7ef1dda3a56dca3ce2c71a66368067097021bdf0a15b100c43872.webp)