How to set up a Datex Fulfillment Channel (BETA) [Step-by-step guide]

To connect Datex, 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:

1. Onboarding Requirements
2. Create the Fulfillment Channel
3. Configure Additional Parameters
4. Specific Behaviors

  NOTE : Make sure that you are operating at the correct Vendor/Warehouse beforehand.

I. ONBOARDING REQUIREMENTS

• Datex connection details required by the channel: Api Url, Client Id, Client Secret, Tenant Id, and Scope.
• Operational values required by the integration: Owner and Project.
• Confirm the Vendor/Warehouse context before configuring or operating the channel.

II. CREATE THE FULFILLMENT CHANNEL

To create a Datex Fulfillment Channel, follow: How to Create a Fulfillment Channel [Step-by-step guide].

III. CONFIGURE ADDITIONAL PARAMETERS

To configure additional parameters:

1. Click Channels from the left menu under the Fulfillment Channels section.
2. Click on the created channel's name.
3. Use the highlighted areas in the screenshots 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 Shipments From Channel: Receives shipments from Datex.
• 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].
  
  The Main settings view for this channel includes:
  
  
  • General: Displays the base channel information and configuration fields, including Key, Host,
    Application, Name, and Mode.
  • Recurring Jobs: Displays the recurring job configuration, including Type, Delay, Main Job Period, and Emergency Job Period.
  • Inventory Setting: Displays the inventory configuration section, including Type and Mode.
    
    
• Channel settings: Sets the channel integration parameters listed below
  • Api Url: Datex API endpoint used by techOMS to connect to the channel.
  • Client Id: Microsoft authorization client identifier used by the integration.
  • Client Secret: Microsoft authorization client secret used by the integration.
  • Tenant Id: Microsoft authorization tenant identifier used by the integration.
  • Scope: Microsoft authorization scope used by the integration.
  • Owner: Value used by the plugin for shipment creation and order filtering.
  • Project: Value used by the plugin for shipment creation and order filtering.
  • Throughput: Processing mode used by 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

• The Client Id, Client Secret, Tenant Id, and Scope fields are used for Microsoft authentication required by the integration.
• The configured Owner and Project values are used when shipments are created in Datex.
• The configured Owner and Project values are also used for order filtering, together with warehouse filtering.
• By default, orders are created with order_class="SO" (Sales Order). This default can be changed through Reference Mappings.
• Custom references cannot be added by the channel when sending orders to Datex. However, configured custom references can be retrieved during order fulfillment.
• The Notes field may be updated by WMS system messages.

  NOTE : Datex uses asynchronous order creation. After an order is submitted, Datex returns a request ID while the order continues processing in the WMS. If processing fails, the error is recorded in the WMS logs. To check the result, copy the request ID from the techOMS error log, open Integrations - Import Entities in Datex, and review the status column.

  WARNING: When redefining Lot and VendorLot values at line level, only valid values can be used. Invalid values cause an order processing error in the WMS.