> 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/shopify/error-notifications.md).

# Shopify Error Notifications

Get an email alert as soon as customers hit a configurator or cart error. Learn how critical alerts and optional diagnostics work and how to set them up.

Once you've installed the Mimeeq app in your Shopify store, you can enable instant email notifications. They alert you when customers experience issues with the 3D configurator or with adding a product to cart. This helps you quickly identify and resolve problems that could impact your sales, ensuring a smooth shopping experience for your customers.

{% hint style="warning" %}
**Action required:** if you have the Mimeeq app installed in your Shopify store, you must configure a primary email address to receive error notifications. This applies to all store admins. Without a primary email, no email alerts are sent when issues occur. Errors are still logged in the Error Recovery Center.
{% endhint %}

For each notification category, you choose what happens when the error occurs:

* **Track only:** a record is created in the Error Recovery Center with the error details.
* **Track and email:** a record is created in the Error Recovery Center and you also receive an instant email notification.

The customer error form is separate from notifications. When the form is shown on your storefront, customers who hit an error can leave their contact information, and it's added to the error record.

{% hint style="info" %}
To learn more about how the Error Recovery Center works and how to use it, see [Shopify Error Recovery Center](/commerce-and-integrations/shopify/error-recovery.md). To customise the appearance and messages of the error form on your storefront, see [Shopify Theme Extension](/commerce-and-integrations/shopify/theme-extension.md).
{% endhint %}

***

## Notification groups

The **Notifications** page splits notifications into two groups: **Critical alerts** and **Optional diagnostics**.

<table><thead><tr><th width="76.1953125">#</th><th>Group</th><th>What it covers</th><th>Default</th></tr></thead><tbody><tr><td>1</td><td><strong>Critical alerts</strong></td><td>Issues that stop a customer from completing a purchase</td><td>On. We recommend keeping these on.</td></tr><tr><td>2</td><td><strong>Optional diagnostics</strong></td><td>Deeper technical signals for troubleshooting a specific customer issue or setup problem, like a configurator that won't load, a missing shortcode, or a customer data error</td><td>Off. Turn on individually as needed.</td></tr></tbody></table>

***

## Critical alerts

Critical alerts cover issues that block a sale. They are turned on by default and marked **Recommended** on the **Notifications** page. We recommend keeping them on.

<table><thead><tr><th width="76.1953125">#</th><th>Error type</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td><strong>Product price missing</strong></td><td>A customer tried to add a product with no price set, or with a $0 price, usually indicating a pricing setup issue in your catalogue</td></tr><tr><td>2</td><td><strong>Add to cart failed</strong></td><td>A customer couldn't add a configured product to cart due to a connection or configuration problem between Mimeeq and Shopify. This also covers a selected variant that doesn't exist in the product catalogue</td></tr><tr><td>3</td><td><strong>Variant not available</strong></td><td>A customer selected a product variant that is currently unavailable or out of stock</td></tr></tbody></table>

***

## Optional diagnostics

Optional diagnostics are off by default. Turn them on one at a time when you need to troubleshoot a specific customer issue or validate a new setup.

{% hint style="warning" %}
**These reports don't always mean something is wrong.** They can include isolated loading failures caused by unstable connections, ad blockers, privacy settings, network security restrictions, or temporary service interruptions. A single report doesn't necessarily point to an ongoing problem with your store configuration or Mimeeq. On busy stores, enabling all of these at once can mean a high volume of notifications. We recommend turning them on temporarily to validate a setup, then off again if they get noisy.
{% endhint %}

<table><thead><tr><th width="76.1953125">#</th><th>Error type</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td><strong>Configurator failed to initialize</strong></td><td>The configurator failed to load or become ready, caused by script errors, missing templates, or a custom interface that couldn't be loaded</td></tr><tr><td>2</td><td><strong>Product failed to load</strong></td><td>The configurator couldn't load product data, for example due to a missing or deleted product, an invalid shortcode, a server error, or invalid product data</td></tr><tr><td>3</td><td><strong>Customer data unavailable</strong></td><td>Required Mimeeq account metadata couldn't be retrieved, possibly due to a temporary service outage. This may affect personalised pricing or saved configurations</td></tr><tr><td>4</td><td><strong>Product not linked to configurator</strong></td><td>The configurator embed is missing a product shortcode, or the shortcode lookup returned no result, usually caused by an incorrect page setup</td></tr></tbody></table>

***

## Set up notifications

{% stepper %}
{% step %}

### Configure the primary email

The primary email receives all error notifications and is **required** for email alerts. It doesn't affect tracking in the Error Recovery Center.

1. Navigate to the **Notifications** settings.
2. Enter your primary email address in the **Primary email settings** field.

This email receives all email notifications by default.

![Notifications settings with the primary email address field](https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2Fx9PRgXIQeJF4O5leh5mW%2Fshopify-notification-v2-new-ne_19eiqu2.png?alt=media)
{% endstep %}

{% step %}

### Review critical alerts and turn on optional diagnostics

The **Notifications** page has **seven categories**: three under **Critical alerts** and four under **Optional diagnostics**. Some categories cover more than one underlying error type, which you can see in more detail in the [Shopify Error Recovery Center](/commerce-and-integrations/shopify/error-recovery.md).

Each category has a toggle to turn it on or off, and two controls:

* **Track in Error Recovery Center:** logs the error so you can review it later
* **Send email notification:** sends an alert to your team when the error occurs

**Critical alerts** are already on. Leave them on unless you have a specific reason to turn one off. **Optional diagnostics** are off; use the toggle to turn on only the ones you need.

You can also uncheck the two controls individually to mix and match, with one thing to keep in mind:

{% hint style="warning" %}
Unchecking **Send email notification** also turns off tracking. To keep tracking without emails, uncheck **Send email notification**, then re-check **Track in Error Recovery Center**, and click **Save**.
{% endhint %}

![Notification category cards with Track in Error Recovery Center and Send email notification checkboxes](https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2FlTB4Ccl595lgiBlY0y2F%2Ferror-new-email.png?alt=media\&token=ad808447-9f0b-45b5-9727-c6e892e04771)
{% endstep %}

{% step %}

### Add recipients and save

You can add extra recipients (comma-separated) to any category. The primary email is always included in all notifications.

Changes take effect after you click **Save**. **Discard** resets to the last saved state.

{% hint style="warning" %}
**Important:** zero price notifications are only sent when **Block adding to cart** is selected in the **Zero Price Product Handling** settings.
{% endhint %}

![Zero Price Product Handling setting with Block adding to cart selected](https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2FFoJ5zBsrCFfGIhNA3JLd%2Fshopify-notification2-v2-new_hc2ge7.png?alt=media)
{% endstep %}
{% endstepper %}

***

## Example email structure

Each notification email contains:

* **Error type:** e.g. "Zero Price Error", "Configurator Not Loading"
* **Timestamp:** when the error occurred
* **Product URL:** direct link to the affected product
* **Error ID:** unique identifier for tracking
* **Configuration details:** short and long configuration code
* **Customer details:** if provided by the customer

![Example error notification email with error type, timestamp, product URL and configuration details](https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2FjGsyokw6t3loRRxNl4xr%2Fshopify-email-image-4_1g9g80u.png?alt=media)

***

## Best practices

1. **Keep critical alerts on** so you hear about every issue that blocks a purchase.
2. **Use optional diagnostics temporarily** to validate a new setup or investigate a specific customer report, then turn them off if they get noisy.
3. **Test your notifications** after setup to ensure emails are delivered.
4. **Add team members** who need immediate awareness of issues.
5. **Check spam folders** if notifications aren't received.
6. **Review the Error Recovery Center** regularly for patterns.

***

## 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>Shopify Error Recovery Center</strong></td><td>Track errors and follow up with affected customers.</td><td><a href="/commerce-and-integrations/shopify/error-recovery.md">Shopify Error Recovery Center</a></td></tr><tr><td><strong>Shopify Admin Settings</strong></td><td>Connect your API key, products and cart settings.</td><td><a href="/commerce-and-integrations/shopify/admin-settings.md">Shopify Admin Settings</a></td></tr><tr><td><strong>Shopify Theme Extension</strong></td><td>Add configurators and buttons to your storefront theme.</td><td><a href="/commerce-and-integrations/shopify/theme-extension.md">Shopify Theme Extension</a></td></tr><tr><td><strong>Changelog</strong></td><td>See the latest Shopify app features, improvements and fixes.</td><td><a href="/commerce-and-integrations/shopify/changelog.md">Changelog</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/shopify/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.