What syncs between Katana and Linnworks Core (SKUVault)
The table below summarizes each data type and the direction it flows between Katana and Linnworks Core (SKUVault).
Data | Direction | Status |
Orders | Two-way | Available |
Products | Linnworks Core (SKUVault) → Katana | Available |
Inbound stock transfers | Linnworks Core (SKUVault) → Katana | Available |
Inventory sync | Linnworks Core (SKUVault) → Katana | Available |
Locations and mapping
After the connection is approved, the configuration screen opens on the Location tab. Each Linnworks Core (SKUVault) warehouse maps 1:1 to its own dedicated Katana location.
Add to Katana creates the Katana location for a warehouse. Until then, the warehouse shows Not mapped.
Unlink pauses a mapped warehouse, and its status shows Unlinked.
Relink resumes syncing for an unlinked warehouse.
Only mapped warehouses sync.
Products sync
Product mapping creates a required link between each Linnworks Core (SKUVault) product and a Katana item. First, choose how SKUs are matched: 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 the SKU is unknown in Katana, the product is created when it's first needed.
Kits and bundles are imported as Katana products. Add a bill of materials (BOM) of their components in Katana. A kit order line stays a single row on the sales order.
SKU aliases
A SKU alias links a Linnworks Core (SKUVault) SKU to a different Katana SKU. Use aliases when the same product has different SKUs in the two systems, so both SKUs point to one Katana item. Upload your SKU alias mapping before the product import runs.
Orders sync
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 order becomes one Katana sales order, with one row per order line. The order source is Linnworks Core (SKUVault).
Each shipped package becomes a Katana fulfillment with its carrier and tracking number. Multi-package shipments create one fulfillment per package, and together these never exceed the ordered quantities.
A canceled Linnworks Core (SKUVault) order is deleted in Katana only if the sales order is still open.
Sending orders from Katana
When a Katana sales order reaches the Ready for fulfillment status, Katana pushes it to Linnworks Core (SKUVault) as an outbound order. Its progress then syncs back to Katana through the import flow above.
Canceling the Katana sales order does not cancel the pushed order.
Changes you make in Katana after the push do not update the pushed order.
Inventory sync
Linnworks Core (SKUVault) stock levels appear in Katana as read-only External inventory at each warehouse's mapped location. The number shown is the on-hand quantity.
Reconciliation compares Katana's in-stock quantity against the partner's on-hand quantity. It runs on a schedule or on demand. When the numbers differ, Katana creates stock adjustments so its in-stock quantities match. Katana never sends inventory changes back to Linnworks Core (SKUVault).
Inbound shipments
Each Linnworks Core (SKUVault) inbound shipment becomes one Katana stock transfer.
Transfer number: the PO number, if the inbound has one. Otherwise, the inbound ID.
Destination: the Katana location mapped to the inbound's warehouse.
Origin: the location assigned to each destination warehouse. This must be mapped.
The stock transfer follows the inbound's status, and received quantities update the transfer. Katana stock transfers move from in transit to received in one step. Partial receipts therefore show as updated expected and received quantities until the shipment is fully received. A canceled inbound deletes its stock transfer.
What does not sync
Product or stock changes from Katana are never pushed to Linnworks Core (SKUVault).
Changes made in Katana to an order that has already been pushed are not sent to Linnworks Core (SKUVault).
Canceling a Katana sales order does not cancel the pushed order.
Returns and RMAs are not supported.
Serial numbers are not tracked. Lot and batch data appears read-only where Linnworks Core (SKUVault) provides it.
Disconnecting
To disconnect, open Katana's Integrations page, find the Linnworks Core (SKUVault) tile, and disconnect the integration. Syncing stops right away. Records already imported into Katana stay in Katana, including sales orders, fulfillments, products, and stock transfers.