Skip to main content

Shipfusion integration setup

Map warehouses to locations and set up two-way orders, SKU-matched products, inventory, and inbound transfer syncs.

A
Written by Argo Ohvril

What syncs between Katana and Shipfusion

Data flow between Shipfusion and Katana

The table below shows which data flows between Katana and Shipfusion, and in which direction.

Data

Direction

Status

Orders

Two-way

Available

Products

Shipfusion → Katana

Available

Inbound stock transfers

Shipfusion → Katana

Available

Inventory sync

Shipfusion → Katana

Available

Locations and mapping

After you connect, the configuration screen opens on the Location tab. Each Shipfusion warehouse maps to its own dedicated Katana location.

  • Add to Katana creates the Katana location for a warehouse and maps it 1:1.

  • 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.

  • To resume a paused warehouse, 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 Shipfusion configuration screen, listing Shipfusion warehouses with their statuses (Not mapped, mapped, Unlinked), an Add to Katana button on an unmapped warehouse, Unlink and Relink actions on mapped ones, and the Activate sync button in the header

Products sync

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

Products are imported by SKU:

  • If the SKU already exists in Katana, the product is matched to that item.

  • If the SKU is unknown, Katana creates the product when it is needed.

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

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

SKU aliases

A SKU alias links a Shipfusion SKU to a different Katana SKU. Use aliases when the same product has different SKUs in the two systems, so it matches the correct Katana item instead of creating a new one. Upload your SKU alias mapping before you import products.

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

Orders sync

From Shipfusion 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 Shipfusion order becomes one Katana sales order, and each order line becomes one row. The order source is Shipfusion.

  • Each shipped package becomes a Katana fulfillment with the carrier and tracking number.

  • A multi-package shipment creates one fulfillment per package, so one order can show several fulfillments. Together they never exceed the ordered quantities.

  • If an order is canceled in Shipfusion, it is deleted in Katana only if it 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 Shipfusion

When a Katana sales order reaches the Ready for fulfillment status, Katana sends it to Shipfusion as an outbound order. From then on, its progress syncs back to Katana in the same way as imported orders.

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

  • Changes you make in Katana after the order has been sent do not update the Shipfusion order.

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

Inventory sync

Shipfusion stock levels appear in Katana as read-only External inventory at each warehouse's mapped location. Katana shows the on-hand quantity.

Reconciliation compares Katana's in-stock quantity with Shipfusion's on-hand quantity. It runs on a schedule or whenever you start it. For any difference, Katana creates a stock adjustment, so Katana stays aligned with the warehouse.

the inventory sync settings screen for Shipfusion, showing read-only External inventory on-hand quantities per mapped location and the reconciliation schedule and run-now options

Inbound shipments

Each Shipfusion inbound shipment becomes one Katana stock transfer. The transfer number is the PO number when one exists, or the inbound ID otherwise.

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

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

The stock transfer follows the inbound's status, and received quantities update the transfer. If the inbound is canceled, its stock transfer is deleted.

Katana stock transfers have two states: in transit and received. Partial receiving shows as updated expected and received quantities until the shipment is fully received.

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

What does not sync

  • Product or stock changes are not sent from Katana to Shipfusion.

  • Changes made in Katana to an order after it has been sent to Shipfusion.

  • Canceling a sent order in Katana does not cancel it in Shipfusion.

  • Returns and RMAs.

  • Serial-number tracking. Lot and batch data appears read-only where Shipfusion provides it.

Disconnecting

To disconnect, open the Shipfusion integration from Katana's Integrations page. When you disconnect, syncing stops immediately: Katana no longer imports or updates orders, fulfillments, inventory, or inbound shipments, and no longer sends orders to Shipfusion.

Records already brought into Katana stay in Katana, including sales orders, fulfillments, products, and stock transfers.

Did this answer your question?