Skip to main content

NLRP integration setup

Map NLRP warehouses to Katana locations and set up two-way orders plus product, stock, and inbound shipment syncs.

A
Written by Argo Ohvril

What syncs between Katana and NLRP

Data flow between NLRP and Katana

The table below summarizes how data moves between Katana and NLRP for this integration.

Data

Direction

Status

Orders

Two-way

Available

Products

NLRP → Katana

Available

Inbound stock transfers

NLRP → Katana

Available

Inventory sync

NLRP → Katana

Available

Locations and mapping

After NLRP approves the connection, the configuration screen opens on the Location tab. Each NLRP warehouse maps 1:1 to its own dedicated Katana location. Click Add to Katana to create that location automatically.

  • Not mapped: the warehouse has never been mapped. It stays this way 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.

the warehouse location mapping panel on the Location tab of the NLRP configuration screen, listing NLRP warehouses with their mapped Katana locations, an Add to Katana button for a warehouse showing Not mapped, an Unlinked status with a Relink option, and Unlink options for mapped warehouses

Products sync

Product mapping creates a required link between each NLRP product and a Katana item. You choose how SKUs are matched:

  • Direct 1:1: SKUs must match exactly.

  • SKU aliases: SKUs are matched through an alias mapping.

Products are imported by SKU. If a product with that SKU already exists in Katana, it is matched. If the SKU is unknown, Katana creates the product just-in-time.

Kits and bundles from NLRP become Katana products. Add a BOM of the kit's components in Katana. On orders, a kit line stays a single sales order row.

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

SKU aliasing

A SKU alias links an NLRP SKU to a different Katana SKU. Use aliases when the same product has different SKUs in NLRP and in 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 NLRP SKUs paired with different Katana SKUs and the option to upload an alias mapping file

Orders sync

From NLRP to Katana

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

Each NLRP order becomes one Katana sales order, with one row per order line. The order source is NLRP.

Each shipped package becomes a Katana fulfillment with the carrier and tracking number. A multi-package shipment creates one fulfillment per package, so a single order can show several fulfillments. Together, these never exceed the ordered quantities.

A canceled NLRP order is deleted in Katana only if the sales order 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 NLRP

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

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

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

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

Inventory sync

NLRP's stock numbers appear in Katana as read-only External inventory at each warehouse's mapped location. The number shown is NLRP's On hand quantity.

Reconciliation compares Katana's in-stock quantity with NLRP's on-hand quantity. It runs on a schedule or on demand, and creates stock adjustments for any differences. This keeps Katana's stock figures aligned with what is physically in the warehouse.

the inventory sync settings screen for NLRP showing read-only External inventory On hand quantities per mapped location and the reconciliation schedule and on-demand reconcile option

Inbound shipments

Each NLRP inbound shipment becomes one Katana stock transfer. The transfer number is the PO number when one is present; otherwise it is the inbound ID.

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

  • Origin: the location assigned for each destination warehouse. It 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 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 an NLRP 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 are never pushed from Katana to NLRP.

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

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

  • Returns and RMAs.

  • Serial-number tracking. Lot and batch data is shown read-only where NLRP provides it.

Disconnecting

Go to Katana's Integrations page, open NLRP, and disconnect. Syncing of orders, products, inventory, and inbound shipments stops immediately, and Katana no longer pushes sales orders to NLRP. Records already imported into Katana stay in Katana. This includes sales orders, fulfillments, products, stock transfers, and stock adjustments.

Did this answer your question?