Skip to main content

Camelot integration setup

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

A
Written by Argo Ohvril

What syncs between Katana and Camelot

Data flow between Camelot and Katana

The table below summarizes the data flows for this integration.

Data

Direction

Status

Orders

Two-way

Available

Products

Camelot → Katana

Available

Inbound stock transfers

Camelot → Katana

Available

Inventory sync

Camelot → Katana

Available

Locations and mapping

After Camelot approves the connection, the configuration screen opens on the Location tab. Each Camelot warehouse is mapped 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. Use Add to Katana to create its location.

  • Unlink: pauses syncing for a mapped warehouse. Its status shows Unlinked.

  • Relink: resumes syncing for an unlinked warehouse.

Only mapped warehouses sync.

the warehouse location mapping panel on the Location tab of the Camelot configuration screen, listing Camelot 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 the required link between each Camelot product and a Katana item. Products are matched by SKU, and you choose how SKUs are matched:

  • Direct 1:1: the SKU is the same in both systems.

  • SKU aliases: a Camelot SKU is linked to a different Katana SKU.

When products are imported, existing Katana products with a matching SKU are linked. Katana creates new products automatically for SKUs it doesn't recognize.

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

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

SKU aliasing

An SKU alias links a Camelot SKU to a Katana SKU that differs from it. Use aliases when the same item is identified differently in Camelot and in Katana. Upload your SKU alias mapping before importing products, so mismatched SKUs link to the correct Katana items instead of creating new products.

the products mapping screen with SKU alias mapping, showing a Camelot SKU column paired with a different Katana SKU column and the option to upload an alias mapping file

Orders sync

Orders from Camelot to Katana

Orders import 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 Camelot order becomes one Katana sales order, with one row per order line.

  • The order source is shown as Camelot.

  • Each shipped package becomes a Katana fulfillment with the 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 Camelot, 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

Orders from Katana to Camelot

Katana pushes a sales order to Camelot as an outbound order when it reaches the Ready for fulfillment status. From then on, the import flow above tracks its progress back in Katana.

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

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

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

Inventory sync

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

Reconciliation compares Katana's in-stock quantity against Camelot's on-hand quantity only. It runs on a schedule or on demand. Where the two differ, it creates stock adjustments in Katana so your Katana stock matches the warehouse.

the inventory sync settings screen for Camelot, showing read-only External inventory on-hand quantities per mapped location and the scheduled and on-demand reconciliation options

Inbound shipments

Each Camelot 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 to the inbound's warehouse.

  • Origin: the location assigned for each destination warehouse. It must be mapped.

Stock transfers follow the inbound status, and received quantities update the transfer. A canceled inbound deletes its stock transfer.

Katana stock transfers have two states: in transit and received. Partial receipts show as updated expected and received quantities until the shipment is fully received.

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

What does not sync

  • Products and stock changes are not sent from Katana to Camelot.

  • Changes to a Katana sales order after it has been pushed do not update the Camelot order.

  • Canceling a Katana sales order does not cancel the Camelot order.

  • Returns and RMAs are not supported.

  • Serial numbers are not tracked. Lot and batch data is shown read-only where Camelot provides it.

Disconnecting

To disconnect, open the Camelot integration from Katana's Integrations page and disconnect it. Syncing stops immediately: Katana no longer imports orders, fulfillments, inbound shipments or inventory from Camelot, and no longer pushes sales orders to Camelot.

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

Related Articles
Did this answer your question?