csv_export_documentation:csv_format
Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
csv_export_documentation:csv_format [2023/01/18 16:08] rihad [The columns in detail] |
csv_export_documentation:csv_format [2023/02/22 10:55] rihad [Exporting variants with parent id] |
||
---|---|---|---|
Line 34: | Line 34: | ||
^**''[[#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. | No | No | | + | ^**''[[#url]]''**|Absolute or relative link to the article-detail-page. | Yes | 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. 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 | | ||
^**''[[#attributes]]''**|Categories and attributes (used for filters) of the article. | Yes | Yes | | ^**''[[#attributes]]''**|Categories and attributes (used for filters) of the article. | Yes | Yes | | ||
Line 40: | Line 40: | ||
^**''[[#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. Must be a numeric value. | 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?" Must not be negative. | Yes | 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. Use ISO-8601 as format. | 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 | | ||
Line 156: | Line 156: | ||
**categories** | **categories** | ||
- | * Categories **must** be given with the key ''cat''. This is important! | + | * Categories **must** be given with the key ''attrib_cat''. This is important! |
- | * Sub-categories have to be separated with an underline character ''_'', which **must not** be URL-encoded. | + | * Sub-categories have to be separated with an underline character ''_''. |
- | * For example, an article from the category ''Bikes > Mountain Bikes'' has to look like this: ''cat=Bikes_Mountain+Bikes'' | + | * For example, an article from the category ''Bikes > Mountain Bikes'' has to look like this: ''Bikes_Mountain Bikes'' |
---- | ---- | ||
Line 165: | Line 165: | ||
- | In order to use Findologic Navigation with Direct Integration, the parameter ''cat_url'' has to be added with the category path to the "attributes" column. If a product is shown in several categories, all paths have to be exported. | + | In order to use Findologic Navigation with Direct Integration, the parameter ''attrib_cat_url'' has to be added with the category path to the "attributes" column. If a product is shown in several categories, all paths have to be exported. |
<note>You have to export both main-''cat_url's'' and sub-''cat_url's'' for the main- and sub-categories, that an article is assigned to.</note> | <note>You have to export both main-''cat_url's'' and sub-''cat_url's'' for the main- and sub-categories, that an article is assigned to.</note> | ||
For example for a product, which is assigned to the following categories ... | For example for a product, which is assigned to the following categories ... | ||
Line 250: | Line 250: | ||
=== properties === | === properties === | ||
- | These values can have freely choosable names, which can be used as properties: | + | |
* The values in this column won't be used by for the calculation of the search results. | * The values in this column won't be used by for the calculation of the search results. | ||
* All informations given here can be used for your specific needs. | * All informations given here can be used for your specific needs. | ||
Line 316: | Line 316: | ||
=== Format === | === Format === | ||
- | * A parent product must contain all ordernumbers of its variants and the variants must not contain any ordernumber at all. | + | * A parent product must contain all ordernumbers of its variants and each variant needs a dedicated ordernumber as well. |
* A variant export must contain a column called parent_id | * A variant export must contain a column called parent_id | ||
* Variant products must follow the parent product immediately, without any other parent products in between. | * Variant products must follow the parent product immediately, without any other parent products in between. | ||
Line 322: | Line 322: | ||
* Only the attributes of the parent have a effect on the outputAttributes. | * Only the attributes of the parent have a effect on the outputAttributes. | ||
* Attributes which should be applied to all variants must be defined in the attributes field of the parent. | * Attributes which should be applied to all variants must be defined in the attributes field of the parent. | ||
- | * ItemVariants/children without attributes will not be imported. | + | * ItemVariants/children without attributes will break the export. |
* A child must not contain keywords. This will break the export. | * A child must not contain keywords. This will break the export. | ||
* Prices of variant items won't be used for sorting. | * Prices of variant items won't be used for sorting. |