Best Practices for Carrier and Service Code Mappings setup [Information]
Last updated: September 29, 2026
When setting up Sales and Fulfillment Channel connections, you can create and configure Carrier and Service Level Mappings.
These are done over what's called the Carrier Master Table. Before configuring channel connections, you must build this baseline (as detailed in How to Manage the Carriers and Services Master List: Create, Edit, Delete, and Import [Step-by-Step Guide]).
This master table, alongside your specific channel setups (detailed in How to map Carriers and Services in a Sales Channel [Step-by-step guide] and How to map Carriers and Services in a Fulfillment Channel [Step-by-step guide]), indicates which codes are expected to be received from the Sales Channels, what techOMS will use in that case, and how it is defined in the Fulfillment Channel, defining an end-to-end information passage between systems.
This document provides an example and best practices.

NOTE: You can have all the Sales and Fulfillment Channels mapped to the same techOMS codes, funneling different variants into a single value.
The case to be analyzed is the following, as the warehouse:
Is shipping Ground via 3 Carriers:
FedEx
UPS
USPS
Is connected to 3 Sales Channels:
Shopify
WooCommerce
eBay
Is connected to 2 Fulfillment Channels:
Extensiv
Logiwa
Considering the case, this is how the Mappings would be configured:
![]() Sales Channel | ![]() techOMS | ![]() Fulfillment Channel | ||||||
Carrier Code | Service Code | Carrier Code | Service Code | Carrier Code | Service Code | |||
Shopify | Standard Shipping | FedEx | Ground | FDEG | Extensiv | |||
WooCommerce | FDEX | Ground | FEDEX | GRND | Logiwa | |||
eBay | FDEG | |||||||
This setup, starting from left to right, receives from the Sales Channels:
Shopify
Carrier Code: Standard Shipping
Service Code: No value
WooCommerce
Carrier Code: FDEX
Service Code: Ground
eBay
Carrier Code: FDEG
Service Code: No value
This is possible, given that each Sales Channel could have different values configured, or even not support some.
Considering that, techOMS, will funnel and interpret these variants into two values:
Carrier Code: FedEx
Service Code: Ground
When the Fulfillment Channels handle FedEx and Ground, these will:
Extensiv
Carrier Code: FDEG
Service Code: No value
Logiwa
Carrier Code: FEDEX
Service Code: GRND

NOTE: In the example above, the Primary setting in the Carrier Mapping Table tells techOMS whether to send the code for Extensiv or the one for Logiwa. By marking one mapping as Primary, you ensure that the system consistently uses that specific code when sending information to the Fulfillment Channel. For more information, see: How to map Carriers and Services in a Fulfillment Channel [Step-by-step guide].

NOTE: You can set up Carrier and Service Codes in the Master List that you don't use at the moment as a pre-emptive setup, for example, if you're not using UPS yet, you could still configure a setup like this:
![]() Sales Channel | ![]() techOMS | ![]() Fulfillment Channel | ||||||
Carrier Code | Service Code | Carrier Code | Service Code | Carrier Code | Service Code | |||
Shopify | UPSG | UPS | Ground | UPS | GND | Extensiv | ||
WooCommerce | UPS | Ground | Logiwa | |||||
eBay | UPS | |||||||

NOTE: If you have a single Fulfillment Channel, we recommend setting up your techOMS Carrier Master List to match your Fulfillment Channel ones (cloning). You can rapidly achieve this using the bulk import feature described in How to Manage the Carriers and Services Master List: Create, Edit, Delete, and Import [Step-by-Step Guide]. Doing this removes the need for term conversion between systems, making it much simpler to track and configure.


