When an order changes status in Veeqo we can send a confirmation email to your customers. We can do this after an order is Created, Shipped, Cancelled or Refunded. You should only enable this when you are ready for Veeqo to start sending emails immediately.

Quick Link: This Guide explains how to enable the shipping confirmation emails setting for your store.

Note: At the moment, you can only have one email template that is used for every store connected to Veeqo.

Before you edit your email templates

  • Make sure your email address is correct. Your default email address is used as the sent from address for order confirmation emails (this only applies for Shopify and manually placed orders). You can edit your email address here.
  • You can choose a different email address for shipping confirmation emails by following this guide.
  • We recommend adding your company logo. For instructions on how to simply change the company logo check out the Change Email Template Logo article.

How do I edit my email confirmation templates?

  • Go to Settings
  • Click Email Templates
  • Choose the template you wish to edit
  •  The following window will then open. 
  • In this window you can edit the HTML / Source of the template and style this to how you would like or you may be happy with the way the template is already set up.
  • If you would like to see the current layout, you need to click on 'Source' again:
  • When you have finished editing your template, click Save Template

Advanced Editing

Our email templates uses the Liquid Scripting Language created by Shopify. Details of how this works can be found here. Click the SOURCE button to view the raw HTML email.

AVAILABLE EMAIL TEMPLATE ATTRIBUTES

This list includes all the available data fields that can be inserted into the email templates.

Shipment

(Only available in shipping confirmation email)

  • {{ shipment.carrier_name }}
  • {{ shipment.tracking_number.tracking_number }}
  • {{ shipment.insured_value }}
  • {{ shipment.weight }}
  • {{ shipment.aftership_url }}

Order

  • {{ order.deliver_to }} 
  • {{ order.deliver_to.company }} 
  • {{ order.deliver_to.first_name }} 
  • {{ order.deliver_to.last_name }} 
  • {{ order.deliver_to.company }} 
  • {{ order.deliver_to.address1 }} 
  • {{ order.deliver_to.address2 }} 
  • {{ order.deliver_to.city }} 
  • {{ order.deliver_to.country }} 
  • {{ order.deliver_to.state }} 
  • {{ order.deliver_to.zip }} 
  • {{ order.number }} 
  • {{ order.customer_note }}
  • {{ order.currency_symbol }} 
  • {{ order.total_discounts }}
  • {{ order.delivery_method.name }} 
  • {{ order.delivery_method.cost }} 
  • {{ order.subtotal_price }} 
  • {{ order.total_price }}
  • {{ order.total_tax }}

Customer

  • {{ customer.first_name }}
  • {{ customer.email }} 
  • {{ customer.phone }} 
  • {{ customer.mobile }}

Company

(this is your company)

  • {{ company.name }}

Line Items

In order to access each attributes for each line item this needs to be in a loop. 

In shipping confirmation emails, it will only show the line items in the specific allocation that is being shipped.

  • {{ line_item.product_title }} 
  • {{ line_item.sellable_title }} 
  • {{ line_item.product_description }}
  • {{ line_item.quantity }} 
  • {{ line_item.product_image_src }}
  • {{ line_item.price_per_unit }} 
  • {{ line_item.price_per_unit_inc_tax }}

However they can be accessed individually, for example:

{{ line_items[0].product_title }}

Kit Contents

In order to access all kit contents, for each line item, these need to be in a nested loop as per the example below but can be accessed individually in the same way that line items can.

  • {{ line_items.contents.product_title }}
  • {{ line_items.contents.sellable_title }}
  • {{ line_items.contents.product_description }}
  • {{ line_items.contents.quantity }}

Example:

{% for line_item in line_items %}

<strong>{{ line_item.product_title }}:</strong>

{% for kit_content in line_item.contents %}

{{ kit_content.product_title }} {{ kit_content.sellable_title }} (x {{ kit_content.quantity }})

{% endfor %}

{% endfor %}

Did this answer your question?