2015-05-05
Rating 0 stars - 0 votes

PrestaShop Combination Import Pitfalls and Ways to Overcome Them

PrestaShop import of combinations prevails over manual combination input or update, since shows itself as more efficient and time-saving method of data handling. One might have large database with abundance of products listings what require regular updates or replenishment. Nothing but accurate data upload maximizes combination management and helps arrange product variants in a worthwhile manner.


Although, importing files to PrestaShop with Store Manager, you can find out that something goes wrong and seems not to be accurate, as it has been mentioned above. The reason is you have improperly configured import settings and should look through them one more time. Store Manager for PrestaShop guarantees flawless combination import if you organize the process in a suitable manner, since each What inconveniences may happen, what are their reasons and how to avoid them is outlined below in this publication.


First of all it must be accentuated that the first thing to be considered when it comes to PrestaShop import of combinations is how data are arranged in the file. Details, you include into the spreadsheet, depend on whether you are uploading new products with combinations, adding combinations to new products or updating variables. File sample and import instructions can be found in the article – tips-tricks/tips-on-how-to-import-prestashop-attributes

Product Variants are Not Created Though Import Ran Successfully

Oftentimes merchants are nonplused, since after data upload completes successfully, no variations are created. There are several reasons behind, you should get acquainted with to bypass “combination gaps” and get variants created after import.


1) No attribute group created in Store Manager

You should differentiate “attribute group” and “attribute” notions. First you are creating attribute group, which is like container for attribute values, e.g “material” is an attribute group, when “silk”, “cotton” and “wool” are its values.

Groups can not be created via import, you can only create values and assign them to corresponding group. If product combinations, you are uploading to PrestaShop, base on attribute groups that have not been used yet, you are obliged to create these groups in Store->Attributes&Groups.

2) “Create new attributes” unchecked

As it has been mentioned above, new attribute values are being created in the course of PrestaShop import on condition that attribute group exists. If combinations consists of new attribute value, you should check “Create new attributes” box on Import Options step of the import wizard. As for example, “material” attribute group has “silk”, “cotton” and “wool” values assigned only. You are starting to sell another product, made of denim, but there is no “denim” attribute value. To get the combination created and the value ascribed to “material” attribute group, do not forget to enable “Create new attribute” option.


3) Incorrect import method

Configuring the import settings, you have to select suitable identifier or action on “Assign .csv Column to Database Fields” step for product and combinations. Depending on whether you are updating existing combinations or creating new ones, you are choosing one of provided identifiers. There is also “Skip combination import” option. If you check radio button for it, combinations will be ignored by the application and no variants will be created respectively.


4) No attribute values in the file

Product variation is a unique combination of two or more attribute values. For Store Manager to create this or that combination, you should specify the values in each row for each attribute group. If you leave the fields empty, combination won’t be created.


5) Combination ID as identifier

Oftentimes merchants are uploading new combinations having their IDs in the file and selecting IDs as combination identifier. The upshot of matter is that no combinations are added. The reason is, IDs are using for updates only, with Store Manager for PrestaShop you can’t force ID creation and, accordingly PrestaShop import of combinations does not bring expected outcomes. To get combinations created, you must have their references in the file and select combination reference as identifier.



Product Becomes “Out of Stock” after Combinations Are Added or Updated

Another issue, store owners are bumping against, is that product quantity is ceased to 0 and it automatically acquires “Out of Stock” status.



The matter is in PrestaShop product quantity depends on combination quantity, in the other words it is the total of combination quantities. Consequently, if quantity of each combination is 0, product quantity will also be 0.

To bypass this, indicate quantity for each variation in corresponding column of the .csv file you append data from.



Existing Combinations Disappear After New Ones Were Added to Products

There might occur the necessity to add new combinations to merchandise that already have combinations, for example, you sold skirts that differed in three colors and now you need them to differ in five colors or you want to offer extra material to your customers. PrestaShop import from the file being fulfilled, you find out that new variations appeared but existing variations have been removed.


Most likely, you have chosen “Regenerate product combination” action on “Assign .csv Columns to Database Fields” step. As a result combinations were overwritten – current variants were substituted with new ones, whereas the aim was to add new without removing existing ones.


To add new PrestaShop combinations and leave previously added you should:

  1. include combination reference to the feed you import from
  2. select combination reference as combination identifier at “Assign .csv Columns to Database Fields” step and map the fields correctly
  3. make sure you have selected suitable product identifier

New Products Instead of Combinations Were Created

Having configured import setting improperly, you can create abundance of new product records instead of combinations created after data appending to PrestaShop. If you:

  • did not assign file columns including attribute group values to database fields
  • linked combination reference to product reference database field
  • provided product name in each row (for combinations)

As it has been already indicated, you must have identifier for both – combination and product, include attribute combinations and details to the file and correctly link file columns to database fields.


Image Does Not Change When Certain Combination Is Selected

Usually you want to ascribe different images to product selections, but reveal that they do not change when this or that variation is selected at the storefront.



When you upload combination pictures, you should consider how they are organized in the file. Each combination takes separate row in the import file and represents product variation respectively. There should be provided image for each of combinations in Combination Image column of .csv file. These very images (names or URLs), separated by image delimiter should also be placed to product image column.


Detailed instruction on how to import combination image to PrestaShop is outlined in the article – set-different-images-to-prestashop-product-combinations



It is always better to prevent import mishaps than experience them and waste time to improve matters. Look through the issues, accompanying combination upload, find out their reasons and make PrestaShop import of combinations with Store Manager for PrestaShop accurate.