Customer Fields has built-in logic that triggers emails to be sent directly to customers when certain events occur. There's a total of seven (7) different customer-facing emails that are related to the app:

The emails for 'Customer account request' and 'Customer account deny' are truly unique to the Customer Fields app since these emails are used when approving or denying pending customers, which is a part of the app's account approval feature. These two emails are sent directly to customers using the app's email service.

You can fully customize the email templates for both of these emails using the app admin. Go to Settings > Email notifications > Email templates and then click on the name of the template you wish to edit:

The email for 'Customer account verification' is also unique to Customer Fields, but it's very similar to Shopify's 'Customer account invite' email. This particular email is sent by the app's email service, and the reason it exists is to ensure that the data collected by a form is not lost when the app runs into the "email verify" error (see more details here). This email is sent directly to customers using the app's email service.

If needed, you can customize the template for this email using the app admin by going to Settings > Email notifications > Email templates > Customer account verification. Please note that this specific template does not support the customer object; the only variables available for this email are the shop resource and verification_url.

The emails for 'Customer account approval' and 'Customer account invite' are essentially app-triggered versions of Shopify's 'Customer account invite' email. These emails are not sent by the app's email service -- the app simply tells Shopify to send the customer an invite email with a customized subject and message.

You're welcome to edit the default subject and message for these emails in the app admin, but the actual template for these emails is controlled in Shopify (found in the Shopify admin under Settings > Notifications > Customers notifications > Customer > Customer account invite).

The 'Customer account welcome' email comes directly from Shopify, and it's sent to a customer when their account is activated. This email is not sent by the app's email service nor is it intentionally triggered by the app -- Shopify's system just happens to be designed to send this email automatically whenever a new customer account is created/activated.

This email template cannot be edited within Customer Fields since it's controlled entirely by Shopify. If needed, you can customize the template for this email using the Shopify admin by going to Settings > Notifications > Customer > Customer account welcome.

The 'Customer account password reset' email comes from Shopify and is sent to a customer when they reset their password. In the context of Customer Fields, password resets will normally only occur on forms that have the 'Display password reset link' enabled in the form settings. This email is not sent by the app's email service -- the app simply tells Shopify to send the customer the store's native password reset email.

This email template cannot be edited within Customer Fields since it's controlled entirely by Shopify. If needed, you can customize the template for this email using the Shopify admin by going to Settings > Notifications > Customer > Customer account password reset.

The app's template editor for emails is completely Liquid friendly! This means you can use things like control flow tags, iteration tags, and filters to add logic and render content in your ideal format & layout.

You can also use Liquid variables for dynamic content within certain email templates. Variable support is template-specific, so the template editor in the app admin will display a list of the variables that are available based on the template you're editing. The two most common variables are detailed below:

The shop resource from Shopify can be used to output certain details about the store in email templates. Simply type in {{ shop. in the app's template editor to see a list of the properties available for this variable. You can also use the following documentation from Shopify to find more details on the different properties (aka attributes) for the shop resource:

The customer object can be used to output certain details about the customer receiving the email. Simply type in {{ customer. in the app's template editor to see a list of the properties available for this variable. The customer object supports all of the data columns in the app; including Shopify data columns and custom data columns.

If you want to display the value for a custom data column for maturity_date in the email body, along with the values for the customer's State/Province and Country, then you could use something like the following:

Or perhaps you want to display the customer's first name in the email subject, along with the store's name. You can do so using something like this:

By default, the emails triggered by Customer Fields are designed to use the 'Store contact email' or 'Sender email' as the "from" address. Both of these email addresses can be managed in the Shopify admin under Settings > Store details > Profile.

Note: When manually approving/denying customers or sending account invites, the app will allow you to choose which specific email address is used as the "from" address. In addition to the 'Store contact email' and 'Sender email', the app will also display a list of email addresses for each admin user who has accessed the app admin.

If you're using your own domain name for the 'Store contact email' and 'Sender email' in Shopify (found in the Shopify admin under Settings > Store details > Profile), then you may want to update your domain's DNS records to ensure that the emails sent by Customer Fields are delivered to your customer's inbox.

This is due to the fact that the app's emails are designed to use either of the Shopify email addresses as the "from" address. Since the app-specific emails are being sent by our app's email system (SendGrid), some email providers might flag the emails as spam unless you establish sender authentication for your domain using SPF and/or DKIM.

Adding an SPF record to your domain which references the hostname for Customer Fields' email system will help email providers determine that the emails being sent are valid and that they're not spam or phishing attempts.

Adding a DKIM record to your domain further enhances deliverability, and it's part of the requirements for implementing a DMARC policy (see details here). If your administrator has established a DMARC policy on your domain, then you'll need to contact our Customer Success team so we can get your domain added as an authenticated sender in our app's email service provider (SendGrid).

Reach out to our Customer Success team via chat or email and we'll be happy to help!