What syncs between Katana and Elite Ops
The table below summarizes how data moves between Katana and Elite Ops.
Data | Direction | Status |
Orders | Two-way | Available |
Products | Elite Ops → Katana | Available |
Inventory sync | Elite Ops → Katana | Available |
Locations and mapping
After Elite Ops approves the connection, the configuration screen opens on the Location tab. Each Elite Ops warehouse maps 1:1 to its own dedicated Katana location. Click Add to Katana to create that location automatically.
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 an unlinked warehouse.
Only mapped warehouses sync.
Products sync
Product mapping creates a required link between each Elite Ops product and a Katana item. Products are imported by SKU, and you choose how SKUs are matched: direct 1:1 or through SKU aliases. Matching works like this:
An Elite Ops SKU that matches an existing Katana product links to that product.
An unknown SKU creates a new Katana product just-in-time.
Kits and bundles become Katana products. You can add a BOM of components to them in Katana. A kit order line stays a single sales-order row.
SKU aliasing
A SKU alias links an Elite Ops SKU to a different Katana SKU. Use aliases when the same product is coded differently in the two systems, so that it matches the existing Katana product instead of creating a new one. Upload your SKU alias mapping before importing products.
Orders sync
Orders from Elite Ops
Orders import once they reach the configured import-from status, which is Open by default. After import, they keep updating automatically through every later status change.
Each Elite Ops order becomes one Katana sales order, with each line as one row.
The order source is shown as Elite Ops.
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 Elite Ops order is deleted in Katana only if the order is still open.
Orders from Katana
Katana pushes a sales order to Elite Ops as an outbound order when it reaches the Ready for fulfillment status. Katana then tracks its progress back through the import flow above.
Canceling the Katana sales order does not cancel the Elite Ops order.
Changes made in Katana after the push do not update the Elite Ops order.
Inventory sync
Elite Ops stock levels appear in Katana as read-only External inventory at each mapped warehouse's Katana location. The number surfaced is On hand.
Reconciliation compares Katana's in-stock quantity against the Elite Ops on-hand quantity only. It runs on a schedule or on demand, and Katana creates stock adjustments for any differences. Katana never pushes inventory changes to Elite Ops.
What does not sync
Products and stock changes from Katana to Elite Ops.
Changes made in Katana after a sales order has been pushed to Elite Ops.
Inbound shipments and stock transfers.
Returns and RMAs.
Serial-number tracking. Lot and batch data is shown read-only where Elite Ops exposes it.
Disconnecting
To disconnect, open the Elite Ops integration from Katana's Integrations page and disconnect it. Syncing stops right away: orders, fulfillments, products and inventory no longer import, and Katana no longer pushes sales orders to Elite Ops. Records already brought into Katana, such as sales orders, fulfillments, products and stock adjustments, stay in Katana.