What syncs between Katana and MasonHub
The table below summarizes each data flow between Katana and MasonHub.
Data | Direction | Status |
Orders | Two-way | Available |
Products | MasonHub → Katana | Available |
Inbound stock transfers | MasonHub → Katana | Available |
Inventory sync | MasonHub → Katana | Available |
Locations and mapping
To connect, go to Katana's Integrations page and enter the account slug and bearer token from your MasonHub representative. After MasonHub approves the connection, the configuration screen opens on the Location tab.
Each MasonHub 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.
To pause a mapped warehouse, click Unlink. It shows Unlinked until you click Relink to resume it.
Only mapped warehouses sync. Nothing syncs until you click Activate sync in the header.
Products sync
Product mapping creates a required link between each MasonHub product and a Katana item. Choose how SKUs are matched: direct 1:1, or through SKU aliases.
Products are imported by SKU.
A MasonHub SKU that already exists in Katana matches the existing product.
An unknown SKU creates a new Katana product just-in-time.
Kits and bundles become Katana products. Add a BOM of the components in Katana. A kit order line stays a single sales order row.
SKU aliasing
An SKU alias links a MasonHub SKU to a different Katana SKU when the same item uses different SKUs in each system. Use aliases when your MasonHub SKUs don't match your Katana SKUs. Upload your SKU alias mapping before the product import so those SKUs match your existing Katana products.
Orders sync
From MasonHub to Katana
Orders import once they reach the configured import-from status (default: Open). They keep updating automatically through every later status change.
Each MasonHub order becomes one Katana sales order, with one row per order line. The order source is MasonHub.
Each shipped package becomes a Katana fulfillment with carrier and tracking details. Multi-package shipments create one fulfillment per package, so one order can show several fulfillments. Together, these never exceed the ordered quantities.
A canceled MasonHub order is deleted in Katana only if the order is still open.
From Katana to MasonHub
When a Katana sales order reaches the Ready for fulfillment status, Katana pushes it to MasonHub as an outbound order. From then on, the import flow above tracks its progress back in Katana.
Canceling the Katana sales order does not cancel the MasonHub order.
Changes you make in Katana after the push do not update the MasonHub order.
Inventory sync
MasonHub's stock numbers appear in Katana as read-only External inventory at each warehouse's mapped location. The number shown is MasonHub's on-hand quantity. Katana never pushes stock changes to MasonHub.
Reconciliation compares Katana's in-stock quantity with MasonHub's on-hand quantity only. It runs on a schedule or on demand, and creates stock adjustments in Katana for any differences. This keeps the stock Katana uses for planning aligned with what MasonHub physically holds.
Inbound shipments
Each MasonHub inbound shipment becomes one Katana stock transfer. The transfer number is the PO number when one is present; otherwise it is the inbound ID.
Destination: the Katana location mapped 1:1 to the inbound's MasonHub warehouse.
Origin: the location assigned for each destination warehouse. It must be mapped.
Stock transfers follow the inbound's status, and received quantities update the transfer.
Katana stock transfers move from in transit to received. Partial receiving shows as updated expected and received quantities until the shipment is fully received.
A canceled inbound deletes its stock transfer.
What does not sync
Products and stock changes are never pushed from Katana to MasonHub.
Changes to a Katana sales order after it is pushed don't update the MasonHub order.
Canceling a pushed Katana sales order doesn't cancel the MasonHub order.
Returns and RMAs.
Serial-number tracking. Lot and batch data appears read-only where MasonHub exposes it.
Disconnecting
To disconnect, open MasonHub from Katana's Integrations page and disconnect the integration. Syncing stops right away:
Orders, fulfillments, inventory and inbound shipments no longer update.
No new sales orders are pushed to MasonHub.
Records already imported stay in Katana, including sales orders, fulfillments, products, stock transfers and locations.