Help center

Your voice. Your HTML. Your emails.

Create branded messages, check every tag and choose when to send.

EnglishStep by step · Made simple

01 / 10

Your first email in five steps

Connect the provider and verify a sender.
Duplicate an Atlas template or import your HTML.
Complete the subject and copy in Spanish and English.
Open preview and send a test to your own inbox.
Create a sequence, review its steps and enable it when ready.

02 / 10

Connect the provider and sender

In Email & automations, select Configure delivery and connect Resend.
Add a sender with a display name, email, domain and optional reply address.
Copy Atlas’s verification records into your domain provider, then select Check DNS.
Complete delivery-status setup: copy the displayed URL into Resend and save the requested secret in Atlas.
Select that sender in the settings of each shop that should use it.

The sender should show Verified and a test should arrive in your inbox. Check the spam folder too.

03 / 10

Paste your HTML and keep your design

Create a template, import an HTML file or start with an Atlas design. Add an internal name and a subject customers will recognize. Paste HTML into the editor and personalize it using catalog tags. Save both language versions.

Use public images without private information. Remote images may not load in the protected preview; check them in a test email. Email apps may render layouts differently.

04 / 10

Every available tag

A tag is text Atlas replaces when sending. Use the exact spelling and both pairs of braces. For example, {{customer.firstName}} becomes the customer’s first name. A missing value may be empty: check sentences that depend on optional fields.

Tag	What it shows	Example / usage
`{{customer.name}}`	Customer · name	Alex MorganFilled from the saved order or shop data.
`{{customer.firstName}}`	Customer · first name	AlexFilled from the saved order or shop data.
`{{customer.email}}`	Customer · email	alex@example.testFilled from the saved order or shop data.
`{{order.number}}`	Order number	#1001Filled from the saved order or shop data.
`{{order.id}}`	Internal order reference	sample-orderFilled from the saved order or shop data.
`{{order.date}}`	Order date	18 October 2026Filled from the saved order or shop data.
`{{order.status}}`	Order status	paidFilled from the saved order or shop data.
`{{order.items}}`	Products · text	1 × Example product — €39.95Filled from the saved order or shop data.
`{{order.itemsHtml}}`	Products · table with images	Table with products, quantities and amountsPaste directly between HTML blocks, never inside an attribute.
`{{order.total}}`	Order total	€64.90Filled from the saved order or shop data.
`{{order.subtotal}}`	Subtotal	€69.90Filled from the saved order or shop data.
`{{order.shipping}}`	Shipping amount	€0.00Filled from the saved order or shop data.
`{{order.discount}}`	Discount	€5.00Filled from the saved order or shop data.
`{{order.currency}}`	Currency	EURFilled from the saved order or shop data.
`{{order.tracking}}`	Tracking · link or reference	SAMPLE123Requires tracking saved on the order.
`{{tracking.number}}`	Tracking number	SAMPLE123Requires tracking saved on the order.
`{{tracking.carrier}}`	Carrier	Example carrierRequires tracking saved on the order.
`{{tracking.url}}`	Tracking URL	https://example.test/tracking/SAMPLE123Use as the complete destination: href="{{tracking.url}}". Requires tracking saved on the order.
`{{refund.total}}`	Refund amount	€29.95Available when a refund is confirmed.
`{{shop.name}}`	Shop name	Your shopFilled from the saved order or shop data.
`{{shop.supportEmail}}`	Support email	help@example.testFilled from the saved order or shop data.
`{{checkout.url}}`	Continue checkout	https://example.test/checkout/sampleUse as the complete destination: href="{{checkout.url}}". Filled from the saved order or shop data.
`{{payment.recoveryUrl}}`	Authenticate or recover payment	https://example.test/checkout/sampleUse as the complete destination: href="{{payment.recoveryUrl}}". Filled from the saved order or shop data.
`{{subscription.name}}`	Membership name	Monthly membershipRequires a subscription linked to the order.
`{{subscription.amount}}`	Membership amount	€14.90Requires a subscription linked to the order.
`{{subscription.nextDate}}`	Next membership payment	25 November 2026Requires a subscription linked to the order.
`{{subscription.manageUrl}}`	Manage monthly plan	https://example.test/subscription/sampleUse as the complete destination: href="{{subscription.manageUrl}}". Requires a subscription linked to the order.
`{{email.unsubscribeUrl}}`	Email preferences	https://example.test/email/preferences/sampleUse as the complete destination: href="{{email.unsubscribeUrl}}". Cart reminder email preferences.

05 / 10

A simple example to start with

Paste this example into an HTML template and open Preview. Use order.itemsHtml as content, not inside an attribute. Link tags must fill the entire link destination.

<h1>Thank you, {{customer.firstName}}</h1>
<p>Your order {{order.number}} is confirmed.</p>
{{order.itemsHtml}}
<p><strong>Total: {{order.total}}</strong></p>
<p>Need help? {{shop.supportEmail}}</p>

06 / 10

Check the preview

Select the template language and event type.
Review the subject, greeting, products, total and buttons using fictional data.
Resolve unknown or incomplete tag warnings.
Check mobile preview, then send a test. Compare links, images and spacing in your email app.

Illustrative exampleEmail preview

SubjectYour order #1001 is confirmed

GreetingHi Alex,

Sample total€64.90

Fictional data. This example does not change your account.

07 / 10

Create an automation

Open Automations and select Create sequence.
Choose an event: order paid, abandoned cart, shipping, refund, membership paid, membership failed or payment action.
Select the shop or available scope.
Add 1–10 steps. Choose a template and a 0–30 day delay for each step. Delays are measured from the event that starts the sequence.
Review each preview, save and activate when ready.

Illustrative exampleSequence · Order paid

EventPurchase confirmed

First stepImmediately · Order confirmation

StatusPaused

Fictional data. This example does not change your account.

08 / 10

What changes when you enable or pause

Enabling schedules emails for new events; it does not replay old purchases or recover cancelled sends. Pausing cancels pending sends for that sequence and prevents new ones. A send already in progress may complete. Keep templates used by active sequences enabled.

09 / 10

Check delivery history

Open an email in history and review recipient, shop, template, time and status. Pending or sent does not always mean delivered. If it fails, read the reason and check connection, sender, domain and recipient address before retrying.

10 / 10

Before enabling a sequence

The sender is correct and verified.
The subject and content have been reviewed in both languages.
Tags match the event and links open the intended destination.
The test reached my inbox and looks good on a phone.
Scope and frequency match the messages the customer should receive.