Skip to main content

Clarus integration setup

Map Clarus warehouses to locations, then configure order, product, inventory, and inbound shipment syncs.

A
Written by Argo Ohvril

What syncs between Katana and Clarus

Data flow between Clarus and Katana

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

Data

Direction

Status

Orders

Two-way

Available

Products

Clarus → Katana

Available

Inbound stock transfers

Clarus → Katana

Available

Inventory sync

Clarus → Katana

Available

Locations and mapping

After Clarus approves the connection, the configuration screen opens on the Location tab. Each Clarus warehouse maps 1:1 to its own dedicated Katana location. Click Add to Katana to create that location automatically.

  • A warehouse that has never been mapped shows Not mapped until you use Add to Katana.

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

  • To resume syncing, click 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 Clarus configuration screen, listing Clarus warehouses with their mapped Katana locations and statuses (Not mapped, Unlinked), the Add to Katana, Unlink and Relink actions, and the Activate sync button in the header

Products sync

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

Products are imported by SKU:

  • If a Katana product already has the same SKU, the two are matched.

  • If a SKU is unknown in Katana, a new product is created when it is first needed.

Kits and bundles from Clarus become Katana products. You can then add a BOM of components to them in Katana. On a sales order, a kit order line stays a single row.

the products mapping settings screen in the Clarus integration, showing the choice between direct 1:1 SKU matching and matching via SKU aliases

SKU aliases

A SKU alias links a Clarus SKU to a different Katana SKU. Use aliases when the same product has different SKUs in the two systems. Upload your SKU alias mapping before you import products, so mismatched SKUs match correctly instead of creating new products.

the products mapping screen with SKU alias mapping, showing Clarus SKUs paired with different Katana SKUs and the option to upload an alias mapping file

Orders sync

From Clarus to Katana: orders import once they reach the import-from status you configure (the default is the Open state). After import, they keep updating automatically through every later status change.

Each Clarus order becomes one Katana sales order, with one row per order line. The order source is Clarus.

Each shipped package becomes a Katana fulfillment with its carrier and tracking number. A shipment with several packages creates one fulfillment per package. Together, these fulfillments never exceed the ordered quantities.

If an order is canceled in Clarus, it is deleted in Katana only if the sales order is still open.

the order sync settings screen with the import and status options, showing the import-from status selector set to Open

From Katana to Clarus: when a Katana sales order reaches Ready for fulfillment, it is pushed to Clarus as an outbound order. From then on, its progress is tracked back in Katana through the import flow above.

  • Canceling the Katana sales order does not cancel the Clarus order.

  • Changes made in Katana after the push do not update the Clarus order.

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

Inventory sync

Clarus stock levels appear in Katana as read-only External inventory at each warehouse's mapped location. The number shown is the Clarus On hand quantity.

Reconciliation compares Katana's in-stock quantity with the Clarus on-hand quantity only. You can run it on a schedule or on demand. For any difference it finds, Katana creates a stock adjustment, so your Katana stock reflects the physical stock in the warehouse.

the inventory sync settings screen in the Clarus integration, showing read-only External inventory on hand per mapped location and the scheduled and on-demand reconciliation options

Inbound shipments

Each Clarus inbound shipment becomes one Katana stock transfer. The transfer number is the PO number if there is one; otherwise it is the inbound ID.

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

  • Origin: the location assigned for each destination warehouse. This origin must be mapped.

The stock transfer follows the status of the inbound shipment, and received quantities update the transfer. Katana stock transfers have only two states: in transit and received. Partial receipts therefore show as updated expected and received quantities until the shipment is fully received. If an inbound shipment is canceled in Clarus, its stock transfer is deleted.

the inbound shipments screen showing a Clarus inbound shipment as a Katana stock transfer with PO number, origin and destination locations, status, and expected versus received quantities

What does not sync

  • Products and stock changes are not pushed from Katana to Clarus.

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

  • Canceling a Katana sales order does not cancel the Clarus order.

  • Returns and RMAs are not synced.

  • Serial-number tracking is not supported. Lot and batch data is shown read-only where Clarus provides it.

Disconnecting

To disconnect, go to Katana's Integrations page and open the Clarus integration. Once you disconnect, syncing stops right away: orders, fulfillments, inventory and inbound shipments no longer update, and Katana no longer pushes orders to Clarus. Records already imported into Katana, such as sales orders, fulfillments, products and stock transfers, stay in Katana.

Did this answer your question?