Skip to main content

Nimble integration setup

Map warehouses to locations and set up two-way orders, SKU-based products, read-only inventory, and inbound transfers.

A
Written by Argo Ohvril

What syncs between Katana and Nimble

Data flow between Nimble and Katana

The table below summarizes how data moves between Katana and Nimble.

Data

Direction

Status

Orders

Two-way

Available

Products

Nimble → Katana

Available

Inbound stock transfers

Nimble → Katana

Available

Inventory sync

Nimble → Katana

Available

Locations and mapping

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

  • Not mapped: The warehouse has never been mapped. Click Add to Katana to create its Katana location automatically.

  • 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, listing Nimble warehouses with their status (Not mapped, Unlinked, mapped) and the Add to Katana, Unlink and Relink actions next to each warehouse

Products sync

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

Products are imported by SKU:

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

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

Kits and bundles become Katana products. Add a bill of materials (BOM) with the components in Katana. A kit order line stays a single sales order row.

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

SKU aliases

A SKU alias links a Nimble SKU to a different Katana SKU. Use aliases when the same product has a different SKU in Nimble than in Katana.

Upload your SKU alias mapping before importing products. Otherwise, mismatched SKUs may create new products instead of matching your existing ones.

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

Orders sync

From Nimble to Katana

Orders import once they reach the configured import-from status (default: Open). After that, they keep updating automatically through every later status change.

  • Sales orders: Each Nimble order becomes one Katana sales order, with one row per order line. The order source is Nimble.

  • Fulfillments: Each shipped package becomes a Katana fulfillment with the carrier and tracking number. A multi-package shipment creates one fulfillment per package. Together, these fulfillments never exceed the ordered quantities.

  • Cancellations: A canceled Nimble order is deleted in Katana only if the order is still open.

the order sync settings screen with the import and status options, showing the import-from status dropdown set to Open

From Katana to Nimble

When a Katana sales order reaches the Ready for fulfillment status, Katana pushes it to Nimble as an outbound order. From there, the import flow above tracks its progress back in Katana.

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

  • Changes you make in Katana after the push do not update the Nimble order.

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

Inventory sync

Nimble is the source of truth for physical stock. Katana shows Nimble's stock numbers as read-only External inventory at each warehouse's mapped location. The number shown is Nimble's on-hand quantity.

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

the inventory sync settings screen showing read-only External inventory per mapped location and the reconciliation schedule with an on-demand reconcile option

Inbound shipments

Each Nimble 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 Nimble warehouse.

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

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 receipts therefore 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 a Nimble inbound as a Katana stock transfer with its PO number, origin and destination locations, status, and expected versus received quantities

What does not sync

  • Products and stock changes from Katana to Nimble

  • Changes to a Katana sales order after it has been pushed to Nimble

  • Cancellations of Katana sales orders (the Nimble order stays active)

  • Returns and RMAs

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

  • Warehouses that are not mapped or are unlinked

Disconnecting

To disconnect, go to Katana's Integrations page and open the Nimble integration.

Once disconnected, Katana stops exchanging data with Nimble. This includes order imports, order pushes, fulfillment and tracking updates, inventory and inbound updates, and reconciliation.

Records already imported into Katana stay in Katana, such as sales orders, products, fulfillments and stock transfers.

Did this answer your question?