Skip to main content

ShipMonk integration setup

Map ShipMonk warehouses to locations; set up two-way orders, SKU products, stock reconciliation, and inbound transfers.

A
Written by Argo Ohvril

What syncs between Katana and ShipMonk

Data flow between ShipMonk and Katana

The table below summarizes each data flow between Katana and ShipMonk.

Data

Direction

Status

Orders

Two-way

Available

Products

ShipMonk → Katana

Available

Inbound stock transfers

ShipMonk → Katana

Available

Inventory sync

ShipMonk → Katana

Available

Locations and mapping

After the connection is approved, the configuration screen opens on the Location tab. Each ShipMonk warehouse maps to its own dedicated Katana location. Click Add to Katana to create that location automatically.

  • Not mapped: A warehouse that has never been mapped shows this status until you click Add to Katana.

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

  • Relink: Resumes syncing for an unlinked warehouse.

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 ShipMonk configuration screen, listing ShipMonk warehouses with their statuses (mapped, Unlinked, Not mapped), the Add to Katana button for an unmapped warehouse, Unlink and Relink actions, and the Activate sync button in the header

Products sync

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

Products are imported by SKU:

  • If a Katana product already has the SKU, the two are matched.

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

ShipMonk kits and bundles become Katana products. You can add a BOM of their components in Katana. A kit order line stays a single sales order row.

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

SKU aliases

A SKU alias links a ShipMonk SKU to a different Katana SKU. Use aliases when the same item has different SKUs in ShipMonk and Katana. Upload your SKU alias mapping before importing products, so mismatched SKUs match existing items instead of creating new products.

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

Orders sync

From ShipMonk to Katana

ShipMonk 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 ShipMonk order becomes one Katana sales order, with one row per line. The order source is ShipMonk.

  • Each shipped package becomes a Katana fulfillment with carrier and tracking details. Multi-package shipments create one fulfillment per package. Together, these fulfillments never exceed the ordered quantities.

  • When an order is canceled in ShipMonk, it is deleted in Katana only if the Katana order is still open.

the order sync settings screen for ShipMonk with the import-from status option (default Open) and order status settings

From Katana to ShipMonk

A Katana sales order is pushed to ShipMonk as an outbound order when it reaches the Ready for fulfillment status. After that, its progress is tracked back in Katana like any imported order.

  • Canceling the Katana sales order does not cancel the pushed ShipMonk order.

  • Changes made in Katana after the push do not update the ShipMonk order.

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

Inventory sync

ShipMonk's stock numbers appear in Katana as read-only external inventory at each warehouse's mapped location. On hand is the number shown.

Reconciliation compares Katana's in-stock quantity with ShipMonk'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 reflect what ShipMonk physically holds. Katana never pushes inventory changes to ShipMonk.

the inventory sync settings screen for ShipMonk, showing read-only external on-hand inventory per mapped location and the reconciliation schedule and run-now option

Inbound shipments

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

  • Destination: The Katana location mapped to the inbound's warehouse. This location receives the stock.

  • Origin: The location assigned to each destination warehouse. It must be mapped.

Stock transfers follow the inbound's status, and received quantities update the transfer. Katana stock transfers move from in transit to received. Partial receipts show as updated expected and received quantities until the shipment is fully received. A canceled inbound deletes its stock transfer.

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

What does not sync

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

  • Changes to a Katana sales order after it is pushed are not sent to ShipMonk.

  • Canceling a Katana sales order does not cancel the ShipMonk order.

  • Returns and RMAs.

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

  • Warehouses that are not mapped, or are Unlinked.

Disconnecting

To disconnect, go to the ShipMonk integration on Katana's Integrations page. Syncing stops immediately: no new orders, fulfillments, inventory, or inbound updates arrive, and no sales orders are pushed to ShipMonk. Records Katana already imported stay in Katana, including sales orders, fulfillments, products, stock transfers, and stock adjustments.

Did this answer your question?