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 Account beforehand.
I. ONBOARDING REQUIREMENTS
- Extensiv WM API connection details must be available before creating the channel, including the API URL, API key, API secret, and the Extensiv WM account name.
- The Extensiv WM account used in the channel must match the account used in the external Extensiv WM system.
- If carrier mappings will be used, confirm the Extensiv WM carrier/service ID to enter in the Channel Carrier Code field.
II. CREATE THE FULFILLMENT CHANNEL
To create a Extensiv WM 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:
- Health Check: Checks whether the channel connection is active.
- Sync: Enables manual synchronization as detailed in How to Synchronize data through a Fulfillment Channel [Step-by-step guide].
Supported sync options:- Export Products to Channel: Exports the Products from techOMS to the connected Fulfillment Channel.
- Receive Inventory Levels from Channel: Receives Inventory levels from the connected Fulfillment Channel.
- Receive Shipments from Channel: Receives Shipments from the connected Fulfillment Channel.
- Receive Receipts from Channel: Receives Receipts from the connected Fulfillment Channel.
NOTE : The options displayed in the Sync dropdown are managed by techOMS based on the Master Product Source and the features supported by the specific Fulfillment Channel.- 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 settings, recurring jobs, and inventory synchronization behavior using: How to configure Automations for Sales/Fulfillment channels [Step-by-step guide].
- 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.
NOTE: The fields displayed in this section are dynamic. Based on your previous selections and the inherent capabilities of the channel, certain fields may be hidden, disabled, or cascaded.
Channel Settings (Fields)- Api Url: Enter the Extensiv WM API URL using URL format, for example
https://api.scoutsft.com. This URL is used by the integration to send API requests to Extensiv WM. - Api Key: Enter the Extensiv WM API key as plain text. This value is obtained from the Extensiv WM admin console.
- Api Secret: Enter the Extensiv WM API secret as a secure password value. This value is obtained from the Extensiv WM admin console.
- Account: Enter the account name used in Extensiv WM, for example
Test Company Inc.. This value identifies the external account used by the integration. - Throughput: Select the request throughput value, for example
Default. This value defines the maximum number of requests per minute allowed for the integration.
- Api Url: Enter the Extensiv WM API URL using URL format, for example
- 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: Sets reference mappings for the channel.
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
- Quantity handling: Extensiv WM supports decimal quantities for sales orders, purchase orders, and inventory. techOMS supports integer quantities only; therefore, decimal quantities are rounded down before they are saved or processed in techOMS. For example,
10.9becomes10,5.1becomes5, and3.0remains3. - Products: When products are pushed from techOMS to Extensiv WM, the vendor is required. The vendor must be available as a product variant reference using
ExtensivWMVendorName. When products are pulled from Extensiv WM into techOMS, the integration automatically creates this reference using the vendor value received from Extensiv WM. - Purchase Orders: When purchase orders are pushed from techOMS to Extensiv WM, the vendor is required. The vendor value is taken from Purchase Order > Supplier Pick Up > Company.
- Carrier Mapping: In Extensiv WM, carrier and service are represented by a single unique ID that identifies both values together. When creating carrier mappings in techOMS, enter this unique Extensiv WM ID in the Channel Carrier Code field.
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