> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/using-peakcommerce/system-communications/email-templates.md). # Notification Templates PeakCommerce reacts to platform events — a subscription is renewed, an order is paid, a product is added — by sending a notification. **Notification Templates** let you decide which of those events produce a message, on which channel, and exactly what the customer sees. Manage them from the **user menu** (your name, bottom-left) → **Settings → Notification Templates**: add a template, edit its subject and body, switch its channel, activate or deactivate it, and remove ones you no longer need. ## How a template works Each template binds to one **event type** (for example a subscription change or payment event) and one **channel** — **Email** or **In-App**. When that event fires, PeakCommerce renders any matching **active** template and delivers it. Inactive templates are skipped, so deactivating a template is a clean way to silence a notification without deleting it. Subject and body support `{{variable}}` placeholders that are filled from the event's data at send time. Dot-paths drill into nested values (for example `{{customer.firstName}}` or `{{order.total}}`); a placeholder with no matching value renders empty, so keep names aligned with the event payload. ## Account emails Sign-in and account emails — account activation and verification, password reset and change — are sent by **Auth0**, PeakCommerce's identity provider. You can override them with notification templates when you need custom branding or copy; otherwise the Auth0 defaults apply. ## Subscription-change notifications Confirmations sent when a subscription changes: * **Add product**, **Remove product**, **Update subscription** (upgrade/downgrade), **Renew subscription**, and **Cancel subscription**. Depending on your billing system, some of these may also be sent by the billing system itself (for example, Zuora amendment emails). Coordinate the two so customers don't receive duplicates. ## Payment notifications * **Invoice payment thank-you** and **subscription payment thank-you** — which can include billing details and an order summary. ## Gotchas * A template only sends if it's **Active** and its event type and channel match a fired event. If a notification isn't arriving, confirm all three. * Placeholder names must match the event payload exactly; a typo renders as blank text, not an error. * Templates control content and channel only — **how** email leaves PeakCommerce is set separately. See [Using Your Own Email Provider](/product/using-peakcommerce/system-communications/using-your-own-smtp-email-provider.md). * To embed hosted payment-page links inside billing-system emails, see [Add payment page links to Zuora email templates](/product/journeys-and-pages/pages/add-payment-page-links-to-zuora-email-templates.md). --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.peakcommerce.com/product/using-peakcommerce/system-communications/email-templates.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.