csv_export_documentation:csv_format

csv_export_documentation:csv_format

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
csv_export_documentation:csv_format [2023/02/22 10:34]
rihad [The columns in particular]
csv_export_documentation:csv_format [2023/02/22 12:04] (current)
rihad
Line 1: Line 1:
-===== Findologic CSV export format =====+===== Findologic CSV 1.0 export format =====
 If your are using CSV-export for the data synchonization between your shop data and Findologic, the CSV-data provided by you has to be formatted in the way that is described below. If your are using CSV-export for the data synchonization between your shop data and Findologic, the CSV-data provided by you has to be formatted in the way that is described below.
  
Line 11: Line 11:
  
 <note important>​Control characters (**[#​x01-#​x08]** | **[#​x0B-#​x0C]** | **[#​x0E-#​x1F]**) are not allowed in any value of the feed.</​note>​ <note important>​Control characters (**[#​x01-#​x08]** | **[#​x0B-#​x0C]** | **[#​x0E-#​x1F]**) are not allowed in any value of the feed.</​note>​
- 
-<note important>​The summary, description and the attribute values should not contain any HTML-Tags. 
-A warning will be shown during import and the tags get stripped automatically.</​note>​ 
  
 ---- ----
Line 30: Line 27:
 ^**''​[[#​summary]]''​**|Short description of the article, which can be displayed optionally. | No | Yes | ^**''​[[#​summary]]''​**|Short description of the article, which can be displayed optionally. | No | Yes |
 ^**''​[[#​description]]''​**|Detailed article description.| No | Yes | ^**''​[[#​description]]''​**|Detailed article description.| No | Yes |
-^**''​[[#​price]]''​**|Currently valid retail price incl. taxes (f.e. currents sales price). Must have a dot (.) as decimal delimiter only. | Yes | No | +^**''​[[#​price]]''​**|Currently valid retail price incl. taxes (f.e. currents sales price).| Yes | No | 
-^**''​[[#​overriddenPrice]]''​**|Regular price of the article incl. taxes. | No | No |+^**''​[[#​instead]]''​**|Regular price of the article incl. taxes. | No | No |
 ^**''​[[#​maxprice]]''​**|Currently valid retail price incl. taxes with the highest available option. | No | No | ^**''​[[#​maxprice]]''​**|Currently valid retail price incl. taxes with the highest available option. | No | No |
 ^**''​[[#​taxrate]]''​**|Taxrate of the article. | Yes | No | ^**''​[[#​taxrate]]''​**|Taxrate of the article. | Yes | No |
-^**''​[[#​url]]''​**|Absolute or relative link to the article-detail-page. | Yes | No | +^**''​[[#​url]]''​**|Absolute or relative link to the article-detail-page. | No | No | 
-^**''​[[#​image]]''​**|Absolute or relative link to article image. We recommend to deliver the image in thumbnail-size. Export supports more than 1 product image. Just add another column image0, image1 and so on. Syntax is “imageX” where X is any number. | No | No |+^**''​[[#​image]]''​**|Absolute or relative link to article image. We recommend to deliver the image in thumbnail-size. | No | No |
 ^**''​[[#​attributes]]''​**|Categories and attributes (used for filters) of the article. | Yes | Yes | ^**''​[[#​attributes]]''​**|Categories and attributes (used for filters) of the article. | Yes | Yes |
 ^**''​[[#​keywords]]''​**|Keywords,​ which are related to the article. | No | Yes | ^**''​[[#​keywords]]''​**|Keywords,​ which are related to the article. | No | Yes |
 ^**''​[[#​groups]]''​**|Groups,​ which the article is related to. (f.e. subshops). | No | No | ^**''​[[#​groups]]''​**|Groups,​ which the article is related to. (f.e. subshops). | No | No |
-^**''​[[#​bonus]]''​**|Bonusvalue related to the specific article. This is useful to push products on top of the search results. Must be a numeric value. | No | No | +^**''​[[#​bonus]]''​**|Bonusvalue related to the specific article. This is useful to push products on top of the search results. | No | No | 
-^**''​[[#​sales_frequency]]''​**|Salesfrequency of the article. "How often was the specific article sold?" ​Must not be negative. ​| No | No | +^**''​[[#​sales_frequency]]''​**|Salesfrequency of the article. "How often was the specific article sold?" | No | No | 
-^**''​[[#​date_added]]''​**|The date, on which the article was added to the shop. Use ISO-8601 as format. | No | No |+^**''​[[#​date_added]]''​**|The date, on which the article was added to the shop. | No | No |
 ^**''​[[#​sort]]''​**|This value can be used to sort the articles and to have influence on the position of specific articles on the search result pages. Has to be an integer. | No | No | ^**''​[[#​sort]]''​**|This value can be used to sort the articles and to have influence on the position of specific articles on the search result pages. Has to be an integer. | No | No |
 ^**''​[[#​visibilities]]''​**| Indicates the visibility of all/some products | No | No | ^**''​[[#​visibilities]]''​**| Indicates the visibility of all/some products | No | No |
Line 110: Line 107:
 ---- ----
  
-=== overriddenPrice ​===+=== instead ​===
 The gross price shown instead of the base price, for example ''​Now only 39.95$ instead of 59.95$''​ --> ''​base price=59.95,​ instead=39.95''​. The gross price shown instead of the base price, for example ''​Now only 39.95$ instead of 59.95$''​ --> ''​base price=59.95,​ instead=39.95''​.
     * The same rules as in the column ''​price''​ (described above) apply.     * The same rules as in the column ''​price''​ (described above) apply.
Line 144: Line 141:
  
 === attributes === === attributes ===
-    * Each attribute gets its own column, that will be used as filters. [[:​customer_account:​filter_configuration|Here]] you can find our documentation about filter configuration. +This column ​is used to set all values, that will be used as filters. Examples for these filters are: categories, vendor, color, size, etc. [[:​customer_account:​filter_configuration|Here]] you can find our documentation about filter configuration. 
- +    * Attribute ​name length **must not** exceed **247 characters** and attribute value length **must not** exceed **16383 characters**. 
-    * The column ​name will be “attrib_” + “FILTERNAME”Examples“attrib_color”,​ “attrib_size”,​ “attrib_cat”,​ “attrib_vendor” +    * **All attributes have to be encoded in URL-style**Exampleproduct with vendor "Dolce & Gabbana"​ from category "​Schnürschuhe"​ should have attributes like ''​vendor=Dolce%20%26%20Gabbana&​cat=Schn%C3%BCrschuhe''​. 
- +      * It is **very important** that you also encode characters like ''​=''​ or ''&''​ that are contained in the values. 
-    * For an attribute with multiple valuesuse comma “,” as separator. If a comma is used within the valueit must be escaped ​like \A comma in column name must not be escaped+      * For example, a bike made by a manufacturer called ''​Sons&​Partners''​ would look like this: ''​vendor=Sons%26Partners&​cat=bikes''​. 
- +      * It is also important that all attributes are UTF-8 encoded **before** you URL encode them. 
-^ attrib_color ​     ^ attrib_vendor ​      ^ attrib_cat ​         ^ attrib_Sport ​         ^ +      * If you use sliderdo not export the values ​like this: //100 cm//Correct: //100//. You can set the unit in the filter ​     configuration in the Findologic customer account.  
-| blue,​black ​   | Nike     | Running ​       | Basic\,​Sports ​       |+    * More than one value of the same attribute may be used: Use it like this: ''​color=red&​color=green''​
 +    ​* All attribute names and values are case-insensitive.
  
 ---- ----
Line 254: Line 252:
     * All informations given here can be used for your specific needs.     * All informations given here can be used for your specific needs.
     * F.e.: stock information,​ shipping details, etc.      * F.e.: stock information,​ shipping details, etc. 
-    * The column name must be prefixed with “prop_”. Example “prop_shipping”,​ “prop_stock”+
  
 ---- ----