Skip to main content

WMS Sandbox integration setup

Map warehouses to locations, set up two-way orders, SKU-based products, read-only inventory, and inbound transfers.

A
Written by Argo Ohvril

What syncs between Katana and WMS Sandbox

Data flow between WMS Sandbox and Katana

The table below summarizes each data type and the direction it moves between the two systems.

Data

Direction

Status

Orders

Two-way

Available

Products

WMS Sandbox → Katana

Available

Inbound stock transfers

WMS Sandbox → Katana

Available

Inventory sync

WMS Sandbox → Katana

Available

Locations and mapping

After WMS Sandbox approves the connection, the configuration screen opens on the Location tab. Each WMS Sandbox 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 add it.

To pause a mapped warehouse, click Unlink. Its status then shows Unlinked. Click Relink to resume it. Only mapped warehouses sync. Nothing syncs until you click Activate sync in the header.

the warehouse location mapping panel on the Location tab, listing WMS Sandbox warehouses with statuses Mapped, Not mapped and Unlinked, the Add to Katana, Unlink and Relink buttons, and the Activate sync button in the header

Products sync

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

  • SKUs that already exist in Katana match the existing product.

  • Unknown SKUs create new Katana products just-in-time.

You choose how SKUs are matched, either direct 1:1 or through SKU aliases. 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.

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

SKU aliasing

An SKU alias links a WMS Sandbox SKU to a different Katana SKU. Use aliases when the same item carries different SKUs in the two systems, so it matches the correct Katana product instead of creating a duplicate. Upload your SKU alias mapping before importing products.

the products mapping screen with SKU alias mapping, showing WMS Sandbox SKUs paired with different Katana SKUs and the option to upload an alias mapping file

Orders sync

Orders from WMS Sandbox

Orders import once they reach the configured import-from status, which is the Open state by default. After import, they keep updating automatically through every later status change.

  • Each order becomes one Katana sales order, with one row per line.

  • The order source is shown as WMS Sandbox.

  • Each shipped package becomes a Katana fulfillment with carrier and tracking. Multi-package shipments create one fulfillment per package. Together these fulfillments never exceed the ordered quantities.

  • An order canceled in WMS Sandbox is deleted in Katana only if the order is still open.

the order sync settings screen with the import-from status option set to Open and the order status update options

Orders from Katana

A Katana sales order is pushed to WMS Sandbox as an outbound order when it reaches the Ready for fulfillment status. From then on, its progress is tracked back in Katana like an imported order. Changes made in Katana after the push do not update the WMS Sandbox order. Canceling the Katana sales order does not cancel the WMS Sandbox order.

the order push settings screen showing that Katana sales orders are sent to WMS Sandbox when they reach Ready for fulfillment

Inventory sync

Stock numbers from WMS Sandbox appear in Katana as read-only External inventory at each warehouse's mapped location. The number shown is On hand.

Reconciliation compares Katana's in-stock quantity against the WMS Sandbox on-hand quantity only. It runs on a schedule or on demand, and creates stock adjustments for any differences. This keeps Katana's stock aligned with the warehouse's physical stock.

the inventory sync settings screen showing read-only External inventory On hand quantities per mapped location and the reconciliation schedule and run-now options

Inbound shipments

Each WMS Sandbox inbound shipment becomes one Katana stock transfer. The transfer is numbered with the PO number when one is present, otherwise with the inbound ID.

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

  • Origin: the location you assign for each destination warehouse. This must be mapped.

The stock transfer follows the inbound status, and received quantities update the transfer. Katana transfers move only from in transit to received. Partial receipts therefore show as updated expected and received quantities until the shipment is fully received. A canceled inbound deletes its stock transfer.

the inbound shipments screen listing WMS Sandbox inbounds as Katana stock transfers with origin, destination location, status, and expected versus received quantities

What does not sync

  • Products and stock changes are never pushed from Katana to WMS Sandbox.

  • Changes made in Katana to an order after it has been pushed are not sent to WMS Sandbox.

  • Canceling a Katana sales order does not cancel the WMS Sandbox order.

  • Returns and RMAs are not supported.

  • Serial numbers are not supported. Lot/batch data is shown read-only where WMS Sandbox provides it.

Disconnecting

To disconnect, open the WMS Sandbox integration from Katana's Integrations page. Disconnecting stops all syncing immediately, including order imports, order pushes, fulfillment and tracking updates, inventory updates, and inbound updates. Records that have already been ingested stay in Katana, including sales orders, fulfillments, products, stock transfers, and stock adjustments.

Did this answer your question?