> For the complete documentation index, see [llms.txt](https://help.mimeeq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.mimeeq.com/commerce-and-integrations/woocommerce/error-notifications.md).

# WooCommerce Error Notifications

Hear about configurator and cart problems before customers complain. Learn which errors trigger an email and how to route each type to the right people.

The plugin can email your team automatically whenever a customer runs into one of a handful of technical problems with the 3D configurator or the cart. Every notification is also recorded in the [Error Recovery Center](/commerce-and-integrations/woocommerce/error-recovery.md), so you'll have a record even if an email gets missed.

{% hint style="info" %}
To get started, add at least one email address.
{% endhint %}

***

## Problems that can trigger an email

<table><thead><tr><th width="65.5078125">#</th><th>Problem</th><th>What it means</th></tr></thead><tbody><tr><td>1</td><td><strong>Zero price</strong></td><td>The product loaded without a price (only sent if your settings are configured to block adding it to the cart in that situation)</td></tr><tr><td>2</td><td><strong>Configurator not loading</strong></td><td>The 3D configurator didn't finish loading on the page</td></tr><tr><td>3</td><td><strong>Add to cart error</strong></td><td>Something went wrong while adding the configured product to the cart</td></tr><tr><td>4</td><td><strong>Variant not available</strong></td><td>The selected variant isn't available</td></tr></tbody></table>

***

## Setting it up

{% stepper %}
{% step %}

### Add your main email address

1. Go to **WP Admin → Mimeeq → Notifications**
2. Enter your main email address
3. This address is used for every notification type by default
   {% endstep %}

{% step %}

### Turn on the problem types you care about

Each of the four problem types above can be switched on or off independently. Each can also have its own list of email addresses (separate multiple addresses with a comma) — handy if, say, pricing errors should go to one person and technical errors to another.

![Notifications settings screen with main email address and per-type recipient lists](https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2FWLY5ZWa78OalMMt6nqzU%2F05-error-notifications-01-noti_13gd0u5.png?alt=media)
{% endstep %}
{% endstepper %}

***

## What's in the email

Each notification includes:

* Which type of problem occurred
* When it happened
* The product involved, if known
* A reference ID (the same one you'll find in the Error Recovery Center, if you want to look up more detail)

***

## Best practices

* **Send yourself a test:** after setting this up, confirm emails actually arrive
* **Check spam folders:** if you don't see anything land
* **Add whoever's responsible:** for each type of issue — you don't have to send everything to one inbox
* **Check the Error Recovery Center now and then:** not every problem type triggers an email

***

## Related articles

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Error Recovery</strong></td><td>Review, filter and resolve logged configurator and cart errors.</td><td><a href="/commerce-and-integrations/woocommerce/error-recovery.md">WooCommerce Error Recovery</a></td></tr><tr><td><strong>WooCommerce Storefront Setup</strong></td><td>Add the configurator with Gutenberg blocks, Elementor or shortcodes.</td><td><a href="/commerce-and-integrations/woocommerce/storefront-setup.md">WooCommerce Storefront Setup</a></td></tr><tr><td><strong>WooCommerce Admin Settings</strong></td><td>Configure API, cart, product naming and sync settings.</td><td><a href="/commerce-and-integrations/woocommerce/admin-settings.md">WooCommerce Admin Settings</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.mimeeq.com/commerce-and-integrations/woocommerce/error-notifications.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.