Skip to main content

WarehouseOS integration setup

Map warehouses to locations, match products by SKU or alias, sync orders both ways and reconcile on-hand stock.

A
Written by Argo Ohvril

What syncs between Katana and WarehouseOS

Data flow between WarehouseOS and Katana

The table below lists each data type and the direction it syncs between Katana and WarehouseOS.

Data

Direction

Status

Orders

Two-way

Available

Products

WarehouseOS → Katana

Available

Inventory sync

WarehouseOS → Katana

Available

Locations and mapping

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

  • Not mapped: the warehouse has never been mapped. Click Add to Katana to create its location.

  • Unlink: pauses a mapped warehouse. Its status then shows Unlinked.

  • Relink: resumes syncing for an unlinked warehouse.

Only mapped warehouses sync.

the warehouse location mapping panel on the Location tab of the WarehouseOS configuration screen in Katana, listing WarehouseOS warehouses each paired with a Katana location, with an Add to Katana button on a warehouse showing Not mapped, an Unlink action on a mapped warehouse, and a Relink action on a warehouse showing Unlinked

Products sync

Product mapping creates a required link between each WarehouseOS product and a Katana item. You choose how SKUs match: direct 1:1, or through SKU aliases.

Products import by SKU:

  • If a SKU already exists in Katana, the WarehouseOS product links to that Katana product.

  • If a SKU is unknown, Katana creates the product just-in-time.

Kits and bundles become Katana products. Add a bill of materials (BOM) of their components in Katana. A kit order line stays a single sales order row.

the products mapping settings screen for WarehouseOS in Katana, showing the choice between direct 1:1 SKU matching and matching via SKU aliases

SKU aliases

An SKU alias links a WarehouseOS SKU to a different Katana SKU. Use aliases when the same product has mismatched SKUs in the two systems. Upload your SKU alias mapping before importing products, so the products match correctly instead of being created as new ones.

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

Orders sync

From WarehouseOS to Katana

Orders import once they reach the configured import-from status. The default is the Open state. After import, they keep updating automatically through every later status change.

  • Each WarehouseOS order becomes one Katana sales order.

  • Each order line becomes one row.

  • The order source is WarehouseOS.

Each shipped package becomes a Katana fulfillment with its carrier and tracking number. Multi-package shipments create 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 WarehouseOS, Katana deletes the order only if it is still open.

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

From Katana to WarehouseOS

When a Katana sales order reaches the Ready for fulfillment status, Katana pushes it to WarehouseOS as an outbound order. From then on, its progress in WarehouseOS is tracked back in Katana through the import flow above.

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

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

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

Inventory sync

WarehouseOS stock numbers appear in Katana as read-only External inventory at each warehouse's mapped location. The number shown is On hand. You can't edit these numbers in Katana.

Reconciliation compares Katana's in-stock quantity against the WarehouseOS on-hand quantity only. It runs on a schedule or on demand. Where the two differ, Katana creates stock adjustments, so its stock levels match WarehouseOS.

the inventory sync settings screen for WarehouseOS in Katana, showing read-only External inventory On hand quantities per mapped location and the reconciliation schedule with an option to run reconciliation on demand

What does not sync

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

  • Changes made in Katana to a sales order after it is pushed don't update the WarehouseOS order.

  • Canceling a pushed Katana sales order doesn't cancel the WarehouseOS order.

  • Inbound shipments don't sync, so no stock transfers are created from them.

  • Returns and RMAs.

  • Serial-number tracking. Lot and batch data appears read-only where WarehouseOS exposes it.

Disconnecting

To disconnect, open the WarehouseOS tile on Katana's Integrations page and disconnect the integration. Syncing stops immediately:

  • No more orders, fulfillments, or inventory updates come in from WarehouseOS.

  • No more sales orders are pushed to WarehouseOS.

Records already brought into Katana stay in Katana. This includes sales orders, fulfillments, products, and locations.

Did this answer your question?