Three things have to be true
An order confirmation only reaches a customer when all three of these are in place:- A sender. SMTP credentials on the brand, or an email integration on the merchant that is connected and not paused.
- A template. The email itself, from the template list (Settings → Apps → Emails). Your brand has a Default template for each standard event.
- A merchant whose payments run through ElasticFunnels. NMI, Stripe, PayPal, Klarna and Authorize.Net checkouts send order emails. BuyGoods, ClickBank, Digistore24, JVZoo and Shopify email their own receipts, so ElasticFunnels sends none for them.
Step 1: connect a sender
Go to Settings → Emailing. This is the SMTP relay ElasticFunnels connects to for every transactional email this brand sends.1
Enter the server details
Your email provider gives you these. This example uses Mailgun:
Mailgun, Postmark, Amazon SES, SendGrid, Gmail, and any other relay that speaks SMTP all
work here.
2
Set the sender identity
This is what the customer sees in their inbox:
Set Reply-to to a mailbox someone reads. Customers reply to order emails constantly,
asking to change an address or cancel. Leave it blank and their replies go to the From
address instead, which is often an unmonitored sending mailbox.
3
Save, then send a test
Save SMTP, then Send test. The test message goes to the email address of the user
who is logged in, not to the From address.If it arrives, the card shows a green Verified badge.
“Verified” means one test message was accepted by your SMTP server. It is not domain
verification. It does not check SPF, DKIM, or DMARC, and it does not confirm your provider
will accept the From address you entered. Send a real test order before you trust it.
The From address on the template is ignored
Email templates have their ownfrom_name, from_email, and reply_to_email fields. When
the brand sends over SMTP, those are not used. The three values on the Emailing tab win
for every template. Change the sender in one place and every transactional email follows.
Alternative: a per-merchant email integration
Instead of brand SMTP, a merchant can carry its own sending service. Merchant → Email tab → Email Integration lists your Amazon SES, Postmark, Brevo, Resend, Mailgun, SendGrid and Mailrelay integrations from Integrations. How to connect each one is on Email Sending Accounts. Brand SMTP takes priority. If the brand has SMTP configured, the merchant integration is ignored for order emails. Use the merchant integration when a single brand sells through merchants that need to mail from different providers. A paused or disabled integration sends nothing. If it is the only sender a merchant has, its order and subscription emails are skipped and a Brand Action asks you to choose a sending account. ElasticFunnels never sends those emails from its own servers in its place. Members area login codes and links, and the course welcome email, are the exception: when the brand has no SMTP, ElasticFunnels sends them under your brand name so customers are not locked out.Step 2: create the templates
Open Settings → Apps → Emails in the sidebar. Tabs filter the templates by type (Orders, Subscriptions, Members and login, Courses, Custom). Your brand has a Default template for each standard event, and you can create your own. See Emails for the list, Building an email for the builder and Template Variables for the merge tags. The fastest route is Step 3: the merchant screen can create a pre-built template and select it in one click.Step 3: wire the templates to the merchant
Go to Merchants, open the merchant, and switch to the Email tab. This is the step people miss. Templates live on the brand. Sending is decided per merchant. A brand with three merchants has three separate sets of these slots, and filling them in for one does nothing for the other two.Order Emails
Subscription Emails
Visible for NMI and Stripe merchants:
Each row has a Create template button that seeds a ready-made template for that type and
selects it immediately. A row showing Not set uses the brand’s template for that event (see
below). The Pre-Renewal Reminder is the exception: with Not set, no reminder is sent.
Which template actually gets used
For each email, ElasticFunnels checks these in order and sends the first template it finds:- The merchant’s Email tab. This wins.
- Settings → Subscriptions, which holds brand-wide picks for the same events (not for the Pre-Renewal Reminder).
- The brand’s Default template for that event, marked with a Default badge in the template list (Settings → Apps → Emails).
What sends, and from where
Order emails are queued and sent by ElasticFunnels a couple of seconds after the conversion lands, so Elasticsearch has time to index the line items. Members area login codes are sent directly by the page runtime and arrive immediately.Deliverability
The SMTP form gets the message to your provider. Getting it to the inbox is your provider’s job, and it depends on DNS records you set once:- SPF and DKIM for the sending domain, at your email provider. Every provider documents the exact records. Without them, order confirmations land in spam or get rejected.
- A From address on a domain your provider is authorised to send for.
team@example.comonly works onceexample.comis added and verified as a sending domain at your provider. - A real reply-to mailbox. Providers score unmonitored senders poorly, and customers who cannot reach you open chargebacks instead.
Related docs
- Order Emails - What each order email contains
- Subscription Emails - Renewals, paused, canceled, dunning
- Emails Not Sending - Checklist when a customer got nothing
- Template Variables - Complete merge tag reference
- Email Sending Accounts - Amazon SES, Postmark, Brevo, Resend and the sender rule
- Email Marketing Integrations - Mailgun, SendGrid, generic SMTP