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

OpenCart Migration: Changes in the Mapping

Since the latest OpenCart version brings more value for our users, we decided to stop supporting the old integration, and we want to migrate our OpenCart users to the latest version. 

What is changing?

Previously, in older versions, to create product variants in OpenCart, you had to:

  • set the attributes based on that you wanted to create variants,

  • create the appropriate rules in the mapping in DataFeedWatch.

This process caused product URL issues, leading to the rejection of the variants from our customers' feeds by the channels. That’s why we decided to find another way to improve this process.

The latest version:

  • Lets you create variants from your OpenCart Dashboard. This way of creating variable products in OpenCart is more intuitive and gives you more control over the variants you want to display. 

  • Allows us to fetch this data automatically. You won’t need to create complex rules in mapping anymore. 

Unfortunately, we can’t automate the migration process, and we need you to go ahead.

How to prepare for migration?


1. Create all the variants of the products in your OpenCart store (if you haven’t done it already).

👉 Check this instruction on How to create variable products in OpenCart to learn how to create a variant step by step.
Please remember that creating new variants may require some time, so we’d recommend doing so at your earliest convenience. 


2. Upgrade Your Shops.

3. Check what's changing in the mapping below and adjust your mapping to the new changes if necessary. 

 

After a due date, we can automatically upgrade your shops, but we can’t adjust your mapping to the changes.

What will happen if you don't adjust your current mapping?
1. Your current mapping and master fields setups may not match the required settings of the updated source version.
2. This mismatch will prevent the creation of product feeds for channels.
3. Consequently, the channel output feed will be either unavailable or defective.

Changes in the mapping:

  1. We’re removing the fields: 

  • size_jewels - we needed this value to generate virtual variants, as we no longer support them. You don’t need to map this field.

  • net_price - We no longer download this field. 

2. We’re replacing the following fields with the others: 

  • image_url (and related image_url_1, image_url_2, etc.) - After migration, each product and variant will have a separate image,  so we’re splitting this field into product_image_url and variant_image_url. So if you have this field in your mapping, we’ll migrate its data automatically, and you don’t need to change anything.