What syncs between Katana and ShippingTree
The table below summarizes each data flow between Katana and ShippingTree.
Data | Direction | Status |
Orders | Two-way | Available |
Products | ShippingTree → Katana | Available |
Inbound stock transfers | ShippingTree → Katana | Available |
Inventory sync | ShippingTree → Katana | Available |
Locations and mapping
After ShippingTree approves the connection, the configuration screen opens on the Location tab. The integration status shows Connected with Sync inactive. Nothing syncs until you click Activate sync in the header.
Each ShippingTree 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 click Add to Katana.
To pause a mapped warehouse, click Unlink. Its status then shows Unlinked. Click Relink to resume it.
Only mapped warehouses sync.
Products sync
Product mapping creates a required link between each ShippingTree product and a Katana item. You choose how SKUs are matched: direct 1:1 or via SKU aliases.
Products are imported by SKU.
If a Katana product already has that SKU, the two are matched.
If the SKU is unknown in Katana, a new product is created when it is first needed.
Kits and bundles also become Katana products. Add a BOM of components to them in Katana. A kit order line stays a single sales order row.
SKU aliasing
A SKU alias links a ShippingTree 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 importing products, so the products match correctly instead of being created as duplicates.
Orders sync
Orders from ShippingTree to Katana
Orders import once they reach the configured import-from status (by default, the "Open" state). After that, they keep updating automatically through every later status change.
Each ShippingTree order becomes one Katana sales order, with one row per order line. The order source is ShippingTree.
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 ShippingTree, it is deleted in Katana only if the order is still open there.
Orders from Katana to ShippingTree
A Katana sales order is pushed to ShippingTree as an outbound order when it reaches the Ready for fulfillment status. After that, the import flow above tracks its progress back in Katana.
Canceling the Katana sales order does not cancel the ShippingTree order.
Changes made in Katana after the push do not update the ShippingTree order.
Inventory sync
ShippingTree's 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 ShippingTree's on-hand quantity only. It runs on a schedule or whenever you trigger it, and it creates stock adjustments for any differences. Katana never pushes inventory changes to ShippingTree.
Inbound shipments
Each ShippingTree inbound shipment becomes one Katana stock transfer. The transfer number is the PO number when there is one; otherwise it is the inbound ID.
Destination: the Katana location mapped to the inbound's warehouse.
Origin: the location assigned to each destination warehouse. This location must be mapped.
Stock transfers follow the inbound's status, and received quantities update the transfer. If an inbound is canceled, its stock transfer is deleted.
Katana stock transfers have only two states: in transit and received. Partial receiving therefore shows as updated expected and received quantities until the shipment is fully received.
What does not sync
Products and stock changes are never pushed from Katana to ShippingTree.
Changes made in Katana to a sales order after it is pushed do not update the ShippingTree order.
Canceling a Katana sales order does not cancel the pushed ShippingTree order.
Returns and RMAs are not synced.
Serial numbers are not tracked. Lot and batch data appears read-only where ShippingTree provides it.
Warehouses that are not mapped do not sync.
Disconnecting
Disconnect ShippingTree from the ShippingTree tile on Katana's Integrations page. Once disconnected, orders, inventory, inbound shipments and products stop syncing in both directions.
Records already brought into Katana stay in place, including sales orders, fulfillments, stock transfers, products and locations.