Page Comparison - Apparel & Accessories (v.12 vs v.13) - EN documentation - REES46 Manual
Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Apparel & Accessories algorithm is developed to automatically identify particular characteristics of a new potential customer interested in apparel with certain parameters, and specify product recommendations based on this data.

Panel
titleFollowing steps are covered

Table of Contents

 


Add Additional Parameters to Your XML-file

For the algorithm to work properly every product in your XML Product Feed should have additional properties:

  • gender this product is targeted at;
  • product size and sizing systems;
  • additional category-specific data.

This data should be included into the XML-file in the formofspecific product parameters and send to REES46.

Section <fashion>

A distinctive feature of a product from Apparel & Accessories category is presenceofthe <fashion> subsection inside the <offer>  section.

Add the following parameters to each product to your XML-File

Gender

Optional parameter <gender>. Placed inside the <offer> section, within the <fashion> subsection.

Consider the following table of possible attributes:

ValueDescription
mMale
fFemale

 


Consider the following example of use:

Code Block
languagexml
titleXML example
 ...
<offer ...>
    ...
	<fashion>
	    <gender>f</gender>
	</fashion>
</offer>
...


Info

No need to specify the gender this particular product is targeted at, if you do not have this data (gender). In this case, this particular product will simply be marked as 'unisex' and will have a lower displaying priority in relation to other products with the specified gender parameter.

Clothing Type

Mandatory parameter <type>. Placed inside the <offer> section, within the <fashion> subsection.

Consider the following table of possible attributes:

ValueDescription
shoeShoes
shirtShirts, blouses and dresses
tshirtT-shirt
underwearUnderwear
trouserPants, jeans, shorts, skirts and swimsuits
jacketJackets, coats, fur coats
blazerBlazers, vests,pullovers and cardigans
sockSocks
beltBelts
hatHats
gloveGloves


Info

No need to specify the type of the particular product if you do not have the size parameter.

Consider the following example of use:

Code Block
languagexml
titleXML example
...
<offer ...>
	...
	<fashion>
		<gender>f</gender>
		<type>shoe</type>
	</fashion>
</offer>
...

 


Clothing Size

Mandatory parameter <sizes>. Placed inside the <offer> section, within the <fashion> subsection.

Taking into account variety of world sizing systems,every clothing size should have the respective prefix.

Consider the following table of possible prefixes:

Sizing systemDescriptionExample
Prefix is not needed or prefix is 'r'Russian sizing systemr44, 44
'e'European sizing systeme38
Prefix is not needed, if only the letters used, otherwise - prefix 'u'U.S. / international sizing systemXS, u30
'b'British sizing systemb6
'h'Height (for baby and children apparel)h89-95
Prefix is not neededUnisize (fits all sizes)null


Info

Single product can have more than one size, hence all the available sizes should be passed in the form of a list - each size wrapped in the tag <size>.


Consider the following example of use:

Code Block
languagexml
titleXML example
 ...
<offer ...>
	...
	<fashion>
		<gender>f</gender>
		<type>shoe</type>
		<sizes>
			<size>e40</size>
			<size>e42</size>
			<size>e44</size>
			<size>e48</size>
		</sizes>
	</fashion>
</offer>
...


Color

Optional parameter <color>. Placed inside the <offer> section. 

Info

One product can have several colors. The "picture" attribute may be missing, in which case the main image of the product is used.

Consider the following example of use:

Code Block
languagexml
titleXML example
 ...
<offer ...>
	...
	<fashion>
		<gender>f</gender>
		<type>shoe</type>
		<sizes>
			<size>e40</size>
			<size>e42</size>
			<size>e44</size>
			<size>e48</size>
		</sizes>
        <color>red></color>
        <color picture="https://mystore.com/product/100500/pictures/yellow.jpg">yellow</color>
	</fashion>
</offer>
...

 


Features

Optional parameter <feature>. Placed inside the <offer> section, within the <fashion> subsection.

Consider the following table of possible attributes:

ValueDescription
pregnantMaternity clothing

 


Consider the following example of use:

Code Block
languagexml
titleXML example
 ...
<offer ...>
    ...
	<fashion>
	    <gender>f</gender>
	    <type>jacket</type>
		<feature>pregnant</feature>
	</fashion>
</offer>
...

Return to the top of the page Proceed to the next page


Panel
titleTable of Contents

Page Tree
rootNiche Solutions