Skip to main content

Logiwa integration setup

Map warehouses to locations and set up two-way orders, SKU-matched products, stock levels, and inbound transfers.

A
Written by Argo Ohvril

What syncs between Katana and Logiwa

Data flow between Logiwa and Katana

The table below summarizes each data type and the direction it moves between Katana and Logiwa.

Data

Direction

Status

Orders

Two-way

Available

Products

Logiwa → Katana

Available

Inbound stock transfers

Logiwa → Katana

Available

Inventory sync

Logiwa → Katana

Available

Locations and mapping

After the connection is approved, the configuration screen opens on the Location tab. Each Logiwa warehouse maps 1:1 to its own dedicated Katana location.

  • Add to Katana automatically creates a Katana location for a warehouse.

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

  • To pause a mapped warehouse, click Unlink. Its status then shows Unlinked.

  • Click Relink to resume syncing it.

Only mapped warehouses sync.

the warehouse location mapping panel on the Location tab of the Logiwa configuration screen, listing Logiwa warehouses with their status (Mapped, Unlinked, Not mapped), the linked Katana location for each, and the Add to Katana, Unlink and Relink buttons

Products sync

Product mapping creates a required link between each Logiwa product and a Katana item. Products are matched by SKU:

  • If a Katana product already has the SKU, it is matched.

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

You can choose to match SKUs directly (1:1) or through SKU aliases.

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

Kits and bundles from Logiwa become Katana products. You can then add a BOM of components to them in Katana. On a sales order, a kit order line stays a single row.

SKU aliases

A SKU alias links a Logiwa SKU to a different Katana SKU. Use aliases when the same item has different SKUs in the two systems, so it matches the existing Katana product instead of creating a duplicate. Upload your SKU alias mapping before importing products.

the products mapping screen with SKU alias mapping, showing a list of Logiwa SKUs paired with their differing Katana SKUs and the option to upload an alias mapping file

Orders sync

Orders from Logiwa

Orders import once they reach the configured import-from status. The default is the Open state. After import, they update automatically through every later status change.

  • Each Logiwa order becomes one Katana sales order, with one row per order line.

  • The order source is shown as Logiwa.

  • Each shipped package becomes a Katana fulfillment with its carrier and tracking number.

  • Multi-package shipments create one fulfillment per package. Together, these fulfillments never exceed the ordered quantities.

  • A canceled Logiwa 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

Orders from Katana

A Katana sales order is pushed to Logiwa as an outbound order when it reaches the Ready for fulfillment status. Its progress then syncs back to Katana in the same way as imported orders.

Canceling the Katana sales order does not cancel the Logiwa order. Changes you make in Katana after the push do not update the Logiwa order.

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

Inventory sync

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

Reconciliation compares Katana's in-stock quantity against Logiwa's on-hand quantity. It runs on a schedule or on demand. For any difference, it creates stock adjustments, so the stock Katana uses matches Logiwa.

the inventory sync settings screen for Logiwa in Katana, showing read-only External inventory on-hand quantities per mapped location and the reconciliation schedule with an on-demand reconcile option

Inbound shipments

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

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

The stock transfer follows the inbound status, and received quantities update the transfer. Katana stock transfers have two states: in transit and received. Partial receiving therefore shows as updated expected and received quantities until the shipment is fully received. A canceled inbound deletes its stock transfer.

the inbound shipments screen in Katana, showing a stock transfer created from a Logiwa inbound shipment with its PO number, origin and destination locations, in transit status, and expected versus received quantities

What does not sync

  • Product changes and stock changes made in Katana are not pushed to Logiwa.

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

  • Canceling a pushed sales order in Katana does not cancel it in Logiwa.

  • Returns and RMAs.

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

Disconnecting

To disconnect, go to Katana's Integrations page, open the Logiwa integration, and disconnect it. Syncing stops right away, and no further orders, inventory or inbound updates are exchanged. Records already imported into Katana remain, including sales orders, fulfillments, products and stock transfers.

Did this answer your question?