Transactional email

Invoice emails, approval requests, chase emails and password resets, sent from your own domain so they arrive reliably and look like you.

Connecting

Insight, then Integrations, then the Transactional email card.

Field	Value
Driver	postmark or resend
API token / key	From your provider
From email	The address customers see, for example hello@yourshop.com
From name	Optional. Defaults to your shop name

Authenticate your domain first

Before you connect, set up SPF, DKIM and DMARC for your sending domain in your provider's dashboard. This is not optional in practice:

• Without DKIM, a meaningful share of your invoice emails go to spam.
• With a from address on a domain you do not control, some receivers reject the message outright.

Both Postmark and Resend walk you through the DNS records. It is fifteen minutes with your DNS provider and it is the difference between customers receiving invoices and customers not.

Transactional and marketing are different

	Transactional	Marketing
Examples	Invoice, approval request, dispatch notice	Broadcasts
Triggered by	Something the customer did	You deciding to send
Unsubscribe	Not applicable	One-click, mandatory

Do not send marketing through a transactional template to dodge unsubscribes. Providers suspend accounts for it, and it is unlawful in most jurisdictions.

Testing

Send yourself one of each message from a test customer and check: from-name, reply-to, links, variable substitution, and how it looks on a phone. Details in templates.

Troubleshooting

Symptom	Check
No emails	Credentials verified, template active
Emails go to spam	SPF, DKIM and DMARC on your sending domain
Replies go nowhere	The contact email in brand settings is the reply-to
Some recipients never receive	Your provider's suppression list. A previous bounce or complaint blocks the address