Skip to main content

Amphora integration setup

Map warehouses, then set up two-way order sync, SKU-based product import, read-only inventory and inbound transfers.

A
Written by Argo Ohvril

What syncs between Katana and Amphora

Data flow between Amphora and Katana

The table below summarizes how data moves between Katana and Amphora.

Data

Direction

Status

Orders

Two-way

Available

Products

Amphora → Katana

Available

Inbound stock transfers

Amphora → Katana

Available

Inventory sync

Amphora → Katana

Available

Locations and mapping

After the connection is approved, the configuration screen opens on the Location tab. Each Amphora warehouse maps 1:1 to its own dedicated Katana location.

  • Not mapped means the warehouse has never been mapped. Click Add to Katana to create its Katana location automatically.

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

  • To resume syncing, click Relink.

Only mapped warehouses sync. Nothing syncs at all until you click Activate sync in the header.

the warehouse location mapping panel on the Location tab of the Amphora configuration screen, listing Amphora warehouses each paired with a dedicated Katana location, with one warehouse showing Not mapped and an Add to Katana button, one mapped warehouse with an Unlink action, and one warehouse showing Unlinked status with a Relink button

Products sync

Product mapping creates a required link between each Amphora product and a Katana item. Katana imports products by SKU:

  • If a SKU matches an existing Katana product, Katana links to that product.

  • If a SKU is unknown, Katana creates the product just-in-time.

You choose how SKUs are matched: direct 1:1, or through SKU aliases.

Kits and bundles from Amphora become Katana products. You can then 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 Amphora in Katana, showing the SKU matching choice between direct 1:1 matching and matching via SKU aliases

SKU aliasing

A SKU alias links an Amphora SKU to a different Katana SKU. Use an alias when the same item has different SKUs in the two systems. Upload your SKU alias mapping before product import so mismatched SKUs link to the correct Katana products instead of creating new ones.

the products mapping screen with SKU alias mapping selected, showing an uploaded alias list pairing Amphora SKUs with differing Katana SKUs

Orders sync

Orders from Amphora

Amphora orders import once they reach the configured import-from status (default: Open). After import, they keep updating automatically through every later status change.

Each Amphora order becomes one Katana sales order, with one row per order line. The order source is shown as Amphora.

Each shipped package becomes a Katana fulfillment with its carrier and tracking number. A multi-package shipment creates one fulfillment per package, so a single order can show several fulfillments. Together, these fulfillments never exceed the ordered quantities.

If an order is canceled in Amphora, Katana deletes it only if the order is still open in Katana.

the order sync settings screen for Amphora in Katana, showing the import-from status selector set to Open and the order import options

Orders from Katana to Amphora

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

Canceling the Katana sales order does not cancel the Amphora order. Changes you make in Katana after the push do not update the Amphora order.

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

Inventory sync

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

Reconciliation compares Katana's in-stock quantity against Amphora's on-hand quantity only. It runs on a schedule or on demand and creates stock adjustments for any differences, keeping Katana's stock aligned with Amphora's physical stock.

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

Inbound shipments

Each Amphora 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. This location receives the stock.

  • 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 directly from in transit to received. Partial receiving therefore shows as updated expected and received quantities until the shipment is fully received.

If an inbound is canceled in Amphora, Katana deletes its stock transfer.

the inbound shipments screen in Katana showing Amphora inbound shipments as stock transfers with PO or inbound ID numbers, origin and destination locations, in transit or received status, and expected versus received quantities

What does not sync

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

  • Katana-side changes to an order after it has been pushed to Amphora are not sent.

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

  • Returns and RMAs are not supported.

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

Disconnecting

To disconnect, open the Amphora integration from Katana's Integrations page. Once you disconnect, syncing stops: no new orders, fulfillments, inbound shipments, or inventory updates come in, and no sales orders are pushed to Amphora.

Records already brought into Katana remain, including sales orders, fulfillments, products, stock transfers, and stock adjustments.

Did this answer your question?