Skip to main content

CartonCloud integration setup

Map warehouses to locations and set up two-way orders, SKU product import, inventory, and inbound stock transfers.

A
Written by Argo Ohvril

What syncs between Katana and CartonCloud

Data flow between CartonCloud and Katana

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

Data

Direction

Status

Orders

Two-way

Available

Products

CartonCloud → Katana

Available

Inbound stock transfers

CartonCloud → Katana

Available

Inventory sync

CartonCloud → Katana

Available

Locations and mapping

After CartonCloud approves the connection, the configuration screen opens on the Location tab. Each CartonCloud warehouse maps 1:1 to its own dedicated Katana location. Click Add to Katana to create that location automatically.

  • Not mapped: The warehouse has never been mapped. It stays this way until you click Add to Katana.

  • Unlink: Pauses a mapped warehouse. Its status 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, listing CartonCloud warehouses with their mapped Katana locations, status labels Not mapped and Unlinked, and the Add to Katana, Unlink and Relink actions

Products sync

Product mapping creates a required link between each CartonCloud product and a Katana item. You choose how SKUs are matched: direct 1:1 or through SKU aliases.

  • Products are imported by SKU.

  • CartonCloud products whose SKU already exists in Katana are matched to that Katana product.

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

Kits and bundles become Katana products. Add a bill of materials (BOM) of their components in Katana. A kit on an order stays a single sales order row.

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

SKU aliases

A SKU alias links a CartonCloud SKU to a different Katana SKU. Use one when the same item carries different SKUs in the two systems, for example a warehouse-specific code. Upload your SKU alias mapping before importing products, so mismatched SKUs match existing Katana items instead of creating new ones.

the products mapping screen with SKU alias mapping, showing CartonCloud SKUs paired with different Katana SKUs and the alias upload option

Orders sync

From CartonCloud to Katana

  • Orders import once they reach the configured import-from status (default: Open).

  • After import, they keep updating automatically through every later status change.

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

  • Each shipped package becomes a Katana fulfillment with carrier and tracking details.

  • Multi-package shipments create one fulfillment per package. Together, these fulfillments never exceed the ordered quantities.

  • When an order is canceled in CartonCloud, it is deleted in Katana only if the Katana sales 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 CartonCloud

  • A Katana sales order is pushed to CartonCloud as an outbound order when it reaches the Ready for fulfillment status.

  • From then on, the import flow above tracks the order's progress back in Katana.

  • Canceling the Katana sales order does not cancel the CartonCloud order.

  • Changes made in Katana after the push do not update the CartonCloud order.

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

Inventory sync

CartonCloud's stock numbers appear in Katana as read-only external inventory at each warehouse's mapped location. The number shown is the on-hand quantity.

Reconciliation compares Katana's in-stock quantity against CartonCloud'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 works with in line with what is physically in the warehouse.

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

Inbound shipments

Each CartonCloud inbound shipment becomes one Katana stock transfer. The transfer number is the PO number when one exists; 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.

The stock transfer follows the inbound's status, and received quantities update it. Katana stock transfers move from in transit to received. Partial receiving appears as updated expected and received quantities until the shipment is fully received. A canceled inbound deletes its stock transfer.

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

What does not sync

  • Product or stock changes from Katana to CartonCloud.

  • Changes made in Katana to a sales order after it has been pushed to CartonCloud.

  • Canceling a pushed order: canceling in Katana does not cancel it in CartonCloud.

  • Returns and RMAs.

  • Serial-number tracking. Lot and batch data is shown read-only where CartonCloud provides it.

Disconnecting

Go to Katana's Integrations page, open the CartonCloud integration and disconnect it. Syncing stops immediately:

  • No new orders, fulfillments, inbound shipments or inventory updates are imported.

  • No sales orders are pushed to CartonCloud.

Records already brought into Katana, such as sales orders, fulfillments, stock transfers, products and locations, remain in Katana.

Did this answer your question?