Retailers can easily monitor their imports (Product and Offer) in the ShopSimon™ Portal. They can also download error reports in order to understand how to amend their product or offer. Error reports are generated to help you to identify issues within your data while creating products or offers. Understanding how to manage and resolve these is a very important aspect of success on ShopSimon™.
Monitoring Product Imports
Price and stock > File Imports > Track Product Imports
A 'Status' summary will be listed to provide details around the product import. If there are errors, there will be links on the right side under 'Actions' to download error reports.
- Integration Error Report - This report contains errors around required fields, this is the report you should view/fix first.
- Transformation Error Reports - This report will have errors in fields that you will want to fix, however will not prevent your item from being published in the ShopSimon™ portal.
The product import file will be listed under 'File Name,' you can access the file by clicking on the link.
Below is a list of the most common product import errors:
Code | Error message | Cause | Solution |
1000 | Attribute is required. | A required attribute does not have a defined value. | In the imported product file, enter a value for this attribute. |
1001 | The category is unknown. | This catalog category does not exist or is not properly written. | If the category exists, the seller should check whether it is properly written or the seller must create its category and map it to a ShopSimon™ category. |
1002 | Incorrect number of fields. | The number of fields defined in the line is different from the number of headers defined. | If there is the same number of fields in the line and in the header, check if there is no duplicated header. |
1004 | The category could not be identified. | The column which must contain the Catalog category is not specified in the file or not detected. | Check if the attribute name is properly written in the header of the file (without space character). |
1005 | The catalog category must be mapped to a leaf ShopSimon™ catalog category. | Sellers can only create products in the bottom level ShopSimon™ Catalog category. | Sellers must change their mapping configuration to map their catalog categories to the bottom level (leaf) catalog categories, otherwise you cannot create categories. |
1006 | The catalog category must be mapped to a ShopSimon™ catalog category. | The seller's catalog category is not mapped to your catalog category. Mapping is mandatory for the seller to import his/her product. | In the back office, map your catalog category to ShopSimon™ catalog category. |
2001/3001 | The attribute must have a minimum value of {1}. | The value is lower than the configured value. | In the imported product file, enter a value higher than {x}. |
2002/3002 | The attribute must have a maximum value of {1}. | The value is greater than the configured value. | In the imported product file, enter a value higher than {x}. |
2003/3003 | The attribute must have a minimum of {1} characters. | The length of the text string is smaller than the configured value. |
Recommend your seller to increase the length of the value
|
2004/3004 | The attribute must have a maximum of {1} characters. | The length of the text string is longer than the configured value. | Recommend your seller to decrease the length of the value |
2005/3005 | The attribute length must be {1}. | The length of the text string is smaller or longer than the configured value. | In the imported product file, enter a text string equal to {x} characters. |
2006/3006 | The attribute is not in the possible values set in the value list. | The attribute value does not exist in the value list. | In the imported product file or enter a text string equal to {x} characters. |
2010/3010 | The attribute must be an integer. | The value is not an integer. | In the imported product file, enter an integer value (with no decimals). |
2011/3011 | The attribute must be numeric. | The value is not numeric. | In the imported product file, enter a numeric value (1, 5, 45, and so on). |
2012/3012 | The attribute must be a date. | The value is not a date. | In the imported product file, enter a date value. |
2014 | The attribute must be a valid URL. | The value is not an URL. | In the imported product file, enter a URL value. |
2015 | The file format is not supported. | The mentioned media file is not supported. | The value must refer to a file type such as: .pdf, .jpg, and so on. |
Monitoring Offer Imports
Price and stock > File Imports > Track Offer Imports
Click on to view a summary of your offer import. If there are errors, there will be an error icon listed under 'Errors.' Click on this access your error report.
Below is a list of the most common offer import errors:
Error message | Cause | Solution |
The product does not exist | Sellers must indicate in their file the "product-id" and "product-id-type" to match their offers with products. If they have this error message, it is because no product with this identifier exists in Mirakl. | If you recently imported your product as new, it may be awaiting approval by the ShopSimon™ team. Once you rule that out, check the product-id-type your submitting matches that used within your product import. |
No existing offer to update | A seller is using the "UPDATE" mode to import its offers and the offer SKU does not match an existing offer in Mirakl. | Check if the SKU is correct or use the "NORMAL" mode to add the offer. |
The field 'sku' is duplicated in the source file | In your seller's file, several offers have the same "sku". This reference needs to be unique for each offer. | Only one SKU must be included to create offers. Check if an offer has been duplicated by mistake |
The state of the product is unknown | The product state your seller entered does not exist (e.g. New, Refurbished, Second-hand). | You must enter the state technical code, not the label |
This import type does not allow the use of the 'update-delete' column | Sellers cannot use the "update-delete" column with the current import mode. | Use the "NORMAL" import mode to use the "update-delete" column in their import file. |
The product linked to the new offer is different from the product linked to the existing offer | You are trying to create an offer using the ID of a deleted offer. The new offer is linked to a different product than the product the deleted offer was linked to. | To avoid the 24 hr wait period, you can create the new offer with another ID to avoid waiting, but this is not recommended unless it's urgent. |
The field 'price' is mandatory | The "price" field is not found in your seller's file. This information is mandatory to create an offer. | If a value is present in this field, check if it is properly written or formatted. |
The logistic family is unknown | The logistic family the seller entered does not exist. | Sellers must specify an existing logistic family. |
The field 'price' has an invalid range | The price of the seller's offer is lower or greater than the limit price that you set on your platform. | Create A Support Ticket |
The field 'leadtime-to-ship' has an invalid value. | The "leadtime-to-ship" field value is incorrect. Must be a positive integer and not exceed the limit defined by the operator | Change the value of the "leadtime-to-ship" field and/or ask the operator about the maximum value. |
Discount date range is incorrect | The correct format of each date is "yyyy-mm-dd". |
Check if:(a) the date format is "yyyy-mm-dd" and (b) the start date is prior or identical to the end date. |
The field 'discount_price' has an invalid range | The discount price of your sellers offer is lower or greater than the limit price set by the operator. | Create A Support Ticket and ask for the limit and adjust the discount price of your offer. |
Discount price is incorrect: must not be null or must be lower than price | You cannot specify a discount price equal or greater than the original offer price. | Check if the discount price is strictly lower of the offer price. |
Available date range is incorrect | The correct format of each date is "yyyy-mm-dd". | Check if:(a) the date format is "yyyy-mm-dd" and (b) the start date is prior or identical to the end date. |
The additional field "{x}" is mandatory but was missing | A mandatory additional field you set-up is missing in your seller's file. | See ShopSimon™ Feed Requirements and Offer Attributes requirements. |
Click here for more information on troubleshooting imports
Please contact ShopSimon™ Seller Support if you have any questions or need additional information - sellersupport@shopsimon.com