There are three cases of how Products are imported from BigCommerce to Katana
Products can be imported from Bigcommerce to Katana in the following cases:
You can choose to import all your products from BigCommerce to Katana during the initial integration connection.
If you choose not to import all products, only those products will be imported to Katana during the initial connection that appears on imported Sales Orders.
Later, when new Sales Orders are synced from BigCommerce to Katana, then products on those orders are imported to Katana.
Products cannot be synced from Katana to BigCommerce.
Creating and matching products
Katana matches products imported from BigCommerce to your existing products in Katana.
If a match is found, no new products are created.
If a match is not found, a new product is created in Katana.
Note: Importing "Custom items" on BigCommerce Sales Orders is optional during integration configuration. Any custom items will not be matched between Katana and BigCommerce in the future.
This is how we identify whether a product already exists in Katana:
1. Checking SKU code. SKU code in BigCommerce will be compared to Variant Code in Katana as the primary condition to make the match. SKU codes are case-sensitive. For example, if SKU in BigCommerce is "code-1" and Variant Code in Katana is "CODE-1", these are not considered equal and a new product variant for "code-1" is created in Katana.
2. Checking BigCommerce ID. If you do not use SKU codes for your products or if there is no SKU match, then we use BigCommerce ID to match the product. This match cannot be made the first time you are syncing the product. When a product variant is pulled from BigCommerce to Katana for the first time, a BigCommerce ID (hidden from the user) is added to the product variant in Katana for future identification. If the same product variant is pulled in the future, Katana matches the ID.
If the imported product does not match with any existing products in Katana, then a new product is created in Katana. Katana will recognize whether the new item is a new variant of an existing product or a completely new product.
Product data from BigCommerce is imported to Katana product data fields as follows:
Katana product data
Variant code / SKU
Katana imports only "Physical" / "Variations" for variants.
Default Sales Price
When you have chosen to import all products during the initial connection, the Default sales price for product variants in Katana is determined based on the selected tax rate settings. Read more.
BigCommerce category can not be matched with Katana category. BigCommerce supports multilevel and one-to-many categorization
Unit of measure
In BigCommerce UOM is not determined. Katana will use "pcs" as a default value for UOM.
I make this product
By default all products imported are marked in Katana as "I make this product"
I buy this product
By default all products imported are not marked in Katana as "I buy this product"
Product recipe / BOM
Editing or deleting a product is not synced
Editing data in either BigCommerce or Katana for a product that has already been imported does not reflect in the other system. Any changes to the product name, variant structure, or sales price are not synced.
Deleting products in either Katana or BigCommerce does not delete the product automatically in the other system.
Syncing new products when the integration is already enabled
After you have enabled the BigCommerce x Katana integration, new products created in BigCommerce or Katana are not synced to the other system automatically.
New products are imported from BigCommerce to Katana only if:
The product is included in a Sales Order that is synced from BigCommerce to Katana.
The reconfiguration flow for BigCommerce integration is completed in Katana and you select to import all your products. Read more.
Product import if multiple BigCommerce stores are connected to Katana
If you have connected more than one BigCommerce store to Katana, the integration works exactly in the same way for each store. Product import and matching work identically for all stores.
For example, if the same product (i.e. same SKU code) exists at multiple stores, then products will be matched (i.e. duplicates not created) in Katana if the same product has already been imported from another BigCommerce store.