Skip to main content

OSA Commerce integration setup

Map warehouses, match products by SKU or alias, and set up order, fulfillment, inventory, and inbound transfer syncs.

A
Written by Argo Ohvril

What syncs between Katana and OSA Commerce

Data flow between OSA Commerce and Katana

The table below summarizes each data type and how it moves between OSA Commerce and Katana.

Data

Direction

Status

Orders

OSA Commerce → Katana

Available

Products

OSA Commerce → Katana

Available

Inbound stock transfers

OSA Commerce → Katana

Available

Inventory sync

OSA Commerce → Katana

Available

Locations and mapping

After you connect OSA Commerce from Katana's Integrations page using the username and password from your OSA Commerce representative, the configuration screen opens on the Location tab. Nothing syncs until you click Activate sync in the header.

  • Each OSA Commerce warehouse maps 1:1 to its own dedicated Katana location. Click Add to Katana to create that location automatically.

  • A warehouse that was never mapped shows Not mapped.

  • To pause a mapped warehouse, click Unlink. Its status shows Unlinked. Click Relink to resume it.

  • Only mapped warehouses sync.

the warehouse location mapping panel on the Location tab, listing OSA Commerce warehouses with their mapped Katana locations, the Add to Katana button for a Not mapped warehouse, and Unlink and Relink actions with an Unlinked status shown

Products sync

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

  • Products whose SKU already exists in Katana are matched to the existing Katana product.

  • Products with an unknown SKU are created in Katana just in time.

  • Kits and bundles become Katana products. Add a BOM of components to them in Katana. A kit order line stays a single sales order row.

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

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

SKU aliases

A SKU alias links an OSA Commerce SKU to a different Katana SKU. Use aliases when the same item has different SKUs in the two systems. Upload your SKU alias mapping before the product import so that mismatched SKUs match existing Katana products instead of creating new ones.

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

Orders sync

Orders flow one way, from OSA Commerce into Katana.

  • Which orders import: Orders import once they reach the configured import-from status. The default is the "Open" state.

  • Status updates: After import, an order keeps updating automatically in Katana through every later status change in OSA Commerce.

  • How orders appear: Each OSA Commerce order becomes one Katana sales order, and each order line becomes one row. The order source is shown as OSA Commerce.

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

  • Cancellations: When an order is canceled in OSA Commerce, Katana deletes the matching sales order only if it is still open.

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

Inventory sync

OSA Commerce stock numbers appear in Katana as read-only External inventory at each mapped warehouse's Katana location. The number shown is OSA Commerce's On hand quantity. You can't edit it in Katana.

Reconciliation compares Katana's in-stock quantity against OSA Commerce's on-hand quantity. It runs on a schedule or on demand, and Katana creates stock adjustments for any differences.

the inventory sync settings screen showing read-only External inventory with On hand quantities per mapped location and the scheduled and on-demand reconciliation options

Inbound shipments

Each OSA Commerce inbound shipment becomes one Katana stock transfer.

  • Number: The transfer uses the PO number when one is present. Otherwise it uses the inbound ID.

  • Destination: The Katana location mapped 1:1 to the inbound's warehouse. This location receives the stock.

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

  • Status and quantities: The transfer tracks the inbound's status, and received quantities update the transfer.

  • Partial receiving: Katana stock transfers are either in transit or received. A partial receipt shows as updated expected and received quantities until the shipment is fully received.

  • Cancellations: Canceling an inbound deletes its stock transfer.

the inbound shipments screen showing OSA Commerce inbounds as Katana stock transfers with transfer number, origin and destination locations, status, and expected versus received quantities

What does not sync

  • Katana does not send orders to OSA Commerce. Orders flow from OSA Commerce into Katana only.

  • Katana does not push products or stock changes to OSA Commerce.

  • Returns and RMAs.

  • Serial number tracking.

  • Lot and batch data is shown read-only, where OSA Commerce provides it, and can't be edited.

Disconnecting

To disconnect, open the OSA Commerce tile on Katana's Integrations page. After you disconnect, syncing of orders, fulfillments, products, inventory, and inbound shipments from OSA Commerce stops. Records already brought into Katana, such as sales orders, fulfillments, products, and stock transfers, stay in Katana.

Did this answer your question?