Skip to main content

Bigblue integration setup

Map Bigblue warehouses to locations, then configure order, product, SKU alias, inventory, and inbound transfer syncs.

A
Written by Argo Ohvril

What syncs between Katana and Bigblue

Data flow between Bigblue and Katana

The table below lists each type of data and how it moves between Katana and Bigblue.

Data

Direction

Status

Orders

Bigblue → Katana

Available

Products

Bigblue → Katana

Available

Inbound stock transfers

Bigblue → Katana

Available

Inventory sync

Bigblue → Katana

Available

Locations and mapping

Connect Bigblue from Katana's Integrations page by entering the API key you created in the Bigblue web app. The configuration screen then opens on the Location tab. Nothing syncs until you click Activate sync in the header.

  • Each Bigblue warehouse maps to its own Katana location. Add to Katana creates that location for you.

  • To pause a mapped warehouse, click Unlink. Its status then shows Unlinked. Click Relink to resume it.

  • A warehouse that has never been mapped shows Not mapped.

  • Only mapped warehouses sync.

the warehouse location mapping panel on the Location tab of the Bigblue configuration screen in Katana, listing Bigblue warehouses with their statuses (Not mapped, Unlinked, mapped) and the Add to Katana, Unlink and Relink actions

Products sync

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

  • If a Katana product already has the SKU, it is matched to the Bigblue product.

  • If the SKU is unknown in Katana, a new product is created when it is first needed.

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

the products mapping settings screen of the Bigblue integration in Katana, showing the SKU matching choice between direct 1:1 and via SKU aliases

Kits and bundles become Katana products. Add a BOM of their components in Katana. A kit order line stays a single sales order row.

SKU aliases

A SKU alias links a Bigblue SKU to a different Katana SKU. Use aliases when the same product has different SKUs in Bigblue and Katana. Upload your SKU alias mapping before you import products.

the products mapping screen of the Bigblue integration in Katana with the SKU alias mapping option selected, showing Bigblue SKUs paired with different Katana SKUs and the upload control for the alias mapping

Orders sync

Orders flow one way, from Bigblue into Katana.

  • An order imports once it reaches the configured import-from status. By default, this is the Open state.

  • After import, the Katana sales order updates automatically with every later status change in Bigblue.

  • Each Bigblue order becomes one Katana sales order. Each order line becomes one row. The order source is Bigblue.

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 Bigblue order is deleted in Katana only if the Katana sales order is still open. Canceling a sales order in Katana does not cancel the order in Bigblue.

the order sync settings screen of the Bigblue integration in Katana, showing the import-from status option set to Open

Inventory sync

Bigblue's stock numbers appear in Katana as read-only External inventory at each warehouse's mapped location. Katana shows Bigblue's On hand quantity.

Reconciliation compares Katana's in-stock quantity with Bigblue's on-hand quantity. It runs on a schedule, or you can run it on demand. For any difference, Katana creates a stock adjustment, so your Katana stock levels match the physical stock in Bigblue's warehouses.

the inventory sync settings screen of the Bigblue integration in Katana, showing read-only External inventory per mapped location and the reconciliation schedule with a run-now option

Inbound shipments

Each Bigblue inbound shipment becomes one Katana stock transfer. The transfer number is the PO number if there is one; otherwise, it is the inbound ID.

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

  • Origin: the location you assign for each destination warehouse. This location must be mapped.

The stock transfer follows the inbound's status, and received quantities update the transfer. If an inbound is canceled, its stock transfer is deleted.

Katana stock transfers have only two states: in transit and received. During partial receiving, the expected and received quantities update until the shipment is fully received.

the inbound shipments screen of the Bigblue integration in Katana, listing Bigblue inbounds as stock transfers with PO or inbound number, origin and destination locations, status, and expected versus received quantities

What does not sync

  • Orders from Katana to Bigblue. Orders flow one way only, from Bigblue to Katana.

  • Product or stock changes from Katana to Bigblue.

  • Returns and RMAs.

  • Serial-number tracking. Lot and batch data appears read-only where Bigblue provides it.

Disconnecting

To disconnect, open the Bigblue integration from Katana's Integrations page. Once you disconnect, syncing with Bigblue stops immediately.

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

Did this answer your question?