Skip to main content

Mintsoft integration setup

Map warehouses, then set up two-way orders, SKU-matched products, read-only stock, and inbound stock transfers.

A
Written by Argo Ohvril

What syncs between Katana and Mintsoft

Data flow between Mintsoft and Katana

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

Data

Direction

Status

Orders

Two-way

Available

Products

Mintsoft → Katana

Available

Inbound stock transfers

Mintsoft → Katana

Available

Inventory sync

Mintsoft → Katana

Available

Locations and mapping

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

  • Add to Katana creates the Katana location for a warehouse and maps it.

  • A warehouse that has never been mapped shows Not mapped.

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

  • To resume syncing, click Relink.

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 Mintsoft configuration screen, listing Mintsoft warehouses with their statuses (Not mapped, mapped to a Katana location, Unlinked) and the Add to Katana, Unlink, and Relink actions, with the Activate sync button in the header

Products sync

Product mapping creates the required link between each Mintsoft product and a Katana item. Products are imported by SKU:

  • A Mintsoft SKU that matches an existing Katana product is linked to that product.

  • A Mintsoft SKU that Katana doesn't recognize creates a new Katana product when it's needed.

You choose how SKUs are matched: directly 1:1, or through SKU aliases.

Mintsoft kits and bundles become Katana products. To track their components, add a bill of materials (BOM) to the product in Katana. A kit order line stays a single row on the sales order.

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

SKU aliases

A SKU alias links a Mintsoft SKU to a different Katana SKU. Use an alias when the same product has a different SKU in Mintsoft than in Katana, so it maps to the existing Katana item instead of creating a duplicate. Upload your SKU alias mapping before products are imported.

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

Orders sync

Orders from Mintsoft

Mintsoft orders import into Katana once they reach the configured import-from status. The default is the Open state. After import, they keep updating automatically through every later status change.

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

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 Mintsoft, Katana deletes it only if the sales order is still open.

the order sync settings screen for Mintsoft, showing the import-from status option set to Open and the order import settings

Orders from Katana

Katana pushes a sales order to Mintsoft as an outbound order when the sales order reaches the Ready for fulfillment status. From then on, Katana tracks the order's progress in Mintsoft like an imported order.

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

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

Inventory sync

Mintsoft stock levels appear in Katana as read-only external inventory, at the location mapped to each warehouse. The number shown is Mintsoft's on-hand quantity. You can't edit external inventory in Katana, and Katana never sends stock changes to Mintsoft.

Reconciliation compares Katana's in-stock quantity with Mintsoft's on-hand quantity. It runs on a schedule, or you can run it on demand. For any difference, Katana creates a stock adjustment, so your Katana stock reflects the warehouse's physical stock.

the inventory sync settings screen for Mintsoft, showing read-only external inventory per mapped location and the scheduled and on-demand reconciliation options

Inbound shipments

Each Mintsoft inbound shipment becomes one Katana stock transfer.

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

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

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

The stock transfer follows the inbound's status, and received quantities update the transfer. Katana stock transfers move straight from in transit to received. Until the shipment is fully received, partial receipts show as updated expected and received quantities. If the inbound is canceled in Mintsoft, Katana deletes its stock transfer.

the inbound shipments screen showing a Mintsoft inbound shipment as a Katana stock transfer, with its PO number, origin and destination locations, status, and expected and received quantities

What does not sync

  • Product changes and stock changes made in Katana aren't sent to Mintsoft.

  • Changes to a sales order in Katana after it's pushed don't update the Mintsoft order.

  • Canceling a Katana sales order doesn't cancel the pushed Mintsoft order.

  • Returns and RMAs don't sync.

  • Serial numbers aren't tracked. Lot and batch data appears read-only where Mintsoft provides it.

Disconnecting

To disconnect, open the Mintsoft integration from Katana's Integrations page and disconnect it. Syncing stops right away. No more orders, fulfillments, inbound shipments, or stock levels come in from Mintsoft, and Katana stops pushing sales orders to Mintsoft.

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

Did this answer your question?