Skip to main content

TPS integration setup

Map warehouses and set up two-way orders, SKU and alias product matching, stock reconciliation, and inbound transfers.

A
Written by Argo Ohvril

What syncs between Katana and TPS

Data flow between TPS and Katana

The table below summarizes how each type of data moves between Katana and TPS.

Data

Direction

Status

Orders

Two-way

Available

Products

TPS → Katana

Available

Inbound stock transfers

TPS → Katana

Available

Inventory sync

TPS → Katana

Available

Locations and mapping

After TPS approves the connection, the configuration screen opens on the Location tab. Nothing syncs until you click Activate sync in the header.

  • Each TPS warehouse maps 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.

  • Only mapped warehouses sync.

the warehouse location mapping panel on the Location tab of the TPS configuration screen, listing TPS warehouses with their mapped Katana locations, one warehouse showing Not mapped with an Add to Katana button, and one showing Unlinked with a Relink button

Products sync

Product mapping creates a required link between each TPS product and a Katana item. Products are matched by SKU, and you choose how SKUs are matched: direct 1:1 or through SKU aliases.

  • When a product is imported, Katana matches it to an existing product with the same SKU.

  • If no Katana product has that SKU, Katana creates the product just-in-time.

  • Kits and bundles become Katana products. To define their components, add a BOM to the product in Katana.

  • On a sales order, a kit order line stays a single row.

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

SKU aliasing

A SKU alias links a TPS SKU to a different Katana SKU. Use aliases when the same item has different SKUs in TPS and Katana, so the two records still match.

Upload your SKU alias mapping before you import products. Otherwise, unmatched SKUs create new products.

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

Orders sync

Orders from TPS to Katana

  • Orders import once they reach the configured import-from status, which is the "Open" state by default.

  • After import, each order updates automatically through every later status change.

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

  • Each shipped package becomes a Katana fulfillment with its carrier and tracking number. A multi-package shipment creates one fulfillment per package. Together, these fulfillments never exceed the ordered quantities.

  • If an order is canceled in TPS, Katana deletes the 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

Orders from Katana to TPS

  • A Katana sales order is pushed to TPS as an outbound order when it reaches the Ready for fulfillment status.

  • After the push, the order's progress in TPS is tracked back in Katana, the same way as imported orders.

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

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

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

Inventory sync

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

Reconciliation compares Katana's in-stock quantity with TPS's on-hand quantity. It runs on a schedule or whenever you start it manually. When the numbers differ, Katana creates stock adjustments for the difference, which keeps Katana's stock in line with what TPS physically holds.

the inventory sync settings screen in the TPS integration, showing read-only External inventory on-hand quantities per mapped location and the reconciliation schedule with a run-now option

Inbound shipments

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

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

  • Origin: the location you assign for each destination warehouse. This assignment is required.

  • The stock transfer follows the inbound's status, and received quantities update the transfer.

  • Katana stock transfers have only two states: in transit and received. If an inbound is partially received, the expected and received quantities update until it is fully received.

  • If an inbound is canceled in TPS, Katana deletes its stock transfer.

the inbound shipments screen in the TPS integration, showing inbound shipments listed as Katana stock transfers with transfer number, origin location, destination location, status, and expected versus received quantities

What does not sync

  • Katana does not push products or stock changes to TPS.

  • Changes made in Katana to an order after it has been pushed do not update the TPS order.

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

  • Returns and RMAs do not sync.

  • Serial numbers are not tracked. Lot and batch data appears read-only where TPS provides it.

  • Warehouses that aren't mapped to a Katana location do not sync.

Disconnecting

To disconnect, open the TPS integration from Katana's Integrations page and disconnect it. Syncing between Katana and TPS stops right away.

Records already brought into Katana stay there. This includes sales orders, fulfillments, products, and stock transfers.

Did this answer your question?