> 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/guided-walkthroughs/shipping-fulfillment-and-returns/how-to-set-up-shipping-method-matches.md).

# How to Set Up Shipping Method Matches

Order Desk integrates with several retail middleware cart platforms (such as [**DSCO Supplier**](/integration-setup-guides/sales-channels/dsco-supplier-integration.md), [**Rithum**](/integration-setup-guides/sales-channels/rithum-integration.md) and more). These services connect to multiple retail vendors, and each vendor may require a specific, supported shipping service whenever a shipment is created for an order.

This guide explains how to set up **Shipping Method Matches**, which let you map your shipment details into the format your retail vendors expect.

### Overview

Some middleware retail vendors require a specific *shipping service value* to be passed back when submitting shipments. However, the shipping carrier and shipping method values on your shipments might not always match what the vendor is expecting.

The Shipping Method Match feature lets you map carrier and method combinations on incoming shipments to the shipping service your vendor requires.

**TIP**

Order Desk has some built-in logic to estimate what the shipping service value should be when sending shipment details back to your integration.

The Shipping Method Match setting gives you an extra layer of control by letting you define exactly how the matching should work.

### Shipping Method Match Settings

If you’re using a supported middleware integration, you’ll find the Shipping Method Match section in the integration settings page.

![](/files/XK8qaG9zlMkmhQODtobe)

**TIP**

\[Integration] here is just a placeholder. If you’re using Rithum, for example, you’ll see **Rithum Class** instead:

![](/files/4fyM7q1G2JrLSDxmRrHS)

**\[Integration] Class**

Set the shipping service or method you want Order Desk to send back to your middleware cart service. This is the value your retail vendor is expecting to receive.

**Shipping Carrier**

Set the carrier code you expect to receive from your fulfillment service. Order Desk will look at the carrier value on the shipment and, if it matches, will use the shipping service you’ve entered above in the *\[Integration] Class* field.

If you expect shipments to come in without a carrier, leave this field blank.

To match **any** carrier on your shipments, enter `_ANY_` .

**Shipping Method**

Set the shipping method name you expect to receive from your fulfillment service. Order Desk will look at this value on the shipment and try to match it to the *\[Integration] Class* you’ve specified.

If you expect shipments to come in without a method, leave this field blank.

To match **any** method, enter `_ANY_` .

**IMPORTANT**

Shipping Method Matches are *case-insensitive*.

#### Examples

For these examples, we’d imagine using DSCO Supplier as the integration of choice:

**Matching a specific carrier and method**

* **DSCO Supplier Class:** FESP
* **Shipping Carrier:** FedEx
* **Shipping Method:** Ground

![](/files/DCeXqcuCOA9IFAf4qnl6)

**Result**

When a shipment comes in with **FedEx** as the carrier and **Ground** as the method, Order Desk will send back **FESP** to DSCO supplier.

**Matching any method for a specific carrier**

* **DSCO Supplier Class:** FESP
* **Shipping Carrier:** FedEx
* **Shipping Method:** *ANY*

![](/files/tBbYTAozin07JE6QcuQX)

**Result**

Any **FedEx** shipment will be matched, regardless of method. Order Desk will send back **FESP**.

**Matching any carrier and any method**

* **DSCO Supplier Class:** FESP
* **Shipping Carrier:** *ANY*
* **Shipping Method:** *ANY*

![](/files/e3V1g837xS1auP1Wr6hd)

**Result**

This is a catch-all. Any shipment carrier or method will default to **FESP**.


---

# 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/guided-walkthroughs/shipping-fulfillment-and-returns/how-to-set-up-shipping-method-matches.md?ask=<question>&goal=<endgoal>
```

`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.