Skip to main content

Monta integration setup

Configure warehouse mapping, SKU or alias product import, on-hand inventory reconciliation, and inbound transfers.

A
Written by Argo Ohvril

What syncs between Katana and Monta

Data flow between Monta and Katana

The table below summarizes each data flow between Monta and Katana.

Data

Direction

Status

Products

Monta → Katana

Available

Inbound stock transfers

Monta → Katana

Available

Inventory sync

Monta → Katana

Available

Locations and mapping

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

  • Not mapped: the warehouse has never been mapped. Click Add to Katana to create its Katana location automatically.

  • Unlink: pauses 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 Monta configuration screen in Katana, listing Monta warehouses with statuses Not mapped, Unlinked and mapped, an Add to Katana button on a Not mapped warehouse, Unlink and Relink actions, and the Activate sync button in the header

Products sync

Product mapping creates a required link between each Monta product and a Katana item. Products are imported by SKU. If a Katana product already has that SKU, the two are matched. If the SKU is unknown in Katana, a new product is created when it is needed. You choose how SKUs are matched: direct 1:1, or through SKU aliases.

Kits and bundles from Monta are imported as Katana products. To define what goes into a kit, add a bill of materials (BOM) of its components in Katana.

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

SKU aliases

A SKU alias links a Monta SKU to a different Katana SKU. Use aliases when the same item has a different SKU in Monta than in Katana. Upload your SKU alias mapping before importing products, so mismatched SKUs match existing Katana products instead of creating duplicates.

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

Inventory sync

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

Reconciliation compares Katana's in-stock quantity with Monta's on-hand quantity only. It runs on a schedule or on demand. When the numbers differ, Katana creates stock adjustments for the difference, so the stock it uses matches what is physically in Monta's warehouses.

the inventory sync settings screen of the Monta integration in Katana, showing reconciliation of Katana in-stock against Monta on-hand with schedule and run-on-demand options, and External inventory On hand per mapped location

Inbound shipments

Each Monta inbound shipment becomes one Katana stock transfer.

  • Number: the PO number when one exists. Otherwise, the inbound ID.

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

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

Each stock transfer follows its inbound's 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. If an inbound is canceled, its stock transfer is deleted.

the inbound shipments screen of the Monta integration in Katana, showing inbound shipments as stock transfers with PO or inbound number, origin and destination locations, in transit or received status, and expected versus received quantities

What does not sync

  • Orders: Monta orders are not imported into Katana, and Katana sales orders are not sent to Monta.

  • Fulfillments, carriers and tracking numbers.

  • Product or stock changes from Katana to Monta.

  • Returns and RMAs.

  • Serial-number tracking. Lot and batch data appears read-only where Monta provides it.

Disconnecting

To disconnect, go to Katana's Integrations page and open the Monta integration. Once you disconnect, syncing with Monta stops: no new inventory, product or inbound data comes in. Records Katana has already imported stay in Katana, including products, locations and stock transfers.

Did this answer your question?