How to set up a Da Vinci Unified Fulfillment Channel [Step-by-Step guide]

Modified on Fri, 17 Jul at 8:41 AM

To connect Da Vinci Unified, 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  NOTE: Make sure that you are operating at the correct Account beforehand.

 

I. ONBOARDING REQUIREMENTS


  • API URL for the Da Vinci Unified API environment.
  • Username for the Da Vinci Unified API connection.
  • Password for the Da Vinci Unified API connection.
  • License value provided for the Da Vinci Unified account.
  • Database value provided for the Da Vinci Unified account.
  • Vendor value to be used by the channel configuration.
  • SKU Delimiter to separate the item identity values used by the integration.
  • Throughput value to define the processing throughput for the channel.


NOTE  NOTE: Confirm the correct SKU Delimiter before synchronizing products, inventory, shipments, or receipts. The delimiter is used to build and parse the composite SKU required by Da Vinci Unified.


II. CREATE THE FULFILLMENT CHANNEL


To create a Da Vinci Unified 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 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].

    Supported sync options:
    • Import Products from Channel: Imports products from Da Vinci Unified into techOMS.
    • Export Products to Channel: Exports products from techOMS to Da Vinci Unified.
    • Receive Inventory Levels from Channel: Receives inventory levels from Da Vinci Unified.
    • Receive Shipments from Channel: Receives shipment updates from Da Vinci Unified.
    • Receive Receipts from Channel: Receives receipt updates from Da Vinci Unified.
NOTE  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.
NOTE  NOTE : Product synchronization supports creation and updates. Product deletion is not supported during product synchronization.
NOTE  NOTE : To receive inventory levels from the channel, the account must use the Fulfillment Channel as the Master Product Source, and one warehouse must be selected as the Master Product Channel.
NOTE  NOTE : Disabled products are not updated with inventory when inventory levels are received from the channel.
NOTE  NOTE : If a completed shipment is cancelled in techOMS, the shipment remains in Sent to Warehouse status when Da Vinci Unified rejects the cancellation. The rejection reason is recorded in the Fulfillment Channel logs.
  • 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: 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  NOTE: The SKU Delimiter in Channel settings is used to build and parse the composite SKU. Do not use the selected delimiter inside the item code.
  • Carrier mappings: Maps carrier values between techOMS and the Fulfillment Channel.
  • SKU mappings: Maps SKU values between techOMS and the Fulfillment Channel.
  • Reference mappings: Maps reference values between techOMS and the Fulfillment Channel.
  • Webhooks: Displays webhook-related settings when available.

    NOTE  NOTE: Webhooks for receiving shipments, receipts, and inventory adjustments are not supported for this channel.


C) CONTENT VIEW displays the fields or settings for the tab selected in View Selection.


Channel settings


FieldExpected value / formatDescription
API URLhttps://{host}/v1Da Vinci Unified API host and version URL.
Username{username}User used for the Da Vinci Unified API connection.
Password{password}Password for the configured Da Vinci Unified user.
License{license}License value used to connect to the Da Vinci Unified database.
Database{database}Database name used by the Da Vinci Unified connection.
Vendor{vendor}Vendor value used by the channel configuration.
SKU Delimiter{delimiter}Delimiter used to build and parse the composite SKU required by Da Vinci Unified.
Throughput{throughput}Processing throughput configuration for the channel.


 

NOTE  NOTE : The expected composite SKU format is {Code}{Delimiter}{UOM}{Delimiter}{EaCaseQty}. The UOM and case quantity included in the SKU must match the actual UOM and case quantity configured for the product variant. If they do not match, product export can fail.
NOTE  NOTE : Item codes that differ only by capitalization can cause ambiguous item matching. Keep item codes unique and consistent in capitalization.
NOTE  NOTE : Make sure to Save changes after editing the channel settings.


IV. SPECIFIC BEHAVIORS


Composite SKU model

  • Da Vinci Unified uses a composite SKU model for item matching.
  • The composite SKU is built using the item code, UOM, and case quantity values.
  • The expected format is {Code}{Delimiter}{UOM}{Delimiter}{EaCaseQty}.
  • When sending data to Da Vinci Unified, the channel splits the composite SKU back into the original values required by the external system.


Shipment cancellation

  • If cancellation succeeds, the shipment status is updated to Cancelled.
  • If the order is already completed in Da Vinci Unified, the shipment remains in Sent to Warehouse status, and the rejection reason is recorded in the Fulfillment Channel logs.
  • If the order does not exist in the external system, the shipment can still be cancelled in techOMS.


Webhooks

  • Webhooks for receiving shipments are not supported.
  • Webhooks for receiving receipts are not supported.
  • Webhooks for receiving inventory adjustments are not supported.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article