Email templates
Email templates control the subject line and HTML body of every transactional email your store sends to customers: order receipts, subscription notifications, and purchase history links. You can rewrite the copy, restyle the HTML, or insert variables like the customer’s username and order ID anywhere you want them.
Editing email templates is a Pro plan feature. On Free and Starter, your store sends the FluxStore defaults. See Plans and Pricing.
Where to find it
Open your store and go to Dashboard > Customization > Emails. The tab shows every template your store can send, with its current subject line and an active indicator next to each one.
If you don’t see any templates listed yet, click Create Default Templates. FluxStore will seed the standard set so you have something to edit.
Which emails you can edit
These are the per-store templates you control. Anything not in this list (account verification, ticket notifications, billing receipts from FluxStore itself) is sent by the platform and isn’t editable.
| Template | When it’s sent |
|---|---|
| Order Receipt | After a successful checkout, confirming the items and total |
| Subscription Started | Once when a recurring subscription becomes active |
| Subscription Payment Failed | When a subscription renewal charge is declined or fails |
| Purchase History Verification | When a customer requests a link to view their orders for your store |
Variables you can use
Variables are written with single curly braces, like {orderId}. When the email is sent, FluxStore replaces them with the real values for that customer. Unknown variables are left as-is, so a typo will show up in the email rather than silently disappear.
The editor lists the variables available for the template you’re editing under Available Variables (click the panel at the bottom of the editor to expand it, then click a variable to insert it at the cursor). The common ones:
| Variable | Available in |
|---|---|
{storeName} | All templates |
{playerUsername} | Order Receipt, Subscription emails |
{customerName} | Subscription emails |
{orderId}, {orderDate}, {totalAmount}, {orderItems} | Order Receipt |
{packageName}, {amount}, {currency} | Subscription emails |
{billingInterval}, {nextBillingDate}, {manageUrl} | Subscription Started |
{renewalNumber}, {periodEnd} | Subscription Payment Failed |
{verificationLink}, {expiryMinutes} | Purchase History Verification |
Editing a template
- Click any template card in the Emails tab. The editor opens with the current subject and body.
- Edit the Subject Line at the top. You can put variables here too, for example
Order confirmed - {orderId}. - Edit the HTML Body. Use Rich Text for a visual editor or switch to Code to write raw HTML.
- Optionally fill in Plain Text Body, which is shown to email clients that don’t render HTML. If you leave it blank, FluxStore falls back to the default.
- Click Send Test Email at the top right to preview the rendered email in your inbox before saving. Variables are replaced with sample values so you can see exactly what the customer will get.
- Click Save Template. The next email of that type uses your new version immediately.
Restoring the defaults
There’s no per-template “reset” button, so before you make big changes copy the current HTML somewhere safe.
If you’ve deleted a template entirely, click Create Default Templates to reseed any that are missing. That button only adds templates that don’t exist yet; it won’t overwrite ones you’ve already edited.
Per-store vs platform defaults
The defaults you see when you first click Create Default Templates are seeded into your store as your own editable copies. They are not a live fallback. Once seeded, your store always sends your version of the template, even if FluxStore later improves the defaults. If you want the latest copy, delete the template and reseed it.
A handful of emails (account verification, support ticket notifications) are sent by FluxStore at the platform level and don’t appear in this tab. Those aren’t editable per store.
Common pitfalls
- Email clients render HTML differently. Outlook, Gmail, and Apple Mail each support a different slice of HTML and CSS. Stick to inline styles and table-based layouts, and always send a test email to at least one webmail and one desktop client before assuming it looks right.
- Don’t change variable names. Renaming
{orderId}to{order_id}won’t work. FluxStore only substitutes the exact names listed in the editor. - Deliverability depends on your From address. Editing the template doesn’t change who the email comes from. If you’ve changed the From address to your own domain, make sure SPF and DKIM are set up. See Email.
- Test emails use placeholder data. Sample values won’t match a real order, so use the test email to check formatting, not numbers.
Next steps
- Email for sender settings, custom SMTP, and email logs.
- Plans and Pricing for what’s included on the Pro plan.