Skip to main content

Longtail integration setup

Set up warehouse-to-location mapping, product import with direct or aliased SKUs, and on-hand inventory reconciliation.

A
Written by Argo Ohvril

What syncs between Katana and Longtail

Data flow between Longtail and Katana

The table below shows each data type and how it flows between Longtail and Katana.

Data

Direction

Status

Products

Longtail → Katana

Available

Inventory sync

Longtail → Katana

Available

Locations and mapping

After Longtail approves the connection, the configuration screen opens on the Location tab. Each Longtail warehouse maps to its own dedicated Katana location. Click Add to Katana to create that location automatically. Until then, the warehouse shows as Not mapped.

To pause a mapped warehouse, click Unlink. Its status then shows Unlinked. Click Relink to resume syncing. Only mapped warehouses sync.

Nothing syncs until you click Activate sync in the header.

the warehouse location mapping panel on the Location tab of the Longtail configuration screen, listing Longtail warehouses with statuses Mapped, Unlinked and Not mapped, 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 Longtail product and a Katana item. First, choose how SKUs are matched:

  • Direct 1:1: each Longtail SKU matches the same Katana SKU.

  • SKU aliases: a Longtail SKU matches a different Katana SKU.

Products are imported by SKU. Longtail SKUs that already exist in Katana match the existing products. Unknown SKUs create new Katana products as they are needed.

Kits and bundles also become Katana products. To define what a kit contains, add a bill of materials (BOM) of its components in Katana.

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

SKU aliasing

A SKU alias links a Longtail SKU to a different Katana SKU. Use aliases when the same item has different SKUs in Longtail and Katana, so it maps to your existing Katana item instead of creating a duplicate. Upload your SKU alias mapping before the product import runs.

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

Inventory sync

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

Katana reconciles its in-stock quantity against Longtail's on-hand quantity, either on a schedule or on demand. Any difference is recorded as a stock adjustment, so your Katana stock matches what Longtail physically holds.

the inventory sync settings screen for Longtail, showing the reconciliation schedule, the on-demand reconcile option, and read-only External inventory on-hand quantities per mapped location

What does not sync

  • Orders: Longtail orders are not imported, and Katana sales orders are not sent to Longtail.

  • Fulfillments, carrier details and tracking numbers.

  • Inbound shipments and stock transfers.

  • Product or stock changes from Katana to Longtail. Katana never sends these to Longtail.

  • Returns and RMAs.

  • Serial-number tracking.

Disconnecting

Go to Katana's Integrations page, open the Longtail integration and disconnect it. Product and inventory syncing from Longtail stops right away. Records Katana has already imported, such as products and stock adjustments, stay in Katana.

Did this answer your question?