Data used from BigCommerce in Omnivore
Practical guide to data used from BigCommerce in Omnivore
This article provides a table to help you better understand the data used from BigCommerce in Omnivore and why it's important.
Data used from BigCommerce in Omnivore
This table explains the data between Omnivore and BigCommerce:
| Omnivore Data | BigCommerce Data | Marketplace Data |
| SKU | This is the BigCommerce product ID - a number generated by BigCommerce when you create a product | SKU |
| Retailer Reference | This is a unique value constructed by eBay Link from Bigcommerce data to provide a unique value for each product variant in case of multi variant products | |
| MPN | This is the value of the MPN that has been entered into the optional Manufacturer Part Number field within a product in BigCommerce. If there is no data in the MPN field in BigCommerce eBay Link will use the SKU value from BigCommerce | MPN field in marketplace |
| UPC EAN ISBN | This can be entered into the optional Product UPC/EAN field within a product in BigCommerce | UPC field in Marketplace |
Important Points on Data with Omnivore and BigCommerce
- Product Groups must be created using the SKU shown in Omnivore, not the SKU entered in BigCommerce.
- The SKU field in BigCommerce is optional and is not required for products, so it cannot always be relied upon as a consistent source of SKU data.
- Marketplace listings require a SKU. Because BigCommerce does not always provide a value in the SKU field, our app generates an Omnivore SKU using the BigCommerce Product ID.
- The Omnivore SKU is system-generated and cannot be edited.
- When creating Product Groups, Promotions, Bundles, or other SKU-based configurations, you must use the Omnivore SKU (Bigcommerce Product ID) rather than the BigCommerce SKU.