> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-commerce/how-to-guides/how-to-test-email-templates.md).

# Test Your Email templates

Learn how to test your email templates.

Want to see how your email templates look before sending them to the real customers? Umbraco Commerce 16.2.0 supports testing your email templates.

{% hint style="info" %}
As of now, only templates under the **Cart**, **Order**, **Gift Card**, and **Discount** categories can be tested using the steps below.
{% endhint %}

## Steps

1. Go to *Umbraco Backoffice* > *Settings*.
2. Select a store name.
3. Navigate to the *Email Templates* section.
4. Open the template you want to test.

![Email Template Details screen in Umbraco backoffice](https://961659879-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FP5oHq9zZ5dr8blWsnRJc%2Fuploads%2Fgit-blob-c562d5fd190a256158b14201e3d28a77c21874d8%2F0.email-template-details.png?alt=media)

5. Click the *Send Test Email* button.
6. Fill in the fields in the modal, and **make sure that the recipient is a test email address**.

![The "Send Test Email" modal](https://961659879-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FP5oHq9zZ5dr8blWsnRJc%2Fuploads%2Fgit-blob-58dcf70278f8f840b77f8872f43b550247f54f97%2F1.send-test-email-modal.png?alt=media)

![Order entity picker in the "Send test email" modal](https://961659879-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FP5oHq9zZ5dr8blWsnRJc%2Fuploads%2Fgit-blob-eb8f0e64e8d092e85e2e680cb6765dd961abf4e7%2F2.order-entity-picker.png?alt=media)

7. Click the *Send* button.

An email with the information you provided will be sent to the test email address shortly.


---

# 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://docs.umbraco.com/umbraco-commerce/how-to-guides/how-to-test-email-templates.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.