> 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/podbase-integration.md).
# Podbase Integration
Order Desk can submit your print on demand orders to [**Podbase**](https://www.podbase.com/). 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 Podbase, click **Manage Integrations** in the left sidebar. Under the **Print on Demand** tab, find and enable the Podbase integration.
Alternatively, search for *Podbase* from the available integrations search.
Enter your Podbase **API Key**, then click **Connect**:
> Order Desk isn’t able to help find or reset your credentials, as they can only be provided by the Podbase team.
### Integration Settings
Once connected, you’ll have a few settings where you can set your preferences for this integration.
#### Default Shipping Type
Select your preferred default shipping class. This will be used for any orders where the shipping method on the order doesn’t exactly match one of the shipping method names used by Podbase, or hasn’t been mapped to one of the shipping method names Podbase uses.
If you need to apply specific methods for certain orders, match your method names to Podbase’s names in the [Shipping Class Match](#shipping-class-match) section below.
#### After Import, Move To
Select the folder you want orders to be moved into after they are sent to Podbase.
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 Order Desk fetches shipment information from Podbase.
{% hint style="info" icon="lightbulb" %}
#### Podbase can also send shipment updates to Order Desk from their end.
Podbase may also send shipment updates directly to Order Desk through the Order Desk API. When a shipment is added this way, the **After Shipment, Move To** setting won’t run because the Podbase integration itself wasn’t the one that added the shipment.
If you want Podbase orders to move to a specific folder no matter how the shipment is added, you can create a rule with these settings:
* **Rule Type:** Order Rule
* **Event:** Shipment Is Added
* **Filter:** Order Fulfillment Service Equals Podbase
* **Action:** Change Folder
* **Folder Name:** *Your preferred folder name*
If you aren't familiar with rules, see the [**How to Work With Rules**](/guided-walkthroughs/rules-and-automations/how-to-work-with-rules.md) guide.
{% endhint %}
#### If Canceled, Move To
Select the folder you want orders to be moved into if a cancellation happens in Podbase.
#### Default Phone Number
Podbase requires a contact phone number for every order sent their way. Set this field and it will be used if your customer did not provide a phone number with their order. Make sure it starts with a country code, for example `+14185438090` for the USA.
#### View Products
This option links you to a page where you can see **all** available Podbase products. You’ll be able to find your Podbase `print_sku` and `variant_sku` here. Both details are **essential** for sending orders to Podbase.
#### Product Settings
For detailed information about what the product settings within the Podbase integration do, read the [**Print on Demand Product Settings**](/guided-walkthroughs/print-on-demand-walkthrough/print-on-demand-integration-product-settings.md) guide.
#### Shipping Class Match
The shipping methods you have set up in your shopping carts may not match the methods Podbase uses. To make sure your shipping preferences are sent to Podbase with each order, match your methods to theirs in the Shipping Class Match feature. If your shipping method name doesn’t match their shipping method name exactly, your [default shipping type](#default-shipping-type) will be used instead.
For information about how to set up your shipping preferences, read the [**Shipping Class Match**](/guided-walkthroughs/shipping-fulfillment-and-returns/how-to-set-up-shipping-class-matches.md) guide.
### Sending Orders to Podbase
Getting your orders ready to send to Podbase will take some setup time. For a detailed walkthrough of how to use Order Desk with your print on demand orders, read the [**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 Podbase exactly what to print for each order item.
| Field Name | Description |
| ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| print\_sku | **Required**. This is the SKU of the blank item you want Podbase to print on. You’ll be able to find this on the [available products](#view-products) page. |
| variant\_sku | **Required**. This is the SKU of the specific variant of the blank item you want Podbase to print on. You’ll be able to find this on the [available products](#view-products) page. |
| print\_url | **Required**. This is the publicly accessible link to the artwork file you want Podbase to print. |
### Rules Reference
In addition to the [**general set of rule events and actions**](/resources/rules-reference-events-filters-and-actions.md) in Order Desk, Podbase 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 the [**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 Podbase. To find them, type ***Podbase*** in the **Event** dropdown menu in the Rule Builder:
| Event | Description |
| ------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Order Scheduled to Podbase | Triggered when an order is scheduled to be sent from Order Desk to Podbase. This triggers immediately after the order is scheduled, so it can be used when you want to take action on the order at that point. |
| After Order Submitted to Podbase | Triggered after an order has been successfully submitted to Podbase. |
| Before Order Submitted to Podbase | Triggered just before an order is sent from Order Desk to Podbase. This is useful when you want to make last-minute updates before an order is sent. |
| Order Not Submitted to Podbase Because of Invalid SKU | Triggered when an order submission fails because one or more SKUs aren’t valid in Podbase. |
| Order Not Submitted to Podbase Because of General Error | Triggered when a general error prevents the order from being submitted to Podbase. |
| Order Not Submitted to Podbase Because No Products Available | Triggered when an order submission fails because no valid products were found for submission. |
#### Rule Actions
Podbase also supports specific rule actions that you can apply to your orders. These can be found in the **Actions** dropdown by searching for ***Podbase***:
| Action | Description |
| ----------------------- | ------------------------------------------ |
| Submit Order to Podbase | Sends an order from Order Desk to Podbase. |
---
# 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/podbase-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.
