Fulfillment Integration Product Settings

In most fulfillment integrations, there is a series of additional settings which provide more control over the information you want sent to your fulfillment service. This guide will cover how those settings can be used and how to set them up.

If you are looking for information on the product settings section in a print on demand integration, see the Print on Demand Product Settings guide instead.

Limitations

There is a 10,000 character limit on each integration page in Order Desk. Once this limit is passed, your data will be cleared off the page. If this happens to you, contact Order Desk support to see if your data can be retrieved. If you expect to put more than 10,000 characters in the Product Code Match and Product Code Skip fields, use the alternate options described under each setting instead.

Product Code Match

If the SKUs for your products listed in your shopping cart or a marketplace do not match the SKUs your fulfillment service uses, you can use the Product Code Match feature to tell Order Desk what SKUs should be changed to when sending orders to your fulfillment service.

As an example, if you have an item with the SKU PCT-099 in your shopping cart, this is how it will come into Order Desk in the order:

If your fulfillment service needs to know a different SKU for this same item, set the original SKU from the cart = to the SKU the fulfillment service needs to know:

If creating multiple matches, add them one per line.

Doing this will not change the SKU in Order Desk. Instead, Order Desk will swap the SKUs in the order information it sends to your fulfillment service so they receive the SKUs they need to fulfill your orders.

Product Code Match Bundles

Product Code Match can also be used to unpack bundles from a single SKU. This works the same as matching one SKU to another but using multiple SKUs instead:

PCT099=SKU1,SKU2,SKU3

You can also use the same SKU more than once:

DGT123=SKU1,SKU1,SKU2

When to Use Code Replace Instead

When using the Product Code Match feature, stock counts cannot be synced back into Order Desk from your fulfillment service or to your shopping cart for the original SKUs. If you would rather have the SKU changed directly in Order Desk, use the code replace inventory feature instead of Product Code Match.

Depending on the shopping cart or marketplace integration, code replace does have some options for syncing the stock counts on replaced SKUs.

Product Code Skip

In the product code skip box, you can add any SKUs that you do not want sent to your fulfillment service. Separate multiple SKUs with a comma or add them on separate lines.

If all items in an order have their SKUs in the Product Code Skip section, the entire order will be skipped and not submitted to the fulfillment integration.

Wildcard

Use * as a wildcard to skip any SKU that is a partial match. For example, if you want to skip sending all SKUs that have "mug" somewhere in the SKU, add mug* to the Product Code Skip feature.

When to Split Orders Instead of Using Product Code Match

The Product Code Skip feature is best used when you need to skip an item that will not be physically shipped, such as a gift card, or if you have items that you do not need to take action on from Order Desk.

If you have a more complex process in place, especially if you are sending orders to more than one integration or vendor, splitting your orders will be a better solution than Product Code Skip.

Gift Message Field

Some shopping cart and marketplace integrations send gift messages through with your orders. Order Desk stores these as Checkout Data:

In the above example, the Checkout Data field name is message_from_buyer. Set the exact Checkout Data field name, as it is on your orders, in the Gift Message Field box in the fulfillment integration settings:

If this Checkout Data field exists on an order, it will be sent to your fulfillment service in the Gift Message Field.

For information on what Checkout Data is and how to use it, read the How to Work with Checkout Data guide.

Inventory Location Match

For inventory that is stored in Order Desk, there is a Location field on each item:

To send specific items to your fulfillment service, add a Location name that is exactly the same on all items for the fulfillment service, then set that same name in the Inventory Location Match field in the integration settings. This setting is case and space sensitive. For example, if mugrunner is used in the integration settings but some items have MugRunner in the Location name field, those items will be skipped, causing errors and delays in your fulfillment process.

Only the items in orders with a Location name that matches what is set in this field will be submitted to the fulfillment integration, and any orders where all items do not match will not be submitted at all.

For this to work, the Add Inventory Details to Order Items setting must be enabled in your store settings, or a rule must be in place to sync the inventory details into your orders before they are submitted for fulfillment.

For more information on inventory in Order Desk, see the How to Work with Inventory Details guide.

When to Split Orders Instead of Using Inventory Location Match

For merchants with a simple workflow and a limited number of fulfillment integrations they work with or products already stored in Order Desk, this setting can be used. 

For merchants who work with multiple fulfillment services, have more than a few products or add to or change their products regularly, it is better to avoid confusion by splitting orders rather than using the Inventory Location Match field.

Picklist Message Field

Set the name of a Checkout Data field to be sent to the fulfillment integration as a note about the order.

For information on what Checkout Data is and how to use it, read the How to Work with Checkout Data guide.