Skip to main content

Quickbox (LogicPod) integration setup

Map warehouses to locations, then configure two-way orders, SKU-matched products, inventory, and inbound transfers.

A
Written by Argo Ohvril

What syncs between Katana and Quickbox (LogicPod)

Data flow between Quickbox (LogicPod) and Katana

The table below summarizes how each type of data moves between Katana and Quickbox (LogicPod).

Data

Direction

Status

Orders

Two-way

Available

Products

Quickbox (LogicPod) → Katana

Available

Inbound stock transfers

Quickbox (LogicPod) → Katana

Available

Inventory sync

Quickbox (LogicPod) → Katana

Available

Locations and mapping

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

  • Add to Katana creates that location for a warehouse.

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

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

  • To resume a paused warehouse, click Relink.

Only mapped warehouses sync.

the warehouse location mapping panel on the Location tab of the Quickbox (LogicPod) configuration screen, listing Quickbox warehouses with statuses Not mapped, Unlinked and mapped, and the Add to Katana, Unlink and Relink actions

Products sync

Product mapping creates a required link between each Quickbox (LogicPod) product and a Katana item.

  • Matching: Products are imported by SKU. You choose whether SKUs match directly 1:1 or through SKU aliases.

  • Existing SKUs: SKUs that already exist in Katana match the existing products.

  • Unknown SKUs: Katana creates these products just in time.

  • Kits and bundles: These become Katana products. Add a BOM of components to them in Katana. A kit order line stays a single sales order row.

the products mapping settings screen for Quickbox (LogicPod), showing the choice between direct 1:1 SKU matching and matching via SKU aliases

SKU aliases

A SKU alias links a Quickbox (LogicPod) SKU to a different Katana SKU. Use one when the same product has different SKUs in the two systems. Upload your SKU alias mapping before the product import so that mismatched SKUs match existing Katana products.

the products mapping screen with SKU alias mapping, showing Quickbox (LogicPod) SKUs paired with different Katana SKUs and the option to upload an alias mapping

Orders sync

From Quickbox (LogicPod) to Katana

  • Orders import once they reach the configured import-from status. The default is the Open state.

  • Imported orders keep updating automatically through every later status change.

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

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

  • If an order is canceled in Quickbox (LogicPod), it is deleted in Katana only if the order is still open.

the order sync settings screen with the import and status options, showing the import-from status selector set to Open

From Katana to Quickbox (LogicPod)

When a Katana sales order reaches the Ready for fulfillment status, it is pushed to Quickbox (LogicPod) as an outbound order. From then on, its progress is tracked back in Katana.

  • Canceling the Katana sales order does not cancel the Quickbox (LogicPod) order.

  • Changes made in Katana after the push do not update the Quickbox (LogicPod) order.

the order push settings screen for Quickbox (LogicPod), showing that sales orders are pushed when they reach the Ready for fulfillment status

Inventory sync

Quickbox (LogicPod) stock levels appear in Katana as read-only External inventory at each warehouse's mapped location. On hand is the number shown.

Reconciliation compares Katana's in-stock quantity with the Quickbox (LogicPod) on-hand quantity. It runs on a schedule or on demand, and creates stock adjustments for any differences. Katana never pushes inventory changes to Quickbox (LogicPod).

the inventory sync settings screen for Quickbox (LogicPod), showing read-only External inventory on hand per mapped location and the scheduled and on-demand reconciliation options

Inbound shipments

Each Quickbox (LogicPod) inbound shipment becomes one Katana stock transfer. The transfer number is the PO number when there is one; otherwise it is the inbound ID.

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

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

  • Status: The stock transfer follows the inbound's status. Received quantities update the transfer.

  • Partial receiving: Katana stock transfers move from in transit to received in one step. Partial receipts show as updated expected and received quantities until everything is received.

  • Cancellation: A canceled inbound deletes its stock transfer.

the inbound shipments screen for Quickbox (LogicPod), showing inbound shipments as Katana stock transfers with PO number, origin and destination locations, status, and expected versus received quantities

What does not sync

  • Products and stock changes are not pushed from Katana to Quickbox (LogicPod).

  • Changes made in Katana after an order is pushed do not update the Quickbox (LogicPod) order.

  • Canceling a Katana sales order does not cancel the pushed Quickbox (LogicPod) order.

  • Returns and RMAs are not supported.

  • Serial-number tracking is not supported. Lot and batch data is shown read-only where Quickbox (LogicPod) provides it.

Disconnecting

To disconnect, open the Quickbox (LogicPod) integration from Katana's Integrations page. Once disconnected, orders, fulfillments, inventory, products and inbound shipments stop syncing, and Katana no longer pushes sales orders to Quickbox (LogicPod). Records already imported into Katana, such as sales orders, fulfillments, products and stock transfers, stay in Katana.

Did this answer your question?