Skip to main content

DCL integration setup

Map DCL warehouses and set up two-way orders, SKU product import, inventory sync and inbound stock transfers.

A
Written by Argo Ohvril

What syncs between Katana and DCL

Data flow between DCL and Katana

The table below summarizes how each type of data moves between Katana and DCL.

Data

Direction

Status

Orders

Two-way

Available

Products

DCL → Katana

Available

Inbound stock transfers

DCL → Katana

Available

Inventory sync

DCL → Katana

Available

Locations and mapping

After you connect DCL, the configuration screen opens on the Location tab. Each DCL warehouse is mapped 1:1 to its own dedicated Katana location.

  • Add to Katana creates a Katana location for a DCL warehouse and maps it.

  • A warehouse that has never been mapped shows Not mapped.

  • To pause a mapped warehouse, use Unlink. Its status then shows Unlinked.

  • To resume a paused warehouse, use Relink.

Only mapped warehouses sync. Nothing syncs until you click Activate sync in the header.

the warehouse location mapping panel on the Location tab of the DCL configuration screen, listing DCL warehouses with statuses Mapped, Unlinked and Not mapped, an Add to Katana button on a Not mapped warehouse, Unlink and Relink actions on mapped warehouses, and the Activate sync button in the header

Products sync

Product mapping creates a required link between each DCL product and a Katana item. First, choose how SKUs are matched: either direct 1:1 or through SKU aliases.

  • Products are imported by SKU.

  • A DCL SKU that already exists in Katana is matched to that product.

  • An unknown SKU creates a new Katana product when it is needed.

Kits and bundles from DCL become Katana products. To define their components, add a bill of materials (BOM) to the product in Katana. A kit order line stays a single row on the sales order.

the products mapping settings screen for DCL showing the SKU matching choice between direct 1:1 matching and matching via SKU aliases

SKU aliases

A SKU alias links a DCL SKU to a Katana SKU that differs from it. Use aliases when the same item is coded differently in DCL and Katana, so the item matches your existing Katana product instead of creating a duplicate. Upload your SKU alias mapping before the product import runs.

the products mapping screen with SKU alias mapping, showing DCL SKUs in one column matched to different Katana SKUs in another, with an option to upload the alias mapping

Orders sync

Orders from DCL to Katana

  • DCL orders import once they reach the configured import-from status. The default is the "Open" state.

  • Imported orders keep updating automatically through every later status change.

  • Each DCL order becomes one Katana sales order, with each line as one row. The order source is DCL.

  • Each shipped package becomes a Katana fulfillment with its carrier and tracking number. A multi-package shipment creates one fulfillment per package, so one order can show several fulfillments. Together, these fulfillments never exceed the ordered quantities.

  • If an order is canceled in DCL, Katana deletes the matching sales order only if that sales order is still open.

the order sync settings screen for DCL with the import-from status option set to Open and the order status options

Orders from Katana to DCL

  • A Katana sales order is pushed to DCL as an outbound order when it reaches the Ready for fulfillment status.

  • After the push, Katana tracks the order's progress through the import flow described above.

  • Canceling the Katana sales order does not cancel the pushed DCL order.

  • Changes you make in Katana after the push do not update the pushed DCL order.

the order push settings screen for DCL showing that Katana sales orders are sent to DCL when they reach the Ready for fulfillment status

Inventory sync

DCL's stock numbers appear in Katana as read-only external inventory at each warehouse's mapped location. The figure Katana shows is DCL's on-hand quantity. You can't edit these numbers in Katana, and Katana never sends stock changes to DCL.

Reconciliation compares Katana's in-stock quantity against DCL's on-hand quantity. It runs on a schedule, or you can run it on demand. Any difference creates a stock adjustment in Katana.

the inventory sync settings screen for DCL showing read-only external on-hand inventory per mapped location and the reconciliation schedule with a run on demand option

Inbound shipments

Each DCL inbound shipment becomes one Katana stock transfer. The transfer number is the PO number when one exists, otherwise the inbound ID.

  • Destination: the Katana location mapped to the inbound's DCL warehouse.

  • Origin: the location you assign for each destination warehouse. This location must be mapped.

  • The stock transfer follows the inbound's status, and received quantities update the transfer.

  • If the inbound is canceled in DCL, its stock transfer is deleted.

Katana stock transfers have only two states: in transit and received. While an inbound is partially received, the transfer shows updated expected and received quantities. It moves to received once everything has arrived.

the inbound shipments screen for DCL showing inbound shipments as Katana stock transfers with transfer number, origin and destination locations, expected and received quantities, and status

What does not sync

  • Products and stock changes are never pushed from Katana to DCL.

  • Changes made to a Katana sales order after it has been pushed do not update the DCL order.

  • Canceling a Katana sales order does not cancel the pushed DCL order.

  • Returns and RMAs do not sync.

  • Serial-number tracking does not sync. Lot and batch data appears read-only where DCL provides it.

Disconnecting

To disconnect, go to Katana's Integrations page, open the DCL integration and disconnect it. Syncing stops immediately: Katana no longer imports orders, inventory or inbound shipments, and no longer pushes sales orders to DCL.

Records already brought into Katana stay in place. This includes sales orders, fulfillments, products, stock transfers and stock adjustments.

Did this answer your question?