> 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/integration-setup-guides/print-on-demand/usha-merchantile-integration.md).
# USHA Merchantile Integration
Order Desk can submit your print on demand orders to [USHA Mercantile](https://www.ushamercantile.com/). As orders are fulfilled, the shipment info will automatically be pulled back into Order Desk and sent back to the original shopping cart.
### Setup
To connect to USHA Mercantile, click on **Manage Integrations** in the left sidebar. Under the **Print on Demand** tab, find and click to enable the USHA Mercantile integration.
Alternatively, search for USHA Mercantile from the available integrations search.
Enter your USHA Mercantile credentials, then click to connect:
{% hint style="info" %}
Please note that Order Desk isn’t able to help find or reset your credentials, as they can only be provided by USHA Mercantile.
{% endhint %}
### Integration Settings
Set your preferences for the Usha Merchantile integration.
#### USHA Mercantile Help
Click *Need Help Getting Started?* to access helpful resources for using USHA Mercantile.
#### **After Import, Move To**
Select the folder you want orders to be moved into after they are sent to USHA Mercantile.
If you want to use a custom folder, create your own from Store Settings. See the[Working with Folders](https://help.orderdesk.com/article/180-quick-start-overview#folders) guide for more information.
#### **After Shipment, Move To**
Select the folder you want orders to be moved into when USHA Mercantile sends shipment details back into Order Desk.
### Product Settings
For more information on what the product settings within the USHA Mercantile integration do, please read the [Print on Demand Product Settings](https://help.orderdesk.com/article/405-print-on-demand-product-settings) guide.
### Sending Orders to USHA Mercantile
Getting your orders ready to send to USHA Mercantile will take some set up time. For a detailed walkthrough of how to use Order Desk with your Print on Demand orders, please read through our [Print on Demand Fulfillment](https://help.orderdesk.com/article/15-print-on-demand-fulfillment) guide.
#### **Preparing Your Orders**
The following details can be submitted for an order as either checkout data or order metadata.
| Field Name | Field Description |
| ----------- | ---------------------------------------------- |
| PackingSlip | Use to incluse a packing slip with your order. |
If you are unfamiliar with checkout data, see the [How to Work with Checkout Data](https://help.orderdesk.com/article/390-how-to-work-with-checkout-data) guide.
#### **Preparing Your Items**
The following fields can be set as variations or item metadata for each order item.
| Field Name | Field Description |
| ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| print\_url | Link to your artwork file so USHA Mercantile can print it. If product is part of a kit and requires multiple images, print\_url\_x can be used (e.g. print\_url\_1, print\_url\_2). Up to 6. |
| print\_sku | USHA Mercantile's product code/SKU for the item. If product is part of a kit and contains multiple printed items, print\_sku\_x can be used (e.g. print\_sku\_1, print\_sku\_2). Up to 6. |
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.orderdesk.com/integration-setup-guides/print-on-demand/usha-merchantile-integration.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
