Skip to main content

Skulabs integration setup

Map Skulabs warehouses to locations, then configure order, product, inventory and inbound stock transfer syncs.

A
Written by Argo Ohvril

What syncs between Katana and Skulabs

Data flow between Skulabs and Katana

The table below summarizes how each type of data is handled between Skulabs and Katana.

Data

Direction

Status

Orders

Skulabs → Katana

Available

Products

Skulabs → Katana

Available

Inbound stock transfers

Skulabs → Katana

Available

Inventory sync

Skulabs → Katana

Available

Locations and mapping

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

  • Add to Katana: Creates the matching Katana location for a warehouse automatically.

  • Not mapped: Shown for a warehouse that has never been mapped. It stays this way until you click Add to Katana.

  • Unlink: Pauses a mapped warehouse. Its status then 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 of the Skulabs configuration screen, listing Skulabs warehouses with their status (Not mapped, Unlinked, mapped), the Add to Katana button for an unmapped warehouse, Unlink and Relink actions for mapped warehouses, and the Activate sync button in the header

Products sync

Product mapping creates a required link between each Skulabs product and a Katana item. Products are imported by SKU:

  • If a Katana product already has the same SKU, the two are matched.

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

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

Kits and bundles from Skulabs become Katana products. You can then add a bill of materials (BOM) of components to them in Katana. A kit order line stays a single row on the sales order.

the products mapping settings screen in the Skulabs configuration, showing the SKU matching options: direct 1:1 matching or matching via SKU aliases

SKU aliases

A SKU alias links a Skulabs SKU to a different Katana SKU. Use aliases when the same item has mismatched SKUs in the two systems, so it maps to the correct Katana item instead of creating a duplicate. Upload your SKU alias mapping before the product import.

the products mapping screen with SKU alias mapping, showing the option to upload a SKU alias mapping file and a list pairing Skulabs SKUs with their corresponding Katana SKUs

Orders sync

Orders flow one way only, from Skulabs into Katana. An order imports once it reaches the configured import-from status, which is the "Open" state by default. After that, the order keeps updating automatically through every later status change in Skulabs.

How orders are created in Katana:

  • Each Skulabs order becomes one Katana sales order.

  • Each order line becomes one row on that sales order.

  • The order source is shown as Skulabs.

Fulfillments and tracking

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

Cancellations

A canceled Skulabs order is deleted in Katana only if the Katana sales order is still open.

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

Inventory sync

Skulabs is the source of physical stock truth. Its 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 the Skulabs on-hand quantity only. It runs on a schedule or on demand, and it creates stock adjustments in Katana for any differences. This keeps Katana's stock aligned with what is physically in the warehouse.

Katana never pushes inventory changes to Skulabs.

the inventory sync settings screen in the Skulabs configuration, showing read-only External inventory on-hand quantities per mapped location and the reconciliation options for running on a schedule or on demand

Inbound shipments

Each Skulabs inbound shipment becomes one Katana stock transfer.

  • Number: The PO number when one is present. Otherwise, the inbound ID.

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

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

Stock transfers follow the inbound's status, and received quantities update the transfer. Katana stock transfers have two states: in transit and received. While an inbound is partially received, the transfer shows updated expected and received quantities until it is fully received.

If an inbound is canceled in Skulabs, its stock transfer is deleted in Katana.

the inbound shipments screen showing Skulabs inbound shipments listed as Katana stock transfers with transfer number, origin and destination locations, status (in transit or received), and expected versus received quantities

What does not sync

  • Orders are not sent from Katana to Skulabs. Order sync is one way, from Skulabs to Katana.

  • Products and stock changes are not pushed from Katana to Skulabs.

  • Returns and RMAs.

  • Serial-number tracking.

  • Lot and batch data is not synced as editable data. Where Skulabs exposes it, it is shown read-only.

Disconnecting

To disconnect, go to Katana's Integrations page and open the Skulabs integration. Once you disconnect, data stops syncing between Skulabs and Katana right away.

Records already imported into Katana stay in place, including sales orders, fulfillments, products, stock transfers and stock adjustments.

Did this answer your question?