Page tree
Skip to end of metadata
Go to start of metadata

Cosmetics & Perfumes algorithm is developed to identify particular characteristics of a new potential customer, such as a predisposition to certain cosmetic and hygiene products and brands, and specify product recommendations based on this data.

Following steps are covered

 

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 volume and type;
  • additional category-specific information.

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

Section <cosmetics>

A distinctive beauty (incl. fragrances) and cosmetic product feature is presence of the <cosmetics> subsection inside the <offer>  section.

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

Gender

Mandatory parameter <gender>. Placed inside the <offer> section, within the <cosmetics> subsection.

Consider the following table of possible values:

ValueDescription
mMale
fFemale

 

Consider the following example of use:

XML example
 ...
<offer ...>
    ...
	<cosmetic>
	    <gender>f</gender>
	</cosmetic>
</offer>
...

No need to specify the gender this particular product is targeted at, if you do not have correct 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.

Hypoallargenic Properties

Oprtional parameter <hypoallergenic>. Placed inside the <offer> section, within the <cosmetics> subsection.

Consider the following table of possible values:

ValueDescription
1Product is hypoallergenic
0Product is non-hypoallergenic

 

Consider the following example of use:

XML example
 ...
<offer ...>
    ...
	<cosmetic>
	    <hypoallergenic>1</hypoallergenic>
	</cosmetic>
</offer>
...

No need to specify the gender this particular product is targeted at, if you do not have correct data (hypoallergenic properties). By default, every cosmetic product is set to non-hypoallergenic.

Subsection <skin>

Subsection <skin> contains additional characteristics of Skin Care products.

Add the following parameters to each skin care product to your XML-File.

Skin Type 

Optional parameter <type>. Placed inside the <offer> section, within the <cosmetics> subsection, within the <skin> sub-subsection.

Consider the following table of possible values:

ValueDescription
drydry skin
normalnormal skin
oilyoily skin
combycombination skin

Current Skin Condition 

Optional parameter <condition>. Placed inside the <offer> section, within the <cosmetics> subsection, within the <skin> sub-subsection.

Consider the following table of possible values:

ValueDescription
dehydrateddehydrated
sensitivesensitive
problempropblematic
fadingageing

 

Consider the following examle of use:

XML example
 ...
<offer ...>
    ...
	<cosmetic>
	    <skin>
			<part>face</part>
			<part>body</part>
			<type>normal</type>
			<type>oily</type>
			<condition>sensitive</condition>
			<condition>fading</condition>
		</skin>
	</cosmetic>
</offer>
...

Local Application

Optional parameter <part>. Placed inside the <offer> section, within the <cosmetics> subsection, within the <skin> sub-subsection.

Consider the following table of possible values:

ValueDescription
facefacial care, makeup and oral hygiene products
bodybody care products, perfume
intimpersonal hygiene products
handhand and nail care products
legfoot care products

If this particular product is intended for various purposes/various local applications, additional data is passed in the form of a list in the <part> section.

 

Consider the following examle of use:

XML example
 ...
<offer ...>
    ...
	<cosmetic>
	    <skin>
			<part>face</part>
			<part>body</part>
		</skin>
	</cosmetic>
</offer>
...

Subsection <hair>

Subsection <hair> contains additional characteristics of Hair Care products.

Hair Type

Optional parameter <type>. Placed inside the <offer> section, within the <cosmetics> subsection, within the <hair> sub-subsection.

Consider the following table of possible values:

Valuedescription
drydry type
normalnormal type
oilyoily type
combycombination type

Current Hair Condition

Optional parameter <condition>. Placed inside the <offer> section, within the <cosmetics> subsection, within the <hair> sub-subsection.

Consider the following table of possible values:

Value Description
coloreddyed hair
damageddamaged hair
wavedcurly hair
seboreadandruff
akneaсne, others head skin conditions
losshair loss treatment
growhair growth help

 

Consider the following example of use: 

XML example
 ...
<offer ...>
    ...
	<cosmetic>
	    <hair>
			<type>normal</type>
			<type>oily</type>
			<condition>colored</condition>
			<condition>damaged</condition>
		</hair>
	</cosmetic>
</offer>
...


Subsection <nail>

Subsection <nails> contains additional characteristics of Nail Care Care products.

Care Type

Optional parameter <type>. Placed inside the <offer> section, within the <cosmetics> subsection, within the <nail> sub-subsection.

Consider the following table of possible values:

Valuedescription
toolNail care tool
polishNail polish
gelGel polish
oilNail oil
cleanerNail cleaner

 

Consider the following example of use:

XML example
 ...
<offer ...>
    ...
	<cosmetic>
	    <nail>
			<type>tool</type>
            <polish_color>red</polish_color>
		</nail>
	</cosmetic>
</offer>
...

Subsection <perfume>

Subsection <perfume> contains characteristics of fragrances.

Main fragrance families (<family>)

Mandatory parameter <family>. Placed inside the <offer> section, within the <cosmetics> subsection, within the <perfume> sub-subsection.

Consider the following table of possible values:

ValueDescription
floralFloral notes
orientalOriental notes
woodyWoody notes
freshFresh notes

 

Consider the following example of use:

XML example
 ...
<offer ...>
    ...
	<cosmetic>
	    <perfume>
			<family>woody</family>
		</perfume>
	</cosmetic>
</offer>
...

Subgroups of fragrance families (<aroma>)

Optional parameter <aroma>. Placed inside the <offer> section, within the <cosmetics> subsection, within the <perfume> sub-subsection, within the <family> sub-sub-subsection.

RelationsValueDescriptionCommentary

 

 

Floral notes

 

 

 

 

Oriental notes

 

 

 

 

 

 

Woody notes

 

 

 

 

 

 

 

 

 

 

 

Fresh notes

fruity_floralFruity Floral (Fruity + Floral Notes)Main notes include fruits and floral notes
floralFloral (Floral + Fresh Notes)Main notes include fresh-cut flowers.
soft_floralSoft Floral (Floral Notes)Main notes include aldehydes and powdery notes.
floral_orientalFloral Oriental (Floral + Oriental Notes)Main notes include white flowers (such as orange blossom) and sweet spices.
soft_orientalSoft Oriental (Oriental + Floral Notes)Main notes include incense and amber.
orientalOriental (Oriental Notes)Main notes include oriental resins such as frankincense, and vanilla.
woody_orientalWoody Oriental (Oriental + Woody Notes)Main notes include sandalwood and patchouli.
woodsWoodsMain notes include aromatic woods and vetiver.
mossy_woodsMossy Woods (Woody + Oriental Notes)Main notes include oakmoss and amber.

dry_woods

Dry Woods (Woody Notes)Main notes include dry woods and leather.
aromaticAromatic Fougère (Fresh Notes)Main notes include lavender and aromatic herbs. This universal fragrance group includes elements from different families: the freshness from the Citrus family, floral notes of lavender, the spicy-sweetness of a Floral Oriental, the ambery depth of an Oriental and the Mossy Woods warmth of sandalwood and oakmoss.
citrusCitrus (Woody + Fresh Notes)Main notes include bergamot and other citrus oils.
waterWater (Fresh + Floral Notes)Main notes include marine and aquatic notes, generally from the chemical calone.
greenGreen (Fresh + Floral Notes)Main notes include galbanum and green notes.
fruityFruity (Fresh + Floral Notes)Main notes include berries and other non-citrus fruits.

 

Consider the following example of use:

XML example
 ...
<offer ...>
    ...
	<cosmetic>
	    <perfume>
			<family>woody</family>
            <aroma>mossy_woods</aroma> 
		</perfume>
	</cosmetic>
</offer>
...

Product Volume

Optional parameter <volume> and <price> are wrapped in the parameter <volumes>. Placed inside the <offer> section, within the <cosmetics> subsection.

<volumes> allows to specify product volume and volume-dependable pricing.

Consider the following table of possible sub-parameters:

ParameterDescription
<volume>Wrapper for each product volume (for parameters <value> and <price>)
<value>Volume in milliliters
<price>Price for each volume

 

Consider the following example of use:

XML example
 ...
<offer ...>
    ...
	<cosmetic>
		<volumes>
 			<volume>
    			<value>200</value>
				<price>1000</price>
  			</volume>
			<volume>
    			<value>400</value>
				<price>2000</price>
  			</volume>
		</volumes>
	</cosmetic>
</offer>
...

IMPORTANT

Measurment units for the <value> parameter are milliliters.

 

Purchase Frequency

Optional parameter <periodic>. Placed inside the <offer> section, within the <cosmetics> subsection.

Consider the following table of possible values:

ValueDescription
1Product is purchased frequently
0Product is purchased occasionally

 

Consider the following example of use:

XML example
 ...
<offer ...>
    ...
	<cosmetic>
	    <periodic>1</periodic>
	</cosmetic>
</offer>
...


Professional Products

Optional parameter <professional>. Placed inside the <offer> section, within the <cosmetics> subsection.

Consider the following table of possible values:

ValueDescription
1Product is purchased for professional use (by professionals)
0Product is purchased for everyday use (by ordinary customers)

 

Consider the following example of use:

XML example
 ...
<offer ...>
    ...
	<cosmetic>
	    <professional>1</professional>
	</cosmetic>
</offer>
...

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

Table of Contents

  • No labels