It is important to always apply the same methodology to create articles, apply a reference to them, an EAN code, etc. Therefore, your catalog will be structured for your internal and external needs, so marketplaces in this case.
In all cases, the reference field is used as SKU for the marketplace. That means that the Reference field is your unique internal identifier for CDiscount, commonly called SKU.
This field will be used to identify your offers and import orders. If the Reference field is not present or misinformed, it will not work correctly. If the Reference field is duplicated, meaning that is used twice in your catalog, it will not work properly either.
Case 1 – Product with combinations:
On the Information tab, the only field required is the reference. The reference will match the SKU on CDiscount:
On the Combinations tab, the required fields are the reference (SKU) which must be unique and the EAN code or UPC:
Case 2 – Product without combinations:
Known issue:
The Prestashop combination generator generates double references, it generates “Duplicates”. You get therefore duplicate references in your database.
This issue will need to be corrected, and references modified so that they are unique, in all cases a unique reference field for a product will be needed, a combination being a product.
Nota Bene:
You will retain then that the “Reference” field of your product sheet Prestashop matches the SKU field on CDiscount, this point is key. Using a single SKU guaranties you a listing with unique products.
