Meta Variables of Qapla’

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 with your own company information.

 

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
[*TICKET_URL*] Ticketing URL on Qapla’ system
[*SITE_NAME*] The name of your site as set on Settings > Company & Channels
[*SITE_URL*] The link to your site as set in Settings > Company & Channels
[POD][/POD] e [*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.
[AMAZON]

[/AMAZON]

 The text inside these two tags will be shown in case the receiver’s email address is like “@marketplace.amazon”.
[NOAMAZON]

[/NOAMAZON]

 The text inside these two tags won’t be displayed in case the consignee’s email address is like “@marketplace.amazon”.
[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]Messagge only for UPS[/COURIER]

the text will appear only if the email is related to a UPS shipment.
[*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.
[*GLS-ITA_ECOM*] URL per GLS-ITA per lo svincolo ECOM (https://www.gls-italy.com/[…] )
[*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. (Meta Variable available for Aliexpress, Commercelayer e Shopware 6)
[*PRODUCT_LIST_IMG_NO_PRICES*] List of shipment products in table format with the product images, if available without prices. (Meta Variable available for Aliexpress, Commercelayer e Shopware 6)

 

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
[*CUSTOM1*] The three custom fields that can be loaded via API (together with [*CUSTOM2*] and [* CUSTOM3*])
[*STATUS_NAME*] The name of shipment current status (Ex. shipped)
[*UID*] Univocal value that is generated 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, enter on the email the link Tracking, to the tracking page.
[*SITE_NAME*] The name of your site as set on Settings > Company & Channels
[*SITE_URL*] The link to your site as set in Settings > Company & Channels
[POD][/POD] e [*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
[*CUSTOM1*] The three custom fields that can be loaded via API (together with [*CUSTOM2*] and [*CUSTOM3*])

Meta variables for tickets

Here is the list of available meta variables for 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”