> 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/podos-integration.md). # podOS Integration Order Desk can submit your print on demand orders to [**podOS**](https://printondemandsoftware.com/contact-us/). As orders are fulfilled, shipment details will automatically be pulled back into Order Desk and sent to the original shopping cart. ### Setup To connect to podOS, click on **Manage Integrations** in the left sidebar. Under the **Print on Demand** tab, find and click to enable the podOS integration. ![](https://d33v4339jhl8k0.cloudfront.net/docs/assets/57b0032590336059d4edf94f/images/690dfb343b2dd4515af0bc44/file-96o3D0no7l.png) Alternatively, search for *podOS* from the available integrations search. ![](https://d33v4339jhl8k0.cloudfront.net/docs/assets/57b0032590336059d4edf94f/images/690dfb5c404b9558a3b6dc20/file-kmU28WgrQu.png) Enter your podOS **Project Name** and **API Token**, then click Connect: ![](https://d33v4339jhl8k0.cloudfront.net/docs/assets/57b0032590336059d4edf94f/images/690dfb973b2dd4515af0bc46/file-o2YFDPGd5a.png) Please note that Order Desk isn’t able to help find or reset your credentials, as they can only be provided by the podOS team. ### 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/6939751fcfb32c6db5eaf09a/file-yu4iLHVVTt.png) #### After Import, Move To Select the folder you want orders to be moved into after they are sent to podOS. 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. #### Default Mail Class Select your preferred default mail class. The shipping class you set here will be used for all of your orders where the shipping method on the order does not match one of shipping method names used by podOS exactly or that has not been mapped to one of the shipping method names that podOS uses. If you need to apply specific methods for certain orders, match your method names to podOS names in the [Shipping Class Match section](#shipping-class-match) below. #### After Shipment, Move To Select the folder you want orders to be moved into when podOS sends shipment details back into Order Desk. #### View Base Products If you already know your product style codes but need to find the GFN Product IDs (`podos_gfn_product_id`), you can use this option. It will take you to a page where you can look up the GFN Product IDs by searching with those style codes. ![](https://d33v4339jhl8k0.cloudfront.net/docs/assets/57b0032590336059d4edf94f/images/6939769eca3f096f03a55b43/file-WbGgbSaj0T.png) Once you have the GFN Product IDs, you can use them to look up the related `podos_gfn_variant_id` if you need the specific variations later on. #### View GFN Variants This option links you to a page where you can see **all** of your podOS products. You’ll be able to find their `podos_gfn_variant_id` and all other related information: ![](https://d33v4339jhl8k0.cloudfront.net/docs/assets/57b0032590336059d4edf94f/images/6929b1b933236419124c97ba/file-ghtUDNCs84.png) You can also narrow down the list by searching for specific GFN Product IDs. The details you find on this page can be used to [prepare your items](#preparing-your-items) before you send orders for fulfillment. #### Inventory Management You can import your products from podOS into Order Desk by clicking the **Download Products** button. This will pull your blank product information from podOS and store it as inventory data in Order Desk. ![](https://251457507-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAQOLMUJWMYtrpQ7Oxxca%2Fuploads%2FQGV8QJOtvWZW8lHVkCWg%2Flegacy-0b7cd2f6195e2cedaf82.png?alt=media) #### Sync inventory Choose whether to have Order Desk regularly download products and their stock counts from podOS. #### Sync Update Interval Select how often you want Order Desk to pull stock counts from podOS. #### Product Settings ![](https://d33v4339jhl8k0.cloudfront.net/docs/assets/57b0032590336059d4edf94f/images/690dfda4404b9558a3b6dc27/file-XtpmBlcdfz.png) For detailed information on what the product settings within the podOS 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/691c8c28370c207c24ab3ad6/file-D7s0m2WfGu.png) The shipping methods that you have set up in your shopping cart(s) may not match the methods that podOS uses. To make sure your shipping preferences are sent through to podOS with each order, match your methods to theirs in the shipping class match feature. If your shipping method name does not match their shipping method name exactly, your [default mail class](#default-mail-class) will be used instead. For information on how to set up your shipping preferences, please read the [Shipping Class Match guide](/guided-walkthroughs/shipping-fulfillment-and-returns/how-to-set-up-shipping-class-matches.md). ### Sending Orders to podOS Getting your orders ready to send to podOS 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 Items The following fields can be set as variations or item metadata for each order item. These fields tell podOS exactly what to print for each order item. Depending on how your products are stored in Order Desk and how you manage products in podOS, you will use different fields. Choose the option that best matches your use case; whether you are sending pre saved products or building custom products on the fly. #### Pre-saved Products If you’ve already set up your products in podOS (including designs) ahead of time, you can set an item metadata or variation field called **podos\_variant\_id**. This should be the variant ID of the exact finished product you want podOS to print. | Field Name | Description | | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | podos\_variant\_id | Use this when you already know the exact pre designed product to print in podOS. This field points podOS directly to a single, specific product variation. | #### Custom Products Use this option when your products are not set up in podOS ahead of time and you want to send the product details along with the print files. In this case, you will use one of the product ID options below, plus your print file fields. | Field Name | Description | | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | podos\_gfn\_variant\_id | Use this for custom products where each SKU in your inventory represents one unique variation. Example: a Men’s Plain T Shirt with Color: White and Size: XS.You can find this data using the [View GFN Variants](#view-gfn-variants) option on the integration settings page. | | podos\_gfn\_product\_id | Use this if your inventory stores only the base product (for example, “Men’s Plain T Shirt”), and the variation details (like *size* and *color*) come from the order item itself.You can find this data using the [View Base Products](#view-base-products) option on the integration settings page.Order Desk will look at the available variations in podOS and automatically select the one that matches the variation data on the order item. | #### Print File Fields for Custom Products When sending custom products, you will also need to send the artwork file links and optional print settings below. | Field Name | Description | | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | print\_url\_x | Set a publicly accessible link to the artwork you want podOS to print. You can pass multiple artworks using **print\_url\_1** through **print\_url\_5**. | | print\_location\_x | Set the print location for the corresponding artwork. Supports **print\_location\_1** through **print\_location\_5**. If this is not set, the default location is **front**. | | print\_type\_x | Set the print type for the corresponding artwork. If this is not set, the default value is **DTG**. | ### Rules Reference In addition to the [**general set of rule events and actions**](/resources/rules-reference-events-filters-and-actions.md) in Order Desk, podOS 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 podOS. To find them, type ***podOS*** in the **Event** dropdown menu in the Rule Builder: ![](https://d33v4339jhl8k0.cloudfront.net/docs/assets/57b0032590336059d4edf94f/images/690e00a01fc20b0e46080a82/file-nklBBNwg5r.png) | Event | Description | | ------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | *Order Scheduled to podOS* | Triggered when an order is scheduled to be sent from Order Desk to podOS.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 podOS* | Triggers after an order has been successfully submitted to podOS. | | *Before Order Submitted to podOS* | Triggered just before an order is sent from Order Desk to podOS. This is useful in cases where you want to make last-minute updates before an order is sent. | | *Order Not Submitted to podOS Because of Invalid SKU* | Triggers when an order submission fails because one or more SKUs aren’t valid in podOS. | | *Order Not Submitted to podOS Because of General Error* | Triggers when a general error prevents the order from being submitted to podOS. | | *Order Not Submitted to podOS Because No Products Available* | Triggers when an order submission fails because no valid products were found for submission. | #### Rule Actions podOS also supports specific rule actions that you can apply to your orders. These can be found in the **Actions** dropdown by searching for ***podOS***: ![](https://d33v4339jhl8k0.cloudfront.net/docs/assets/57b0032590336059d4edf94f/images/690e010388188c55b8be1abc/file-6rDnsthM19.png) | Action | Description | | ----------------------- | ---------------------------------------- | | *Submit Order to podOS* | Sends an order from Order Desk to podOS. | --- # 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/podos-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.