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

Datex Fulfillment Channel (BETA)

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, Project, and the default billing address values used for purchase orders.
• Before synchronizing products, configure packaging in Datex so it matches the techOMS Primary UOM.

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 Inventory Levels From Channel: Receives inventory levels from Datex.
  • Receive Shipments From Channel: Receives shipments from Datex.
  • Receive Receipts From Channel: Receives receipts from Datex.
  • Import Products From Channel: Imports products from Datex.
  • Export Products To Channel: Sends products from techOMS to Datex.
• Save: Saves and commits changes.
• Delete: Deletes the channel connection.

Product synchronization

• Product synchronization supports product creation only. Product updates are not supported.
• Datex can store multiple packaging options for the same product. However, because techOMS uses a different product structure, the integration uses only the first packaging option during product synchronization.

  WARNING : If an unknown Primary UOM is sent when synchronizing products, Datex returns an error.

  NOTE : Datex returns only the first 5,000 products per account. Products containing special characters may fail in Datex. When this happens, the related message is visible in the logs.

Inventory synchronization

• Receive Inventory Levels From Channel imports inventory levels from Datex.

  NOTE : Datex can store fractional inventory quantities. Products with fractional inventory are excluded from inventory results and generate an invalid quantity warning.

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 settingsview for this channel includes:
  • General: Displays the base channel information and configuration fields, including Key, Host, Application, Name, and Mode.
  • Recurring Jobs: Displays recurring job configuration for the available automated processes, including Receiving Shipments, Receiving Receipts, Import Products, and Export Products. Each recurring job row includes 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 authentication client identifier used by the integration.
  • Client Secret: Microsoft authentication client secret used by the integration.
  • Tenant Id: Microsoft authentication tenant identifier used by the integration.
  • Scope: Microsoft authentication scope used by the integration.
  • Owner: Value used when shipments are created in Datex and when orders are filtered.
  • Project: Value used when shipments are created in Datex and when orders are filtered.
  • Receipt Bill to Address Name: Default billing address name used when sending purchase orders to Datex.
  • Receipt Bill to Address line 1: First billing address line used when sending purchase orders to Datex.
  • Receipt Bill to Address line 2: Second billing address line used when sending purchase orders to Datex, if applicable.
  • Receipt Bill to Address City: Billing address city used when sending purchase orders to Datex.
  • Receipt Bill to Address State: Billing address state or province used when sending purchase orders to Datex.
  • Receipt Bill to Address Postal code: Billing address postal code used when sending purchase orders to Datex.
  • Receipt Bill to Address Country: Billing address country used when sending purchase orders to Datex.
  • Throughput: Processing mode used by the channel.

  NOTE : The Client Id, Client Secret, Tenant Id, and Scope fields are used for Microsoft authentication required by the integration.

  NOTE : A billing address is required when sending purchase orders. Because techOMS does not provide one, a default billing address must be entered in the channel settings.

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

• Order and purchase order defaults: By default, orders are created with order_class = "SO" (Sales Order), and purchase orders are created with order_class = "PO" (Purchase Order). These defaults can be changed through Reference Mappings.
• Reference behavior: Custom references cannot be added by the channel when sending orders or purchase orders to Datex. However, configured custom references can be retrieved during order fulfillment.
• Shipment and order filtering: The configured Owner and Project values are used when shipments are created in Datex and are also used for order filtering together with warehouse filtering.
• Notes behavior: The Notes field may be updated by WMS system messages.

  NOTE : Datex uses asynchronous creation for orders and purchase orders. After a request is submitted, Datex returns a request ID while processing continues 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, VendorLot, or Requested Lot values at line level, only valid values can be used. Invalid values cause an order processing error in the WMS.