Skip to main content

Bergen integration setup

Map Bergen warehouses to locations and configure order, product SKU, inventory, and inbound stock transfer syncs.

A
Written by Argo Ohvril

What syncs between Katana and Bergen

Data flow between Bergen and Katana

The table below shows what data moves between Katana and Bergen.

Data

Direction

Status

Orders

Two-way

Available

Products

Bergen → Katana

Available

Inbound stock transfers

Bergen → Katana

Available

Inventory sync

Bergen → Katana

Available

Locations and mapping

After you connect Bergen from Katana's Integrations page and Bergen approves the connection, the configuration screen opens on the Location tab. Each Bergen warehouse maps 1:1 to its own dedicated Katana location. Click Add to Katana to create that location automatically.

  • A warehouse that has never been mapped shows Not mapped until you click Add to Katana.

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

  • To resume syncing, click Relink.

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

the warehouse location mapping panel on the Location tab, listing Bergen warehouses with their mapped Katana locations and statuses (mapped, Unlinked, Not mapped), plus the Add to Katana, Unlink and Relink actions

Products sync

Product mapping creates a required link between each Bergen product and a Katana item. You can match SKUs in one of two ways:

  • Direct 1:1: the Bergen SKU and the Katana SKU are the same.

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

Products are imported by SKU. If a SKU already exists in Katana, the Bergen product is matched to it. If a SKU is unknown, Katana creates the product when it's needed.

Kits and bundles come into Katana as products. Add a BOM of components to them in Katana. A kit order line stays a single row on the sales order.

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

SKU aliases

A SKU alias tells Katana that a Bergen SKU and a different Katana SKU refer to the same item. Use aliases when the SKUs don't match between the two systems, for example when an item was set up with different codes in Bergen and Katana. Upload your SKU alias mapping before you import products.

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

Orders sync

Orders from Bergen to Katana

Bergen 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 Bergen order becomes one Katana sales order, and each line becomes one row. The order source is set to Bergen.

  • Each shipped package becomes a Katana fulfillment with carrier and tracking details. Multi-package shipments create one fulfillment per package. Together, these fulfillments never exceed the ordered quantities.

  • If an order is canceled in Bergen, Katana deletes it 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 Bergen

Katana pushes a sales order to Bergen as an outbound order when the order reaches the Ready for fulfillment status. From then on, its progress in Bergen is tracked back in Katana.

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

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

Inventory sync

Bergen's stock numbers appear in Katana as read-only external inventory at each warehouse's mapped location. The number shown is Bergen's on hand quantity. You can't edit these figures in Katana.

Reconciliation compares Katana's in-stock quantity with Bergen's on-hand quantity only. It runs on a schedule, or you can run it on demand. For any difference, it creates stock adjustments in Katana, so Katana's stock reflects the physical stock at Bergen.

the inventory sync settings screen showing read-only external inventory per mapped location and the scheduled and on-demand reconciliation options

Inbound shipments

Each Bergen inbound shipment becomes one Katana stock transfer. The transfer number is the PO number when there is one. Otherwise, it's 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.

The stock transfer follows the inbound's status, and received quantities update the transfer. Katana stock transfers have only two states: in transit and received. While an inbound is partially received, the transfer shows updated expected and received quantities until it's fully received. If the inbound is canceled, its stock transfer is deleted.

the inbound shipments screen showing Bergen inbound shipments as Katana stock transfers with origin, destination, status, and expected versus received quantities

What does not sync

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

  • Changes made in Katana to a sales order after it has been pushed to Bergen don't update the Bergen order.

  • Canceling a Katana sales order doesn't cancel the pushed Bergen order.

  • Returns and RMAs aren't supported.

  • Serial-number tracking isn't supported. Lot and batch data appears read-only where Bergen provides it.

  • Warehouses that aren't mapped don't sync.

Disconnecting

To disconnect Bergen, open its tile on Katana's Integrations page. When you disconnect, syncing stops immediately. Orders, fulfillments, inventory updates and inbound shipments no longer come in from Bergen, and Katana stops pushing sales orders to Bergen.

Records that were already imported stay in Katana, including sales orders, products, stock transfers and stock adjustments.

Did this answer your question?