Skip to main content

ShipNetwork integration setup

Configure warehouse-to-location mapping, SKU-based product import with aliases, and on-hand inventory reconciliation.

A
Written by Argo Ohvril

What syncs between Katana and ShipNetwork

Data flow between ShipNetwork and Katana

The table below shows how each data type is handled between ShipNetwork and Katana.

Data

Direction

Status

Products

ShipNetwork → Katana

Available

Inventory sync

ShipNetwork → Katana

Available

Locations and mapping

Ask your ShipNetwork representative to set up API access. You will receive a client ID, API user identifier, and API user secret. On Katana's Integrations page, click Connect on the ShipNetwork tile and enter these credentials. Once ShipNetwork approves the connection, the configuration screen opens on the Location tab.

Each ShipNetwork warehouse maps to its own dedicated Katana location. Click Add to Katana to create that location. Until then, the warehouse shows Not mapped. To pause a mapped warehouse, click Unlink. Its status then shows Unlinked. Click Relink to resume it. Only mapped warehouses sync. Nothing syncs until you click Activate sync in the header.

the warehouse location mapping panel on the Location tab, listing ShipNetwork warehouses with statuses Mapped, Unlinked and Not mapped, with Add to Katana, Unlink and Relink buttons, and the Activate sync button in the header

Products sync

Product mapping creates a required link between each ShipNetwork product and a Katana item. Products are imported by SKU. If a SKU matches an existing Katana product, the two are linked. If the SKU is unknown, Katana creates the product just-in-time. You can match SKUs directly (1:1) or through SKU aliases.

ShipNetwork kits and bundles are imported as Katana products. To define their components, add a BOM to them in Katana.

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

SKU aliases

A SKU alias links a ShipNetwork SKU to a different Katana SKU. Use an alias when the same item has different SKUs in the two systems. Upload your SKU alias mapping before importing products. Otherwise, mismatched SKUs are created as new products instead of matching your existing items.

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

Inventory sync

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

Reconciliation compares Katana's in-stock quantity with ShipNetwork's on-hand quantity. It runs on a schedule or whenever you trigger it. For any difference, Katana creates a stock adjustment, so its stock levels match what is physically in the warehouse. Katana never sends inventory changes back to ShipNetwork.

the inventory sync settings screen for ShipNetwork, showing read-only External inventory On hand quantities per mapped location and the reconciliation schedule with a run-now option

What does not sync

  • Sales orders, in either direction

  • Fulfillments, carrier and tracking details

  • Inbound shipments and stock transfers

  • Products or stock changes sent from Katana to ShipNetwork

  • Returns and RMAs

  • Serial-number tracking (lot/batch data is shown read-only where ShipNetwork provides it)

Disconnecting

Disconnect ShipNetwork from its tile on Katana's Integrations page. Product imports and inventory updates from ShipNetwork stop right away. Records already brought into Katana stay in Katana after you disconnect, including imported products and the locations created for your warehouses.

Did this answer your question?