Qapla' : Meta Variables (for emails and tracking page)

Created by Dagmar Sporck, Modified on Fri, 26 Apr, 2024 at 10:52 AM by Dagmar Sporck

How to use Meta Variables of Qapla’?

The meta variables can be entered in different communications of Qapla’, to include information that are within the shipments, making these communications to the end customer more personalized.

Meta variables for transactional e-mails

Here is the list of available meta variables for transactional e-mails:

Variable	Definition
[LOGO]	The logo
[REFERENCE]	The field that has been uploaded as “Reference”
[ORDER_DATE]	The field that has been uploaded as “Order date”
[DELIVERY_DATE]	The delivery date occurred as communicated by the courier.
[NAME]	The field that has been uploaded as “Name”
[ADDRESS]	The uploaded field as “Address” and the field “City” and “Province”
[EMAIL]	The field that has been uploaded as “email”
[COURIER]	The courier’s name
[TRACKING_NUMBER]	Tracking number of the shipment
[TRACKING_LINK]	Tracking on Qapla’ system, enter on the email the link Tracking, to the tracking page.
[TRACKING_URL]	URL Tracking on Qapla’ system, enter the link such as https://tracking.qapla.it/****
[COURIER_TRACKING_URL]	URL tracking to the courier’s site
[TICKET_LINK]	Ticketing on Qapla’ system, if the function is active.
[TICKET_URL]	Ticketing URL on Qapla’ system, if the function is active.
[SITE_NAME]	Your site name as set in: [Channel name] > Configure > 1. Channel
[SITE_URL]	The link to your site as set in: [Channel name] > Configure > 1. Channel
[POD][/POD] and [AMOUNT]	Two conditional tags and the metavariable have been introduced for the payment on delivery [AMOUNT] [POD] The amount to pay on delivery is [AMOUNT][/POD] If the order is not set as POD the sentence won’t be written in the mail.
[COURIER:COURIER_CODE][/COURIER]	The text between two tags, with COURIER_CODE equal to a courier code of Qapla’, will be shown only inside the emails for that courier. Example:[COURIER:UPS]Message only for UPS[/COURIER] will make the text appear only if the email is related to a UPS shipment. Find the corresponding carrier code here
[CUSTOM1]	The three custom fields that can be loaded via API (together with [CUSTOM2] and [CUSTOM3])
[PRODUCT_LIST]	List of the shipment products in table format.
[PRODUCT_LIST_NO_PRICES]	List of the shipment products in table format without prices.
[STATUS_NAME]	The name of shipment current status (Ex. shipped)
[STATUS_ICON]	HTML tag is created to display the icon corresponding to the shipment current status
[STATUS_ICON_LINK]	The link corresponding to the icon of current status
[ORDER_ID]	Any IDs of the platform order
[PRODUCT_LIST_IMG]	List of shipment products in table format with the product images, if available.
[PRODUCT_LIST_IMG_NO_PRICES]	List of shipment products in table format with the product images, if available without prices.
[EAN8][/EAN8]	A barcode EAN-8 is created from a text, number or link entered within.
[EAN13][/EAN13]	A barcode EAN-13 is created from a text, number or link entered within.
[QRCODE][/QRCODE]	A QR code is created from a text, number or link entered within.

Meta variables for tracking page

Here is the list of available meta variables for the tracking page:

Variable	Definition
[REFERENCE]	The field that has been uploaded as “Reference”
[ORDER_DATE]	The field that has been uploaded as “Order date”
[NAME]	The field that has been uploaded as “Name”
[ADDRESS]	The uploaded field as “Address” and the field “City” and “Province”
[EMAIL]	The field that has been uploaded as “email”
[TRACKING_NUMBER]	Tracking number of the shipment
[TICKET_LINK]	Ticketing on Qapla’ system, if the function is available.
[CUSTOM1]	The three custom fields loadable via API (together with [CUSTOM2] and [* CUSTOM3*])
[STATUS_NAME]	The name of shipment current status (Ex. shipped)
[UID]	Univocal value that is created each time the variable is replaced

Meta variables for SMS

Here is the list of available meta variables for text messages:

Name	Definition
[REFERENCE]	The field that has been uploaded as “Reference”
[ORDER_DATE]	The field that has been uploaded as “Order date”
[NAME]	The field that has been uploaded as “Name”
[COURIER]	The courier’s name
[TRACKING_NUMBER]	Tracking number of the shipment
[TRACKING_LINK]	Tracking on Qapla’ system, it enters on the email the link Tracking, to the tracking page.
[SITE_NAME]	Your site name as set in: [Channel name] > Configure > 1. Channel
[SITE_URL]	The link to your site as set in: [Channel name] > Configure > 1. Channel
[POD][/POD] and [AMOUNT]	Two conditional tags and the metavariable [AMOUNT] have been introduced for the payment on delivery [POD] The amount to pay on delivery is [AMOUNT][/POD] If the order is not set as POD the sentence won’t be written in the mail.
[CUSTOM1]	The three custom fields loadable via API (together with [CUSTOM2] and [CUSTOM3])

Meta variables for tickets

Here is the list of available meta variables for the tickets:

Name	Definition
[REFERENCE]	The field that has been uploaded as “Reference”
[NAME]	The field that has been uploaded as “Name”
[ADDRESS]	The uploaded field as “Address” and the field “City” and “Province”
[EMAIL]	The field that has been uploaded as “email”
[COURIER]	The courier’s name
[TRACKING_NUMBER]	Tracking number of the shipment
[TELEPHONE]	The field that has been uploaded as “Phone”

Name	Definition
[REFERENCE]	The field that has been uploaded as “Reference”
[ORDER_DATE]	The field that has been uploaded as “Order date”
[NAME]	The field that has been uploaded as “Name”
[COURIER]	The courier’s name
[TRACKING_NUMBER]	Tracking number of the shipment
[TRACKING_LINK]	Tracking on Qapla’ system, it enters on the email the link Tracking, to the tracking page.
[SITE_NAME]	Your site name as set in: [Channel name] > Configure > 1. Channel
[SITE_URL]	The link to your site as set in: [Channel name] > Configure > 1. Channel
[POD][/POD] and [AMOUNT]	Two conditional tags and the metavariable [AMOUNT] have been introduced for the payment on delivery [POD] The amount to pay on delivery is [AMOUNT][/POD] If the order is not set as POD the sentence won’t be written in the mail.
[CUSTOM1]	The three custom fields loadable via API (together with [CUSTOM2] and [CUSTOM3])