Email Templates and Variables

Shoppex sends your buyers an email when they order, pay, receive their items, or when a payment runs into trouble, and for subscriptions, gifts, licenses, warranties and your reseller program. Every email has a default design with your shop name and logo, drawn in your Brand. You can change the subject and the body of the emails listed under Storefront → Buyer Emails (/store/emails). The list is grouped by topic, and each row says whether the email sends and which switch decides.

​

Customize an email

1. Open Store → Emails and click an email.
2. Pick the Language you want to write in. See Languages.
3. Change the Subject and the Body. The body is the part between the header and the footer, in HTML. Write {{variable}} where order details go, for example {{invoice_id}}. Click a variable in the Variables panel to insert it at the cursor.
4. Check the Preview. It renders on the server with sample data from your shop and shows the whole email: your body inside your Brand’s header and footer.
5. Click Save Email.

Your logo, colors, fonts and footer are not part of the body: they come from your Brand and wrap every email, customized or not. A Brand change or a Shoppex design update of the header and footer reaches your customized emails too. Reset returns the open language to the current default body and deletes your version in that language. Send Test sends your draft in the open language to your verified account email, with sample data. Bounced or complained addresses cannot receive tests. Each shop can send 5 test emails per hour. Things to know about the body:

• A variable is written {{name}}. A variable the email does not receive stays in the email as written, so copy names from the table below. Values go in as they are: a shop name that contains {{…}} is not filled in again.
• Save only the body. A whole HTML document (<html>, <head>, <body> or a doctype) is refused, and so is an empty body.
• Shoppex removes <script> tags, on… event attributes, and javascript: links when you save. A body longer than 512 KB is cut off, and the preview refuses it.
• The Customer Sign-in Code must show {{code}} as visible text, written exactly like that.
• The Reseller Invitation must contain {{accept_url}} in a link or in the text, not only in an HTML comment. It is the one-time link that lets the reseller join.
• Text that someone typed is HTML-escaped: the buyer’s address and the tracking code in the Shipping Confirmation, a gift message, your note on a warranty decision, a reason you give for declining a reseller, and the names and links in the subscription, gift, license, warranty, reseller, refund, partial payment and resent-order emails. Line breaks become <br>. A missing tracking code, renewal date or gift recipient shows as a dash.
• A block (the Blocks column below) is a part of the email that only shows for some orders, such as the rows of a details table, a note you wrote, or the delivered goods. Shoppex fills it in ready-made when it sends the email, and leaves it empty when there is nothing to show. Move or delete a block like any other variable, but you cannot change what is inside.
• The Delivery Email, Order Details Resent and Gift Received emails carry the purchased keys, files and instructions in the {{delivery_content_html}} block, which shows only what the order has. The Delivery Email and Order Details Resent also offer each kind on its own as a {{delivery_…}} variable. If your body has none of them, Shoppex adds the delivery block at the end of the body, so the buyer always gets what they paid for. The gift recipient has no order page, so Gift Received gets the goods added unless your body has {{delivery_content_html}} itself.
• The Plain Text field is the plain text of your body, for inboxes that block HTML. Shoppex adds the shop name above it and the footer below it. Write {{variable}} there too. Leave it empty and Shoppex builds it from your body. In the Delivery Email, Order Details Resent and Gift Received, plain text without any delivery variable gets the goods added at the end, like the body. In the Customer Sign-in Code, the plain text must show {{code}} on its own, never inside a link, and {{sign_in_url}} only on its own. In the Reseller Invitation, it must contain {{accept_url}}.

​

Your logo

Every email shows your shop logo next to the shop name at the top, customized or not. The logo is the image you set as your shop avatar. If your shop has no logo, the email shows your shop name only.

​

Your Brand

The Brand sets the accent color, button shape, fonts and footer text of the emails buyers get from your store. Open it with the Brand row on Store → Emails, or from Settings → Branding → Email Brand (/store/emails/brand). You need the Design permission to change it. The preview next to the settings shows a sample order email with your changes before you save. A store that never saved a Brand sends the Shoppex design. The Brand changes buyer emails only; your own order notices and Shoppex account emails keep the Shoppex design.

​

The Brand in customized emails

A customized email gets the header, fonts, footer text and “Powered by Shoppex” line from your Brand when it is sent, like the default. Inside the body, three variables carry the Brand colors: A body you start customizing uses these variables for its buttons and links, so later color changes reach it. The fonts and the button shape inside the body are written in as they are when you start; after you change them, click Reset to get the current ones.

​

Languages

The default emails go out in the buyer’s language, the language they used at checkout. Shoppex translates their subjects, headings, buttons and labels into German, Spanish, French, Italian, Dutch, Portuguese, Polish, Russian, Finnish, Lithuanian, Turkish and Chinese; some longer sentences stay in English. Other languages get English. For a fully translated email, customize it in that language. Each language has its own customized version. Pick it under Language at the top of the editor. The list next to each language shows Customized or Default. A language you open for the first time starts from the Shoppex default in that language. Which version a buyer gets:

1. Your version in the buyer’s language, if you saved one.
2. Otherwise your English version, if you saved one.
3. Otherwise the Shoppex default in the buyer’s language.

So after you customize English, buyers in German get your English version until you customize German too. The editor tells you when this applies. Emails you customized before languages existed are English versions and keep going to every buyer as before. Blocks are in English in every version, so a German version shows English labels inside its blocks. The list under Buyer Emails shows the English version, and its Reset to Default works on English. It shows only on emails with an edited English version. Send tests from the editor.

​

Turn emails on or off

Three switches at the top of Buyer Emails turn groups of order emails on or off. A switch acts at once, and Undo in the confirmation puts it back. These emails do not depend on the switches:

• Delivery and Gift Received carry the goods and bypass the three switches and buyer notification opt-outs. Developer API completion notices carry no goods and still follow Payment Received and buyer preferences.
• Shipping Confirmation. You decide per shipment with Notify customer by email. See Physical products.
• Customer Sign-in Code, sent when a buyer signs in to your store.
• Abandoned Cart. See Abandoned carts.
• Feedback Review Request and Back in Stock have their own settings.
• Subscription Trial Ending and Subscription Renewal Reminder, which tell the buyer about a coming charge.
• License Expiry Reminder, the Warranty emails and the Reseller emails.
• Replies to a buyer’s question or review, and Reward Granted Customer.
• Emails you send yourself, such as Order Details Resent.

Buyer opt-outs stop order notifications and receipts, including Developer API completion notices. They do not stop delivery emails with goods or the steps needed to receive them. Explicit send suppression and bounce/complaint blocking still apply. Headless orders also follow their separate order-email settings; gift-recipient delivery is exempt from that policy.

​

Changelog

• September 28, 2026: Delivery emails now bypass Payment Received and buyer notification opt-outs so buyers can receive their goods. Receipts and Developer API completion notices still respect both preferences. Test emails can only go to your verified account email, subject to bounce/complaint blocking and the shop’s five-per-hour limit.

​

Variables per email

Each row lists the variables the editor offers for that email and the ones its default design uses, and the email’s blocks. {{shop_name}} is your store name. Every email also gets the three Brand variables, which the table leaves out. A few emails receive more; the Shipping Confirmation is one. Some variables are empty for some orders, for example {{customer_name}} when the buyer gave no name. Stored templates have no conditions, so write your text so that it reads well without them.

​

Locked emails

Shoppex manages these emails itself. You cannot customize, preview or reset them, because they carry statements about payment and account security that must stay exactly as written:

• order_completed_pending_custom_fields_customer: Sent after payment when the buyer still has to fill in your custom fields before delivery.
• order_completed_manual_api_customer: Sent when you complete an order through the Developer API. It says that Shoppex did not verify the payment.
• order_completed_merchant: Your own notice of a completed order.
• feedback_appeal_decided: Tells you whether Shoppex upheld or declined your appeal of a review, with Shoppex’s note when there is one. An upheld appeal hides the review and revokes its points and unspent reward.
• reward_rules_paused_merchant: Notifies you that every-order reward rules are paused and asks you to review them in Loyalty & Rewards. Existing grants remain available.
• referral_payout_status: Tells you whether Shoppex completed or refused your referral payout, with the transaction reference or refusal reason.
• auth_discord_link_confirmation: Asks a buyer to allow Discord sign-in for their customer account.
• wallet_otp: The code a buyer enters to pay with their store credit. It tells them not to share it.