Onboard carriers
The data import functionality can be used to quickly and efficiently onboard carriers. All required data must be obtained before performing the import, and converted into one of the supported import file structures. For the imports to succeed, data must be imported in a specific order. If not ordered correctly, the import will fail.
Carrier onboarding import
Use data import to onboard carriers using the data entities in the order listed below. Note that the order works on the assumption that Users and Profiles are already configured. See Import Users for detail.
- Number Ranges (Package Numbers)
- Accounts
- Security Credentials
- Shipping Keys
- Consolidated Shipping Defaults
- International Defaults
- User Defaults
- Outputs
API Data Requests
Additionally, certain carriers, outlined in the table below, support requesting security credentials and/or shipping keys from the carriers' own API during the import process. This means these values are not required prior to import.
Configuration
Alongside importing the ordered entities listed above, the following actions are required:
- The Security Credentials files must have the following fields present but unpopulated: Identifier and Password.
- The Shipping Keys files must have the following field present but unpopulated: ShippingKeyValue.
- The following User Defaults elements must be configured:
- The RequestFromCarrier column must be set to True.
- All Account (e.g. AccountUserTitle), ShippingLocation (e.g. ShippingLocationAddress1), BillingLocation (e.g. BillingLocationAddress1) and ContactLocation (e.g. ContactLocationAddress1) detail must be populated.
Supported carriers
The following carriers support requesting data from carrier APIs.
Carrier | Supported Data Request |
---|---|
FedEx Web Services |
|
FedEx SmartPost Web Services |
|
FedEx Freight Web Services |
|
UPS API |
|
UPS Freight API |
|
UPS Freight API |
|
PB Shipping API - USPS |
|