> For the complete documentation index, see [llms.txt](https://vu-custom.gitbook.io/vu-custom/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vu-custom.gitbook.io/vu-custom/vu-oms/order-travelers.md).

# Order Travelers

## What is a Traveler?

A Traveler is a specialized document (digital or printed) generated for the factory floor. It acts as the definitive instruction set for the manufacturing or decoration team fulfilling a customized order.

A Traveler focuses on production details. It includes:

* **Order & Recipe Details:** Precise order and recipe details required to build the product.
* **Visual Perspectives:** Reference photos showing exactly what the customized product should look like.
* **Artwork:** Reference to the specific artwork generated by VU or uploaded by the customer.

### **Key functions of a Traveler:**

* **Factory Efficiency:** Provides clear instructions to operators building or decorating the product.
* **Barcodes for Tracking:** The system can generate barcodes on the Traveler. When scanned by factory workers, these barcodes can pull up real-time order information, update statuses, or track the item as it moves between different stations on the factory floor.
* **Customizability:** The layout is not static; it is fully configurable to match specific factory requirements.

## Association to Factory

Travelers are deeply associated with specific Factory workflows. Since every manufacturing facility has different equipment, layout, and Quality Control processes, the Traveler must be adaptable.

* **Workflow Integration:** If a factory uses handheld scanners, the Traveler is configured to display Barcodes at the top of the page.
* **Brand Specific:** Factories producing for multiple brands can use different Traveler templates that load the specific logo and shipping rules for that client.<br>

## Configuring a Traveler

Travelers are fully configurable using **HTML**, **CSS**, and **Liquid** templating language. This allows for complete control over the layout, logic and you can inject dynamic data.

To configure a traveler, navigate to **Production > Travelers** and select **Add New** or **Edit**.

### The Configuration Screen

The configuration screen consists of general settings and the code body:

1. **Name:** The descriptive name that will appear in the "Print" dropdown menu on the Production dashboard.
2. **Code:** A unique system identifier used by the backend.
3. **HTML Body:** This contains the layout code. Using Liquid logic, you can perform advanced functions.

<table><thead><tr><th width="345">Field</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Traveler name.</td></tr><tr><td>Code</td><td>Traveler code.</td></tr><tr><td>Product Codes</td><td>Products to include in the Traveler.</td></tr><tr><td>Type</td><td>Traveler format.</td></tr><tr><td>HTML Body</td><td>Customisable code</td></tr></tbody></table>

{% hint style="warning" %}
Use the "Traveler Configuration" document to know and use all the variables in the traveler
{% endhint %}

## Sample Traveler

Below is an example of a configured Traveler output. This specific layout is optimized for a garment factory:

<figure><img src="/files/zXD7oT5ujBHmvmvV25rK" alt=""><figcaption></figcaption></figure>

### **The Header (Logistics)**

Located at the top of the page, this section is for the shipping and logistics team.

* **Brand Logo:** Immediate visual identification of the client.
* **Order Barcode:** Scannable code linked to the specific Order ID.
* **Dates & Counts:** Displays the order date and, the "Item Count" (e.g., Item 1 of 1 or Item 1 of 5) to prevent partial shipments.

### **The Body (Production Details)**

Located in the center, this guides the customization operator.

* **Product:** SKU, Description, and **Quantity** (highlighted in red for visibility).
* **Personalization Info:** This displays the dynamic "Recipe" data.
  * Inputs: "Team Captain" (Text), "White" (Color).
* **Thumbnails:** A composite image generated by the Customizer, giving the operator a visual proof for quality assurance.


---

# 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://vu-custom.gitbook.io/vu-custom/vu-oms/order-travelers.md?ask=<question>&goal=<endgoal>
```

`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.