xml_export_documentation:xml_2_format

xml_export_documentation:xml_2_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
xml_export_documentation:xml_2_format [2023/04/20 10:58]
tobi
xml_export_documentation:xml_2_format [2023/07/13 09:16] (current)
rihad [Using variants in search results]
Line 43: Line 43:
 ^**''<​[[#​descriptions]]>''​**| Detailed article description | Yes | No | Yes | ^**''<​[[#​descriptions]]>''​**| Detailed article description | Yes | No | Yes |
 ^**''<​[[#​prices]]>''​**| Current article price including taxes | Yes | Yes | **filterable only** | ^**''<​[[#​prices]]>''​**| Current article price including taxes | Yes | Yes | **filterable only** |
-^**''<​[[#​overriddenPrices]]>''​**| ​Current article ​price including taxes | No | No | No |+^**''<​[[#​overriddenPrices]]>''​**| ​Strike-through ​price including taxes | No | No | No |
 ^**''<​[[#​urls]]>''​**| URL to the article page, must be absolute | Yes | Yes | No | ^**''<​[[#​urls]]>''​**| URL to the article page, must be absolute | Yes | Yes | No |
 ^**''<​[[#​images]]>''​**| URL to the article image, must be absolute. | Yes | No | No | ^**''<​[[#​images]]>''​**| URL to the article image, must be absolute. | Yes | No | No |
Line 57: Line 57:
 ^**''<​[[#​using_variants_in_search_results|variants]]>''​**| Product variants | Yes | Yes | No | ^**''<​[[#​using_variants_in_search_results|variants]]>''​**| Product variants | Yes | Yes | No |
 ^ | [[#​attributes_and_properties_in_xml-feed|Attributes and properties in XML-feed]] | ^ | [[#​attributes_and_properties_in_xml-feed|Attributes and properties in XML-feed]] |
-^ | [[#​using_properties_for_product_variants_in_search_results|Using properties for product variants in search results]] | 
  
 ---- ----
Line 246: Line 245:
 <note tip>​**Using our export toolkit?** <note tip>​**Using our export toolkit?**
  
-Creating an url element with [[https://​github.com/​findologic/​libflexport/​wiki#​url|libflexport]].</​note>​+Creating an overriddenPrice ​element with [[https://​github.com/​findologic/​libflexport/​wiki#​overriddenPrice|libflexport]].</​note>​
  
 ---- ----
Line 352: Line 351:
   ​   ​
  
-=== Using <usergroupsto set the visibility of single information relevant for a returned item ===+=== Using usergroups to set the visibility of single information relevant for a returned item ===
  
-  * By using the ''​<usergroups>''​-tag you can set specific images, keywords, price etc. +  * By using the ''​usergroups'' ​attribute ​you can set specific images, keywords, price etc. 
-  * By using the ''​<usergroup>''​ attribute within XML tags, you can set specific item information for given ''​<usergroups>''​. +  * By using the ''​usergroup''​ attribute within XML tags, you can set specific item information for given ''​usergroups''​. 
-  * If no ''​<usergroup>''​ is requested the default (non-usergroup) value is used for all tags. Therefore default (non-usergroup) tags are required for all elements in the data feed. +  * If no ''​usergroup''​ is requested the default (non-usergroup) value is used for all tags. Therefore default (non-usergroup) tags are required for all elements in the data feed. 
-  * If a ''​<usergroup>''​ is requested the usergroup-specific value is used for all tags.+  * If a ''​usergroup''​ is requested the usergroup-specific value is used for all tags.
        * **Example:​** If the usergrouphash="​ employee " is used -> ''<​name usergroup="​employee "><​![CDATA[Internal product title]]></​name>''​ the name set for this usergroup is used.        * **Example:​** If the usergrouphash="​ employee " is used -> ''<​name usergroup="​employee "><​![CDATA[Internal product title]]></​name>''​ the name set for this usergroup is used.
   * If an item has no usergroup-specific value for a tag then the default (non-usergroup) value is used.   * If an item has no usergroup-specific value for a tag then the default (non-usergroup) value is used.
Line 368: Line 367:
  
 === Recommendation === === Recommendation ===
-  * In case of more than 128 ''<​usergroups>'',​ please contact [[mailto:​support@findologic.com|support@findologic.com]],​ in order to adjust default settings.+  * In case of more than 128 ''<​groups>'',​ please contact [[mailto:​support@findologic.com|support@findologic.com]],​ in order to adjust default settings.
   * To avoid potential misunderstandings,​ preferably use alphanumeric values for usergroups (e.g. ''​18plus'',​ ''​B2B''​).   * To avoid potential misunderstandings,​ preferably use alphanumeric values for usergroups (e.g. ''​18plus'',​ ''​B2B''​).
  
Line 374: Line 373:
 <note tip>​**Using our export toolkit?** <note tip>​**Using our export toolkit?**
  
-Creating an ''<​usergroup>''​ element with [[https://​github.com/​findologic/​libflexport/​wiki#​usergroup|libflexport]].</​note>​+Creating an ''<​group>''​ element with [[https://​github.com/​findologic/​libflexport/​wiki#​group|libflexport]].</​note>​
 ==== bonuses ==== ==== bonuses ====
  
Line 487: Line 486:
 <note tip>​**Using our export toolkit?** <note tip>​**Using our export toolkit?**
  
-Creating a sort element with [[https://​github.com/​findologic/​libflexport/​wiki#​sort|libflexport]].</​note>​+Creating a visibility ​element with [[https://​github.com/​findologic/​libflexport/​wiki#​visibility|libflexport]].</​note>​
  
 ---- ----
Line 655: Line 654:
  
 {{:​integration_documentation:​xml_schema:​attr_prop.png?​1140|}} {{:​integration_documentation:​xml_schema:​attr_prop.png?​1140|}}
- 
- 
----- 
- 
-==== Using properties for product variants in search results ==== 
- 
-If you want to show different variations (colors, sizes etc.) of a certain product in your shop and you want to display those variants in specific product-cards on the search result page, it can be realized by following the steps described below (example for colors): 
- 
-**Functionality:​** 
-  - All color-variants displayed for parent (master)-product. 
-  - While hovering over the variant picture - appropriate image should be displayed. 
-  - By click on a color-variant or on an image the page of the product with the right color should be opened. 
- 
-**1.**{{:​integration_documentation:​xml_schema:​1.1.png?​200|}} 
-**2.**{{:​integration_documentation:​xml_schema:​3.1.1.png?​200|}} 
-**3.**{{:​integration_documentation:​xml_schema:​4.1.1.png?​515|}} 
- 
-**How the XML should look like:** 
- 
-You have to provide an appropriate property (for example "​variants"​) for every parent-product by using a JSON-string. Here is an example of this property: 
- 
-<code xml> 
-[...] 
-<​allProperties>​ 
- <​properties>​ 
-  <​property>​ 
-   <​key>​variants</​key>​ 
-   <​value><​![CDATA[ 
-    { 
-     "​Mud"​ : { 
-      "​VariantIconPic"​ : "​https://​www.shop.com/​media/​jacket_mud_variant_icon.jpg",​ 
-      "​productPic"​ : "​https://​www.shop.com/​media/​jacket_mud_variant_pic.jpg",​ 
-      "​productUrl"​ : "​https://​www.shop.com/​jacket_mud"​ 
-     }, 
-     "​Black"​ : { 
-      "​VariantIconPic"​ : "​https://​www.shop.com/​media/​jacket_black_variant_icon.jpg",​ 
-      "​productPic"​ : "​https://​www.shop.com/​media/​jacket_black_variant_pic.jpg",​ 
-      "​productUrl"​ : "​https://​www.shop.com/​jacket_black"​ 
-     }, 
-     "​Red"​ : { 
-      "​VariantIconPic"​ : "​https://​www.shop.com/​media/​jacket_red_variant_icon.jpg",​ 
-      "​productPic"​ : "​https://​www.shop.com/​media/​jacket_red_variant_pic.jpg",​ 
-      "​productUrl"​ : "​https://​www.shop.com/​jacket_red"​ 
-     }, 
-     "​Navy"​ : { 
-      "​VariantIconPic"​ : "​https://​www.shop.com/​media/​jacket_navy_variant_icon.jpg",​ 
-      "​productPic"​ : "​https://​www.shop.com/​media/​jacket_navy_variant_pic.jpg",​ 
-      "​productUrl"​ : "​https://​www.shop.com/​jacket_navy"​ 
-     } 
-    } 
-   ​]]></​value>​ 
-  </​property>​ 
- </​properties>​ 
-</​allProperties>​ 
-[...] 
-</​code>​ 
- 
  
 ---- ----
Line 735: Line 677:
   * attributes, required   * attributes, required
   * name, optional   * name, optional
-  * price, optional. In case it is not set, the parent price will be used as default.+  * price, optional. ​(In case it is not set, the parent price will be used as default.)
   * groups, optional.   * groups, optional.
   * overriddenPrice,​ optional   * overriddenPrice,​ optional
   * properties, optional   * properties, optional
 +  * urls, optional
 +  * images, optional
 +
  
 <note important>​No other fields are allowed.</​note>​ <note important>​No other fields are allowed.</​note>​
Line 744: Line 689:
 <note tip>​Currently it is not possible to use variants and usergroups together. <note tip>​Currently it is not possible to use variants and usergroups together.
 Variants only work without usergroups. But using groups is still possible. So filtering by group is working fine.</​note>​ Variants only work without usergroups. But using groups is still possible. So filtering by group is working fine.</​note>​
 +
 +<note tip>​**Using our export toolkit?**
 +
 +Creating a variant element with [[https://​github.com/​findologic/​libflexport/​wiki#​variants|libflexport]].</​note>​
 +
 ==== Example XML ==== ==== Example XML ====