{{ store_name }} Receipt

> For the complete documentation index, see [llms.txt](https://help.orderdesk.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.orderdesk.com/guided-walkthroughs/templates-emails-and-order-documents/how-to-use-barcodes.md). # How to Use Barcodes If you need a way to include barcodes in your email or receipt templates, you can do so with Order Desk and some [Twig](/technical-documentation/templates-and-documents/how-to-build-custom-templates.md). ### Adding QR Codes To add a QR Code to a template using Twig, use this filter: `|qrcode` or: `|qrcode(300)` for a larger size. The default size is 150. Example: `

` ### Adding Barcodes To add a barcode, use this Twig filter: `|barcode` or: `|barcode(type, width, height)` Replace (type, width, height) with the values needed. The default values are (“C128”, 2, 80). Example: `

` ### Barcode Types Available barcode options are C39 C39+ C39E C39E+ C93 S25 S25+ I25 I25+ C128 C128A C128B C128C EAN2 EAN5 EAN8 EAN13 UPCA UPCE MSI MSI+ POSTNET PLANET RMS4CC KIX IMB CODABAR CODE11 PHARMA PHARMA2T ### Using Barcode Scanners Order Desk can listen for your USB scanner input. Depending on how your barcodes are set up, you can do one of three things with a scanner. Enable this functionality by adding **USBSCANNER** to the feature tag section of your [Store Settings](/guided-walkthroughs/using-order-desk/manage-store-settings.md#store-settings) page. #### Access Order Detail Page This works with regular QR codes or barcodes. Example code to pull up the order number: `

` #### Move Order to Different Folder This works with regular QR codes or barcodes. Example code for moving an order to folder 300: `

` #### Execute Button Action or Integration Submission In order to execute a button action from Order Desk using your QR code and scanner you will need to use the following code (using a button called “Blue” as an example): `

` Please note: You have to have the Order Desk app open and in focus to ensure this works. Also, the output from the QR code must end in a new line. If you wish to test this we recommend opening a text-editor, such as notepad, scanning a QR code and you should see the output to the text-editor as below, with a new line at the end. `^submit_to_blue_zvoxh9^` If you are not using a USB Scanner but just wish to use your phone to generate links that can be pressed to activate buttons, you need to be logged in on your phone and use the code below: `

` Note: For best results, we recommend using a **WoneNice USB Laser Barcode Scanner**. Additionally, your keyboard language must be US. ### Sample Barcode Email Template The following code is an example of an email template you can use in Order Desk that would send the customer a receipt and create barcodes on the spot. The variable field names are slightly different from the receipt template itself. In this example a barcode is generated for every item on the order, and the barcode will read the item’s unique ID. ### Related Articles * [How to Build Custom Templates](/technical-documentation/templates-and-documents/how-to-build-custom-templates.md) ### Embedded code sample ``` {{ store_name }} Receipt Print {% for key, order in orders %} {{ key > 0 ? '

' }}

{# This is a good place to put in a logo if you want should be https: #} {# ${{ store_name|e }}$ #}

{{ store_name }}

Receipt
Date: {{ order.date_added|date_modify("+0 hours")|date(store_date_format, store_timezone) }}
Order Number: {{ order.source_id }}
Email: {{ order.email }}
Phone: {{ order.shipping.phone }}
Shipping: {{ order.shipping_method }}
{{ key }}: {{ val }}

Invoice Address:
{{ order.customer.first_name }} {{ order.customer.last_name }}
{% if order.customer.company %}{{ order.customer.company }}
{% endif %} {{ order.customer.address1 }}
{% if order.customer.address2 %}{{ order.customer.address2 }}
{% endif %} {{ order.customer.city }}, {{ order.customer.state }} {{ order.customer.postal_code }}
{{ order.customer.country != store_country ? order.customer.country }}

Shipping Address:
{{ order.shipping.first_name }} {{ order.shipping.last_name }}
{% if order.shipping.company %}{{ order.shipping.company }}
{% endif %} {{ order.shipping.address1 }}
{% if order.shipping.address2 %}{{ order.shipping.address2 }}
{% endif %} {% if order.shipping.address3 %}{{ order.shipping.address3 }}
{% endif %} {% if order.shipping.address4 %}{{ order.shipping.address4 }}
{% endif %} {{ order.shipping.city }}, {{ order.shipping.state }} {{ order.shipping.postal_code }}
{{ order.shipping.country != store_country ? order.shipping.country }}

{# Show Products #} {# List of Items in Order #} {% for item in order.order_items %} {% endfor %} {# Show Totals #} {% if order.shipping_total > 0 %} {% endif %} {% if order.tax_total > 0 %} {% endif %} {% if order.discount_list|length > 0 %} {% for discount in order.discount_list %} {% endfor %} {% endif %}

Product	Price	Qty	Subtotal
{{ item.name }} {# Checkout Data and Variations #} {% if item.variation_list\|length > 0 %} {% for key, val in item.variation_list %} {{ key }}: {{ val }} {% endfor %} {% endif %}	{{ item.price\|money_format }}	{{ item.quantity }}	{{ (item.quantity * item.price)\|money_format }}
Shipping:			{{ order.shipping_total\|money_format }}
Tax:			{{ order.tax_total\|money_format }}
{{ discount.name\|e }}:			{{ discount.amount\|money_format }}
Total:			{{ order.order_total\|money_format }}

{# Show a Nice Shadow Image at the Bottom of The Table #}

{# This is a nice place to put a thank-you message #}

{% endfor %} ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.orderdesk.com/guided-walkthroughs/templates-emails-and-order-documents/how-to-use-barcodes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.