---
title: Transactional Emails
slug: oms/transactional-emails
docTags: 
createdAt: 2022-07-18T12:28:37.000Z
---

## Introduction 

Transactional Emails are the mandatory post-purchase email communications you can send to customers. These emails are content managed in Contentful or Sanity and sent via Chord's email services.‌

## Default Email Templates 

(**email name: ***slug*)

**Subscriptions**

- **Subscription Reminder Email**: *subscription\_default\_reminder*
- **Subscription Insufficient Stock**: *subscription\_ insufficient\_stock*
- **Subscription Last Chance Reminder Email**: *subscription\_last\_chance\_reminder*
- **Subscription Installment Failed**: *subscription\_installment\_failed*
- **Subscription Installment Payment Failed**: *subscription\_installment\_payment\_failed*

::File{src="https://api.archbee.com/api/presign/TmutqdeXiIw-V3gBZXVjd/o6F7pJe8bj9_hCLW_mXFD_subscriptionemail.json" label="subscription_email.json" isUploading="false"}

**Stock Requests **

- **Item Back In Stock Email**: *back\_in\_stock*

::File{src="https://api.archbee.com/api/presign/TmutqdeXiIw-V3gBZXVjd/3kJ3cKoK66BMIe_swQ7-e_stockrequstemail.json" label="stock_requst_email.json" isUploading="false"}

**Reimbursements **

- **Order Reimbursement Email**: *reimbursement\_email*

::File{src="https://api.archbee.com/api/presign/TmutqdeXiIw-V3gBZXVjd/FWz_UwJlivq8IyDbbr1L9_reimbursementemail.json" label="reimbursement_email.json" isUploading="false"}

**Refunds **
(The same email template is used for refunds/reimbursements, they are two different things that coincide with a refund of money and/or an exchange)

- **Order Refund Email**: *reimbursement\_email*

::File{src="https://api.archbee.com/api/presign/TmutqdeXiIw-V3gBZXVjd/0ILimTy2whyKw5_GeiJoY_refundemail.json" label="refund_email.json" isUploading="false"}

**Referrals **

- **Reward Confirmation Email‌**: *reward\_confirmation*
- **Referral Prompt Email**: *referral\_prompt*

::File{src="https://api.archbee.com/api/presign/TmutqdeXiIw-V3gBZXVjd/jWPaaGM87vPPOqlrQxl7X_referralemail.json" label="referral_email.json" isUploading="false"}

**Orders **

- **Order Confirmation Email**: *confirm\_email*
- **Order Cancelation Email**: *cancel\_email*
- **Order Cross Sell Email**: *cross\_sell\_email*
- **Checkout Abandoned Email‌**: *abandoned\_email*

::File{src="https://api.archbee.com/api/presign/TmutqdeXiIw-V3gBZXVjd/JAl0YWnNwFKytqp9GVun8_ordermail.json" label="order_mail.json" isUploading="false"}

**Cartons/Shipments **

- **Order Shipped Email**: *shipped\_email*

::File{src="https://api.archbee.com/api/presign/TmutqdeXiIw-V3gBZXVjd/I7e5ZGpDJNYL0XQBouuTG_cartonmail-shipped-email.json" label="carton_mail (shipped email).json" isUploading="false"}

**Gift Cards **

- **Gift Card Email**: *gift\_card\_email*

::File{src="https://api.archbee.com/api/presign/TmutqdeXiIw-V3gBZXVjd/UZdGvY6xm6FnbB8vUNmb__giftcardemail.json" label="gift_card_email.json" isUploading="false"}

### Example(s) Content Types in Contentful

![](https://api.archbee.com/api/optimize/TmutqdeXiIw-V3gBZXVjd/iRMCuVbLY6cHGoPKYMzpl_image-2-22-2023-at-1238-pm.jpg)

## Inky

In order to be more flexible in creating emails, we are using [Inky](https://github.com/foundation/inky-rb) as a templating language to essentially convert complex HTML tags into a much simpler approach.‌Inky simplifies the process of creating HTML emails by expanding out simple tags like  and  into full table syntax.



With Inky, we can inject variables into our HTML templates that will be replaced with values from the order when they are compiled into HTML (see \{\{ship\_address.firstname}} in the example below).

![](https://api.archbee.com/api/optimize/TmutqdeXiIw-V3gBZXVjd/jv1PyEkv4JZczVwYo0OxW_untitled.png)

:::hint{type="success"}
**Note**: You can still use HTML‌‌! 
:::

## Variables

:::BlockQuote
\{\{ship\_address.firstname}} \{\{#first\_package\_tracking.url}} \{\{#line\_items}} \{\{name} \{\{#options\_text}} \{\{#is\_bundle}} \{\{/parts}} \{\{price}} \{\{quantity}}
\{\{#promo\_total}} \{\{#payment\_charge}} \{\{shipment\_total}} \{\{#store\_credit\_applied}} \{\{ship\_address.full\_name}} \{\{ship\_address.address1}} \{\{#ship\_address.address2}} \{\{ship\_address.city}} \{\{ship\_address.state}} \{\{ship\_address.zipcode}} \{\{shipping\_method}} \{\{#trackings}} \{\{#url}} \{\{order\_total\_after\_store\_credit}} \{\{purl\_link} \{\{email}} \{\{credit}} \{\{reimbursement\_total}} \{\{updated\_order\_total}} \{\{credit\_balance}} \{\{order.subscription\_order}} \{\{order.spree\_channel.name}} \{\{ order.state}} \{\{order.display\_item\_total.to\_s}} \{\{order.display\_tax\_total.to\_s}} \{\{order.display\_total\_applicable\_store\_credit.to\_s}} \{\{payment\_information}} \{\{order.cart\_url.to\_s}} \{\{order.subscription\_in\_cart?}} \{\{fully\_cross\_sold\_line\_items}} \{\{partially\_cross\_sold\_line\_items}}
\{\{non\_cross\_sold\_line\_items}} \{\{order.metadata}} \{\{order.shipments.first&.shipping\_method&.code}} \{\{shipping\_method\_name}}\{\{order.display\_order\_total\_after\_store\_credit.to\_s}} 
:::



**Example one:**

![](https://api.archbee.com/api/optimize/TmutqdeXiIw-V3gBZXVjd/-XvzV1b1XbOW62OkJ2axd_untitled.png)

**Example two:**

![](https://api.archbee.com/api/optimize/TmutqdeXiIw-V3gBZXVjd/ihBTBpz4Bng6Ux7sjTr29_untitled-1.png)



## Sections 

Sections render blocks of text one or more times, depending on the value of the key in the current context.A section begins with a pound and ends with a slash. That is \{\{[#person](https://paper.dropbox.com/?q=%23person)}}begins a "person" section while \{\{/person}} ends it.
More information [here](https://mustache.github.io/mustache.5.html)



## Additional Information

The main way to get started is with [Foundation for Emails](http://foundation.zurb.com/emails) and [CSS styled emails without the hassle](https://github.com/fphilipe/premailer-rails)

A tool to help implement and test customizations to Chord email templates.

If you can achieve your needs by overriding a few styles within the Contentful Email's Custom Styles field, this tool isn't necessary. It exists for those looking to completely customize the branding of their email templates.

Chord email templates are powered by [Foundation for Emails](https://get.foundation/emails/docs/) and this repository is based on their [foundation/foundation-emails-](https://github.com/foundation/foundation-emails-template)



## Disabling Mailers 

### Globally

You may decide to disable our transactional templates. Instead, you can use `Email Queued` events to trigger your own transactional emails with an external service like Klaviyo or Iterable.

Disabling all transactional emails is accomplished by setting `TRANSACTIONAL_EMAILS_ENABLED` to `disabled` . This setting is configurable on a per-store basis in the **Environment Variables** section in **Settings / Store **

### Disable transactional emails individually

You also have the option to deactivate specific email template. This functionality allows you to enable or disable transactional emails individually by incorporating an optional boolean field, "enabled," into the Email content type within Contentful. If this field is present and set to "no," the respective email template will be deactivated.

::Image[]{src="https://api.archbee.com/api/optimize/TmutqdeXiIw-V3gBZXVjd/ro7v5kECqGRofuT6JNCik_untitled.jpeg" size="66" width="3121" height="1584" position="flex-start" showCaption="false"}



:::hint{type="success"}
If you have questions or need more information, please reach out to help\@chord.co 
:::

##