Email variables reference and how to customize email templates with HTML

Overview

Every notification email in Wishlist Club can be customized using HTML and dynamic variables. This page is your complete reference for editing email templates, inserting dynamic content, displaying products correctly, and testing your emails before you publish changes.

You can customize the content for each email type separately, including wishlist reminders, back-in-stock alerts, and email verification messages.

How to open the email editor

In Shopify, go to AppsWC Wishlist & Back in Stock.

Open Settings and select Email Customization.

Select the email template you want to edit.

Update the Body Content field using HTML and the supported variables listed on this page.

How email variables work

Email variables are placeholders that Wishlist Club replaces with real store, customer, or product information when the email is sent. This lets you create one template that automatically personalizes itself for each recipient.

For example:

<p>Hi {{customer_name}},</p>
<p>Good news—items from your wishlist are available now.</p>

When the email is delivered, {{customer_name}} is replaced with the customer's actual name.

Use variables exactly as shown, including the curly braces. If a variable is misspelled or incomplete, it will not render correctly in the email.

Complete variable reference

All email templates in Wishlist Club use the same core variable library, with one additional variable that is only used in the email verification template.

Store variables

Use these variables to show store information in the email.

  • {{shop}} — Your Shopify store domain, such as yourstore.myshopify.com

  • {{store_name}} — Your store's display name

  • {{store_email}} — Your store's contact email address

  • {{money_format}} — Your store's currency format, such as $, £, or

Customer variables

Use these variables to personalize emails for each subscriber or shopper.

  • {{customer_name}} — The customer's full name

  • {{unsubscribe_url}} — A unique unsubscribe link for that customer

Email verification variable

This variable is only used in the Email Verification template.

  • {{verification_token_url}} — The customer's unique email verification link

The Email Verification template must include {{verification_token_url}}. If you remove it, customers will not be able to verify their email address from that message.

Product variables

Use these variables inside your product table to display details for wishlist items or subscribed products.

  • {{product[title]}} — Product name

  • {{product[sku]}} — Product SKU

  • {{product[price]}} — Current product price

  • {{product[compare_at_price]}} — Original or compare-at price

  • {{product[product_id]}} — Shopify product ID

  • {{product[variant_id]}} — Shopify variant ID

  • {{product[image]}} — Product image URL

  • {{product[add_to_cart_link]}} — Direct add-to-cart link

  • {{product[view_product_link]}} — Product page link

The required wc-product-tbl class

If your email template displays products, the HTML table that contains the product variables must include the class wc-product-tbl. This is required for Wishlist Club to recognize the product section and render product data correctly.

Use this structure:

<table class="wc-product-tbl">
  <tr>
    <td><img src="{{product[image]}}" alt="{{product[title]}}" /></td>
    <td>
      <p>{{product[title]}}</p>
      <p>{{product[price]}}</p>
      <p><a href="{{product[view_product_link]}}">View product</a></p>
    </td>
  </tr>
</table>

If you remove the wc-product-tbl class, product details may not appear in the email even if the variable names are correct.

Recommended email template structure

If you are building or cleaning up a template, use a simple structure that includes:

  • A greeting

  • A short message explaining why the customer received the email

  • A product table with the wc-product-tbl class, when product content is needed

  • A clear call to action such as View product or Add to cart

  • An unsubscribe link when appropriate

Example:

<p>Hi {{customer_name}},</p>
<p>One or more products you're following are now available.</p>

<table class="wc-product-tbl">
  <tr>
    <td><img src="{{product[image]}}" alt="{{product[title]}}" width="120" /></td>
    <td>
      <p><strong>{{product[title]}}</strong></p>
      <p>Price: {{product[price]}}</p>
      <p><a href="{{product[view_product_link]}}">View product</a></p>
      <p><a href="{{product[add_to_cart_link]}}">Add to cart</a></p>
    </td>
  </tr>
</table>

<p>If you no longer want these emails, you can unsubscribe here: <a href="{{unsubscribe_url}}">Unsubscribe</a></p>

Best practices for customizing email templates

  • Keep the layout simple so the email renders well across devices and inboxes.

  • Use inline-friendly, email-safe HTML rather than relying on complex layouts.

  • Make your main call to action easy to spot.

  • Always test changes before saving them as your live version.

  • Keep required variables, especially {{verification_token_url}} in verification emails and wc-product-tbl in product sections.

  • Use both product links and clear copy so customers know what action to take next.

If you are editing an existing template, make one change at a time and preview after each update. This makes it much easier to find formatting problems before customers see them.

Common mistakes to avoid

  • Deleting the wc-product-tbl class from the product table

  • Removing the verification link from the email verification template

  • Typing variable names incorrectly

  • Using product variables outside the product table section

  • Publishing a large HTML change without previewing or testing it first

If a template looks correct in the editor but product details are missing in the delivered email, the first thing to check is whether the product table still includes class="wc-product-tbl".

How to preview and test your email

Before you publish any template update, preview the email and send a test whenever that option is available in the editor. This helps you confirm that:

  • Variables are being replaced correctly

  • Product images and links appear as expected

  • Buttons and text links go to the correct destination

  • The layout works on both desktop and mobile email clients

Finish editing your HTML and save your changes in the template editor.

Use the preview option to confirm the overall structure, spacing, and variable placement.

Send a test message if the option is available so you can review the final rendering in a real inbox.

Make sure product templates still include wc-product-tbl, and verification templates still include {{verification_token_url}}.

Once the preview and test email look correct, keep the updated version as your live template.

Quick checklist before going live

  • Your greeting and message are clear

  • All variable names are spelled correctly

  • The product section uses class="wc-product-tbl"

  • All links work correctly

  • The unsubscribe link is present where needed

  • The verification email includes {{verification_token_url}}

  • You previewed and tested the email before publishing

Frequently asked questions

Yes. You can customize the HTML body of each email template. Just make sure you keep any required variables and the wc-product-tbl class where product content needs to render.

The most common reason is that the product table no longer includes class="wc-product-tbl", or the product variables were changed or removed.

Most of them do. Store and customer variables are shared across templates. The main exception is the email verification template, which also requires {{verification_token_url}}.

Yes. Use {{unsubscribe_url}} to insert a customer-specific unsubscribe link.

Need help?

If you are not sure which file to edit, or you would rather have us handle the installation, contact our support team: