The table below summarizes how each type of data moves between Katana and fulfilmentcrowd.

Connect fulfilmentcrowd from Katana's Integrations page. Click Connect on the tile and enter your fulfilmentcrowd API key. You can also enter an optional numeric Default Channel ID. After fulfilmentcrowd approves the connection, the configuration screen opens on the Location tab. The status shows Connected with Sync inactive. Nothing syncs until you click Activate sync.

Each fulfilmentcrowd warehouse maps to its own dedicated Katana location. A warehouse that was never mapped shows Not mapped, and Add to Katana creates its location. To pause a mapped warehouse, use Unlink, and it shows Unlinked. Use Relink to resume it. Only mapped warehouses sync.

Product mapping creates a required link between each fulfilmentcrowd product and a Katana item. You can choose how SKUs are matched: either direct 1:1 or through SKU aliases. Products are imported by SKU. If a Katana product already has the same SKU, it is matched. If the SKU is unknown, Katana creates the product just-in-time.

Kits and bundles from fulfilmentcrowd become Katana products, and you can add a BOM of components to them in Katana. A kit order line stays a single sales order row.

A SKU alias links a fulfilmentcrowd SKU to a different Katana SKU. Use aliases when the same item has mismatched SKUs in the two systems. Upload your SKU alias mapping before you import products, so items match correctly and no duplicates are created.

fulfilmentcrowd orders import into Katana once they reach your configured import-from status, which is the Open state by default. After import, they keep updating automatically through every later status change. Each order becomes one Katana sales order, with one row per line, and the integration name is shown as the order source.

Each shipped package becomes a Katana fulfillment with carrier and tracking details. Multi-package shipments create one fulfillment per package, and together these never exceed the ordered quantities. If an order is canceled in fulfilmentcrowd, it is deleted in Katana only while it is still open.

Orders also flow out of Katana. When a Katana sales order reaches Ready for fulfillment, it is pushed to fulfilmentcrowd as an outbound order. Its progress is then tracked back in Katana through the import flow described above. Canceling the Katana sales order does not cancel the fulfilmentcrowd order. Changes you make in Katana after the push do not update the fulfilmentcrowd order.

fulfilmentcrowd stock levels appear in Katana as read-only external inventory at each warehouse's mapped location. The figure shown is fulfilmentcrowd's on-hand quantity.

Reconciliation compares Katana's in-stock quantity with fulfilmentcrowd's on-hand quantity only. It runs on a schedule or on demand, and creates stock adjustments for any differences. Katana never pushes inventory changes to fulfilmentcrowd.

Each fulfilmentcrowd inbound shipment becomes one Katana stock transfer. The transfer is numbered with the PO number when one is present, and otherwise with the inbound ID.

The stock transfer follows the inbound's status, and received quantities update the transfer. Katana stock transfers move straight from in transit to received. Partial receiving therefore shows as updated expected and received quantities until the shipment is fully received. If an inbound is canceled, its stock transfer is deleted.

To disconnect, open the fulfilmentcrowd integration from Katana's Integrations page and disconnect it there. Syncing stops right away: orders, fulfillments, inbound shipments, and inventory are no longer imported, and sales orders are no longer pushed to fulfilmentcrowd. Records that were already brought into Katana stay in Katana, including sales orders, fulfillments, products, and stock transfers.