Order Desk can submit your print on demand orders to Podbase. 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 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 guide for more information.
After Shipment, Move To
Select the folder you want orders to be moved into when Podbase sends shipment details back into Order Desk.
If Canceled, Move To
Select the folder you want orders to be moved into if a cancellation happens in Podbase.
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 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 will be used instead.
For information about how to set up your shipping preferences, read the Shipping Class Match 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 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 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 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 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 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. |