> 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/fulfillment-services/commonsku-integration.md).

# commonsku Integration

> New to Order Desk? Order Desk collects all your orders from all your sales channels in one place and sends them to your chosen fulfillment services automatically.
>
> <i class="fa-computer" style="color:$primary;">:computer:</i> [See all integrations](https://www.orderdesk.com/integrations/) . <i class="fa-wallet" style="color:$primary;">:wallet:</i> [Pricing](https://www.orderdesk.com/pricing/) . <i class="fa-arrow-right" style="color:$primary;">:arrow-right:</i> [Start free trial](https://app.orderdesk.me/account-setup)

Order Desk can import orders from your shopping carts, apply any necessary details, and send them to [commonsku](https://commonsku.com/) as projects and sales orders. You can send regular products as well as items that need custom artwork or decoration.

Once orders have shipped, Order Desk can pull the shipment details from commonsku and send them back to your shopping carts, if your store is set up for it.

### Setup

To connect to commonsku, click on the **Manage Integrations** link in the left sidebar and under the **Fulfillment** tab find and enable the commonsku integration.

<figure><img src="https://251457507-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAQOLMUJWMYtrpQ7Oxxca%2Fuploads%2F8Io4WXLo4U1uQ27IACXQ%2FCleanShot%202026-11-20%20at%2015.07.09%402x.png?alt=media&amp;token=5a7687ab-9514-4717-9c11-eba3bd6eaaa3" alt=""><figcaption></figcaption></figure>

Alternatively, search for *commonsku* from the available integration search.

<figure><img src="https://251457507-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAQOLMUJWMYtrpQ7Oxxca%2Fuploads%2FlR3WiNX2aX7hsNhBOYAV%2FCleanShot%202026-11-20%20at%2015.09.05%402x.png?alt=media&amp;token=c37bf9a5-86bb-4868-84e7-e7b9a8df4cfd" alt=""><figcaption></figcaption></figure>

Choose the preferred environment you want to connect to. Production is selected by default and should be used for real orders.

Enter your API key and click **Connect**

<figure><img src="https://251457507-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAQOLMUJWMYtrpQ7Oxxca%2Fuploads%2FNUaY6XYWbdfVlRHqIKMd%2FCleanShot%202026-11-20%20at%2015.11.12%402x.png?alt=media&amp;token=330b7292-1b8b-4095-90f7-30d3408b3b20" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Order Desk isn't able to help find or reset your commonsku API Key. That information can only be provided by the commonsku team.
{% endhint %}

### Integration Settings

After you have connected the integration, you can apply any necessary details or preferences to the settings.

<figure><img src="https://251457507-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAQOLMUJWMYtrpQ7Oxxca%2Fuploads%2FnzRI4HypuicCbwEuM27q%2FCleanShot%202026-11-20%20at%2015.13.29%402x.png?alt=media&amp;token=7d668db9-5757-4099-8de5-5dee629aab03" alt="" width="563"><figcaption></figcaption></figure>

#### Client

Select the commonsku client that Order Desk should create projects and shipping addresses under.

#### Event Type

Select the event type you want commonsku to use when creating projects from your orders.

#### Order Rep

Select the commonsku user who should be assigned as the project creator, order rep, and client rep for your orders.

#### Imprint Method

Select the default imprint method to use for items that have artwork.

#### After Import, Move To

Select the folder where orders should be moved after they're successfully sent to commonsku. See the [**Working with Folders**](https://help.orderdesk.com/start-here/getting-started-series/quick-start-overview.md#working-with-folders) guide for more information on how folders work.

#### After Shipment, Move To

Select the folder you want orders to be moved into as commonsku sends shipment details back to Order Desk.

#### If Canceled, Move To

Select the folder orders should be moved to if they are canceled at commonsku.

### Product Settings

<figure><img src="https://251457507-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAQOLMUJWMYtrpQ7Oxxca%2Fuploads%2F1yCZtaPEuv5GbbmEyt6p%2FCleanShot%202026-11-20%20at%2015.17.20%402x.png?alt=media&amp;token=48ce145e-df3b-4512-a8e7-974149f8b54f" alt=""><figcaption></figcaption></figure>

For more information on what these product settings in the commonsku integration are for and how to use them, read the [Fulfillment Integration Product Settings](https://help.orderdesk.com/integration-setup-guides/fulfillment-services/fulfillment-integration-product-settings) guide.

### Preparing your orders

You can set the following fields as checkout data or order metadata to customize the details sent to commonsku for individual orders.

If you're unfamiliar with checkout data, see the [How to Work with Checkout Data](https://help.orderdesk.com/guided-walkthroughs/orders-and-folders/how-to-work-with-checkout-data) guide.

| Field Name               | Field Description                                                                                                                                                                     |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| commonsku\_client\_id    | The commonsku client ID to create the project and shipping address under. Overrides the **Client** selected in your integration settings.                                             |
| commonsku\_rep\_email    | The login email of the commonsku user who should be assigned as the project's creator, order rep, and client rep. Overrides the **Order Rep** selected in your integration settings.  |
| commonsku\_inhands\_date | The in-hands date for the project. Most common date formats are accepted. If this field is missing or the date can't be read, Order Desk uses the following day as the in-hands date. |
| customer\_po             | The customer PO to include on the commonsku sales order. If this isn't set, Order Desk uses the order's source ID.                                                                    |
| comment or note          | Adds a note to the sales order introduction. The note appears on a separate **Note:** line alongside the order number, email, phone, and shipping method details.                     |

### Preparing your Items

You can add the following fields as variations or item metadata for each item in an order.

#### Product Matching

Order Desk can send regular stock items to commonsku, so you don't need to add print files to every item.

The following fields control how Order Desk identifies the products to include in your commonsku sales orders.

| Field Name             | Field Description                                                                                                                                                                                                                           |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| print\_sku             | The SKU Order Desk should use to find the matching product in commonsku. This is also the SKU used by the [Product Code Match and Product Code Skip settings](#product-settings). If neither field is set, Order Desk uses the item's code. |
| commonsku\_product\_id | The commonsku product ID to use for the item. If this is provided, Order Desk adds the product directly to the sales order without looking it up by SKU.                                                                                    |

#### Artwork and Decoration

If you're sending products that need printing or decoration, you can include artwork URLs and specify where each design should be applied.

commonsku supports up to **five print files** per item. Each print file is added as artwork under its own decoration location.

| Field Name             | Field Description                                                                                                                                                                                              |
| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| print\_url\_x          | The URLs for the artwork files to include with the item. Each file is added to its own decoration location in commonsku. For multi-print items, use up to **5** fields: `print_url_1` through `print_url_5`.   |
| print\_location\_x     | The name of the decoration location for the corresponding print file, such as `Front`, `Back`, or `Left Sleeve`. For multi-print items, use up to **5** fields: `print_location_1` through `print_location_5`. |
| commonsku\_imprint\_id | The commonsku imprint method ID to use for the item's artwork. This overrides the [Imprint Method](#imprint-method) selected in your integration settings.                                                     |

If an item doesn't have any print URLs, Order Desk sends it to commonsku without artwork.

{% hint style="warning" %}
If an item has a print file, an imprint method must be available. You can either select a default[ **Imprint Method**](#imprint-method) in your integration settings or add `commonsku_imprint_id` to the item. If neither is available, the order won't be submitted.
{% endhint %}

### Rules Reference

Along with the [general rule events and actions](https://help.orderdesk.com/resources/rules-reference-events-filters-and-actions.md) available in Order Desk, commonsku has its own events and actions. You won't find these on the integration settings page. Instead, you can find them in the **Rule Builder** by searching for *commonsku*.

If you're new to rules in Order Desk, start with the [How to Work With Rules](https://help.orderdesk.com/guided-walkthroughs/rules-and-automations/how-to-work-with-rules.md) guide.

#### Rule Events

The following events are specific to commonsku. To find them, type *commonsku* in the **Event** dropdown menu in the Rule Builder:

| Event                                                          | Description                                                                                                                                                                                                      |
| -------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Order Scheduled to commonsku                                   | Triggered when an order is scheduled to be sent from Order Desk to commonsku. 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. |
| Before Order Submitted to commonsku                            | Triggered just before an order is sent from Order Desk to commonsku. This is useful when you want to make last-minute updates before an order is sent.                                                           |
| After Order Submitted to commonsku                             | Triggered after an order is successfully sent to commonsku.                                                                                                                                                      |
| Order Not Submitted to commonsku Because of General Error      | Triggered when a general error prevents the order from being submitted to commonsku.                                                                                                                             |
| Order Not Submitted to commonsku Because No Products Available | Triggered when an order submission fails because no valid products were found for submission.                                                                                                                    |
| Order Canceled at commonsku                                    | Runs after Order Desk successfully cancels an order at commonsku.                                                                                                                                                |

#### Rule Actions

commonsku also supports specific rule actions that you can apply to your orders. These can be found in the **Actions** dropdown by searching for *commonsku*:

| Action                    | Description                                                          |
| ------------------------- | -------------------------------------------------------------------- |
| Submit Order to commonsku | Sends an order from Order Desk to commonsku.                         |
| Cancel Order at commonsku | Attempts to cancel an order that has already been sent to commonsku. |


---

# 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/fulfillment-services/commonsku-integration.md?ask=<question>&goal=<user_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.
