Skip to content
  • There are no suggestions because the search field is empty.

Using the Omnivore SKU strategy function

Troubleshoot Use the Omnivore SKU strategy function

Internal only.

Additional Recommended Reading including Marketplaces where we can apply the SKU Strategy Function.  See this article:

https://support.omnivore.com.au/the-marketplace-sku-strategy

Also see this trello from July 2025 https://trello.com/c/0LoZeaNi

Go to Settings - Marketplace Name - General - scroll down - Admin Only Settings



This internal FAQ covers how to use the following Omnivore feature to link and map Store Products to Existing Marketplace Listings (in some but NOT all cases).  

Using this function changes the product SKU that we send to the marketplace, so use wisely as it could do damage.


Scenarios


  1. If a seller is re-platforming and changing eCommerce Systems which means they will have different SKU's
  2. If a seller is onboarding and has existing listings on a marketplace
  3. When the marketplace is compatible with accepting this setting
  4. When the integration team have completed an analysis of the data to check the likelihood of success
  5. When the retailer agrees to use this strategy and is aware it is not always 100% effective

When to make this change ...


(Assuming the seller has a newish Omnivore install)

  1. After the initial product import while they are in setup mode.
  2. After you have assessed and tested the change using a single product
  3. After you have assessed and tested any fall out that may affect other marketplaces (when they are multi marketplace) 
  4. After you have sought a second opinion, particularly if it is not straight forward.
  5. After they have category mapped their products in Omnivore
  6. ...
  7. ...

If unsure at any stage bring to scrum or your team meeting for a second opinion.


SKU Strategy On New Installs.


As of June/July 2025 for BC and Shopify sellers who are new AND with new products, by default the SKU applied in Omnivore will be the SKU in the eCommerce Store (not the product ID).  So the Omnivore SKU Strategy will be set to OMNIVORE_VARIANT_MPN.

More to note here:  Please read the trello above in this FAQ.   From Trello:

For Shopify:

If we have more than 250 active products in Omnivore, we use what we have, otherwise we do a query. The later covers the scenario when they just installed the app and we don’t have products in Omnivore yet.

If 90% or more products have sku values, we chose the OMNIVORE_VARIANT_MPN marketplace sku strategy.

For Bigcommerce:

If we have more than 250 active products in Omnivore, we use what we have, otherwise we use the default strategy. We don’t have a query for Bigcommerce, so if they just installed we can’t determine if they have skus or not.

If 90% or more products in Omnivore have sku values, we chose the OMNIVORE_VARIANT_MPN marketplace sku strategy.

From a troubleshooting perspective you may see issues with new sellers who have just installed the app and their products won't import or create properly because they don't have SKU's in their eComm Store.  Assess the note above and if needed swap the SKU Strategy back to OMNIVORE_DEFAULT.    Again, get a second opinion on how to proceed.


Marketplaces using SKU Strategy


Tables can't be imported directly. Please insert an image of your table which can be found here.

Tables can't be imported directly. Please insert an image of your table which can be found here.

MARKETPLACE NAM E Turned ON RELEVANT DETAILS

Yes

Note this trello also:

https://trello.com/c/mmrYVi4r