Skip to main content

RJW integration setup

Map RJW warehouses to locations, then configure product, order, inventory, and inbound stock transfer syncs.

A
Written by Argo Ohvril

What syncs between Katana and RJW

Data flow between RJW and Katana

This table summarizes the data flows between Katana and RJW.

Data

Direction

Status

Orders

RJW → Katana

Available

Products

RJW → Katana

Available

Inbound stock transfers

RJW → Katana

Available

Inventory sync

RJW → Katana

Available

Locations and mapping

After RJW approves the connection, the configuration screen opens on the Location tab. Each RJW warehouse maps to its own Katana location.

  • Not mapped: The warehouse has never been mapped. Click Add to Katana to create a dedicated Katana location for it.

  • Unlink: Pauses syncing for 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 RJW configuration screen, listing RJW warehouses with their statuses (Not mapped, Unlinked) and the Add to Katana, Unlink and Relink actions, with the Activate sync button visible in the header

Products sync

Every RJW product must be linked to 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, a product is created just in time.

Kits and bundles from RJW become Katana products. You can add a bill of materials (BOM) of components to them in Katana. A kit order line stays a single row on the sales order.

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

SKU aliases

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

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

Orders sync

Orders flow one way, from RJW into Katana.

  • Which orders import: An order imports once it reaches the import-from status you configure. The default is the Open state.

  • Status updates: After import, the order keeps updating automatically through every later status change in RJW.

  • How orders appear: Each RJW order becomes one Katana sales order, with one row per order line. The order source is shown as RJW.

  • Fulfillments and tracking: Each shipped package becomes a Katana fulfillment with its carrier and tracking number. A shipment with several packages creates one fulfillment per package, so an order can show several fulfillments. Together, they never exceed the ordered quantities.

  • Cancellations: When an order is canceled in RJW, it is deleted in Katana only if the sales order is still open. Canceling a sales order in Katana doesn't cancel the order in RJW.

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

Inventory sync

RJW's stock numbers appear in Katana as read-only external inventory, at the Katana location mapped to each warehouse. The number shown is the on-hand quantity.

Reconciliation compares Katana's in-stock quantity with RJW's on-hand quantity. It runs on a schedule or on demand, and creates stock adjustments in Katana for any differences. This keeps the inventory you plan with in Katana aligned with what RJW physically holds.

the inventory sync settings screen for RJW, showing read-only external on-hand inventory per mapped location and the scheduled and on-demand reconciliation options

Inbound shipments

Each RJW inbound shipment becomes one Katana stock transfer. The transfer number is the PO number when there is one; otherwise it's the inbound ID.

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

  • Origin: The location you assign for each destination warehouse. It must be mapped.

  • Status: The stock transfer follows the inbound status.

  • Partial receiving: Katana stock transfers move from in transit to received. Partial receipts show as updated expected and received quantities until the shipment is fully received.

  • Cancellations: A canceled inbound deletes its stock transfer.

the inbound shipments screen for RJW, showing inbound shipments as Katana stock transfers with PO or inbound number, origin and destination locations, status, and expected versus received quantities

What does not sync

  • Orders to RJW: Katana doesn't send orders to RJW. Orders flow one way, from RJW to Katana.

  • Products and stock to RJW: Product and stock changes made in Katana aren't pushed to RJW.

  • Returns: Returns and RMAs don't sync.

  • Serial numbers: Serial-number tracking doesn't sync.

  • Lot and batch data: Shown read-only where RJW provides it.

Disconnecting

To disconnect, go to the Integrations page in Katana, open the RJW integration, and disconnect it. Syncing of orders, inventory, inbound shipments and products stops right away. Records that were already imported stay in Katana, including:

  • Sales orders

  • Fulfillments

  • Stock transfers

  • Products

  • Locations

Did this answer your question?