> 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/inkthreadable-integration.md). # Inkthreadable Integration Order Desk can submit your print on demand orders to [**Inkthreadable**](https://www.inkthreadable.co.uk/). 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 Inkthreadable, click on **Manage Integrations** in the left sidebar. Under the **Print on Demand** tab, find and click to enable the Inkthreadable integration. ![](https://d33v4339jhl8k0.cloudfront.net/docs/assets/57b0032590336059d4edf94f/images/69822a8a687ebe31fc993c7b/file-PoN1IVauhg.png) Alternatively, search for *Inkthreadable* from the available integrations search: ![](https://d33v4339jhl8k0.cloudfront.net/docs/assets/57b0032590336059d4edf94f/images/69822a7f4b437e7a8c1c9ff1/file-uC2JIMMb3h.png) Enter your Inkthreadable credentials (**App ID** and **Secret Key**), then click to connect: ![](https://d33v4339jhl8k0.cloudfront.net/docs/assets/57b0032590336059d4edf94f/images/69822de9cd5410406a95b68a/file-AxdsWEio4b.png) Please note that Order Desk isn’t able to help find or reset your credentials, as they can only be provided by Inkthreadable. ### Integration Settings Once connected, you will have a few settings where you can set your preferences for this integration. ![](https://d33v4339jhl8k0.cloudfront.net/docs/assets/57b0032590336059d4edf94f/images/69822e7ccd5410406a95b68e/file-axLDP8T9Qm.png) #### Default Mail Class Choose the mail class you want Inkthreadable to use for orders. If you need to apply specific methods for certain orders, match your method names to their names in the [Shipping Class Match section](#shipping-class-match) below. #### After Import, Move To Select the folder you want orders to be moved into after they are sent to Inkthreadable. If you want to use a custom folder, create your own from Store Settings. See the [**Working with Folders**](/start-here/getting-started-series/quick-start-overview.md#working-with-folders) guide for more information. #### After Shipment, Move To Select the folder you want orders to be moved into when Inkthreadable sends shipment details back into Order Desk. #### If Canceled, Move To Select the folder you want orders to be moved into when they get canceled at Inkthreadable. #### Notification URL Add this URL to your Inkthreadable account and enable it for both the **Order Shipped** and **Order Updated** events. This lets Order Desk know when the status of your orders changes in Inkthreadable. #### Product Settings ![](https://d33v4339jhl8k0.cloudfront.net/docs/assets/57b0032590336059d4edf94f/images/698234e54b437e7a8c1ca02d/file-XrxN2ZIako.png) For more information on what the product settings within the Inkthreadable integration do, please read the [**Print on Demand Product Settings**](/guided-walkthroughs/print-on-demand-walkthrough/print-on-demand-integration-product-settings.md) guide. #### Shipping Class Match ![](https://d33v4339jhl8k0.cloudfront.net/docs/assets/57b0032590336059d4edf94f/images/698234f5d8db7178f763fd84/file-Afa6TgI7S3.png) If the shipping methods you set up in your shopping cart(s) don’t match the shipping method names Inkthreadable uses, they won’t know what methods you intend for them to use. When this happens, the [default mail class applied above](#integration-settings) will be used instead for all of your orders. To tell Inkthreadable what methods you want them to use, you will need to match your method names to theirs. This can be done in the shipping class match section. For detailed instructions on setting this up, please read through the [shipping class match](/guided-walkthroughs/shipping-fulfillment-and-returns/how-to-set-up-shipping-class-matches.md) guide. ### Sending Orders to Inkthreadable Getting your orders ready to send to Inkthreadable 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**](/guided-walkthroughs/print-on-demand-walkthrough/print-on-demand-fulfillment.md) guide. #### Preparing Your Orders The following details can be submitted for an order as either checkout data or order metadata. | **Field Name** | **Field Description** | | -------------- | ----------------------------------------------------- | | brand | Use this to pass the brand name for the order. | | packing\_slip | Use this to pass the packing slip URL. | | note | Use this to pass additional comments about the order. | If you are unfamiliar with checkout data, see the [**How to Work with Checkout Data**](/guided-walkthroughs/orders-and-folders/how-to-work-with-checkout-data.md) guide. #### Preparing Your Items The following fields can be set as variations or item metadata for each order item. | **Field Name** | **Field Description** | | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | print\_sku | **Required.** Inkthreadable’s product code or SKU for the item. | | print\_url\_x | **Required.** Link to your artwork file. Supports up to 5 files using **print\_url\_1** through **print\_url\_5**. | | print\_location\_x | **Required.** Sets where each artwork should be printed on the item. Supports up to 5 values using **print\_location\_1** through **print\_location\_5**. Each location must match the related **print\_url\_x**.Supported location values include **front** and **back**. For other supported values, reach out to Inkthreadable. | | print\_preview\_x | Optional. Link to a preview image of the finished product. Supports up to 5 values using **print\_preview\_1** through **print\_preview\_5**. | | label\_type | Optional. Sets the label type for the item. Defaults to **printed** if unset. | | item\_brand | Optional. Brand name for the item. | ### Rules Reference In addition to the [**general set of rule events and actions**](/resources/rules-reference-events-filters-and-actions.md) in Order Desk, Inkthreadable includes a number of rule events and actions that are specific to the integration. These aren’t found directly on the integration page. Instead, you’ll need to use the **Rule Builder** to access them. If you’re new to using rules in Order Desk, we recommend starting with our [**How to Work With Rules**](/guided-walkthroughs/rules-and-automations/how-to-work-with-rules.md) guide. #### Rule Events The following events are specific to Inkthreadable. To find them, type ***Inkthreadable*** in the **Event** dropdown menu in the Rule Builder: ![](https://d33v4339jhl8k0.cloudfront.net/docs/assets/57b0032590336059d4edf94f/images/6983926823e398a1db70d5d1/file-n1Tl9KMYPc.png) | Event | Description | | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | *Order Canceled at Inkthreadable* | Triggered when an order is canceled at Inkthreadable. | | *Order Scheduled to Inkthreadable* | Triggered when an order is scheduled to be sent from Order Desk to Inkthreadable.This triggers immediately after the order is scheduled to be sent, so it can be used when you want to take immediate action on the order at that point. | | *After Order Submitted to Inkthreadable* | Triggers after an order has been successfully submitted to Inkthreadable. | | *Before Order Submitted to Inkthreadable* | Triggered just before an order is sent from Order Desk to Inkthreadable. This is useful in cases where you want to make last-minute updates before an order is sent. | | *Order Not Submitted to Inkthreadable Because of Invalid SKU* | Triggers when an order submission fails because one or more SKUs aren’t valid in Inkthreadable. | | *Order Not Submitted to Inkthreadable Because of General Error* | Triggers when a general error prevents the order from being submitted to Inkthreadable. | | *Order Not Submitted to Inkthreadable Because No Products Available* | Triggers when an order submission fails because no valid products were found for submission. | #### Rule Actions Inkthreadable also supports specific rule actions that you can apply to your orders. These can be found in the **Actions** dropdown by searching for ***Inkthreadable***: ![](https://d33v4339jhl8k0.cloudfront.net/docs/assets/57b0032590336059d4edf94f/images/6983929596ea5b1d64be9a03/file-xboKKndDeV.png) | Action | Description | | ------------------------------- | --------------------------------------------------------------------------- | | *Submit Order to Inkthreadable* | Sends an order from Order Desk to Inkthreadable. | | *Cancel Order at Inkthreadable* | Attempts to cancel an order that was previously submitted to Inkthreadable. | --- # 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/integration-setup-guides/print-on-demand/inkthreadable-integration.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.