To connect Canada Cartage CCS, first create the Fulfillment Channel connection, and then set up its parameters.
Once the connection is established between the channel and techOMS, you can use its supported features as listed in: techOMS Fulfillment Channels - Master List [Guides List].
This article is divided into the following sections:
- Onboarding Requirements
- Create the Fulfillment Channel
- Configure Additional Parameters
- Specific Behaviors
NOTE : Make sure that you are operating at the correct Vendor/Warehouse beforehand.
I. ONBOARDING REQUIREMENTS
- Have all required connection settings available before setup, including the API URL, User Name, Password, Company Code, Customer Code, API Key, and Throughput.
- Have access to the appropriate Canada Cartage CCS environment and credentials for the connection you will configure.
- All channel settings are required.
II. CREATE THE FULFILLMENT CHANNEL
To create a Canada Cartage CCS Fulfillment Channel, follow: How to Create a Fulfillment Channel [Step-by-step guide].
III. CONFIGURE ADDITIONAL PARAMETERS
To configure additional parameters:
- Click Channels from the left menu under the Fulfillment Channels section.
- Click on the created channel's name.
- Use the highlighted areas in the screenshot below and configure the required settings.

SECTIONS
A) QUICK ACTIONS lets you perform additional actions:
- Sync: Enables manual synchronization as detailed in How to Synchronize data through a Fulfillment Channel [Step-by-step guide].
Sync options:- Receive Inventory Levels From Channel: Receives inventory levels from Canada Cartage CCS.
- Receive Shipments From Channel: Receives shipment data from Canada Cartage CCS.
- Receive Receipts From Channel: Receives receipt data from Canada Cartage CCS.
NOTE : Shipment retrieval supports ID range only. Shipment data is available only after the order is closed/fulfilled in the external system.
WARNING : Canada Cartage CCS only accepts orders and shipments in the lowest unit of measure, Eaches.- Save: Saves and commits changes.
- Delete: Deletes the channel connection.
B) VIEW SELECTION allows you to navigate the different tabs:
- Main settings (default): Configures general and automation behavior using: Main Settings of a Beta Fulfillment Channel [Information].
- Advanced settings: Configures additional system/privacy settings using: How to manage Fulfillment Channels Advanced settings [Step-by-Step guide].
- Channel settings: Sets the channel integration parameters listed below.
Channel Settings (Fields)
- API URL: URL used to connect Canada Cartage CCS to techOMS.
- User Name: User name used to authenticate the connection.
- Password: Password used to authenticate the connection.
- Company Code: Company code used by Canada Cartage CCS.
- Customer Code: Customer code used by Canada Cartage CCS.
- API Key: API key used to authenticate the connection.
- Throughput: Throughput setting used by the connection.
- Carrier Mappings: Sets carrier/service name mappings as detailed in How to map Carriers and Services in a Fulfillment Channel [Step-by-step guide].
- SKU Mappings: Reviews and sets SKU mappings as detailed in How to map SKUs in a Fulfillment Channel [Step-by-step guide].
- Reference Mappings: Reviews and sets reference mappings as detailed in How to map References in a Fulfillment Channel [Step-by-step guide].
- Recurring Jobs: If enabled for this channel, follow: How to configure Automated Recurring Jobs for Sales/Fulfillment channels [Step-by-step guide].
C) CONTENT VIEW displays and/or allows editing of the settings in the "View Selection" section.
WARNING : Remember to press Save to commit the changes made in this section.
IV. SPECIFIC BEHAVIORS
- Packages: In SSCC, each case is received as a package in techOMS. CaseLabel is used as the container number.
- Lots: Lot information is received from ItemLevel2 at the package level and from InventoryLevel2 in DetailLine at the shipment-line level. Expiration Date is also available in techOMS.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article