E-commerce

Mobile app

Mobile app: Sub campaign
Getting started
In this article, you can find information about the mobile app: sub campaign sub-category. Sub campaigns are blocks of desired content like products, promotion pages, or opensets that will be visible in the mobile app directly below the carousel. Customers are able to select these blocks in order to be redirected to the desired page.
  RememberYou can find more information about the mobile app and other sub-categories in the Mobile app article.
Visualization of the sub campaign on the mobile app
To open the sub campaign view, in the admin panel, navigate to:
Mobile app > sub campaign
All possible operations to perform on the sub campaign view can be done in the Filters (1), and Sub campaigns (2) tabs.
Visualization of the sub campaign sub-category
Table of contents:
 Filters section
Sub campaign
 Creating a sub campaign
 
 
 Filters section
The Filters section allows sorting of the sub campaigns in the mobile app module, based on the available filters. Below you will find a description of available filters
Visualization of the filters section
Is active? - Sub campaign activity status.
Date start - A range of dates that indicate the start date of the sub campaign.
Date end - A range of dates that indicate the end date of the sub campaign.
After defining the above filters, select the Apply Filters button to get a list of sites according to the applied filters.  
 
 
 Sub campaign
The Sub campaign section allows organizing the filtered featured sub campaigns, edit them and create new ones and delete them.
Below you will find a description of all possible actions you can perform in the sub campaign section in the admin panel.
Visualization of the sub campaign section
 Select the Show X entries(1) field to set the number of sub campaigns, displayed on one page (min 10 / max 100).
The names of the columns (2) that contain information about a target sub campaign. Each column is susceptible to sorting.
To sort the records, click on the title of the column in question.
ID - An internal ID of the sub campaign.
Internal name - Internal name of the sub campaign.
Place - Place identification: homepage / boutique. Field is used by mobile application to distinguish which banners should go to home view and which to boutique view.
Sort order - Sort order of the sub campaign.
Date start - Start date when the sub campaign will be visible to the customers.
Date End - End date when the sub campaign will be hidden from the customers.
Is active? - Activity status of the sub campaign.
Actions - List of buttons with possible actions that can be done to the sub campaign.
Edit - Edit desired sub campaign. As editing contains exactly the same fields and actions as creating a new sub campaign you can read more about it in the  Creating a sub campaign chapter.
Delete - Deletes the selected sub campaign without the ability to restore it.
Select the Add (3) button to go to the adding the new sub campaign. You can learn more about adding of the sub campaign in the  Creating a sub campaign chapter.
Search box (4) where you can search for sub campaigns by their system name.
Page buttons(5), which allow users to change the page of the currently viewed content.
 
 
 Creating a sub campaign
Add button allows users to create a new sub campaign.
Below, you will find a description of all possible fields that can be edited while creating a new sub campaign in the admin panel.
Visualization of the creating the sub campaign
Internal name (mandatory) - Internal name of the sub campaign.
Place (mandatory) - Place identification: homepage / boutique. Field is used by mobile application to distinguish which banners should go to home view and which to boutique view.
Link type (mandatory) - Type of a link available in the sub campaign. Depending on the selected type the Object ID field will require different input. There are 5 types of links:
Product - Product available on the website.
Category (tag) - Category tag available on the website.
Promotion page - The promotion page available on the website.
Openset page - Openset page available on the website.
Custom view - Custom object programmed by the mobile app developers.
Object ID (mandatory) - ID of an object selected in Link type section.
Product - Product SKU i.e. J12345
Category (tag) -Tag ID i.e. 76938
Promotion page - Promotion page internal ID i.e. 1234
Openset page - Openset internal ID i.e. 765
Custom view - Custom field that doesn't have any validation. Custom values configured and programmed by mobile app developers can be put here.
Small image (mandatory) - Small image of the sub campaign. Recommended image size is 200x400px. This image will be visible to the customers.
Medium image (mandatory) - Medium image of the sub campaign. Recommended image size is 400x600px. This image will be visible to the customers.
Large image (mandatory) - Large image of the sub campaign. Recommended image size is 800x1000px. This image will be visible to the customers.
Start date - Start date when the sub campaign will be visible to the customers.
End date - End date when the sub campaign will be hidden from the customers.
Sort order (mandatory) - Sort order of the sub campaign. The lower the sort order the earlier in the order selected sub campaign will be visible to the customer.
Is active? - Switch, which defines if the selected sub campaign is visible in the mobile app.
With all necessary fields filled, you can save the changes using the save button.

Mobile app: Carousel
Getting started
In this article, you can find information about the mobile app: Carousel sub-category. Carousel is equivalent to sliders on the e-commerce platform, except it shows only the first carousel depending on their sort order and after selecting it customer will see a story (similar to Instagrams stories), where every available carousel is visible for a short time.
  RememberYou can find more information about the mobile app and other sub-categories in the Mobile app article.
Visualization of the carousel story on the mobile app
To open the Carousel view, in the admin panel, navigate to:
Mobile app > Carousel
All possible operations to perform on the Carousel view can be done in the Filters (1), and Carousel (2) tabs.
Visualization of the carousel sub-category
Table of contents:
 Filters section
Carousel
 Creating a carousel
 Application view
 
 
 Filters section
The Filters section allows sorting of the carousel in the mobile app module, based on the available filters. Below you will find a description of available filters
Visualization of the filters section
Is active? - Carousel activity status.
Date start - A range of dates that indicate the start date of the carousel.
Date end - A range of dates that indicate the end date of the carousel.
After defining the above filters, select the Apply Filters button to get a list of sites according to the applied filters.  
 
 
 Carousel
The Carousel section allows organizing the filtered featured carousels, edit them and create new ones and delete them.
Below you will find a description of all possible actions you can perform in the Carousel section.
Visualization of the carousel section
 Select the Show X entries(1) field to set the number of carousels, displayed on one page (min 10 / max 100).
The names of the columns (2) that contain information about a target carousel. Each column is susceptible to sorting.
To sort the records, click on the title of the column in question.
ID - An internal ID of the carousel.
Title - Internal title of the carousel. This field is not visible to the customers
Story title - Story, public title of the carousel. This field is visible to the customers.
Date start - Start date when the carousel will be visible to the customers.
Date End - End date when the carousel will be hidden from the customers.
Is active? - Activity status of the carousel.
Actions - List of buttons with possible actions that can be done to the desired carousel.
Edit - Edit desired carousel. As editing contains exactly the same fields and actions as creating a new carousel you can read more about it in the  Creating a carousel chapter.
Delete - Deletes the selected carousel without the ability to restore it.
Select the Add (3) button to go to the adding the new carousel. You can learn more about adding of the carousel in the  Creating a carousel chapter.
Search box (4) where you can search for carousels by their system name.
Page buttons(5), which allow users to change the page of the currently viewed carousel.
 
 
 Creating a carousel
Add button allows users to create a new carousel.
Below, you will find a description of all possible fields that can be edited while creating a new carousel.
Visualization of the creating the carousel
Title (mandatory) - Internal carousel name. This field is not visible to the customers.
Story title (mandatory) - Public carousel name. This field is visible to the customers.
Description (mandatory) - Description of the carousel. This field is visible to the customers.
Link type (mandatory) - Type of a link available in the carousel. Depending on the selected type the Object ID field will require different input. There are 5 types of links:
Product - Product available on the website.
Category (tag) - Category tag available on the website.
Promotion page - Promotion page available on the website.
Openset page - Openset page available on the website.
Custom view - Custom object programmed by the mobile app developers.
Object ID (mandatory) - ID of an object selected in Link type section.
Product - Product SKU i.e. J12345
Category (tag) -Tag ID i.e. 76938
Promotion page - Promotion page internal ID i.e. 1234
Openset page - Openset internal ID i.e. 765
Custom view - Custom field that doesn't have any validation. Custom values configured and programmed by mobile app developers can be put here.
Small image (mandatory) - Small image of the carousel. Recommended image size: 200x400.
Medium image (mandatory) - Medium image of the carousel. Recommended image size: 400x600.
Large image (mandatory) - Large image of the carousel. Recommended image size: 800x1000.
Start date - Start date when the carousel will be visible to the customers.
End date - End date when the carousel will be hidden from the customers.
Sort order (mandatory) - Sort order of the carousel. The lower the sort order the earlier in the order selected carousel will be visible to the customer.
Is active? - Switch, which defines if the selected carousel is visible in the mobile app.
With all necessary fields filled, you can save the changes using the save button.
 
 
 Application view
Customers accessing the Yves Rocher application will view the carousel with the lowest sort order a the top of the page.
Visualization of the carousel on the mobile app
When selecting the carousel it will open carousel story where the carousel will change the slide every 10 seconds.
Visualization of the carousel story on the mobile app
Selecting the discover more button will redirect the user to the desired page set in the "link type" and "object id" part of the carousel.
Visualization of the promotional page

Mobile app
Getting started
Mobile API is an interface that allows Yves Rocher Mobile application for android and iOS to get content from Yves-Rocher website. The mobile app should get configured in the Yves Rocher admin panel in order to work properly. The mobile app has its own category in the administrator panel called "Mobile app" where content for the mobile app can be configured. Detailed information about each sub-category can be found in the separate articles listed in the  Mobile app sub-categories section.
  RememberYves Rocher API documentation for developer use can be accessed under URL 
https://yr-api-doc.netlify.app/ 
Table of contents:
 Enabling the Mobile app
 Mobile app sub-categories
 
 
 Enabling the Mobile app
Mobile app by default is disabled on the selected environment. In order to enable or disable it you have to navigate to:
System > System / Settings > Integrations > Mobile App
Visualization of the mobile app system settings
In the mobile app menu you can find three options:
Enable - A switch that enables or disables the mobile application integration. This switch should be always turned on if the selected country is using the mobile app, as turning it off will cause an issue with API communication between Yves Rocher mobile application and Yves Rocher admin panel.
Gifts of choice - An JSON of gifts of choices, which shows up in the mobile application. The JSON has to be set between two square brackets ( [ ] ) and must include two parameters:
"name" - A name of the gifts of choice section.
"min_cart_value" - A minimum cart value that needs to be met for the selected gift of choice to appear.
"products" - An array of product SKUs that are available in the selected gifts of choice.
  ExampleBelow you can find an example JSON of gifts of choice.
[
{"name": "Gifts from 100 EUR", "min_cart_value": 100, "products": ["P12345", "P12346"]},
{"name": "Gifts from 150 EUR", "min_cart_value": 150, "products": ["P92345", "P92346"]}
]
 Paper Mailing - An JSON of paper mailing products that show up in the mobile application. The JSON has to be set between two curly brackets ( { } ) and must include the following parameters:  
 "ver1" or "ver2" - a version of the paper mailing call
"discount_code" - Selected discount code.
"products" - An array of SKUs that are available in the selected paper mailings. The array contains "SKUs" parameter which contains an array of SKU numbers.
  ExampleBelow you can find an example JSON of gifts of paper mailing.
{
"ver1": {
"discount_code": "ABCDEFG",
"products": [
{"skus": ["P12345", "P12346"]},
{"skus": ["P12345", "P12346"]}
]
},
"ver2": {
"offer_id": "offer_id_1",
"discount_code": "ABCDEFG",
"discount_percentage": 10,
"products": [
{"skus": ["12345","12346","12347"]}
],
"additional": {
"validity": "2024-12-31",
"ean_image": "https://example.com/image.jpg",
"image_small": "https://example.com/image-sm.jpg",
"image_medium": "https://example.com/image-md.jpg",
"image_large": "https://example.com/image-lg.jpg"
}
}
}
  RememberYou can find more about paper mailing api calls in
https://yr-api-doc-staging-v6.netlify.app/api-raml/#mobile_app_paper_mailing_get
https://yr-api-doc-staging-v6.netlify.app/api-raml/#mobile_app_paper_mailing_list_get
 
 
With an enabled mobile app all the categories described in the  Mobile app sub-categories can be used in the mobile application.
 
 
 Mobile app sub-categories
The mobile app content can be managed using the "Mobile app" category in the admin panel. In this category, you will find many different subcategories that will be read by the mobile app and shown on the application.
Visualization of the mobile app sub-categories
Below you will find URLs to the articles of the currently available sub-categories
Carousel
Sub Campaign
Boxes
Homepage products
Articles
Current offers
Cms elements
Cms categories
Catalog
Customer private offers
 

Customers

Customer private offers
Getting started
In this article, you can find information about customer private offers, which allow you to set up private offers that will be visible only to the selected customers. Private offers are promotional offers tailored to the selected group of customers, as they are not activated in the altshop but are set to the customers e-mail addresses.
Visualization of the customer private offer in the customer panel (desktop)
Visualization of the customer private offer in the customer panel (mobile)
To open the customer private offers view, in the administration panel, navigate to:
Customers > Customer private offers
Visualization of the customer private offer tab in the admin panel
 Customer private offer tab
 Creating a customer private offer
 Importing customers to the selected customer private offer
 
 
 Customer private offer tab
In the customer private offer tab, you can find all available private offers and their basic data.
Below you will find a description of possible actions.
Visualization of the list of private customer offers tab
 Filter private offers by their is public? (1) status. Available options are "yes" and "no".
Select the Show X entries (2) field to set the number of private offers, displayed on one page (min 10 / max 100).
The names of the columns (3) that contain information about a given private offer. Each column is susceptible to sorting. To sort the records, click on the title of the column.
ID - Internal identification number of a private offer.
System Name - The system name of the private offer. This field is not visible to the customers, but is used in the customer import. You can learn more about customer import in the  Importing customers to the selected customer private offer chapter
Name - A public name of the offer. This field is visible to the customers.
Start date - the date from which the private offer is visible to the store customers.
End date - the date from which the private offer  is hidden for store customers.
Is public? - The is public? status of a selected private offer.
Actions - Buttons that allow to perform various actions. Available actions are:
Edit - Edits selected private offer. Editing is exactly the same as creating a new one, so you can read more about it in the  Creating a customer private offer chapter
Import emails - Import and assign customer email addresses to the selected private offer. More about importing emails can be found in the  Importing customers to the selected customer private offer chapter.
Delete emails - Removes all assigned customer emails from the selected private offer.
Delete - Removes the selected private offer without the ability to restore it.
Select the Add customer private offer (4) button to go to the adding a new customer private offer. You can learn more about adding a new private offer in the  Creating a customer private offer chapter
Search box(5) where you can search for desired private offer by their system name and name.
Page buttons(6), which allows user to change the page of currently viewed private offers.
 
 
 Creating a customer private offer
A private offer can be created using the Add customer private offer button. Below you will find all the fields that can be edited in the private offer creation
Visualization of the customer private offer creation
Name - the system name of the private offer. This field is not visible to the customers.
Visible name (1) - A public name of the offer. This field is visible to the customers.
Description (2) - Description of a private offer. This field is visible to the customers.
Validity text (3) - A field that accepts a string. Usually in this field, there is a range of dates when the selected offer will be active. This field is visible to the customers
Link (4) - An URL where the picture of the private offer will redirect to when clicked in the customer panel.
Picture (5) - A picture of a private offer visible to the customer in the customer panel
Type (6) - A type of private offer. A type doesn't change anything in how the offer works, but it displays in the customer panel what type the offer is. Available types are:
Use online & in retail
Only online
Only in retail
Altshops - A list of altshops where selected private offer will be visible
Start date - the date from which the private offer is visible to the store customers.
End date - the date from which the private offer is hidden for store customers.
Sort order - Sort order of the private offer. Sort offer sets the order in which offers are visible in the customer panel.
Is active? - Activity switch, which turns the private offer on or off.
Is public? - Switch, which decides if the private offer is public or not. This switch can only be changed when creating a new private offer. Public private offers are available for all logged-in customers and uploading e-mail addresses to them described in  Importing customers to the selected customer private offer is not possible.
While creating a new private offer it is also mandatory to fill out the mobile app fields:
Link type - A type of a link. Available types are:
Product
Category (tag)
Promotion page
Openset page
Custom view
Object ID - An internal ID of a selected object. The ID is dependent on the selected Link type.
Small, Medium and Big images - Three images selected from the gallery.
  RememberYou can find more about the mobile app content configuration in the Mobile app article.
Visualization of the private offer tab in the customer panel
Visualization of the customer private offer in the customer panel
With all mandatory fields filled, you can save created private offer using the save button, or cancel its creation using the cancel button.
 
 
 Importing customers to the selected customer private offer
In order for a private offer to be visible to the customers, their e-mail address must be assigned to the selected offer. In order to do that, you have to navigate to import / export > import
Visualization of the import tab in the import/export section
In the import export you have to select Customer private offer type and attach previously created customer private offer .csv file.
Visualization of the example CSV file of a private offer import
Customer private offer .csv file must contain two fields:
Email - Customer's email address.
Offer ID - System name of the private offer.
With prepared file and selected Customer private offer type, you can import the file in into the TauCeti platform, and the selected e-mail addresses will get automatically assigned to the selected offer IDs.

Import / export

Export / orders list
Getting started
In this article, you can learn about export / orders list functionality, which will allow you to export created e-commerce orders with their basic information. In order to access this module you have to have BOK supervisors, MC business admin, Administrator, Super administrator, or Root group.
You can find the example export file under the URL:
https://knowledge.tauceti-digital.com/orders_export_file_example.xlsx
  Visualization of the exported orders list
To open the Export / orders list view, in the admin panel, navigate to:
Import / export > Export / orders list
All possible operations to perform on the Export / orders list view can be done in the Filters (1) and Export / orders list (2) tabs.
  Visualization of the export / orders list module in the administrator panel
Table of contents:
 Filters section
 Export / orders list section
 Exporting orders to the xlsx
 Filters section
The Filters section allows the sorting of the orders in the export / orders list module, based on the available filters. Orders are not visible by default and it is required to apply any filter first in order to see them. Below you will find a description of each filter.
Visualization of the filters tab
Order ID - Orders internal ID.
Processed on - A range of dates when the order was processed.
Order value - A range of total order values.
Alt shop - Altshop name where the order was placed on.
Status - Current status of the order.
Delivery method - Selected orders delivery method.
Payment method - Selected orders payment method.
Deffered payment status - Current status of the deffered payment.
Check status - Current internal check status of the order.
Paid? - Order payment status.
Customer ID - ID of the customer.
Phone number - Customer's phone number.
Package number - Number of the delivery package.
Only with vouchers - A tickbox that allows seeing only orders with vouchers.
Status (Balikobot) - Order status acquired from Balikobot (when Balikobot is used).
After defining the above filters, select the Apply Filters button to get a list of sites according to the applied filters.
 Export / orders list section
The Export / orders list section allows to further narrow down the list of orders. Below you will find a description of possible actions.
      Visualization of the export / orders list section
 Select the Show X entries (1) field to set the number of orders, displayed on one page (min 10 / max 100).
The names of the columns (2) that contain information about a given order. Each column is susceptible to sorting. To sort the records, click on the title of the column in question.
Order ID - Orders internal ID. By clicking on the order ID you will be redirected to the detailed order information located in the Orders > Orders / list. 
Processed on - A range of dates when the order was processed.
Value - A range of total order values.
First name - Customer's first name.
Last name - Customer's last name.
E-mail - Customer's e-mail address.
Paid? - Order payment status.
DP status - Current status of the deffered payment.
Status - Current status of the order.
Phone number - Customer's phone number.
Package number - Number of the delivery package (Carrier Barcode).
Select the Export to xlsx (3) button to export all filtered orders to the xlsx file. You can learn more about exported xlsx file in the  Exporting orders to the xlsx section
Search box (4) where you can search for desired orders by their ID, first name, last name, e-mail address, status, phone number, and package number.
Page buttons (5), which allow users to change the page of currently viewed orders.
 Exporting orders to the xlsx
By pressing the Export to xlsx button shown in the  Export / orders list section chapter you are able to export all the filtered orders to the xlsx file and download it. 
You can find the example export file under the URL:
https://knowledge.tauceti-digital.com/orders_export_file_example.xlsx
      Visualization of the exported orders=s
Xlsx file contains the following fields:
OrderID - Orders internal ID.
Processed on - A range of dates when the order was processed.
Order_value_gross - A range of total order values.
Customer_first_name - Customer's first name.
Customer_last_name - Customer's last name.
Customer_email - Customer's e-mail address.
Paid - Order payment status.
DP status - Current status of the deffered payment.
Status - Current status of the order.
Customer_mobile - Customer's phone number.
Tracking_code - Number of the delivery package (Carrier Barcode).
Invoice_number - Number of the invoice.
Delivery_street - The street name to which the package will be delivered.
Delivery_building - The building number to which the package will be delivered.
Delivery_flat - The flat number to which the package will be delivered.
Delivery_postal_code - The postal code to which the package will be delivered.
Delivery_city - The city name to whihc the package will be delivered.
Delivery_company_name - Company name defined by the customer when placing the order.
Delivery_tax_id - Tax ID defined by the customer when placing the order.
Delivery_company_id - Company ID defined by the customer when placing the order
Delivery_method - Used delivery method in the order.
Parcel_machine_id - Parcel ID in case of deliveries to the parcel points.
Country_code - Country code of the country from which the order was created (e.g. HU).
Product_list - The list of products separated by pipes (" | "), The list contains its SKU, quantity and price in a SKU;Quantity;Price format. For example: 01569;3;38,90|NOGIFT;1;0,00|60735;5;55,90|59137;1;99,00
Tracking_number - Tracking number of the package provided by the delivery service.
Campaign_code - The campaign code that was used when placing the order by the customer.
Delivery_fee - Delivery fee which customer paid for the selected order.
Payment_fee - Payment fee which customer paid for the selected order.

Export customers
Getting started
In this article, you can find information about Yves Rocher e-commerce customer export with various filter options to a .csv file, that will help to export the exact type of customers that have an account on the Yves Rocher e-commerce platform.
  RememberIt is recommended to not queue multiple exports at the same time, as they are resource heavy, and multiple queues will impose a heavy load on the server.
Visualization of the export customers tab location
Table of contents:
 Exporting the e-commerce customers
 Exported file overview 
 Exporting the e-commerce customers
E-commerce customer export can be found in
Import / Export > Export / customers
Below you can find all filter options to customize your export to your needs.
Visualization of the all available export filters
Registration time - A range of dates when customers registered on an Yves Rocher e-commerce platform.
Update time - A range of dates whenever customer information has been updated.
Birthday - A range of dates of customer birthdays.
Active status - Customers current status. Available statuses are: Inactive, Active, Waiting for activation, One-time
Gender - Customers gender. Available options are Man, Woman, Not specified.
Export specific customers - filter - A filter which allows to specify customers by their:
E-mail
ID
JOY ID
Specific customer data - A field where you should put specific customer data with a ";" separator, data will be filtered according to the selected filter. This field is only visible whenever the Export specific customers - filter is selected. Example (with email filter selected): example@example.com;example2@example.com;example3@example.com
Allowed to make test orders - A Yes / No selection if customers are able to make test orders. This is defined by the "Allowed to make test orders" tickbox in the customers profile.
is MC customer? - A Yes / No selection if a customer has a member club rank. All countries that use Member club functionality for various customer ranks (i.e. on Poland Default / Silver / Gold) are MC customers.
Active status - Customers member club current status. This field only filters the member
club customers
MC title - Member club title assigned to the customers (in the case of Poland it can be T0 / TS / TG). This field only filters the member club customers.
Orders count - A range of numbers of created orders on the website.
Orders placement dates - A range of dates when customers have placed new orders using the Yves Rocher e-commerce platform. Using this filter requires a non-zero "orders count: from" value.
Show MD5 e-mail hash column - Shows customers MD5 e-mail hash column in the report.
Export opt-out_mobile - Shows customers current mobile communication
subscription status.
Export opt_out_email - Shows customers current e-mail communication subscription status.
Export agreements -Exports all available agreements as columns and defines which customers have agreed to the selected agreements.
Extended export - Exports customers with the following additional columns:
Company_name - A company name value from the customer profile (if available).
Tax_id - Tax ID value from the customer profile (if available).
Company_id - Company ID value from the customer profile (if available).
Date_of_registration - registration date on the website in DD-MM-YYYY format.
SOURCE_CUSTOMER_ID - Source from where customer registered.
StreetNumber - A combination of building and flat values in one cell separated by the vertical bar "|" (e.g, 3a | 1)
Export FIDEN2 cards -Exports customers FIDEN2 card information. The exported fields are:
cards_active - A list of customers active FIDEN2 cards
cards_waiting - The number of points waiting to be assigned to the selected customer FIDEN2 cards.
cards_balance - Current FIDEN2 balance
cards_balance_time - A date of last balance change for the selected customer.
Only customers which manually assigned retail card - A tickbox which defines if only customers with manually assigned retail cards should be exported.
With selected filters you can export customers using the Export button or clear all filters by using the Clear filters button.
Visualization of the prepared export file
With exported file you are able to download it to your device using the Download file button.
 Exported file overview
The exported file will be in a .csv format with an export date and hour in it's file name (i.e. customers_2023_08_16_131359)
Visualization of the exported csv file
By default in the exported customers file you can find the following columns:
id - Customers internal ID. Example: 123456
first_name - Customers name. Example: Jan
last_name - Customers surname. Example: Kowalski
street - Main street name. Example: Uliczna
building - Main building number. Example: 123
flat - Main flat number. Example: 2
city - Main city name. Example: Warsaw
postal_code - Main postal code. Example: 12-345
email - Customers e-mail address. Example: test@example.com
mobile - Customers mobile number with a country code. Example: 48123123123
birthday - Customers birthday date. Example: 01-01-1990
gender - Customers gender (if selected). Example: Man
With additional fields dependent on selected options:
md5_email - Customers MD5 email value. Example: 26h2cb31af663cdccaa2779c9d165a0b
opt out mobile - Customers mobile communication current status. If the customer is opted in this value will be empty. If the customer is opted out the value will be set to Opted out.
opt out email - Customers e-mail communication current status. If the customer is opted in this value will be empty. If the customer is opted out the value will be set to Opted out.
Customers agreement status to the selected agreements - These fields will have different column names depending on the country and selected agreements (i.e. terms_of_service_vpi, data_processing_mc). Whenever the customer has agreed to the selected agreement there will be a "Selected" value in the column. If the customer has not agreed to the agreement the field will be empty.
cards_active - A list of customers active FIDEN2 cards. Example: 123456789, 987654321.
cards_waiting - The number of points waiting to be assigned to the selected customer cards. Example: 123
cards_balance - Current FIDEN2 balance Example: 5333
cards_balance_time - A date of last balance change for the selected customer.
Example: 05-08-2023
Company_name - A company name value from the customer profile (if available).
Tax_id - Tax ID value from the customer profile (if available).
Company_id - Company ID value from the customer profile (if available).
Date_of_registration - registration date on the website in DD-MM-YYYY format.
SOURCE_CUSTOMER_ID - Source from where customer registered.
StreetNumber - A combination of building and flat values in one cell separated by the vertical bar "|" (e.g, 3a | 1)

Product catalog export and import
Getting started
In this article, you will learn how to extract a product catalog in the form of CSV files and how to import it back. The overview for each product catalog file is here.
Export can be found in Import / Export > Export / catalog (1)
Import can be found in Import / Export > Import > Type > Catalog mass import (2)
Visualization of the product catalog options in the Import / export module
Table of contents:
Export catalog
Catalog files
Catalog import
How to make mass import
Overview - catalog_product.csv
Overview - catalog_product_description.csv
Overview - catalog_product_attribute.csv
Overview - catalog_product_stock.csv
Overview - dict_tag_catalog_product.csv
Overview - dict_property.csv
Overview - dict_tag.csv
 Overview - catalog_product_category.csv
Overview - alt_shop_catalog_product.csv
 Overview - catalog_product_category.csv
 Overview - dict_tag_catalog_product_remove.csv
 Order of processing files
 
 
 Export catalog
Catalog export has some filtering options for thinning out the results of extracted data.
Visualization of the Catalog export
Alt shop - Chooses for which alt shop the catalog should be exported. If left empty, products from all alt shops will be exported. You can learn more about altshops in the Alt shops - Introduction article.
Product status - Chooses between Active and Inactive products. If left empty, all products will be exported.
Is altshop active? - Choose if the product exported are active on chosen altshop or inactive.
Product SKU - A list of product SKUs. A list of multiple SKUs needs to be separated by commas (i.e. 123456,654321,55555).
Two buttons:
Apply filters - A button, which will apply selected filters and automatically start the download of the filtered products.
Clear filters - A button, which clears all already chosen filters.
Exported files described in  Catalog files section are packed in a .zip file, which needs to be unpacked.
 
 
 Catalog files
The downloaded archive will contain the following files:
alt_shop_catalog_product.csv - Contains data for Alt shops > Products / list (You can find more information about this module in Products / list - browsing and managing products in altshop module article)
catalog_product.csv - Contains data for Catalog > Products / list (More information about this module in [UNDER CONSTRUCTION])
catalog_product_attribute.csv - Contains data for Catalog > Products / list > View product > Add color (More information about this module in [UNDER CONSTRUCTION])
catalog_product_description.csv - Contains data for Catalog > Products / list > View product, Description tab (More information about this module in [UNDER CONSTRUCTION])
catalog_product_meta.csv - Contains data for 
Catalog > Products / list > View product, Metadata tab (More information about this module in [UNDER CONSTRUCTION])
catalog_product_stock.csv - Contains data for Catalog > Products / list > View product, Stock tab (More information about this module in [UNDER CONSTRUCTION])
dict_property.csv - Contains data for Catalog > Properties / list (More information about this module in [UNDER CONSTRUCTION])
dict_tag.csv - Contains data for Catalog > Tags / list (More information about this module in [UNDER CONSTRUCTION])
dict_tag_catalog_product.csv - Contains data for Catalog > Products / list > View product, Tags tab (More information about this module in [UNDER CONSTRUCTION])
catalog_product_category.csv - Contains data for Catalog > Products / list > View product, edit product tab. You can find more information about the category module in Catalog categorization article.
dict_tag_catalog_product_remove.csv - Contains exact same data structure as dict_tag_catalog_product.csv, but it removes the assigned tags from the selected products.
 
 
 Catalog import
All the exported files can be edited and imported back to the administration panel to update catalog data. Files can be imported separately or in groups but their import must always be consolidated in a .zip file. The file names must be exactly the same as defined in this article and they cannot be changed. There are no mandatory files, so it is possible to import only catalog_product_description.csv without any other files as long as it is in the .zip file. Packed .csv files can be in any folder structure as long as file names are not duplicated.
Other file formats than .zip will be rejected and won't be uploaded.
Files specification
Since the imported files directly correspond with the database some rules must be followed while creating and editing import files, here is a general specification for these:
Field type BOOLEAN:
0 - NO
1 - YES
Field type DATE must be in the following format "YYYY-MM-DD"
EOL (End Of Line) column must contain EOL in every row with a product. This column shows our system, that for a selected product its info ends with this column, and the system can move to another row. Here is an example of EOL use:
column1;column2;EOL
“abc”;”abc”;EOL
“cde”;”cde”;EOL
The decimal separator must be a dot "." for example: "199.99"
While editing files in text editors (not spreadsheets) all columns have to be separated by semicolon ";"
STRING field type can be filled with any text and/or number. The only exception to this exists in every field with URL value, these must be strings without any special/regional characters besides "/" as a start to the URL and "_" as a separator for word f.x. "/new_product_sku_123"
 
 
 How to make mass import
Mass import is a product import of a ZIP file that contains prepared .csv files. This operation changes the product data based on their SKU or creates a new product if the selected SKU doesn't exist in the catalog database. You don't need to put every .csv file in the .zip, only the ones that you have modified can be put in the .zip file and then imported. In order to import catalog files, they have to be in CSV format, coded in UTF-8. Go to Import/Export > Import and choose Catalog mass import in the Type.
Visualization of Import / Export, Import
  File *    -  Choose a file, and find your zip archive with CSV files.
Type* - Click and choose Catalog mass import in order to perform the change in the catalog database.
Options - Test import allows for virtual database calculation after importing a chosen archive. You'll be able to check the results of this import by receiving a report for each imported file. Test import won't perform any actual changes in the environment.
Import file - Click to perform an import. The file will start processing right after clicking.
  RememberProduct descriptions can be enriched by HTML and CSS codes.
 
 
 Overview - catalog_product.csv
File catalog_product.csv contain mainly data regarding imported products. Mass import of this file allows to:
Adding new records
Updating records (on a base of unique SKU)
#
Column name
Value type
Max length
Can be empty?
Description
What, if empty
1
SKU
STRING
7
No
Product code
-
2
is_active
BOOLEAN (0/1)
1
No
Is the product visible?
-
3
name
STRING
255
No
Product name
-
4
title
STRING
255
Yes
Title for product
Empty product title
5
short_description
STRING
255
Yes
Short description
Empty description
6
capacity
STRING
125
Yes
Capacity/size of the product
Capacity undefined
7
sort_order
INTEGER
1
Yes
Sort Order
0
8
price
DECIMAL
10,2
No
Catalog price
-
9
f_green_point
BOOLEAN (0/1)
1
Yes
Flag: green point 
0 
10
f_bestseller
BOOLEAN (0/1)
1
Yes 
 Flag: bestseller
0 
11
f_limited_edition
BOOLEAN (0/1)
1
Yes 
 Flag: limited edition
0 
12
 f_set
BOOLEAN (0/1)
1
Yes 
 Flag: set
0 
13
 f_gift
BOOLEAN (0/1)
1
Yes 
Flag: gift
0 
14
 f_gift_choice
BOOLEAN (0/1)
1
Yes 
Flag: gift of choice 
0 
15
f_outlet 
BOOLEAN (0/1)
1
Yes 
Flag: outlet 0
0 
16
is_new_until
DATE
10
Yes 
Date till the product is marked as "new". Should be in a DD-MM-YYY format.
The product won't be marked as "new"
17
friendly_url
STRING
255
Yes 
URL for the product
- 
18
ean
STRING
  13
 
Yes
EAN code. Multiple EANs can be separated by a comma (,). The system verifies in the import process if the typed EAN is in correct EAN-8 or EAN-13 format.
-
19
 EOL
STRING
 3 
No 
Always must be “EOL” 
 -
 
 
 Overview - catalog_product_description.csv
File catalog_product_description.csv contains descriptions for the products. Mass import allows to:
Adding new records
Updating records (on a base of unique SKU)
  Warning  There must be a product in the database with SKU matching the value of the SKU column in order to apply any changes. 
#
Column name
Value type
Max length
Can be empty?
Description
What, if empty
1
SKU
STRING
7
No
Product code
-
2
description_main
STRING
undefined
Yes
Main description
empty description
3
description_effect
STRING
undefined
Yes
Effects description
empty description
4
description_usage
STRING
5
Yes
Usage description
empty description
5
description_ingredient
STRING
undefined
Yes
Ingredients
empty description
6
description_capacity
STRING
undefined
Yes
Type of package and capacity
empty description
7
description_additional_info
STRING
undefined
Yes
Additional information
empty description
8
description_notes
STRING
undefined
Yes
Results
empty description
 9 
 EOL
STRING
 3 
No 
Always must be “EOL” 
 -
  RememberNew lines in descriptions fields will be changed to <br> HTML can be used to customize the text.
 
 
 Overview - catalog_product_attribute.csv
File catalog_product_attribute.csv contains data about color variants of imported products. Mass import allows to:
Adding new records
Updating records (on a base of unique SKU)
  Warning  There must be a product in the database with SKU matching the value of the SKU column in order to apply any changes. If there is no color from the color column in the database then a new color will be created and assigned to the new attribute.
#
Column name
Value type
Max length
Can be empty?
Description
What, if empty
1
SKU_parent
STRING
7
No
Code of the parent product
-
2
SKU
STRING
7
No
Code of the color variant
 - 
3
color
STRING
255
No
Color name
 - 
4
is_active
BOOLEAN (0/1)
1
No
Flag: is active?
 - 
 5 
 EOL
STRING
 3 
No 
Always must be “EOL” 
 -
 
 
 Overview - catalog_product_stock.csv
File catalog_product_stock.csv  contains information about the stock resources of the imported products. Mass import allows to:
Updating records (on a base of unique SKU)
  Warning  There must be a product in the database with SKU matching the value of the SKU column in order to apply any changes.
#
Column name
Value type
Max length
Can be empty?
Description
What, if empty
1
SKU
STRING
7
No
Product code
-
2
stock_value
INTEGER
5
No
Amount of stock value
 - 
3
always_in_stock
BOOLEAN(0/1)
1
Yes
Flag: product is always in stock
 0 
4
min_stock_value
INTEGER
5
Yes
Minimal stock value
Default value from the database
5
warn_stock_value
INTEGER 
 5
 Yes
Stock limit at which administrator will receive a warning about low stock value
Default value from the database 
 6 
 EOL
STRING
 3 
No 
Always must be “EOL” 
 -
 
 
  
 Overview - dict_tag_catalog_product.csv
File dict_tag_catalog_product.csv contains information about tags of imported products. Mass import allows to:
Adding new assignments
Updating already existing assignments
  Warning  There must be a product in the database with SKU matching the value of the SKU column in order to apply any changes. The same applies to tags columns and properties.
#
Column name
Value type
Max length
Can be empty?
Description
What, if empty
1
SKU
STRING
7
No
Product code, if color variant then uses parent code.
-
2
property
STRING
45
No
Property name
 - 
3
tag1
STRING
150
No
Tag name
 - 
4
tag2
STRING
150
Yes
Tag name
 - 
5
tag3
STRING
150
Yes
Tag name
 - 
6
tag4
STRING
150
Yes
Tag name
 - 
7
tag5
STRING
150
Yes
Tag name
 - 
 9 
 EOL
STRING
 3 
No 
Always must be “EOL” 
 -
 
In order to assign more than 5 tags to one product, use another row, here is an example of how to assign 6 tags to SKU1 in property "część ciała":
SKU1;”część ciała”;”twarz”;”włosy”;”dłoNo”;”nogi”;”ramiona”;EOL
SKU1;”część ciała”;”uda”;;;;;EOL
In order to delete a tag from a product add “<delete>” before it. Here is an example of deleting the tag "40+":
 “<delete>40+”
  
  
 Overview - dict_property.csv
File dict_property.csv contains information about properties. Mass import allows:
Adding new properties
#
Column name
Value type
Max length
Can be empty?
Description
What, if empty
1
name
STRING
 45 
No
Property name
-
2
url_name
STRING
 45 
Yes
Friendly URL
 Will be generated automatically from the property name 
3
sort_order
INTEGER
5
No
Sort Order
-
4
is_active
BOOLEAN(0/1)
1
No
Flag: Is this property active?
-
 5 
 EOL
STRING
 3 
No 
Always must be “EOL” 
 -
 
 
 
 Overview - dict_tag.csv
File dict_tag.csv contains information about tags. Mass import allows to:
Adding new tags
  Warning  There must be a property in the database in order to add new tags.
#
Column name
Value type
Max length
Can be empty?
Description
What, if empty
1
property_name
STRING
 45 
No
Nazwa cechy, do której jest przypisany tag
-
2
name
STRING
 150 
No
Nazwa tagu (wartość cechy)
 - 
3
url_name
STRING
 150 
Yes
friendly URL for the tag
Will be generated automatically from the tag name
 4 
 EOL
STRING
 3 
No 
Always must be “EOL” 
 -
  
 
 
 Overview - alt_shop_catalog_product.csv
File alt_show_catalog_product.csv contains information about availability in altshops and discounts counted from catalog prices. Mass import allows to:
Adding new altshop assignments and promotions
Editing existing altshop assignments and promotions
  Warning  Adding values to promotion_price, price_discount and percentage_discount won't be updated if the product is_active=0. Rows is_active=0 serves as a forced deactivation in altshop. It is a good practice to add only alt_shops that products should be active.
#
Column name
Value type
Max length
Can be empty?
Description
What, if empty
1
alt_shop
STRING
undefined
No
Altshop system name
-
2
SKU
STRING
 7
No
Product code
-
3
is_active
BOOLEAN(0/1)
 1
No
Is the product active in altshop
-
4
promotion_price
DECIMAL
 undefined
Yes
Promotion price
No promotion price or set-by-price/percentage discounts
5
price_discount
DECIMAL
 undefined
Yes
Price discount subtracts value from the catalog price
No discount or discounted by promotion price/percentage discount
6
percentage_discount
DECIMAL
2
Yes
Percentage discount counted from catalog price.
No promotion or discounted by promotion price/ price discount
7
promotion_start_date
DATE
undefined
Yes
Information:
date of promotion start
No date of promotion start
8
promotion_end_date
DATE
 undefined 
Yes
Information:
date of promotion end
No date of promotion end
9
promotion_valid_text
STRING
 undefined 
Yes
Text informing about promotion validation
Lack of text even, if promotion start and end dates are present.
10
EOL
STRING
 3 
No 
Always must be “EOL” 
EOL
 
 
 
 Overview - catalog_product_category.csv
File catalog_product_category.csv contains information about categories assigned to the products. Mass import allows to:
  RememberYou can find more information about catalog categories in the Catalog categorization article.
Adding currently present categories to the selected products
Editing categories of the selected products.
#
Column name
Value type
Max length
Can be empty?
Description
What, if empty
1
SKU
STRING
7
No
Product code
-
2
category_path
STRING
 undefined
No
Category path. Path steps need to be separated by a Guillemet ("»") i.e. E-commerce » Włosy » Szampony. The category path should always start with E-commerce.
-
3
is_main
BOOLEAN(0/1)
1
No
A flag that shows if a selected category path for a selected SKU is marked as a main one
-
4
EOL
STRING
 3 
No 
Always must be “EOL” 
EOL
  Warning  Please note that this process overwrites product categories for products that are being edited.
In case the user has the following record already in the database on the website:
SKU
category_path
is_main
EOL
32611
E-commerce » Vůně
1
EOL
and there is a need to add a new category the already existing record also needs to be included in the import.
Example of an incorrect import file that overwrites the product categories:
SKU
category_path
is_main
EOL
32611
E-commerce » Vlasy
0
EOL
When the file looks like that the E-commerce » Vůně will be removed from the product, and only E-commerce » Vlasy will be available after the import.
Example of a correct import file that doesn't overwrite the product categories:
SKU
category_path
is_main
EOL
32611
E-commerce » Vůně
1
EOL
32611
E-commerce » Vlasy
0
EOL
In this case both E-commerce » Vůně and E-commerce » Vlasy will be included in the product 32611 after the import.
 
 Overview - dict_tag_catalog_product_remove.csv
File dict_tag_catalog_product_remove.csv contains a list of SKUs with tags, that should be removed from the product. The content of this file is exactly the same as dict_tag_catalog_product.csv. This file is not automatically created when exporting the product catalog.
Mass import allows to:
Removal of tags from the selected SKUs
#
Column name
Value type
Max length
Can be empty?
Description
What, if empty
1
SKU
STRING
7
No
Product code, if color variant then uses parent code.
-
2
property
STRING
45
No
Property name
 - 
3
tag1
STRING
150
No
Tag name
 - 
4
tag2
STRING
150
Yes
Tag name
 - 
5
tag3
STRING
150
Yes
Tag name
 - 
6
tag4
STRING
150
Yes
Tag name
 - 
7
tag5
STRING
150
Yes
Tag name
 - 
 9 
 EOL
STRING
 3 
No 
Always must be “EOL” 
 -
Tag removal doesn't remove properties by itself. Whenever a product has all of it's tags removed, the property is removed automatically.
For example, if the product has the following propety with a tags:
SKU
property
tag1
tag2
tag3
tag4
tag5
EOL
69726
Péče o tělo
Tělové oleje
Tělové peelingy
 
 
 
EOL
And the dict_tag_catalog_product_remove.csv contains the following data:
SKU
property
tag1
tag2
tag3
tag4
tag5
EOL
69726
Péče o tělo
Tělové peelingy
 
 
 
 
EOL
Tělové peelingy will be removed from the product tags list, but Tělové oleje will remain, which would result with the following record:
SKU
property
tag1
tag2
tag3
tag4
tag5
EOL
69726
Péče o tělo
Tělové oleje
 
 
 
 
EOL
If both tags were removed, then the Péče o tělo property would also be removed from the product, as this product doesn't contain any tags from this property.
 
 
 Order of processing files
The system while importing the files is processing them in a selected order, to make sure there will be no mistakes while importing, like changing the price of a product that doesn't exist in the database. You can find an order of processing below:
Order
File name
1
dict_property.csv
2
dict_tag.csv
3
catalog_product.csv
4
catalog_product_description.csv
5
catalog_product_category.csv
6
catalog_product_attribute.csv
7
catalog_product_meta.csv
8
catalog_product_stock.csv
9
dict_tag_catalog_product.csv
10
alt_shop_catalog_product.csv
11
dict_tag_catalog_product_remove.csv
 

Import / export introduction
Getting started
In this article, you will learn about Import / export module, and possible import or export options.
Import / export module allows importing or exporting of desired data to or from the admin panel. By exporting the data you receive an xlsx, txt, or csv file with selected data within the selected scope. By importing the data you import previously prepared zip, xlsx, txt, or csv file and apply it to the data in the admin panel.
  RememberExporting is an action that allows downloading of certain data from the e-commerce database to the user's device.
Importing is the opposite action of exporting, which allows uploading selected files with selected content and extension from the user's device to the e-commerce database.
Import / export module contains of:
Import sections (1) allow users to import external data in zip, xlsx, txt or csv format to the admin panel database. Import sections are described in  Import options section.
Personal codes generator (2) allows for creating unique codes in bulk amounts, which later can be imported to the personal code database and assigned to the main code. You can find more information about promotional codes and how to generate and import them in the Discount codes article.
Various export options, which will allow you to export e-commerce data to your computer.
Visualization of the import module in import/export
  Warning    Most of the exported data is highly confidential. It contains the personal data of the customers. Thus, all downloaded files should be treated with care and security processes.   
Table of Contents:
Import options
Export options
Extracting files
 
 Import options
Import serves as a tool to update databases, following data can be uploaded:
From the main section Import / export > Import
Catalog mass import - Allows to import a .zip file with product configuration (Catalog > Products, Colors, Properties and Tags; Alt shops > Products / list). You can learn more about products and files used in this import in the Product catalog export and import article.
Newsletter subscribers CSV - A CSV file with a subscribers list with an assignment to selected subscriber groups. (Customers > Subscribers / list).
Address dictionary CSV (complete replace) - Address database, which is used in a zip-code / city / street name recommendations while filling up a customer address on e-commerce platform. (Customers > Address Dictionary). This CSV import completely replaces the old database, so by uploading only one, new address it will replace all of the addresses in the database, and only this one address will be available. 
Please make changes to the entire address database first, and then import it to the admin panel instead of importing singular addresses.
Translations XLSX - List of phrases and translations. (System > Translations / list)
Ingredients - List of ingredients for the lexicon functionality. (Herbarium > Plants, Plant families, Regions)
Vouchers - modification dates (XLSX/CSV) - List with expiration dates for fiden2 codes. (Promotions > Vouchers / list)
Customer private offers - Custom private offers for customers. (Customers > Customer Private Offers). You can find more about private offers in Customer private offers article.
Customer contact database for Consultants - imports XLSX - New contact data for Beauty Advisors.  (Beauty Advisors > Contacts). This import is only available for root users.
Admin user import XLSX - Import new Administrator users (System > Admin / list). This import is only available for root users.
Customer contact database for Consultants update - Updating contact data for Beauty Advisors (Beauty Advisors > Contacts) 
Customer contact database for Consultants update (lite version) - Updating contact data for Beauty Advisors in a simpler, faster version that contains less updateable information regarding customers (Beauty Advisors > Contacts).
POS Users - An xlsx file with Beauty Advisor data, which can be used to update their data. (System > Admin / list). This import is only available for root users.
The other two import options in Import / export module require providing additional data (besides the file itself)
Import / FIDEN2 points - Equivalent of Customers > FIDEN2 / Change card balance but additionally allows for multiple balance changes.
Import / discount codes - Unique personal codes for Promotions > Discount codes / list. You can learn more about this module in the Discount codes article.
 
 
 Export options
Export options allow you to export data from e-commerce platform to your computer. They usually allow exporting of certain types of data or data in a certain date range.
In Import / Export module there are the following exports:
Export / SALESmanago tags - 
Export / catalog - Option to extract product catalog which contains the following files:
alt_shop_catalog_product.csv
catalog_product.csv
catalog_product_attribute.csv
catalog_product_description.csv
catalog_product_meta.csv
catalog_product_stock.csv
dict_property.csv
dict_tag.csv
dict_tag_catalog_product.csv
You can learn about product catalog import/export in the Product catalog export and import article.
Export / customers - Exports customers data in a file:
Customers_date_time.csv
Export / subscribers - Exports customers signed to a newsletter in a file:
newsletter_subscribers_date_time.csv
Export POS users - Exports all Points of Sale users in a file:
pos_users_date_time.xlsx
Export / Jumia - Exports pairs (SKU and links) for Jumia (3rd party sales channel) in a file:
jumia_links_date_time.csv
Export / sales - Exports sales in a range of chosen dates in a file:
sales_date_time.xlsx
Export / FIDEN2 cards - Exports cards for the FIDEN2 points system in a file:
fiden2_cards_date_time.csv
Export / Invoices - Exports invoices in a range of chosen dates in a file:
invoice_report_date_time.xlsx
Export / contacts - Exports contacts for Beauty Advisors in files:
ba_contacts_lite_file_date_time.xlsx
ba_contacts_file_date_time.xlsx
Export / orders - Exports orders made by Beauty Advisors in a file:
ba_orders_lite_file_date_time.xlsx
Export / gift cards payment - Exports orders made with gift cards in a file:
gift_cards_payments_date_time.xlsx
  RememberPart of the name in all of the files "date_time" is written in the same format (f.x. Customers_2022_09_23_133700.csv). This date is always referring to the time of creation.
 
 
Extracting data
Most Export options will have additional filters to thin the results, if none of the filters is used then the whole database from this subject will be extracted. After applying filters small green window will show up with information about the file. Successful export will be reported with the title "File has been exported". The file name will be present (1) and the button to download the file (2).
Visualization of the exporting file status, Import / Export module
In case of a failed import or export user will receive an error message explaining why the error has happened. If the error message says so, or you are not sure about it please contact the Tau Ceti helpdesk regarding this error providing the error message content.
In the case of catalog product import user will receive a report, which can be downloaded. In this report, there will be detailed information regarding every product that has failed to import allowing users to fix the affected .csv files and import them again in a .zip file.
  RememberBe advised that some reports due to a large number of records may take up to several minutes to complete extraction. Do not change the tab during the exporting process.

Export / Invoices
Getting started
In this article, you can learn about export / invoices functionality, which will allow you to export list of orders with their basic invoice and order information. In order to access this module you have to have BOK supervisors, MC business admin, Administrator, Super administrator, or Root group.
You can find the example export file under the URL:
https://knowledge.tauceti-digital.com/invoice_report_example.xlsx
  Visualization of the exported invoices list
To open the invoices export view, in the admin panel, navigate to:
Import / export > Export / Invoices
  Visualization of the export / orders list module in the administrator panel
Table of contents:
Export / Invoices section
Exporting invoices to the xlsx
 Export / Invoices section
The Export / Invoices section allows to filter the exported data. Below you will find a description of possible filters.
      Visualization of the export / orders list section
 Order dates - A range of dates between which the orders should be exported.
Include orders - A dropdown menu that defines what type of orders should be exported. There are three possible options:
With invoices - Exports only orders that contain invoices
Without invoices - Exports only orders that do not have an invoice
All - Exports all orders
Anonymise personal data - A switch that defines if the fields Receiver data and E-mail should be anonymised in the exported xlsx file.
Order and Invoices numbers only - A switch that defines if only Order number and Invoice number should be exported.
With the desired options chosen, you can export the xlsx file using the Apply filters and export button.
 Exporting invoices to the xlsx
By pressing the Apply filters and export button shown in the Export / Invoices section chapter you are able to export all the filtered orders to the xlsx file and download it. 
You can find the example export file under the URL:
https://knowledge.tauceti-digital.com/invoice_report_example.xlsx
      Visualization of the exported orders=s
Xlsx file contains the following fields:
Invoice number - Number of the invoice (if exists)
Order number - Order number of the exported row
Receiver data - Customers personal information. This column contains its Name, Surname, Street number, building number, flat number, postal code and city name.
Email - Customers e-mail address
Order date - Date when the order was placed
Total price inc VAT - Order value with VAT
VAT - Percentage VAT rate
Price without VAT - Order value without VAT
Order status - Current status of the order
Payment Status - Current status of the payment. In case of COD orders the COD value will be displayed
Delivery mode - Type of delivery used
Payment mode - Type of payment used.

Altshops

Activating panel elements in the Alt shops module
Getting started
Some changes in the admin panel require additional activation in the Alt shops module in order to be visible to the customers on the store's website.
Table of contents:
Alt shop
Default alt shop
Activating an element in the Alt shops module
 
 
 Alt shop
  RememberAlt shop - an alternative version of an online store. The main idea of the functionality is to provide the ability to create separate offers like different promotions, product prices, or even with a different activity status of individual page elements (static subpages, promotional pages, products), which are presented to different groups of store customers.
One of the main scenarios for using alt shops is to provide people who participate in Member Club (You can find more about Member club in the [UNDER CONSTRUCTION] article) with a separate offer where they can enjoy a fixed discount, such as 10% off.
Originally, the functionality was also to be used for A/B testing.
Default alt shop
The starting point is always the alt shop with id = 1. This is from the point of view of the system: always existing and always active alt shop.
Often, the default alt shop is defined in the panel by business administrators as “alt shop 0” or “alt shop default”. Because of administrators' habits, it is possible to activate the alt shop default by adding the URL parameter ?yras=0 and ?yras=default to the page address, for example:
https://www.yves-rocher.cz/?yras=0 
https://www.yves-rocher.cz/?yras=default
Visualization of the default alt shop on CZ PROD (Desktop version)
Visualization of the default alt shop on CZ PROD (Mobile version)
  
 
 Activating an element in the Alt shops module
Most of the changes made to the elements of the administration panel require activating them in the altshops module. Note that newly created elements are inactive by default in all alt shops. In the following example, you will learn how to activate a CMS page (More about CMS pages can be found in the [UNDER CONSTRUCTION] article). 
To activate a CMS page in the Altshop module, in the administration panel navigate to:
Alt shops > Pages / list
Visualization of the alt shops > pages / list section in the admin panel
Then, in the Select page section, in the Search field (2) find the CMS page you want to activate. After searching, you will find a list of all Altshops on which the desired page can be activated. If you would like to activate the CMS page in only one of the Alt shops, set the switch to “ON” (3) next to the record in question. If you would like to change the activity in bulk, select the fields of interest (1), then choose the status (active/inactive) (4) you want to assign to the selected pages. In the last step, select the Set for selected button to change the defined status to the selected pages, or select the Set for all button to change the activity for all CMS currently filtered CMS Pages.
  RememberPutting the page name in the search field doesn't mean that pages are filtered. When using the Set for all button, remember to filter the pages in the Filter tab.
  RememberIn order to manage the list of CMS pages in the Alt shop module more efficiently, please refer to the Description of the Pages / list module (Alt shops) article.
Visualization of the pages / list in the alt shops module
 
  Warning    If filters are not applied to the CMS pages displayed, the Set for all option will assign the desired action to all pages available in the database. Please be cautious with this setting, as activating every possible CMS page or block might break other active pages or blocks.

Narzędzia CMS

Bloki CMS wprowadzenie
 Wprowadzenie
Panel administracyjny umożliwia tworzenie bloków CMS, które mogą występować na stronie głównej (w nagłówku strony, w sliderach, między nagłówkiem a stopką oraz w stopce) a także na stronach docelowych sklepu. Bloki charakteryzują się odmiennymi parametrami oraz własciwościami. Każdy z nich został opisany w osobnych artykułach.
Wyróżniamy 2 główne miejsca występowania CMS bloków:
Bloki wystepujące na stronie głównej:
Wykaz bloków CMS występujących w nagłówku strony
Wykaz bloków CMS występujących w sliderach
Wykaz bloków CMS występujących między nagłówkiem a stopką strony
Wykaz bloków CMS występujących w stopce strony
Bloki wystepujące poza stroną główną
Wykaz bloków CMS znajdujących poza stroną główną 
  ZapamiętajWięcej informacji na temat struktury sklepu znajdziesz w artykule Budowa strony sklepu.
  ZapamiętajOpis sekcji Bloki/lista oraz procesu dodawania i edycji CMS bloku został opisany w artykułach:
- Opis sekcji Bloki / lista
- Dodawanie i edycja CMS bloku
Spis treści:
 Czym jest CMS block
 
 Czym jest CMS block
CMS to skrót od anglojęzycznej nazwy "Content Management System" co oznacza "System Zarządzania Treścią". Bloki CMS zawierają fragmenty kodu HTML, który administratorzy panelu, z odpowiednimi uprawnieniami, mogą dodawać oraz edytować go według potrzeb. Odpowiednio skonfigurowany blok, może zostać umieszczony na witrynie sklepu, w predefiniowanym miejscu. Bloki doskonale sprawdzają się do przechowywania treści, takich jak: banery, grafiki, teksty a nawet filmy video, by w prosty i przejrzysty sposób, moć zarządzać treścią witryny sklepu. Poniżej znajdziesz wizualizację bloku CMS, występującego na stronie głównej sklepu.
   
Wizualizacja bloku CMS na stronie głównej sklepu Yves Rocher (wersja desktop)
 
   
Wizualizacja bloku CMS na stronie głównej sklepu Yves Rocher (wersja mobile)

Wykaz bloków CMS znajdujących poza stroną główną
 Wprowadzenie
Panel administracyjny umożliwia tworzenie różnych rodzajów bloków CMS, charakteryzujących się odmiennymi parametrami i miejscem występowania na witrynie sklepu. Większość bloków zlokalizowana jest na stronie głównej sklepu. Więcej na temat jej budowy znajdziesz w artykule Budowa strony sklepu.
   
Wizualizacja strony głównej Yves Rocher (wersja desktop)
 
   
Wizualizacja strony głównej Yves Rocher (wersja mobile)
Poniższy artykuł poświęcony jest blokom występującym poza stroną główną. Pozostałe rodzaje bloków CMS zostały opisane w poszczególnych artykułach:
Wykaz bloków CMS występujących w nagłówku strony
Wykaz bloków CMS występujących w sliderach
Wykaz bloków CMS występujących w stopce strony
Wykaz bloków bloków CMS znajdujących poza stroną główną 
Dodatkowe informacji na temat bloków CMS uzyskasz w artykułach:
Dodawanie i edycja CMS bloku
Opis modułu Bloki / lista
 
 
 Bloki CMS występujące poza stroną główną
Bloki CMS zlokalizowane poza stroną główną dzielą się na bloki mobilne oraz bloki desktopowe. Poniżej znajdziesz wykaz bloków dla obu wersji:
Bloki desktopowe:

Wykaz bloków CMS występujących w stopce strony
 Wprowadzenie
Poniższy artykuł poświęcony jest blokom CMS występujących w stopce strony. Pozostałe rodzaje bloków CMS zostały opisane w poszczególnych artykułach:
Bloki CMS występujące w nagłówku strony.
Bloki CMS występujące w sliderach.
Bloki CMS występujące między nagłówkiem a stopką strony.
Bloki CMS występujące poza stroną główną.
  ZapamiętajWięcej informacji na temat struktury sklepu znajdziesz w artykule Budowa strony sklepu.
  ZapamiętajOpis sekcji Bloki/lista oraz procesu dodawania i edycji CMS bloku został opisany w artykułach:
- Opis sekcji Bloki / lista
- Dodawanie i edycja CMS bloku
   Wizualizacja strony głównej Yves Rocher (wersja desktop)
   Wizualizacja strony głównej Yves Rocher (wersja mobile)
 
Spis treści:
 Bloki CMS występujące w stopce strony
 
 
 Bloki CMS występujące w stopce strony
Za pomocą panelu administracyjnego jesteś w stanie wpłynąć na wygląd stopki, edytując zlokalizowane w niej bloki CMS. Aby lepiej zrozumieć jej budowę, poniżej znajdziesz wizualizację, na której zaznaczono wszystkie bloki występujące w stopce desktopowej i mobilnej. 
Wykaz bloków desktopowych:
   Wizualizacja stopki na stronie głównej sklepu Yves Rocher (wersja desktop)
(1) - blok "new layout footer / advantages icons"
(2) - blok "new layout footer / new layout footer / client services"
(3) - blok "new layout footer / column 1"
(4) - blok "new layout footer / column 2"
(5) - blok "new layout footer / column 3"
(6) - blok "new layout footer / column 4"
(7) - blok "new layout footer / legal info"
(8) - blok "desktop / footer / green footer"
Wykaz bloków mobilnych:
   Wizualizacja stopki na stronie głównej sklepu Yves Rocher (wersja mobile)
(9) - blok "mobile / footer / green footer"
(10) - blok "mobile footer navigation"
 
 
 Blok new layout footer / advantages icons
Blok new layout footer / advantages icons dodany z poziomu panelu administracyjnego, na witrynie sklepu wygląda następująco:
 
  Wizualizacja CMS bloku (new layout footer / advantages icons) na witrynie sklepu
W celu zarządzania blokiem new layout footer / advantages icons przejdź do:
CMS > Bloki / lista
Następnie w polu wyszukiwania znajdż blok o nazwie "new layout footer / advantages icons", po czym wybierz przycisk Edytuj. Zostaniesz przeniesiony do okna edycji bloku, gdzie w sekcji Treść będziesz mógł edytować jego zawartość jak na wizualizacji poniżej.
   
Wizualizacja widoku Popraw blok (new layout footer / advantages icons) w panelu administracyjnym
 
 
 Blok new layout footer / new layout footer / client services
Blok new layout footer / client services dodany z poziomu panelu administracyjnego, na witrynie sklepu wygląda następująco:
   
Wizualizacja CMS bloku (new layout footer / client services) na witrynie sklepu
W celu zarządzania blokiem  new layout footer / client services przejdź do:
CMS > Bloki / lista
Następnie w polu wyszukiwania znajdż blok o nazwie " new layout footer / client services", po czym wybierz przycisk Edytuj. Zostaniesz przeniesiony do okna edycji bloku, gdzie w sekcji Treść będziesz mógł edytować jego zawartość jak na wizualizacji poniżej.
   
Wizualizacja widoku Popraw blok (new layout footer / client services) w panelu administracyjnym
 
 
 Blok new layout footer / column 1
Blok new layout footer / column 1 dodany z poziomu panelu administracyjnego, na witrynie sklepu wygląda następująco:
   
Wizualizacja CMS bloku (new layout footer / column 1) na witrynie sklepu
W celu zarządzania blokiem  new layout footer / column 1 przejdź do:
CMS > Bloki / lista
Następnie w polu wyszukiwania znajdż blok o nazwie " new layout footer / column 1", po czym wybierz przycisk Edytuj. Zostaniesz przeniesiony do okna edycji bloku, gdzie w sekcji Treść będziesz mógł edytować jego zawartość jak na wizualizacji poniżej.
   
Wizualizacja widoku Popraw blok (new layout footer / column 1) w panelu administracyjnym
 
 
 Blok new layout footer / column 2
Blok new layout footer / column 2 dodany z poziomu panelu administracyjnego, na witrynie sklepu wygląda następująco:
   
Wizualizacja CMS bloku (new layout footer / column 2) na witrynie sklepu
W celu zarządzania blokiem  new layout footer / column 2 przejdź do:
CMS > Bloki / lista
Następnie w polu wyszukiwania znajdż blok o nazwie " new layout footer / column 2", po czym wybierz przycisk Edytuj. Zostaniesz przeniesiony do okna edycji bloku, gdzie w sekcji Treść będziesz mógł edytować jego zawartość jak na wizualizacji poniżej.
   
Wizualizacja widoku Popraw blok (new layout footer / column 2) w panelu administracyjnym
 
 
 Blok new layout footer / column 3
Blok new layout footer / column 3 dodany z poziomu panelu administracyjnego, na witrynie sklepu wygląda następująco:
   
Wizualizacja CMS bloku (new layout footer / column 3) na witrynie sklepu
W celu zarządzania blokiem  new layout footer / column 3 przejdź do:
CMS > Bloki / lista
Następnie w polu wyszukiwania znajdż blok o nazwie " new layout footer / column 3", po czym wybierz przycisk Edytuj. Zostaniesz przeniesiony do okna edycji bloku, gdzie w sekcji Treść będziesz mógł edytować jego zawartość jak na wizualizacji poniżej.
   
Wizualizacja widoku Popraw blok (new layout footer / column 3) w panelu administracyjnym
 
 
 Blok new layout footer / column 4
Blok new layout footer / column 4 dodany z poziomu panelu administracyjnego, na witrynie sklepu wygląda następująco:
   
Wizualizacja CMS bloku (new layout footer / column 4) na witrynie sklepu
W celu zarządzania blokiem  new layout footer / column 4 przejdź do:
CMS > Bloki / lista
Następnie w polu wyszukiwania znajdż blok o nazwie "new layout footer / column 4", po czym wybierz przycisk Edytuj. Zostaniesz przeniesiony do okna edycji bloku, gdzie w sekcji Treść będziesz mógł edytować jego zawartość jak na wizualizacji poniżej.
   
Wizualizacja widoku Popraw blok (new layout footer / column 4) w panelu administracyjnym
 
 
 Blok new layout footer / legal info
Blok new layout footer / legal info dodany z poziomu panelu administracyjnego, na witrynie sklepu wygląda następująco:
   
Wizualizacja CMS bloku (new layout footer / legal info) na witrynie sklepu
W celu zarządzania blokiem new layout footer / legal info przejdź do:
CMS > Bloki / lista
Następnie w polu wyszukiwania znajdż blok o nazwie "new layout footer / legal info", po czym wybierz przycisk Edytuj. Zostaniesz przeniesiony do okna edycji bloku, gdzie w sekcji Treść będziesz mógł edytować jego zawartość jak na wizualizacji poniżej.
   
Wizualizacja widoku Popraw blok (new layout footer / legal info) w panelu administracyjnym
 
 
 Blok desktop / footer / green footer
Blok desktop / footer / green footer dodany z poziomu panelu administracyjnego, na witrynie sklepu wygląda następująco:
   
Wizualizacja CMS bloku (desktop / footer / green footer) na witrynie sklepu
W celu zarządzania blokiem desktop / footer / green footer przejdź do:
CMS > Bloki / lista
Następnie w polu wyszukiwania znajdż blok o nazwie "desktop / footer / green footer", po czym wybierz przycisk Edytuj. Zostaniesz przeniesiony do okna edycji bloku, gdzie w sekcji Treść będziesz mógł edytować jego zawartość jak na wizualizacji poniżej.
   
Wizualizacja widoku Popraw blok (desktop / footer / green footer) w panelu administracyjnym
 
 
 Blok desktop / footer / green footer
Blok desktop / footer / green footer dodany z poziomu panelu administracyjnego, na witrynie sklepu wygląda następująco:
   
Wizualizacja CMS bloku (desktop / footer / green footer) na witrynie sklepu
W celu zarządzania blokiem desktop / footer / green footer przejdź do:
CMS > Bloki / lista
Następnie w polu wyszukiwania znajdż blok o nazwie "desktop / footer / green footer", po czym wybierz przycisk Edytuj. Zostaniesz przeniesiony do okna edycji bloku, gdzie w sekcji Treść będziesz mógł edytować jego zawartość jak na wizualizacji poniżej.
   
Wizualizacja widoku Popraw blok (desktop / footer / green footer) w panelu administracyjnym
 
 
 Blok mobile / footer / green footer
Blok mobile / footer / green footer dodany z poziomu panelu administracyjnego, na witrynie sklepu wygląda następująco:
   
Wizualizacja CMS bloku (mobile / footer / green footer) na witrynie sklepu
W celu zarządzania blokiem mobile / footer / green footer przejdź do:
CMS > Bloki / lista
Następnie w polu wyszukiwania znajdż blok o nazwie "mobile / footer / green footer", po czym wybierz przycisk Edytuj. Zostaniesz przeniesiony do okna edycji bloku, gdzie w sekcji Treść będziesz mógł edytować jego zawartość jak na wizualizacji poniżej.
   
Wizualizacja widoku Popraw blok (mobile / footer / green footer) w panelu administracyjnym
 
 
 Blok mobile footer navigation
Blok mobile footer navigation dodany z poziomu panelu administracyjnego, na witrynie sklepu wygląda następująco:
   
Wizualizacja CMS bloku (mobile footer navigation) na witrynie sklepu
W celu zarządzania blokiem mobile footer navigation przejdź do:
CMS > Bloki / lista
Następnie w polu wyszukiwania znajdż blok o nazwie "mobile footer navigation", po czym wybierz przycisk Edytuj. Zostaniesz przeniesiony do okna edycji bloku, gdzie w sekcji Treść będziesz mógł edytować jego zawartość jak na wizualizacji poniżej.
   
Wizualizacja widoku Popraw blok (mobile footer navigation) w panelu administracyjnym

Wykaz bloków CMS występujących między nagłówkiem a stopką strony
 Wprowadzenie
Poniższy artykuł poświęcony jest blokom CMS występujących między nagłówkiem a stopką strony. Pozostałe rodzaje bloków CMS zostały opisane w poszczególnych artykułach:
Wykaz bloków CMS występujących w nagłówku strony
Wykaz bloków CMS występujących w sliderach
Wykaz bloków CMS występujących w stopce strony
Wykaz bloków bloków CMS znajdujących poza stroną główną
  ZapamiętajWięcej informacji na temat struktury sklepu znajdziesz w artykule Budowa strony sklepu.
  ZapamiętajOpis sekcji Bloki/lista oraz procesu dodawania i edycji CMS bloku został opisany w artykułach:
- Opis sekcji Bloki / lista
- Dodawanie i edycja CMS bloku
   Wizualizacja strony głównej Yves Rocher (wersja desktop)
   Wizualizacja strony głównej Yves Rocher (wersja mobile)
 
Bloki CMS zlokalizowane między nagłówkiem a stopką strony dzielą się na bloki mobilne oraz bloki desktopowe. Poniżej znajdziesz wykaz bloków dla obu wersji.
Spis treści:
Bloki desktopowe:
new layout index / below bestsellers 1
new layout index / below bestsellers 2
 new layout index / me & my shop / box only one wide
new layout index / below "my store and me" 
 new layout index / above "my store and me"
new layout index / me & my shop / box 1
new layout index / me & my shop / box 2
new layout index / me & my shop / box 3
Bloki mobilne:
 Blok mobile / index / promotion dates info
 Blok mobile / index / me & my shop
 Blok mobile / index / beauty lessons
 Blok mobile / index / social
 
 
 Blok new layout index / below bestsellers 1
Blok new layout index / below bestsellers 1 (1) dodany z poziomu panelu administracyjnego, na witrynie sklepu wygląda następująco:
   Wizualizacja CMS bloku (new layout index / below bestsellers 1) na witrynie sklepu
W celu zarządzania blokiem new layout index / below bestsellers 1 przejdź do:
CMS > Bloki / lista
Następnie w polu wyszukiwania znajdż blok o nazwie "new layout index / below bestsellers 1", po czym wybierz przycisk Edytuj. Zostaniesz przeniesiony do okna edycji bloku, gdzie w sekcji Treść będziesz mógł edytować jego zawartość jak na wizualizacji poniżej.
   
Wizualizacja widoku Popraw blok (new layout index / below bestsellers 1) w panelu administracyjnym
 
 
 Blok new layout index / below bestsellers 2
Blok new layout index / below bestsellers 2 (1) dodany z poziomu panelu administracyjnego, na witrynie sklepu wygląda następująco:
Wizualizacja CMS bloku (new layout index / below bestsellers 2) na witrynie sklepu
W celu zarządzania blokiem new layout index / below bestsellers 2 przejdź do:
CMS > Bloki / lista
Następnie w polu wyszukiwania znajdż blok o nazwie "new layout index / below bestsellers 2", po czym wybierz przycisk Edytuj. Zostaniesz przeniesiony do okna edycji bloku, gdzie w sekcji Treść będziesz mógł edytować jego zawartość jak na wizualizacji poniżej.
   
Wizualizacja widoku Popraw blok (new layout index / below bestsellers 2) w panelu administracyjnym
 
 
 Blok new layout index / me & my shop / box only one wide
Blok new layout index / me & my shop / box only one wide(1) dodany z poziomu panelu administracyjnego, na witrynie sklepu wygląda następująco:
Wizualizacja CMS bloku (new layout index / me & my shop / box only one wide) na witrynie sklepu
W celu zarządzania blokiem new layout index / me & my shop / box only one wide przejdź do:
CMS > Bloki / lista
Następnie w polu wyszukiwania znajdż blok o nazwie "new layout index / me & my shop / box only one wide", po czym wybierz przycisk Edytuj. Zostaniesz przeniesiony do okna edycji bloku, gdzie w sekcji Treść będziesz mógł edytować jego zawartość jak na wizualizacji poniżej.
   
Wizualizacja widoku Popraw blok (new layout index / me & my shop / box only one wide) w panelu administracyjnym
 
 
 Blok new layout index / below "my store and me"
Blok new layout index / below "my store and me" (1) dodany z poziomu panelu administracyjnego, na witrynie sklepu wygląda następująco:
Wizualizacja CMS bloku (new layout index / below "my store and me") na witrynie sklepu
W celu zarządzania blokiem new layout index / below "my store and me" przejdź do:
CMS > Bloki / lista
Następnie w polu wyszukiwania znajdż blok o nazwie "new layout index / below "my store and me"", po czym wybierz przycisk Edytuj. Zostaniesz przeniesiony do okna edycji bloku, gdzie w sekcji Treść będziesz mógł edytować jego zawartość jak na wizualizacji poniżej.
   
Wizualizacja widoku Popraw blok (new layout index / below "my store and me") w panelu administracyjnym
 
 
 Blok new layout index / above "my store and me"
Blok new layout index / above "my store and me"(1) dodany z poziomu panelu administracyjnego, na witrynie sklepu wygląda następująco:
Wizualizacja CMS bloku (new layout index / above "my store and me") na witrynie sklepu
W celu zarządzania blokiem new layout index / above "my store and me" przejdź do:
CMS > Bloki / lista
Następnie w polu wyszukiwania znajdż blok o nazwie "new layout index / above "my store and me"", po czym wybierz przycisk Edytuj. Zostaniesz przeniesiony do okna edycji bloku, gdzie w sekcji Treść będziesz mógł edytować jego zawartość jak na wizualizacji poniżej.
   
Wizualizacja widoku Popraw blok (new layout index / above "my store and me") w panelu administracyjnym
 
 
 Blok new layout index / me & my shop / box 1
Blok new layout index / me & my shop / box 1 (1) dodany z poziomu panelu administracyjnego, na witrynie sklepu wygląda następująco:
Wizualizacja CMS bloku (new layout index / me & my shop / box 1) na witrynie sklepu
W celu zarządzania blokiem new layout index / me & my shop / box 1 przejdź do:
CMS > Bloki / lista
Następnie w polu wyszukiwania znajdż blok o nazwie "new layout index / me & my shop / box 1", po czym wybierz przycisk Edytuj. Zostaniesz przeniesiony do okna edycji bloku, gdzie w sekcji Treść będziesz mógł edytować jego zawartość jak na wizualizacji poniżej.
   
Wizualizacja widoku Popraw blok (new layout index / me & my shop / box 1) w panelu administracyjnym
 
 
 Blok new layout index / me & my shop / box 2
Blok new layout index / me & my shop / box 2 (1) dodany z poziomu panelu administracyjnego, na witrynie sklepu wygląda następująco:
Wizualizacja CMS bloku (new layout index / me & my shop / box 2) na witrynie sklepu
W celu zarządzania blokiem new layout index / me & my shop / box 2 przejdź do:
CMS > Bloki / lista
Następnie w polu wyszukiwania znajdż blok o nazwie "new layout index / me & my shop / box 2", po czym wybierz przycisk Edytuj. Zostaniesz przeniesiony do okna edycji bloku, gdzie w sekcji Treść będziesz mógł edytować jego zawartość jak na wizualizacji poniżej.
   
Wizualizacja widoku Popraw blok (new layout index / me & my shop / box 2) w panelu administracyjnym
 
 
 Blok new layout index / me & my shop / box 3
Blok new layout index / me & my shop / box 3 (1) dodany z poziomu panelu administracyjnego, na witrynie sklepu wygląda następująco:
Wizualizacja CMS bloku (new layout index / me & my shop / box 3) na witrynie sklepu
W celu zarządzania blokiem new layout index / me & my shop / box 3 przejdź do:
CMS > Bloki / lista
Następnie w polu wyszukiwania znajdż blok o nazwie "new layout index / me & my shop / box 3", po czym wybierz przycisk Edytuj. Zostaniesz przeniesiony do okna edycji bloku, gdzie w sekcji Treść będziesz mógł edytować jego zawartość jak na wizualizacji poniżej.
   
Wizualizacja widoku Popraw blok (new layout index / me & my shop / box 3) w panelu administracyjnym
 
 
 Blok mobile / index / promotion dates info
Blok mobile / index / promotion dates info (1) dodany z poziomu panelu administracyjnego, na witrynie sklepu wygląda następująco:
Wizualizacja CMS bloku (mobile / index / promotion dates info) na witrynie sklepu
W celu zarządzania blokiem mobile / index / promotion dates info przejdź do:
CMS > Bloki / lista
Następnie w polu wyszukiwania znajdż blok o nazwie "mobile / index / promotion dates info", po czym wybierz przycisk Edytuj. Zostaniesz przeniesiony do okna edycji bloku, gdzie w sekcji Treść będziesz mógł edytować jego zawartość jak na wizualizacji poniżej.
   
Wizualizacja widoku Popraw blok (mobile / index / promotion dates info) w panelu administracyjnym
 
 
 Blok mobile / index / me & my shop
Blok mobile / index / me & my shop (1) dodany z poziomu panelu administracyjnego, na witrynie sklepu wygląda następująco:
Wizualizacja CMS bloku (mobile / index / me & my shop) na witrynie sklepu
W celu zarządzania blokiem mobile / index / me & my shop przejdź do:
CMS > Bloki / lista
Następnie w polu wyszukiwania znajdż blok o nazwie "mobile / index / me & my shop", po czym wybierz przycisk Edytuj. Zostaniesz przeniesiony do okna edycji bloku, gdzie w sekcji Treść będziesz mógł edytować jego zawartość jak na wizualizacji poniżej.
   
Wizualizacja widoku Popraw blok (mobile / index / me & my shop) w panelu administracyjnym
 
 
 Blok mobile / index / beauty lessons
Blok mobile / index / beauty lessons (1) dodany z poziomu panelu administracyjnego, na witrynie sklepu wygląda następująco:
Wizualizacja CMS bloku (mobile / index / beauty lessons) na witrynie sklepu
W celu zarządzania blokiem mobile / index / beauty lessons przejdź do:
CMS > Bloki / lista
Następnie w polu wyszukiwania znajdż blok o nazwie "mobile / index / beauty lessons", po czym wybierz przycisk Edytuj. Zostaniesz przeniesiony do okna edycji bloku, gdzie w sekcji Treść będziesz mógł edytować jego zawartość jak na wizualizacji poniżej.
   
Wizualizacja widoku Popraw blok (mobile / index / beauty lessons) w panelu administracyjnym
 
 
 Blok mobile / index / social
Blok mobile / index / social (1) dodany z poziomu panelu administracyjnego, na witrynie sklepu wygląda następująco:
Wizualizacja CMS bloku (mobile / index / social) na witrynie sklepu
W celu zarządzania blokiem mobile / index / social przejdź do:
CMS > Bloki / lista
Następnie w polu wyszukiwania znajdż blok o nazwie "mobile / index / social", po czym wybierz przycisk Edytuj. Zostaniesz przeniesiony do okna edycji bloku, gdzie w sekcji Treść będziesz mógł edytować jego zawartość jak na wizualizacji poniżej.
   
Wizualizacja widoku Popraw blok (mobile / index / social) w panelu administracyjnym

Beauty Advisor

Beauty Advisor - exports
Getting started
The administrative panel allows the following actions:
export of BA consultants 
export of BA customers 
export of BA orders
Descriptions of each of the above have been included in the following chapters of the article.
  RememberExport - an operation that allows to generate data stored in the administration panel, to a file, usually with the extensions .xlsx or .csv, which can be downloaded to a local disk.
   RememberFor basic information on BA commerce, see the article Beauty Advisor - getting started.
Table of contents:
 Export of BA consultants
 Export of BA customers
Full export version
Lite version
 Export of BA orders
Full export version
Lite version
 
 
 Export of BA consultants
BA consultants can be exported by navigating to the section Import / Export> Export / POS Users (1). Navigating to the tab will automatically initiate the export operation and you will receive a screen with a summary of the performed operation and the option to download the finished file (2) to a local disk.
Screen with a summary of the export operation
 
The generated file contains the following data. A description of each parameter can be found in the article Beauty Advisor - mass imports (chapter: "Mass Update of BA Consultants").
id
first_name
last_name
email
mobile
active
last_login_date
group_name
pos_reports_number
ba_pos_number
default_altshop_id
 
 
 Export of BA customers
The export of BA customers is possible in the section Import / Export> Export / contacts. Due to the current limitations when exporting Excel files, there are two possible types of exports (export in full version (2) and in lite version (3)). Each export type is described in the following chapter. Current exports are limited to approximately 100,000 rows. This limit will be extended with subsequent updates.
In the Filters tab (1), the scope of the generated data can be narrowed down as needed. For a description of the parameters in the tab, see the article Beauty Advisor > Contacts - viewing and managing BA clients. The table and possible actions in the tab Beauty Advisor / Contacts are described in the article Beauty Advisor > Contacts - viewing and managing BA clients.
Section Import/Export > Export / contacts
 
Full export version
The full version generates all BA customer data available in the panel. Below you will find a list of parameters included in the generated export file. Each parameter is described in the article Beauty Advisor - mass imports (chapter: "Mass update of BA customers").
LAST_CUSTOMER_CODE 
FIRST_NAME
NAME 
PHONE
ACTUAL_SHOP
RANKING
CITY
POSTAL_CODE
STREET1
 HOUSE_NUMBER
BOX_NUMBER
EMAIL
DATE_BIRTH
LPD_BA
LPD_ECOMMERCE
LPD_RETAIL
LA
ID
TOP1_TO_PRODUCT
TOP1_TO_PRODUCT_LABEL
TOP1_TO_LPD_TXT
TOP1_TO_PRODUCT_PRICE
TOP1_TO_TO
TOP1_TO_QT
Lite version
The generated file in the lite version contains four columns with data of BA customers. Below you will find a list of parameters included in the generated export file. Each parameter is described in the article Beauty Advisor - mass imports (chapter: "Mass update of BA customers").
ACTUAL_SHOP 
RANKING
LPD_RETAIL
ID
 
 
 Export of BA orders
There are two types of NA order exports (export in full version and in lite version). Each type is described in the chapter below.
Full export version
A full version of the export of BA orders is possible in the section Beauty Advisor > Orders / list, by selecting the Export to XLSX button (1). The scope of the generated data can be narrowed down using the criteria available in the Filters tab. All parameters appearing in the tab are described in the article Beauty Advisor > Orders / list - viewing and handling orders.
 
Section Beauty Advisor > Orders / list
 
Below you will find a list of parameters included in the generated export file. Each parameter is described in the article Beauty Advisor > Orders / list - viewing and handling orders.
ID
Processed on
Value 
First name
Last name
E-mail
Paid?
Package status 
Status
 
Lite version
BA orders in lite version can be exported in the section Import/Export> Export / orders, by selecting the Export to XLSX button (2). The scope of the generated data can be narrowed down using the criterion Processed on, available in the tab Filters (1).
 
Section Import / Export> Export / orders 
 
Below you will find a list of parameters included in the generated export file.
Shop ID - POS store number. More details about POS stores are available in the article Beauty Advisor > POS retail – store management.
Consultant - BA consultant e-mail address.
Order date - BA order placement date.
Product - Product SKU.
Quantity - the number of pieces of the product in the order.
Catalogue price - product catalog price. More information on the list price can be found in the article Beauty Advisor > New order - description of the ordering process.
Price - order price, including discounts. You can find more information about discounts and rebates in the article Beauty Advisor > New order - description of the ordering process.
Order number - BA order number in the administrative panel.

Beauty Advisor - message templates
Getting started
The SMS templates section in the Customers module contains a table with a list of SMS templates that are used on the BA customer data preview screen (for details, see Beauty Advisor > Contacts - viewing and managing BA clients). The table allows to activate the template, define the type of template, edit, delete and add a new item. The templates are sortable and each item can be managed using the drag and drop method.
 
SMS Templates section in the Beauty Advisor module
Table of contents:
 Viewing and managing templates SMS
 Adding a new SMS template
 
 
 Viewing and managing templates SMS
Below you will find a description of the table and the actions that can be performed in the SMS templates tab.
SMS templates tab in the Customers > SMS templates section
(1) Show X entries - option to change the number of displayed SMS templates on one page (available range from 10 to 100).
(2) - columns containing information on SMS templates.  Each column is sortable:
ID - unique number of the SMS template in the administration panel. Parameter value generated by the application.
Name - name of the SMS template, displayed on the button on the BA client preview screen (6). More details is available in the article Beauty Advisor > Contacts - viewing and managing BA clients.
Send SMS column on the BA customer preview screen
Content - text of the SMS that will be sent to the BA client.
Is active? - the ability to activate and deactivate the SMS template.
Type - defining the group for which the template will be visible in the column Send SMS on the BA client preview screen. For more on BA Consultant Groups, see Beauty Advisor - getting started.
Sort order - parameter defining the sequence of buttons on the client’s preview screen (6). The template with the assigned value 0 will be in the first position.
Creation Time - CMS template creation date.
Update Time - data ostatniej edycji szablonu CMS.
Actions 
Edit - select the button to go to the SMS template editing window.
Delete - select the button to delete the SMS template.
(3) - choose the button to go to the window for adding a new CMS template.
(4) - SMS template search engine (search possible by criteria: Name, Content, Creation time, Update time).
(5) - navigation through the list of BA customers in the administration panel.
 
 
 Adding a new SMS template
To create a new SMS template, you must complete the fields: Name, Content, Is active and Type.
Screen for adding a new CMS template
 
In the Content field you can use variables and any placeholders.
  RememberPlaceholder - Attribute, used as a temporary filler or auxiliary text in a text field.
The content in the placeholder can be anything.
Types of variables:
{%n} - BA clinet name.
{%ba} - BA consultant name.
Placeholder construction:
{Placeholder_name}
Example:
Mrs. {% n} Thank you for our conversation.
This is your unique code for free delivery with your next order.
I wish you pleasant shopping at www.yves-rocher.pl.
Best regards, {%ba}
   RememberThe placeholder can be used in the body of the message, but be sure to remove it before sending it to the client. Otherwise, the application will prevent sending the message with the following warning:
 
Warning about incomplete template

Beauty Advisor - getting started
The Beauty Advisor functionality allows BA consultants to place an order on behalf of BA customers, and manage orders, customer base, and POS stores.
Communication between a BA consultant and a BA client takes place via three channels: telephone connection, SMS, or messenger (chat and messenger).
  RememberBA consultant - administrative panel user with “Beauty Advisor” rights. For more information about rights, see User groups in the administrative panel.
  RememberBA customer - a consumer appearing in the BA customer base located in
the module Beauty Advisor > Contacts. Contacts are created using BA customer import. For more information, see Beauty Advisor - mass imports.
   RememberPOS stores - retail outlets, created in the administration panel. For more information, see Beauty Advisor > POS retail – store management.
Due to the complexity of the functionality, the individual modules have been described in separate articles:
Beauty Advisor > Contacts - viewing and managing BA clients
Beauty Advisor > Orders / list - viewing and handling orders
Beauty Advisor > Pending orders - viewing orders
Beauty Advisor > New order - description of the ordering process
Beauty Advisor - description of Recent Activity filter
Beauty Advisor > POS retail – store management
Beauty Advisor - system settings
Beauty Advisor - mass imports
Beauty Advisor - exports
Beauty Advisor - message templates
User groups in the administrative panel

Beauty Advisor - system settings
Getting started
The general settings of the Beauty Advisor module is available in the Beauty Advisor / Retail Orders (2) tab, located in the System> System / settings section. To go directly to the tab, use the search engine (1) and type “beauty”. The next chapter will describe the configurable parameters.
  RememberFor basic information on the Beauty Advisor module, see the Beauty Advisor - getting started.
System> System Settings section
 
Table of Contents:
 Description of parameters in the Beauty Advisor / Retail orders tab
 
 
 Description of parameters in the Beauty Advisor / Retail orders tab
 
   
Beauty Advisor / Retail Orders tab in System> System settings
 
Enabled - a switch that enables / disables the Beauty Advisor functionality.
Campaign code - campaign code assigned to the order placed using BA commerce. The value overrides the default campaign code.
Call center campaign code (optional) - campaign code assigned to the placed order, using BA commerce, by an administrator with Call Center rights. If the field is empty, administrators with the Call Center group will use the campaign code defined in the Campaign code field.
Default delivery cost - the default delivery cost for orders carried out through the BA commerce channel. The value can be changed by the BA consultant when placing the order. For more details, see the article Beauty Advisor > New order - description of the 
ordering process.
Auto correct mobile prefix - phone number auto-correction when importing BA clients and BA consultants.
Price discounts (percentage) - a field with JSON notation where you can modify price discounts granted when placing a BA order. JSON configuration is described in the article Beauty Advisor > New order - description of the ordering process.
Price discounts (amount) - a field with JSON notation where you can modify the amount of discounts granted when placing the BA order. JSON configuration is described in the article Beauty Advisor > New order - description of the ordering process.
Gifts - a field with JSON notation where you can modify the gifts given when placing the BA order. JSON configuration has been described in the article Beauty Advisor > New order - description of the ordering process.
Nuxt.js Catalog URL - path to the product catalog window for BA commerce.
Hide phone number column - a switcher to hide the phone number column in Beauty Advisor> Contacts. Changes are visible only to BA consultants with the following permissions: BA, BAC, BAF. The permissions are described in the article User groups in the 
administrative panel.
SMS Template: translate national to lation characters - a switch that enables / disables the use of Latin characters in the text of the SMS template (section Customers > SMS templates).
Ignored SKU prefixes - Option to omit prefixes for orders placed by BA consultants with BAF privileges. The permissions are described in the article User groups in the administrative panel.
ETD Discount percentages - a field where you can modify the ETD discount given when placing a BA order. Recording configuration is described in Beauty Advisor > New order - description of the ordering process.
Fixed price discount from catalog prices - a switch enabling / disabling the option of granting a quota discount on catalog prices when placing an order.
Allow non super BA to change price - a switch enabling / disabling the option of changing price during placing an order for admin panel users with permissions lower than Super BA. For more information, see User groups in the administrative panel.
Activity segmentation - a field with JSON record, where you can modify the parameters and values of the recent activity filter. For more information, see Beauty Advisor - description of last activity filter.

User groups in the administrative panel
Getting started
Each administrator of the administrative panel is assigned to a specific group of users. Each group is characterized by various sets of rights, described in the following chapters of the article.
  RememberUser groups - predefined authorization groups thanks to which panel administrators are able to view the content and perform specific actions. The scope of the content that can be viewed and the scope of possible actions depends on the assigned group.
   RememberAdministrator - a user who has an account set up in the administrative panel.
   RememberUpon the customer’s request, the development team can create completely new groups with a different collection of user rights.
Upon the customer’s request, the development team can create completely new groups with a different collection of user rights.
Administrator
BAFZBA
Beauty Advisor 
Beauty Advisor CC
Beauty Assistant Franchise
BOK supervisors 
Content editor
Content manager
Customer care service 
External call center
Herbarium editor
Mc business admin
POS admin 
Repository manager 
Root
Super administrator 
Super Beauty Advisor 
Super Beauty Assistant Franchise
Table of contents:
 User groups from the Beauty Advisor family
 
 
 User groups from the Beauty Advisor family
Administrators with an assigned user group from the Beauty Advisor family have access to the Dashboard and the Beauty Advisor module.
Section Dashboard
 
The user groups included in the Beauty Advisor family are:
BAFZBA
Beauty Advisor 
Beauty Advisor CC
Beauty Assistant Franchise
Super Beauty Advisor 
Super Beauty Assistant Franchise
  RememberAll the above groups have access to the same application modules. Only the Super Beauty Advisor and Super Beauty Advisor Franchise groups have access to the additional POS retail section. More information on the POS retail section can be found in the article Beauty Advisor > POS retail – store management.
In the Dashboard, the administrator can see two tabs: Planned interviews and Past interview. Details can be found in the article: Beauty Advisor > Contacts - viewing and managing BA clients.
In the Beauty Advisor module, the administrator can:
Browse and manage BA customers in the Contacts section. More information about the section available in the article Beauty Advisor > Contacts - viewing and managing BA clients.
Browse and handle orders in the section Orders / list. More information about the section available in the article Beauty Advisor > Orders / list - viewing and handling orders.
View pending orders in the section Pending orders. For more information on the section, see the article Beauty Advisor > Pending orders - viewing orders.
Place a new order in the section New order. More information about the section available in the article Beauty Advisor > New order - description of the ordering process.

Beauty Advisor > POS retail – store management
Getting started
The POS retail section in the Beauty Advisor module contains a table with all POS stores, susceptible to sorting, with the possibility of editing stores, viewing and adding new stores.
  RememberPOS stores - retail outlets, created in the administration panel. Shops can be added individually (it is possible from the POS retail tab) and imported in groups from external files. For information on importing, see Beauty Advisor - mass imports.
  POS retail section in the Beauty Advisor module
Table of Contents:
 Viewing and managing POS stores
 
 
 Viewing and managing POS stores
Below you will find a description of the table and possible actions in the Beauty Advisor / POS retail tab. All the following parameters (except the ID parameter) are editable in the
administration panel.
Beauty Advisor / POS retail tab in the POS retail section
(1) Show X entries - option to change the number of stores displayed on one page (available range from 10 to 100).
(2) - table with information about stores. You can sort the data by the contents of any column:
ID - unique store ID in the administration panel. The parameter is generated automatically by the application.
POS number - a unique store number in the administration panel. The number can consist of any characters, of unlimited length. The parameter is editable from the administration panel and overwritten during mass import of POS stores. For more information on importing, see Beauty Advisor - mass imports.
Company - the name of the company which the store is a part of. 
Shop name - Name of the store. Usually, it also contains store number.
Street - The street name on which the store is located at.
City - City name where the store is located at.
Postal code - Store's postal number.
Phone - Store's mobile number.
E-mail - Store's e-mail address.
Actions
Edit – select the button to edit the data of the selected store.
Show – Select to preview information about the selected store.
Window for editing store data
(3) Search - store browser (search possible according to the criteria: City, Street, Store name, Company, POS number)
(4) Add - select the button to add a new store.

Beauty Advisor > Pending orders - viewing orders
Getting started
The Pending orders section in the Beauty Advisor contains the table (2) with the BA’s order pending list. The table is susceptible to sorting, it allows to preview and search for orders. The Filters section (1) allows for selecting orders that meet the specified criteria, described in the
Filters chapter.
  RememberPending BA Order - BA’s placed order, awaiting customer approval.
Once accepted, the orders go to the BA order table in section Beauty Advisor> Orders / List. For more information on order acceptance on the customer’s side, see Beauty Advisor > New order - description of the ordering process.
Pending orders section in the Beauty Advisor module
Table of Contents:
 Filters
 Viewing pending BA orders
 
 
 Filters
The Filters tab allows to narrow down the list of pending BA orders, based on the date range during which the orders are waiting for customer approval. Orders that meet the Creation time criterion will be displayed in the Orders / list tab.
 
Filters tab in section Beauty Advisor> Pending Orders
 
 
 Viewing pending BA orders
Below you will find a description of the table with the list of pending BA orders and the possible actions in the Orders / list tab.
Orders / list tab in Pending orders section
(1) Show X entries - option to change the number of pending BA orders on one page (available range from 10 to 100).
(2) - columns containing information about pending BA orders. Each column is sortable:
Creation time - An exact date and time of the order creation.
First name - Customer's first name.
Last name- Customer's last name.
E-mail- Customer's e-mail address.
Actions
Show (4) - select the button to view the details of the pending BA order. The view is only used to preview order data without the possibility of performing any action.
Detailed order view
(3) - order search engine (search possible by criteria: First name, Last name, Email)
(5) - navigation through the list of orders in the administration panel.

Beauty Advisor > Orders / list - viewing and handling orders
Getting started
The Orders / List section in the Beauty Advisor module contains a table (4) with a list of all correctly processed and accepted BA orders (for more information on processing and accepting orders, see Beauty Advisor > New order - description of the ordering process). The table is susceptible to sorting, it allows you to change order shipment statuses, preview orders, export orders and generate labels. With the help of filters, you can extract orders that meet the criteria specified in the Filters section (3), described in the  Filters chapter.
  RememberBA Order - An order placed by BA consultants in the Beauty Advisor module that has been accepted by a BA customer. For more information on accepting BA orders, see Beauty Advisor > New order - description of the ordering process. For information on BA consultants and BA clients, see Beauty Advisor - getting started.
Table of contents:
 Generating a CSV file with orders and printing labels for the courier
 Filters
 Viewing and handling BA orders
 
 
 Generating a CSV file with orders and printing labels for the courier
In the Orders / list section, you can perform 2 mass operations:
Orders / list section in Beauty Advisor module
Generate a list of orders for the courier in CSV format by selecting the Generate CSV file for courier button (1). After selecting the button, the application generates a csv file and takes you to the operation summary view, where you can download the file to a local disk, using the Download file button.
A message with a summary of the operation
 
  RememberYou can generate a list of all orders for the courier only for orders with the status “Ready to be sent”.
  Note   After generating the file, orders with the status “Ready to be sent” will change their status to “Sent”.   
Generate an order label using the Print all button (2). The application generates a PDF file and displays the generated labels, the options are: downloading the file to a local disk or printing directly.
Generated label
 
  RememberYou can generate a list of all orders only for orders with the status “Waiting for preparation”. 
  Note   After generating the file, orders with the status “Waiting for preparation” will change their status to “Under preparation”.
  
 
 
 Filters
The Filters tab allows you to select orders in terms of the criteria described below. Orders that meet the selected criteria will be displayed in the Orders / list tab.
Filters tab in section Beauty Advisor> Orders / list
 
Processed date – the date range during which the order was registered in the application.
Order value – the scope of the order value.
Status – order status (available: "New", "Processing", "Sent", "Delivered", "Returned", "Cancelled", "Delivery failure", "Shipping in progress"). System parameters are verified and changed automatically by the application. For more information on order statuses, see Beauty Advisor > Orders / list - viewing and handling orders.
Package status – shipment status in the Beauty Advisor module. The BA consultant can manually change each status.
Waiting for preparation - status assigned automatically by the application, after placing the order, only when the COD (cash on delivery) form of payment has been selected. If another form of payment is chosen, the shipment will be given the status “Waiting for payment”. The shipment status automatically changes to “Under preparation” when the order label is generated.
Waiting for payment - status assigned automatically by the application, after placing the order, only when the online payment method has been selected. When the order is paid, the shipment status automatically changes to “Under preparation”.
Under preparation - Status assigned manually by the BA employee. This status causes a window to show up with a field where the employee has to enter the approximate
package weight.
Ready to be sent - a status that can only be set manually.
Sent - status assigned automatically by the application after generating the CSV file for 
the courier.
Delivery method – Shows available delivery methods. filter value depends on the settings in the administration panel.
Payment method – Shows available payment methods. filter value depends on the settings in the administration panel.
Deffered payment status – the available statuses: “paid”, “overdue”, “pending”.
Check status – order verification status (available "new", "successfully checked internally", "internal check failed", "successfully exported", "export failed", "successfully processed"). System parameters, are verified and changed automatically by the application. For more information on order statuses, see Beauty Advisor > Orders / list - viewing and handling orders. 
Paid? - option of selecting payment status (COD / DP, paid, preconfirmed payment, waiting for payment, canceled). System parameters, are verified and changed automatically by
the application. 
Customer ID – unique customer ID. For more information, see Beauty Advisor > Contacts - viewing and managing BA clients.
Only with vouchers – check the checkbox to display orders where the FIDEN2 voucher has been used.
 
 
 Viewing and handling BA orders
Below you will find a description of the table with a list of BA orders and the possible actions in the Orders / list tab.
   Orders / list tab in section Beauty Advisor> Orders / list
(1) Show X entries - option to change the number of BA orders on one page (available range from 10 to 100).
(2) - columns containing information on BA contracts. Each column is sortable:
ID - the unique identifier of the BA order in the administration panel.
Processed on - date and time of BA order processing
Value  - Order value.
First name - Customer's first name.
Last name- Customer's last name.
Email - Customer's e-mail address.
Paid? - Payment status. If the selected delivery was Cash on Delivery it will show COD.
Package status - Shipment status. Pressing the print label button (5) will change this status to “Under preparation”. The BA consultant must manually change the status to “Ready to be sent” in order to bring up a popup (8) where he will enter the weight of the package. This action will enable pressing the Generate CSV file for courier button and the shipment status will change from “Ready to be sent” to “Sent”.
Pop-up with the option to enter the weight of the package
 
Status - Current order status.
Actions
(5) - select the button to generate a label for a given order. The action changes the status to “Under preparation” from all other shipment statuses.
Show (6) - select the button to go to the order details. In the order details view, you can change the shipment status (8), as in the example below.
  Order details in Beauty Advisor> Orders / list
 
(3) - order search engine (search possible by criteria: First name, Last name, Email)
(7) - navigation through the BA orders list in the administration panel.

Beauty Advisor > New order - description of the ordering process
Getting started
The New Order section of the Beauty Advisor module allows BA consultants to submit an order on behalf of BA clients. BA consultants have control over the granted discounts and the selection of gifts added to the order. BA consultants can also modify the customer’s data, as well as choose the method of confirming the purchase. The ordering process consists of several steps. Each process involves different actions, described in the following chapters of the article.
  RememberBelow you will find URL links to articles that describe:
- What is a BA order
- Who is a BA customer and a BA consultant
   
New Order section in Beauty Advisor module
 
Table of Contents:
 “Add product” tab
Product selection by name or SKU code
Selecting a product from the catalog
 “Order” tab
 Tab “+ Add gift”
 “FIDEN2” tab
 "Delivery methods" tab
 “Address data” tab
 Configuration of parameters in the “Order” tab
 Configuration of parameters in the “+ Add gift” tab
 
 
 “Add product” tab
The tab allows you to add a product to an order using two methods: Product selection by name or SKU code or Selecting product from catalog. Before adding a product to the order, you can select the number of items (3) and change the price (catalog or promotional) (4). The product is added to the order by clicking the + Add to order button (5).
Product selection by name or SKU code
To add a product to your order, enter the product’s SKU or name in the SKU field (2). The Paste SKU button (2) allows you to paste the SKU code from the clipboard. The search engine automatically suggests products (6) whose name or SKU code contains the entered characters. The search engine displays only products marked as active in the catalog.
Add Product tab in Beauty Advisor> New Order
 
The Promotion price field (4) contains the current promotional price of the product. If the product does not have a promotional price, the catalog price is displayed. The Promotion Price field (4) allows you to change the price before adding a product to the order. After selecting the + Add to order button (5), the product will appear in the  “Order” tab.
  RememberCatalog price - basic price, not including the promotional price of the product.
 Add a product in the Add Product tab in Beauty Advisor> New Order
 
Selecting a product from the catalog
The second method of adding a product to the order is to select the button
Open a product catalog session (1). You will be taken to a new view where you can view the entire catalog of the store’s products, taking into account all categories and subcategories (8), using the product finder (7) (you can search for the product by the name or SKU code). The top menu with categories (8) and the list of products are fully configurable from the administration panel. For more information, see the articles:
  RememberThe list of products and the top menu with categories correspond 100% to the content available on the store’s website.
An open session of the product catalog in the Beauty Advisor module
 
(9) - buttons used to navigate through the open session of the product catalog.
(10) Close - a button used to close the session and return to the section New order in the Beauty Advisor module.
To add a product to the order, select the Add to order button next to each product. After selecting the button, the following message will be displayed in the upper right corner of the browser window and the product will appear in the  “Order” tab.
  
A message confirming that the product has been added to the order from the open session of the product catalog
 
 
 “Order” tab
The tab contains products added to the order. You can change the catalog price for products, give discounts, and set the cost of delivery. Below you will find a description of the possible actions in the Orders tab.
Order tab in section Beauty Advisor> New order
(1) - changing the catalog price of the product.
(2) - changing the number of items of the product.
(3) - unchecking the product. The unchecked product will not be included in the order.
(4) x -removing e a product from the Order tab.
(5) FIDEN2 discounts - granting a FIDEN2 discount. The discount is calculated on the list price of the product.
(6) Discount - giving a percentage discount. The discount is calculated on the list price of the product. The configuration of button values is described in the chapter Configuration of parameters appearing in the “Orders” tab.
(7) Price - possibility to set the price of the product. The operation will overwrite the value
of field (1).
(8) Fixed price discount from catalog prices - the possibility of granting an amount rebate on product list price.
(9) ETD Discount (End of ticket discount) - additional discount at the end of the order, independent of the discounts granted earlier in the promotional module. The discount is given to all added products in the Order tab.
(10) - a field in which you can set the cost of delivery, included in the total value of the order.
   RememberDiscounts may not be combined. 
   RememberOnly the price of gifts can be “0”. If the product is not a gift, an attempt to submit an order will end with an error.
  RememberA product with several color variants has an additional section Available colors in the Order tab, where you can choose one of the available colors (example below).
The ability to choose the color of the product in the Order tab
 
 
 Tab “+ Add gift”
The tab allows to add a gift to the order using the visible buttons. Each button represents one gift. After clicking a chosen button, a present will appear in the tab  “Order” tab. The headers and gifts assigned to the given buttons are configurable from the level of the administration panel (the configuration method is described in detail in the chapter  Configuration of parameters in the “+Add gift” tab).
 
  
Add gift tab in section Beauty Advisor> New order
 
 
 “FIDEN2” tab
The tab contains the customer’s FIDEN2 points balance, it allows to award of additional points for the order (points will be added to the pool of FIDEN2 points). The tab also contains the customer’s loyalty card number (mother card number) and the points that the customer will receive for the placed order.
 
  
FIDEN2 tab in section Beauty Advisor> New Order 
 
The data of the FIDEN2 tab will be filled in automatically upon choosing the Place order button in the section Beauty Advisor> Contacts (the process is described in the article Beauty Advisor > Contacts - viewing and managing BA clients). After choosing this button, you will be taken to the FIDEN2 tab with the automatically filled data.
 
 
 
 "Delivery methods" tab
The delivery methods tab allows Beauty Advisor employees to select the desired delivery method. This tab is only visible if at least two delivery methods are assigned to the selected BA altshop. At least 1 delivery method must be assigned to the altshop, or there will be a notification, that the order cannot be created, as no delivery method is selected.
  Delivery method tab visualization 
The delivery method tab contains available delivery methods with their logo, name, and regular delivery fee for a selected range of cart value. This fee doesn't apply additional costs for the customer but is only informational for the employees on what fees are normally used. The fee may change depending on the configuration of the delivery method - for example, in this case, Balik do Ruky has a delivery fee of 119Kc between 0 and 899 cart value, and between 900 and 9999999 it has a delivery fee of 0kc.
If the selected method is a pickup point delivery, then in the customer address tab there will be an additional field, where the employee is able to select the point.
  RememberYou can find information about configuring the delivery methods in the selected altshops in the Delivery costs / list - browsing and managing delivery costs article.
 
 
 “Address data” tab
In the address data tab, you can enter the personal data of customers (1). If the selected delivery method uses pick-up points you will see a Delivery point field, which allows you to select such delivery point. By pressing the Select button you will open the delivery point map. You can also indicate the method of payment for the order (2). After selecting the payment method, the BA customer will receive the option to confirm the purchase via SMS or e-mail (according to the method chosen by the BA consultant) and the order placed will be visible in the section:
Beauty Advisor> Pending orders - if the payment method with confirmation has
been selected
Beauty Advisor> Orders / list - if the payment method has been selected
without confirmation
Payments with the required BA customer confirmation include the following methods:
Order with payment on delivery with confirmation
Order with payment on delivery and SMS confirmation
  RememberThe options Place order with COD and confirmation and Place order with on-line payment will only be available if the E-mail field is filled in.
Remember that both COD and PayU payment options need to be assigned to the altshop used in the Beauty Advisor module in order for them to work.
  Address data tab in section Beauty Advisor> New order
  Visualization of the delivery point map
  RememberYou can find more information about the delivery point widget in the Delivery point widget article.
Below you will find an example of an SMS with the option to confirm the order and an e-mail confirming the order with the option to display the order status.
  SMS message with the option to confirm the order 
 
E-mail confirming the submitted order 
After clicking on the link Pokaż status zamówienia (show order status), the BA customer will be taken to the page with the order summary and the possibility of payment. For this purpose, use the Do płatności (to the payment) button.
 
Order summary page
 
  RememberThe address data will be filled in automatically when you choose the button Place order in the section Beauty Advisor> Contacts in the tab Beauty Advisor / Contacts(the process is described in the article Beauty Advisor > Contacts - viewing and managing BA clients).
After selecting this button, you will be taken to the Address data tab with automatically 
filled data.
   RememberThe Consumer data tab will be displayed above the “Add product” tab, with a preview of the consumer’s data and the possibility of going to the section View contact, in the Beauty Advisor module, using the Show customer button (example below).
 
   
The Consumer Details tab in section Beauty Advisor> New Order
 
 
 Configuration of parameters in the “Order” tab
In the system settings of the administration panel, you can modify the values assigned to the following parameters in the Order tab:
Discount (1)
Price(2)
ETD discount(3)
Delivery cost(4)
Orders tab in section Beauty Advisor> New order
To make changes to the settings, go to section System / Settings in the System module, and use the search engine (5) to enter the phrase “beauty”.
After searching for the relevant phrase, the Beauty Advisor / Retail Orders tab (6) will 
be displayed. 
   The Beauty Advisor / Retail Orders Activity tab in the section System / Settings of the module Beauty Advisor
 
Discount
The Price discounts (percentages) field (1) contains JSON that defines the color of the buttons and the values assigned to them, which are visible in the Order tab. Below you will find an explanation of the record.
   Price discounts (percentage) field in the Beauty Advisor / Retail Orders tab in the System / Settings section
 
{"color":"#8b9620","discounts":["5","10","13","15","20","23","25","26","27","30",
"32","33","40","45","50","52"]}
The fragment above contains an object with 2 attributes:
"color" - button color, the value of which may be:
 color name (example: "color":"green")
hexadecimal notation (example: "color":"#8b9620")
"discounts" - a rebate, the value of which may be:
integer (example: "discounts":"5")
decimal number (example: "discounts":"1.5")
Example
{"color":"#8b9620","discounts":["5","10"]}
The above notation will look as follows in the Order tab:
 
   
Buttons assigned to the Discount parameter in the Order tab
 
Price
The Price discounts (amount) field (1) contains the same JSON, with the same structure as in the Discount field.
 The Price discounts (amount) field in the Beauty Advisor / Retail Orders tab in the System / Settings section
 
ETD discount
The ETD discount values can be defined in the ETD Discount percentages field. They can be integers or decimals. An empty field will hide the discount in the Order tab.
 
   The ETD Discount percentages field in the Beauty Advisor / Retail Orders tab in the System / Settings section
Example
[0.5, 1, 5, 10, 15, 20]
The above notation will look as follows in the Order tab:
 Buttons assigned to the ETD discount parameter in the Order tab
Delivery cost
You can change the delivery cost in the Default delivery cost field (1).
   Default delivery cost field in the Beauty Advisor / Retail Orders tab in the System / settings section
 
 
 Configuration of parameters in the “+ Add gift” tab
In the system settings of the administration panel, you can edit the name of the group (1) and the gifts assigned to it (2) in the tab + Add gift.
 
Tab + Add gift in section Beauty Advisor> New order
To introduce changes, go to the Beauty Advisor / Retail Orders tab in the system settings and scroll to the Gifts field. Below you will find an explanation of the notation. 
The Gifts field in the Beauty Advisor / Retail Orders tab in the System / Settings section
 
{"group_name":"I Próg > 59 zł Sklepy Własne ","color":"#8b9620","gifts":[
{ "sku":"P94359","name":"Pur Bleuet dwufazowy płyn do demakijażu oczu z wyciągiem z bławatka BIO 200ml","price":"0.01"}
The fragment above contains an object with 3 main attributes:
"group_name" - the value of which may be:
 string (example: "group_name":"I Próg > 59 zł Sklepy Własne")
"color" - the color of which may be:
 color name (example: "color":"green")
hexadecimal notation (example: "color":"#8b9620")
"gifts" - the value of which is other objects:
"sku" - a unique product number, the value of which is:
SKU of the product. The given number must match the number existing in the product database, otherwise the gift will not be added to the order (example: "sku":"P94359")
"name" - name of the product, the value of which may be:
string (example: "name":"Pur Bleuet dwufazowy płyn do demakijażu oczu z wyciągiem z bławatka BIO 200ml")
"price" - the price of the product, the value of which may be:
integer (example: "price":"5")
decimal number (example: "price":"0.01")
Example
[{"group_name": "II PRÓG > 149 zł", "color":"#b2c11d", "gifts":
[{ "sku": "P76148", "name":"Woda toaletowa Hello Printemps", "price":"0.01"}, 
{ "sku": "P71426", "name":"Przeciwzmarszczkowy krem regenerujący pod oczy", "price":"0.01"},
{ "sku": "PI2171", "name":"Zestaw do makijażu oczu", "price":"0.01"},
{"sku":"2TREE","name":"Zasadz 2 drzewa","price":"0.01"}]}]
The above record will look as follows in the Order tab:  
The name of the group and the gifts assigned to it in the + Add gift tab

Beauty Advisor - description of last activity filter
Getting started
The last activity filter (1) allows to select BA customers based on the selected date range of the last purchase. Customers are marked with different colors - depending on the time that has passed since their last purchase. These colors and the date range assigned to them are configurable in the system settings. For more information, see chapter  Configuration of colors and date range of the “Recent Activity” filter. Clients meeting the criteria specified in the Filters tab will be displayed in the Beauty Advisor / Contacts tab (4). The number of days since the last purchase is shown in the Last activity column (2). The Show data button (3) shows additional information on the last purchases made by the BA customer. Details are available in the chapter  Filter - Last activity and customer
data preview.
  RememberFor more information on BA clients and the Beauty Advisor module, see Beauty Advisor - getting started.
 RememberAccess to the configuration is granted to users of the administration panel, with a higher level of rights (min. “Administrator”). For more information on permissions, see User groups in the administrative panel.
   Contacts section in the Beauty Advisor module
 
Table of Contents:
 Filter - Last activity and customer data preview
 Configuration of colors and date range of the “Recent Activity” filter
 Example of use
 
 
 Filter - Last activity and customer data preview
The Customer data screen shows the dates of the last purchases made by a BA customer in each of the three sales channels: BA commerce (1), in stationery shops (2), and e-commerce (3). Position Last activity item (4), indicates the number of days that have elapsed since the last order of a BA customer in any of the sales channels listed above.
Window with BA client data and information about his Last activity
 
Last BA commerce purchase date (1) - date of the last purchase made by BA commerce. Data on the purchase are generated automatically by the application.
Last retail purchase date (2) - date of the last purchase made at a Yves Rocher store using the customer’s loyalty card. Purchase data is collected from a CSV file daily imported, from the JANTAR database. The value can also be updated during mass import of clients (both in regular and lite versions).
Last e-commerce purchase date (3) - date of last purchase from Yves Rocher online store. The purchase data is generated automatically by the application.
 
 
 Configuration of colors and date range of the “Recent Activity” filter
To edit the colors and date ranges assigned to them, go to the System / settings section in the System module, and use the search engine (1) to enter the phrase “beauty”. After searching for the relevant phrase, the Beauty Advisor / Retail Orders tab (2) will be displayed.
   Beauty Advisor / Retail Orders Activity tab in the System / Settings section of the Beauty Advisor module
The Activity segmentation parameter contains a JSON record that defines the colors and date ranges that appear in the Last activity filter. Below you will find an explanation of the record.
 
Activity segmentation parameter settings in the Beauty Advisor / Retail Orders tab in the System / Settings section
 
"from" - pa parameter that allows to define the number assigned to the filter Last activity from which the defined color will be visible. The field must contain a valid integer.
"to" - a parameter that allows to define the number assigned to the filter Lasy activity to which the defined color will be visible. The field must contain an integer or null (0) if the range is to be open on one side.
"color" - parameter that allows to define the label color assigned to a given range of numbers. The value can be a color name (example: “red”) or hexadecimal notation ( for example: #ff000).
 
 
 Example of use
To better understand the record, see the example below:
{
"from": 8,
"to": 14,
"color": "orange"
}
The above entry will show an orange label (1):
in the filter Last activity
next to customers whose Recent Activity is between 8 and 14 days (example below (2)):
Beauty Advisor / Contacts tab in Beauty Advisor> Contacts
Below you will find the final JSON code that would work as follows:
the red label will be assigned to consumers with activity in the range of 0-7 days
the orange label will be assigned to consumers with an activity in the range of 8-14 days
the label with the color # 00ff00 will be assigned to consumers with an activity ranging from 15 days to infinity
[
 {
  "from": 0,
  "to": 7,
  "color": "red"
 },
 {
  "from": 8,
  "to": 14,
  "color": "orange"
 },
 {
  "from": 15,
  "to": null,
  "color": "#00ff00"
 }
]

Beauty Advisor - mass imports
Getting started
Using the administration panel, you can perform:
mass update of BA clients
mass import of new BA clients
mass import of new BA consultants
mass update of BA consultants
mass customer anonymization
You can perform all types of imports in the Import / Export> Import section Dedicated descriptions are included in the following chapters of the article.
  RememberMass import – an operation that allows the to collective add new data to the administration panel as well as modify and delete the existing data. The operation is initiated by loading one import file or a set of appropriately constructed import files in the indicated location in the administration panel.
  RememberFor basic information on BA commerce, see the article Beauty Advisor - getting started.
Import / Export> Import section
Table of Contents:
 Description of “Import” tab
 Mass update of BA clients
Full import version
Lite version
 Import of new BA clients
 Mass update of BA consultants 
 Import of new BA consultants
 Import of BA customer anonymization
 
 
 Description of “Import” tab
Below you will find a description of the possible actions in the Import tab.
Import tab in the Import / Export> Import section
 
File – option to choose an import file from the local disk. The file format
depends on the type of import performed.
Type – specification of the type of import performed.
Options – option to perform a test import. The operation will not end with data import, but you will receive a report that allows to verify whether the import result is correct.
Import file – click the button to start mass import. Selecting this button and confirming the form will start data processing.
All types of imports described in the current article can be performed by following these steps:
Select the import file from the local disk.
Indicate the type of import.
Press the Import file button.
 
 
 Mass update of BA clients
Due to the current limitations in the import of Excel files, you can perform two types of import (full version import and lite import). Each type is described in the following section. The current import is limited to approximately 100,000 rows. This limit will be extended with further updates.
  RememberImport is possible only for users of the administration panel assigned to one of the following groups:
- Administrator
- Super Administrator
- Root
More information on the administration panel user groups is available in the article User groups in the administrative panel
Full import version
The full import version (import type: “Customer contact database for Consultant update”) contains all the updateable data about the BA customer. Below you will find descriptions of the columns in the import file.
 
Import file content (file type) : „Customer contact database for Consultant update”
  RememberThe fields marked with an asterisk (*) are mandatory fields. If the field remains empty, the import of the given record will return an error. 
  RememberEmpty values in the optional fields will delete the currently existing data in the administration panel, leaving the field empty.
  RememberIf the system detects a row with a new BA client in the imported file during import, the import of the given record will return an error.
All the parameters described below modify the data in the tab Customer Data, located in the customer data preview. For details about the view, see Beauty Advisor > Contacts - viewing and managing BA clients.
LAST_CUSTOMER_CODE - customer’s FIDEN2 card number. 
FIRST_NAME * - BA customer first name.
NAME * - BA customer's last name.
PHONE * - BA customer’s phone number with country code (configuration is described in the article Beauty Advisor - system settings).
ACTUAL_SHOP * - POS store number assigned to the BA customer. For more information about stores, see the article Beauty Advisor > POS retail – store management.
RANKING * - A range of BA customers ranking (1-999999). You can find a description of this parameter in Beauty Advisor > Contacts - viewing and managing BA clients.
CITY - city.
POSTAL_CODE - customer's postal code.
STREET1 - street.
 HOUSE_NUMBER - house number.
BOX_NUMBER - premises number.
EMAIL - BA customer email address.
DATE_BIRTH - date of birth of BA customer.
LPD_BA - date of the last purchase made through BA channel.
LPD_ECOMMERCE - date of the last purchase from Yves Rocher online store.
LPD_RETAIL - date of the last purchase made at Yves Rocher store using the customer’s loyalty card.
LA - the value of the Last activity filter. For details on the filter, see Beauty Advisor - getting started.
ID - unique BA customer identification number. Application generated parameter.
All the parameters below contain information on customer orders made in stationary stores.
Values are created and overwritten only during mass import of BA customers, which represents information stored in the Retail shopping stats tab (details about the tab are available in the article Beauty Advisor > Contacts - viewing and managing BA clients. All fields are optional.
TOP1_TO_PRODUCT
TOP1_TO_PRODUCT_LABEL
TOP1_TO_LPD_TXT
TOP1_TO_PRODUCT_PRICE
TOP1_TO_TO
TOP1_TO_QT
  NoteThe value of the "ID" column cannot be modified. "ID" is a key parameter to identify the client.
Based on this parameter, the application performs appropriate operations on data.
Specification of the import file
file format: .xlsx
file name: any name
Lite version
Import in lite version (import type: “Customer contact database for Consultant
update (lite version) “) allows for update of four BA client data. Below you will find descriptions of the columns in the import file.
Import file content (file type): "Customer contact database for Consultant update (lite version)"
  RememberThe fields marked with an asterisk (*) are mandatory fields. If the field remains empty, the import of the given record will return an error. 
   RememberEmpty values in the optional fields will delete the currently existing data in the administration panel, leaving the field empty.
   RememberIf the system detects a row with a new BA client in the imported file during import, the import of the given record will return an error.
ACTUAL_SHOP * - POS store number assigned to the BA customer. For more information about stores, see the article Beauty Advisor > POS retail – store management.
RANKING * - BA customer ranking range (1-999999). For a description of the parameter, see Beauty Advisor > Contacts - viewing and managing BA clients.
LPD_RETAIL - date of the last purchase made at Yves Rocher store using the customer’s loyalty card.
ID * - unique BA customer identification number. Application generated parameter.
  NoteThe value of “ID” column cannot be modified. “ID” is a key parameter to identify the client. Based on this parameter, the application performs appropriate operations on data.
Specification of the import file
file format: .xlsx
file name: any name
 
 
 Import of new BA clients
With the type of import: “Customer contact database for Consultants – import XLSX” you can import new BA clients that do not exist in the admin panel.
  RememberImport is possible only for users of the administration panel assigned to one of the following groups:
- Administrator
- Super Administrator
- Root
More information on the administration panel user groups is available in the article User groups in the administrative panel.
   RememberIf, during import, the system detects a row in the imported file containing the BA client that exists in the administration panel, then the import of a given record will return an error.
The content of the imported file is identical to the mass update of BA clients in the w Full import version.
  NoteThe import file cannot contain a column named ID, because it is a parameter generated automatically by the application when performing import. 
Specification of the import file
file format: .xlsx
file name: any name
 
 
 Mass update of BA consultants
Import type: “POS Users” allows modification of data of BA consultants, who are in the administration panel. Below you will find descriptions of the columns in the import file.
   RememberImport is possible only for users of the administration panel assigned to one of the following groups:
- Super Administrator
- Root
More information on the administration panel user group is available in the article User groups in the administrative panel
   RememberIf, during import, the system detects a row in the imported file containing a new BA consultant, then the import of a given record will return an error.
 
Import file content (file type): “POS Users”
id - A unique customer identification number generated by the application.
first_name - BA consultant first name.
last_name - BA consultant last name.
email - BA consultant e-mail address.
mobile - BA consultant phone number.
active - a field defining the activity of the BA consultant’s account in the administration panel. The value “1” means an active account, and the value “0” - inactive.
last_login_date - the last date and time when the BA consultant logged in to the administration panel. The parameter value is generated by the application. Import does not overwrite the values in the administration panel.
group_name - group to which the BA consultant is assigned in the administration panel. More information on the administration panel user groups is available in the article User groups in the administrative panel
pos_reports_number - POS store number assigned to the BA consultant, used for reporting purposes.
ba_pos_number - POS number assigned to the BA consultant in the administration panel.
default_altshop_id - unique identification number of the default altshop, assigned in the administration panel to the BA consultant. For more information on altshop, see Alt shops - Introduction
   NoteThe value of “ID” column cannot be modified. “ID” is a key parameter to identify the client. Based on this parameter, the application performs appropriate operations on data.
Specification of the import file
file format: .xlsx
file name: any name
 
 Import of new BA consultants
Type of import: “Admin user import XLSX” allows to import of new BA consultants. The description of the imported data contained in the file is presented below.
   RememberImport is possible only for users of the administrator panel who have been assigned to the group: “Root”. More information on the administration panel user groups is available in the article User groups in the administrative panel
Import file content (file type): "Admin user import XLSX"
NAME - BA consultant first name.
SURNAME - BA consultant last name.
SHOP_ID - shop to which the consultant is assigned.
EMAIL_ADRES - BA consultant email.
MOBILE_NUMBER - BA consultant telephone number with country code telephone.
LANGUAGE - language in which the BA consultant will use the administration panel.
BA_GROUP - group to which the consultant is assigned. Type of import: “Admin user import XLSX” allows to assign only one of the following groups:
Beauty Advisor
Beauty Advisor CC
Beauty Assistant Franchise
Super Beauty Advisor
Super Beauty Assistant Franchise
The administration panel user groups are described in the article User groups in the administrative panel.
DEFAULT_ALTSHOP - default altshop assigned to the customer.  More information on altshops is available in the article Alt shops - Introduction
   RememberIf, during import, the system detects a row in the imported file containing a BA consultant that exists in the administration panel, the import of a given record will return an error.
   RememberImport type: "Admin user import XLSX" only allows you to import employees who are assigned to one of the following groups:
- Administrator
- Super administrator
- Root
Specification of the import file
file format: .xlsx
file name: any name
 
 Import of BA customer anonymization
Import type "Anonymization of the customer contact database for Consultants" allows to import of customer internal IDs located in the .xlsx file and anonymizes all of them in the BA platform. This import triggers the BA customer anonymization, which also can be done manually in the:
BA customer profile > GDPR > Anonymize account (forget customer) 
The reason for the anonymization in the BA > Anonymized contacts after the import is set to "Anonymization import".
   RememberImport type: "Anonymization of the customer contact database for Consultants" can be used by users who are assigned to one of the following groups:
- MC business admin
- Administrator
- Super Administrator
- Root
The import is not limited to the users assigned POS, so users having one of the above-mentioned groups will be able to anonymize all BA users without any restrictions.
Visualization of the example BA customer anonymization xlsx file
As the import searches for the ID column, any .xlsx file can be imported, and the import mechanism will ignore all columns that are not labeled as ID and import ID's from the ID column.
  NoteThe anonymization process cannot be undone after the initiation. Please make sure that the imported file has the correct customers.
Specification of the import file
file format:
.xlsx
.csv, delimiter: ; and enclosure: " , encoding: UTF-8.
file name: any name

Beauty Advisor > Contacts - viewing and managing BA clients
Getting started
The Contacts section in the Beauty Advisor module contains a table (2) with the list of BA clients imported to the administration panel. The table is sortable, it allows for the placement of an order for a given BA customer, displaying their data and searching for the target contact using the search engine. Filters (1) will help you to extract contacts that meet the set criteria. It is described in the  Filters chapter.
  RememberBelow are URL links to articles where you can find the following information:
- Who is a BA customer
- Beauty Advisor > New order - description of the ordering process
- How to import BA clients into the admin panel
 Contacts section in the Beauty Advisor module
Table of Contents:
 Filters
 Viewing and managing BA clients
 Preview of BA customer data - description of possible actions
 
 
 Filters
The Filters tab allows for the selection of BA clients based on the criteria described below. BA clients meeting the selected criteria will be displayed in the Beauty Advisor / Contacts tab.
   
Filters tab in Beauty Advisor > Contacts
 
Status - BA client status. There are 4 types of status:
New - status assigned during mass import of BA customer base.
Unanswered - status assigned manually in the administration panel when the customer did not answer the phone.
Answered without ordering - status assigned manually in the administration panel, when the customer answered the phone but the order was not placed on the customer’s account.
Converted - status assigned to the client automatically by the application after placing the order in the Beauty Advisor module.
Ranking - BA customer ranking range (1-999999). The parameter is editable only when importing BA clients. The parameter value is set by Yves Rocher employees.
It has a birthday on - the range of birthdays of BA customers. The parameter is editable only when importing BA clients.
Last retail purchase date - the range of dates for the BA customer’s last purchase in-store. Purchase data is collected from a daily imported CSV file, from the JANTAR database. The value can also be updated during mass import of clients (both in regular and lite versions).
No BA commerce after - the day from which no BA commerce orders have been recorded at the customer’s premises. The parameter is automatically generated by the application. Mass import of BA clients does not affect the parameter value.
Card number - customer’s FIDEN2 card number.
Last activity - a complex filter that allows to narrow down the list of BA clients in terms of their recent activity. For information on the operation and configuration of the filter, see Beauty Advisor - description of last activity filter.
 
 
 Viewing and managing BA clients
Below you will find a description of the table with the list of BA clients and possible actions in the Beauty Advisor / Contacts tab.
Beauty Advisor / Contacts tab in Beauty Advisor> Contacts
 
(1) Show X entries - option to change the number of BA customers on one page (available range from 10 to 100).
(2) - columns containing information about BA customers. Each column is sortable:
ID - the unique identifier of the BA customer in the administration panel.
Mobile - Customer's mobile number.
First name - Customer's first name.
Last name - Customer's last name.
City - City to where the client will have their BA order delivered.
Birthday - Customer's date of birth.
Last BA commerce purchase date - date of the last BA commerce purchase.
Last activity - days since the last purchase made by a BA customer in any sales channel (physical store, e-commerce, Beauty Advisor).
Status - customer status (“new”, “unanswered”, “answered without ordering”, “converted”).
Ranking - customer ranking range (1-999999).
Last note - last note left by the BA consultant when making the purchase.
Actions 
Place order (3) - select the button to place a new order on the customer’s account. For more information on placing a new order, see Beauty Advisor > New order - description of the ordering process.
Show data (5) - select the button to display the BA customer data. More information on viewing the BA client, see  Preview of BA customer data - description of possible actions.
(4) - BA customer search engine (search possible by criteria: "Mobile", "First name", "Last name", "City").
(6) - navigation through the list of BA customers in the administration panel.
 
 
 Preview of BA customer data - description of possible actions
The View contact section allows to preview the BA customer data placed in the Customer tab (4), move to the BA orders list using the Orders button (3), and switch between the Personal data (1) and Retail shopping stats (2) views.
Sekcja View contact w module Beauty Advisor
 
Personal data
The view contains the Customer tab consisting of 5 fields, described below.
The field Consumer data contains data about the customer and allows to change the status of the BA customer.
The Consumer data column in the Customer tab
 
Customer code - a non-unique BA customer code consisting of only digits, of unlimited length. It is created and overwritten at the time of mass import (optional field).
Card number - customer’s FIDEN2 card number.
  RememberInformation about fields: Last BA commerce purchase, Last stationary purchase, Last e-shop purchase and Recent activity is available in the article Beauty Advisor - description of last activity filter.
The Address data section contains the correspondence data of the BA customer and allows transfer to the order placement window - use the Place order button (6). The consumer’s details will be automatically filled in. For more information on submitting an order Beauty Advisor > New order - description of the ordering process.
Address data column in the Customer tab
 
The Save the note from the conversation column allows for making a note of the conversation with BA customers and to plan contact with them.
 
Save note from the conversation column in the Customer tab
 
The scheduled contact list (7) will be visible in the BA Consultant’s Cockpit. Next to it there is a list of planned contacts from the past (8). The tables contain the first and last name of the BA customer together with the telephone number (if assigned to the customer), the date of the scheduled contact, and the ability to view BA customer data using the Show contact button. You can access the list of all BA clients using the Show all contacts button.
List of planned contacts and past interviews in the BA Consultant’s Cockpit
 
For a chronological list of BA consultant notes, see Recent Notes. The prepared notes and applied cannot be edited.
 
Last notes column in the Customer tab
 
The Send SMS column enables sending an SMS to the telephone number assigned to the BA customer. You can enter any text message or use predefined templates available in the SMS Templates section (more information on creating and editing templates is available in the article Beauty Advisor - message templates.
 
Recent notes column in the Customer tab
 
Retail shopping stats
The view contains information on customer orders made in stationary stores. Values are only created and overwritten during mass import of BA clients (for more information on mass imports, see Beauty Advisor - mass imports).
Retail shopping stats screen in the Customer section 

Built-in functions

Cart synchronization across devices
Getting started
In this article, you can find information about cart synchronization across devices functionality. This change allows you to add the selected products and a discount code to the cart from the URL. Products and a discount code need to exist, and be properly configured in the admin panel - if they are not, they won't be added.
  RememberYou can find more about products in the Product management article.
  RememberYou can find more about discount codes and the promotion module in the Promotion module introduction article.
Table of contents:
 Structure of the URL
 
 Structure of the URL
This functionality adds the /restore/ function into the cart URL with the following parameters:
skus - Adds the selected SKUs to the cart. There can be multiple SKUs separated by commas. Only quantity of 1 of the selected products will be added if the amount of products is not specified in brackets (e.g. 39959(3) will add 3 times 39959). If the selected product already exists in the cart its quantity won't increase. Gifts can be added to the cart this way. Example: https://pluat-v6.yr.tauceti.tech/cart/restore/skus/39959(2),55665
code - Adds the selected main discount code to the cart. The discount code has to exist and be used by a promotion. Example: https://pluat-v6.yr.tauceti.tech/cart/restore/code/TEST123
clear - Removes all of the products from the cart that are not present in the same skus parameter. It's a bool, so 1 removes the products. Example: pluat-v6.yr.tauceti.tech/cart/clear/1
Both of these options can be used simultaneously, which would result in adding the selected products and discount code to the cart.
Example:
https://pluat-v6.yr.tauceti.tech/cart/restore/skus/99291(4),30132/code/TEST123/clear/1

Storelocator
Getting started
In this article, you can find information about store locator functionality. Storelocator allows customers to access configured url  open a Google map of the selected country and see all of the configured stores. The map contains a search field, which allows customers to find their desired street or city as well as an option to get their location automatically.
Visible points on the map are displayed in the left panel with their basic information like name, address, and current opening / closing hours.
Visualization of the store locator
Table of contents:
 Configuration
Stores list
Store creation
 Customer perspective
 
 Configuration
It is possible to configure the storelocator aspects in
System > System / Settings > Integrations > Storelocator v2.
Visualization of the storelocator system settings
In the storelocator system settings you can find the following options:
Enabled - A switch that defines if the functionality is enabled. If this switch is set to OFF customers will get an 404 error when accessing the storelocator URL.
API URL - URL of the storelocator API. It shouldn't be modified.
Backend: Key - Backend key of the functionality provided by Tau  Ceti.
CND URL - URL of the Tau Ceti CDN. It shouldn't be modified.
Frontend: Key - Frontend key of the functionality provided by Tau Ceti.
Google maps Key - Google maps frontend API key.
Use HTTP for local communication - Switch that defines if HTTP protocol should be used for local communication. This switch shouldn't be modified.
Default latitude - Default latitude of the opened map
Default longtitude - Default longitude of the opened map
Default zoom - Default zoom of the opened map between 1 and 10. The higher the value the closer the map is.
The map URL can be changed in the System > Translations / list. You can find it under the translation phrase storelocator_url.
 
Stores list
By default store locator doesn't have any stores created. They are managed from the admin panel in
CMS > Stores / list.
Visualization of stores in stores / list
Below you will find a list of possible actions in Stores / list.
Filters section (1) allows filtering the visible stores by their creation time range
Show X entries (2) section defines how many stores per page should be visible.
Stores table (3) provides basic information about the store. You can find the following columns in the table:
ID - The internal identification number of the created store.
Name - The name of the store. This name is visible to the customers
City - City where the store is located.
Active - Activity status of the store. It can be true or false.
Creation time - A date and time when the selected store was created.
Update time - A date and time when the store was updated last time.
Actions
Edit - Allows to edit the selected store. Store edit form is the same as creating a new one. You can find more about it in the Store creation section.
Delete - A button that allows to delete the selected store from the database. This action cannot be reverted.
Add button (4) allows the creation of a new store entry. You can find more about store creation in the Store creation section.
Search field (5) allows to search for the available stores by their names or a city.
Page number (6) section allows to you show more stores by switching to a different page.
Store creation
When the Add or Edit button is selected you will be redirected to the store edit page
Visualization of the store creation
When creating or editing a store you can define the following fields:
Name - The name of the store. This name is visible to the customers.
Name (additional) - Additional name to the store, that will help customers find it.
GPS: Latitude - A latitude where the store pin will be placed at.
GPS: Longitude - A longitude where the store pin will be placed at.
POS number - POS number of the store.
Active - Activity status of the store.
Image - Image of the store that is displayed with the store popup.
Mobile number - The phone number of the store that customers can call
Landline number - The landline number of the store that customers can call
E-mail address - E-mail address of the store
Opening hours - Opening hours of the store. It is possible to define the exact opening hours for the selected day of the week. It is possible to assign multiple opening hours on the same day as long as they do not interfere with each other.
Services - Services that are available in the selected store. Adding a new service only provides a text field that can be filled in with the type of service and it is displayed to the customers on the popup of the store.
 
 
 Customer perspective
Customers can access the storelocator by the storelocator button in the header or by accessing the defined URL from translations.
Visualization of the store locator
The storelocator page opens on the default longitude and latitude defined in the system settings. Customers are able to search for their selected street or use the find location functionality to find their current location and display stores around them. The left panel also displays 10 stores with their basic information.
When the customer selects one of the stores from the left panel or selects one of the pins on the map the store popup will show
Visualization of the store locator
Store popup contains all of the configured store information described in Store creation section. Customers can select the mobile number to directly call it if they are on a mobile device, or the can press on the directions button next to it, to open Google Maps and get automatic directions from their current location to the selected store.

Newsletters
Getting started
In this article, you can find information about the newsletter functionality, which allows customers to register to a newsletter list, which can be sent to third-party applications via API, like Bloomreach. It is possible to create newsletter groups to categorize types of customers.
Table of contents:
 Functionality configuration
 Registration for the newsletter subscription
Logged-out customers
During registration
Logged-in customers
 Managing subscribers
 Managing subscriber groups
 Subscribers import
 Subscribers export
 
 
 Functionality configuration
To enable the customers to register for the newsletter on the website it needs to be first enabled in the system settings. Newsletter configuration can be found in:
System > System / Settings > Built-in Functions > Newsletter
Visualization of the newsletter functionality system settings
In the Newsletter section you can find three switches:
Enabled - Switch which enables / disables the functionality and the ability to use it by 
the customers.
Show 3rd party agreement checkbox - Switch defining if the 3rd party newsletter agreement should be visible while registering a new account instead of a built-in agreement. This option requires properly configuring the agreement on a 3rd party platform.
Double activation - A switch defining whether unregistered customers should confirm the newsletter subscription in a separate e-mail, before signing them in.
Additionally, the title of the newsletter confirmation e-mail can be changed in the
System > System / Settings > General > E-mails
Visualization of the E-mails tab in the System / Settings
 
 
 Registration for the newsletter subscription
Logged-out customers
Customers who do not have an account on the e-commerce platform, or are not logged in are able to register for the newsletter using the /newsletter webpage. Usually, the /newsletter webpage is linked in the e-commerce platform footer, but that depends on Yves Rocher needs.
Visualization of the /newsletter page
On the /newsletter webpage customers are able to type their e-mail address and their additional information, and register for the newsletters. When the Double activation is activated in the System / Settings customers will receive an e-mail confirmation if they want to register for a newsletter. If this functionality is disabled, the customers will instantly join the newsletter list. Customers are unable to cancel their subscription from this page - it has to be done using the URL in the newsletter or from the customer panel described in Logged-in customers.
During registration
During the registration process, when the customer selects the agreement, that they agree to an e-mail communication they will sign in to the newsletter list.
Visualization of the registration form
Same as for logged-out customers when the Double activation is activated in the System / Settings customers will receive an e-mail confirmation if they want to register for a newsletter. If this functionality is disabled, the customers will instantly join the newsletter list. Customers are able to cancel their subscription using the URL in the newsletter or from the customer panel described in Logged-in customers.
Logged-in customers
Registered and logged-in customers are able to register to the newsletter functionality in their customer panel by accessing the /customer/newsletter option. Logged-in customers will also get redirected to this webpage when they access the previously mentioned /newsletter URL.
Visualization of the /customer/newsletter page
In the /customer/newsletter webpage customer only has to fill in their e-mail address and are able to register to the newsletter list. Customers registering to the newsletters this way do not have to accept the newsletter registration even if the Double activation is enabled.
Visualization of the /customer/newsletter page
When the customer is logged-in and registered to a newsletter functionality they are able to cancel their subscription from the /customer/newsletter webpage.
 
 
 Managing subscribers
All customers that are registered for a newsletter functionality, or have canceled their subscription can be found in the admin panel. Subscribers list is located in the:
Customers > Subscribers / list
This tab contains filters, which will help manage the desired customers
Visualization of the Subscribers / list filters
There are the following filters available:
Creation time - A time range when the subscribers were created
Update time - A time range when the subscribers were last updated
Show MD5 e-mail hash column - Adds a new column that contains MD5 e-mail hash
Visualization of the Subscribers list tab
In the subscriber list table you can find the following options:
(1) Show X Entries allows to filter how many entries should be visible at once
(2) Various table columns. All of them can be sorted by clicking on them.
ID - Subscribers internal ID
First/last name - Subscribers first and last name
E-mail - Subscribers e-mail address
Status - Subscribers status. Available statuses are Active and Blacklisted. Blacklisted customer unsubscribed to the newsletter, or was manually blacklisted, and won't receive receive newsletter e-mails.
Creation time - A date and hour when the customer has subscribed to a newsletter.
Actions - Two available actions:
Edit - Allows to edit the selected customer. More about adding and editing the customer can be found below
View - View the selected subscriber. Viewing doesn't allow to edit any data.
(3) Add button allows to manually add a new subscriber. Adding and editing a subscriber looks exactly the same. Below you can find more information about the available fields, when adding or editing a new customer.
(4) Search field allows to search the subscribers by their name / surname as well as their e-mail address.
(5) Pages list allows to show the next batch of customers on the another pages accoriding to applied sorting option and filters.
Visualization of the customer in the subscribers / list
When editing or adding a new customer you can find there the following fields:
Customer - A button that redirects to customers e-commerce profile. This option is only available if both subscriber e-mail and e-commerce account e-mail are the same.
E-mail - Subscribers e-mail address. This field is mandatory.
Subscriber's groups - Groups that the subscriber is assigned to. You can find more about the subscriber groups in the  Managing subscriber groups chapter.
First name - Customers first name
Last name - Customers last name
Gender - Customers gender
Birthday - Customers birthday date
Active - A switch that defines if the subscriber is active or not. Not active subscribers won't receive any newsletters.
Is blacklisted? - A switch, which defines if the subscriber is blacklisted. Blacklisted subscribers won't receive any newsletters.
Additionally, all agreements the subscriber has agreed on will be visible at the bottom of the page.
 
 
 Managing subscriber groups
Subscribers can be put in subscriber groups, which allows to easily manage them, and send a desire newsletters to a certain selected group. Subscriber groups can be manged in
Customers > Subscribers groups
Visualization of the filters in subscribers groups.
Subscribers groups filters allow to filter by is active? flag, which defines if the selected group is set as active or not.
Visualization of the subscribers groups
In the subscribers groups table you can find the following options:
(1) Show X Entries allows to filter how many entries should be visible at once
(2) Various table columns. All of them can be sorted by clicking on them.
ID - Subscriber group internal ID
Name - Internal name of a subscriber group.
Description - Short description of a subscriber group.
Is active? - Subscriber group activity status.
Actions
Edit - Allows to edit the selected subscriber group. More about adding and editing the customer can be found below
(3) Add button allows to addition of a new subscriber group. Adding and editing a subscriber looks exactly the same. Below you can find more information about the available fields, when adding or editing a new group.
(4) Search field allows to search the subscribers groups by their name.
(5) Pages list allows to show the next batch of groups on the another pages accoriding to applied sorting option and filters.
Visualization of the subscriber group creation
In the subscriber group creation / edition you can define the following fields:
Name (mandatory) - An internal name of a subscriber group.
Description - Internal description of a subscriber group.
Is active? - An activity flag, which defines if the selected group is active for use.
 
 
 Subscribers import
Subscribers can be imported using the import functionality located in
Import / Export > Import
Visualization of the subscribers import
In order to import subscribers you have to select the "Newsletter subscribers CSV" option and select the prepared .csv file.
Visualization of the subscribers csv file
Subscribers .csv file can have any file name and must contain the following columns:
email (mandatory) - Customers e-mail address.
Gender - Customers gender. Accepted values are M for males and F for females.
Group - Subscriber group internal name. This field will assign the selected customer to a selected subscriber group.
first_name - Customers first name
last_name - Customers last name
birthday - Customers birthday in DD/MM/YYYY format.
 
 
 Subscribers export
Subscriber lists can be exported using the:
Import / Export > Export / Subscribers
Visualization of the subscribers csv file
In the Export / Customers you can filter out desirable data by using the selected filters:
Groups - A list of selectable subscriber groups that should be exported.
Creation time - A range of dates whenever the subscriber was created.
Update time - A range of dates whenever the subscriber was updated.
Show MD5 e-mail hash column - Adds the MD5 e-mail hash column in the exported file.
By pressing the "Export" button the file will be exported with the selected filters.
Visualization of the exported subscribers file
In the exported subscribers file you can find the following columns:
ID - Subscriber internal ID.
First_name - Customers first name.
Last_name - Customers last name.
Email - Subscribers e-mail address.
is_active - Activity status of a subscriber. 1 means active, 0 means not active.
is_blacklisted - blacklisted status of a subscriber. 1 is blacklisted, 0 is not blacklisted.
Gender - Customers gender. M is for Male, F is for Female.
Status - Subscribers status. Available statuses are:
Only newsletter - Customer is only registered to the newsletter communication and doesn't have an account on a e-commerce platform.
Customer - The customer has a created account on an e-commerce platform
Mc_hash - MD5 e-mail hash. This field is only visible if the Show MD5 e-mail hash column filter was selected.
Joy_id - Customers JOY ID.
Birthday - Customers birthday date.
Subscribe time - A date with an hour when the customer has subscribed to an 
e-mail communication.

Rate & Review
Getting started
In this article, you can find information about the rate & review functionality. Rate & Review allows customers to review the products on the website by providing a rating from 1 to 5 and a comment. This review then is accepted or denied by the Yves Rocher employee and in case of acceptance, it is visible on the product page under the Reviews section. Customers can earn FIDEN2 points for providing a review that has been accepted.
  RememberYou can find more about FIDEN2 functionality in the FIDEN2 article. 
Table of contents:
Customer perspective
Review by purchasing a product
Review by using the product page
Reviews view on the product page
Configuring the Rate & Review
Built-in fuctions > Reviews
E-commerce > e-mails
FIDEN2 > Loyalty points
 Reviews moderation
Reviews overview 
Moving the reviews
 Rate & Review steps diagram
 
 Customer perspective
When the Rate & Review is enabled customer can review the products according to the options set in system settings and will receive FIDEN2 points for the review, if it is enabled. Customers are unable to edit or remove their reviews by themselves. All of the reviews have to be verified and accepted by Yves Rocher employees. Customer can review products in two ways:
By purchasing a product.
On a product page if the functionality is enabled.
Review by purchasing a product
By default when the functionality is enabled customer will receive an invitation on their e-mail with a list of up to three products after purchasing them on the e-commerce platform. When the customer clicks on one of the products they will be redirected to the review page. The invitation to review a product is sent to the customer after a selected amount of time, which is configured in functionality system settings.
Visualization of the invitation e-mail
These reviews are additionally visible in the customer panel > rate products (e.g. https://uat.yves-rocher.pl/reviews/panel). Here, the customer can see all of the products they are able to review as well as their already reviewed products.
Visualization of the customer panel reviews page
When the customer chooses their product they will be welcomed by the review page, where they are able to:
(1) select their rating
(2) type the review title
(3) Type the review description
Additionally, if the customer doesn't have set up their nickname there will be an additional field to do so, as a nickname is mandatory to place a review.
Visualization of the review creation page
When the review is placed it needs to be accepted by the Yves Rocher employee. You can find more about it in the  Review moderation chapter.
Review by using the product page
This option is only enabled if Everyone can review every product option described in Build-in fuctions > Reviews is turned on. Only logged-in users can review products.
When this option is enabled customers can enter any available product in the product catalog, and press the "Add review" (4) button.
Same as in the other review method customers will be welcomed by the reviewing page, which allows them to:
(1) select their rating
(2) type the review title
(3) Type the review description
Additionally, if the customer doesn't have set up their nickname there will be an additional field to do so, as a nickname is mandatory to place a review.
When the review is placed it needs to be accepted by the Yves Rocher employee. You can find more about it in the  Review moderation chapter.
Reviews view on the product page
Every accepted review will be visible on the product page.
Visualization of the reviews on the product page
Here customers can find:
(4) Add a review button - A button that allows customers to review the product. It is described in more detail in the Review by using the product page chapter.
(5) The amount of reviews placed per rating.
(6) The average review rating.
(7) Sort the reviews by:
Default - Sort by combination of highest rating and best usefulness.
Date new - Sort by the newest review date.
Date old - Sort by the oldest review date.
Rating high - Sort by the highest rating
Rating low -  Sort by the lowest rating
Usefulness best - Sort by the highest ratio of "yes" to "no" buttons.
Usefulness worst - Sort by the lowest ratio of "yes" to "no" buttons.
(8) Customer reviews with an option to rate their usefulness with the "Yes" and "No" buttons. The ratio of this rating affects the usefulness of sorting.
(9) Change the review page
 
 
 Configuring the Rate & Review
Rate & Review functionality can be turned on / off and configured in system settings. Various functionality options are located in different tabs
System / settings > System > Built-in fuctions > Reviews
In built-in functions, you can find the main rate & review functionality options described below
Visualization of the reviews tab
Enabled - A switch that decides if the reviews should be enabled or disabled
Everyone can review every product - A switch that decides if customers should be able to review products without the need to purchase them described in Review by using the 
product page.
Staff e-mail - An e-mail address separated by a comma (",") where the information e-mails with new reviews should be sent to.
Verifications e-mail - An e-mail address separated by a comma (",") where the information e-mails with new reviews should be sent to.
System / settings > System > E-commerce > e-mails
In the e-mails tab you can find two options related to Rate & Reviews functionality
Visualization of the e-mails tab
Sender name - A name that will be visible for the customer in the "Sender" field in their mailbox.
Send review invitation after - A number of days counted from the purchase date after which customers will receive their review invitation and will be able to review their product from the customer panel.
System / settings > System > FIDEN2 > Loyalty points
In the Loyalty points tab, you can find the option to choose how many FIDEN2 points a customer should receive per review.
Visualization of the loyalty points tab
Amount of points for review - The amount of FIDEN2 points customers will review per review. If set to 0 customers won't receive any FIDEN2 points per review.
  RememberYou can find more about FIDEN2 functionality in the FIDEN2 article. 
 
 
 Reviews moderation
Every placed review needs to be moderated and accepted by the Yves Rocher employee. The selected employees will receive e-mail notifications according to the settings in the 
Build-in fuctions > Reviews.
All new reviews can be located in the
Catalog > Reviews / moderation
Visualization of the reviews moderation page
You can find a following options in reviews / moderation:
Select the Show X entries(1) field to set the number of reviews, displayed on one page (min 10 / max 100).
The names of the columns (2) that contain information about target reviews. Each column is susceptible to sorting.
To sort the records, click on the title of the column in question.
ID - TauCeti internal ID of the review
Creation time - A date and hour of the creation by the customer of the review.
Nick  – Nickname of the reviewer.
Rate – Review rate applied by the customer.
Status – Status of the review. Available statuses are:
New
Awaiting verification
Rejected
Needs additional verification
Accepted
Actions - A view button, which will redirect to the review details described below.
Search box (3) where you can search for reviews by customers nickname, product or
review content.
Page buttons (4), which allows user to change the page of currently viewed reviews.
Visualization of the review details
When seeing the review details you can find a more detailed view of the review as well as on this page you are able to change the status of the review as well as apply your own comment to the review.
In this section you can find the following information:
Creation time - A date and hour of the creation by the customer of the review.
Product - A product name and SKU to which this review is related.
Rate – Review rate applied by the customer.
Review title - The title of the review applied by the customer.
Review text - The description of the review applied by the customer.
Note to Yves Rocher - no longer supported field.
Advantages - no longer supported field.
Disadvantages - no longer supported field.
Nick  – Nickname of the reviewer.
E-mail - Customer's e-mail address.
Last edited by - An e-mail address of Yves Rocher employee who last changed this review.
Creation time (Yves rocher reply tab) - Creation date, when this review has been initially edited by the Yves Rocher employee
Update time - Last date that this review has been edited by the employee.
Status – Status of the Yves Rocher comment. Available statuses are:
Visible - Comment will be visible on the website.
Hidden - Comment won't be visible on the website.
Content - Yves Rocher comment. It is visible on the e-commerce platform if the Status of the comment is set to Visible.
Reviews overview
The list of all reviews can be found in
Catalog > Reviews / list
By default, the list is empty and needs to be filtered or searched for in order to see the reviews
Visualization of the
Available filters are:
Status - Current status of the review. Available statuses are:
New - A default review status of a newly posted review. 
Awaiting verification - no longer used status.
Rejected - Reviews that have been rejected by moderators.
Needs additional verification - No longer used status.
Accepted - Reviews that have been accepted by moderators
Adding date - A range of dates when the review was added
YR answer date - A range of dates when the Yves Rocher employee applied a comment to the review.
YR answer status - status of the answer. Available statuses are:
Hidden - The YR comment is hidden to customers.
Visible - The YR Comment is visible to customers.
Only with questions to YR - No longer used option. doesn't do anything anymore.
Only with YR answers - Shows only reviews that have Yves Rocher comments.
Search also in YR answer content - allows to search the YR comment content when using the search (3) functionality.
With applied filters, the reviews that fit the criteria will be visible in the Reviews / list tab. It is possible to show them without applying any filters if there is content in the search box (3).
Visualization of the
You can find the following options in reviews / list:
Select the Show X entries(1) field to set the number of reviews, displayed on one page (min 10 / max 100).
The names of the columns (2) that contain information about target reviews. Each column is susceptible to sorting.
To sort the records, click on the title of the column in question.
Creation time - A date and hour of the creation by the customer of the review.
Review title - The title of the review.
Nick  – Nickname of the reviewer.
Rate – Review rate applied by the customer.
YR answer status - the status of the YR comment. Available statuses are:
Hidden
Visible
YR answer creation time - a date and an hour when the YR comment was applied
Status – Status of the review. Available statuses are:
New
Awaiting verification
Rejected
Needs additional verification
Accepted
Is active? - A switch, which allows to enable or disable the review. When the review is disabled it is no longer visible on the website.
Actions - A view button, which will redirect to the review details described below.
Search box (3) where you can search for reviews by customers nickname, product or
review content.
Page buttons (4), which allows user to change the page of currently viewed reviews.
Visualization of the review details
When seeing the review details you can find a more detailed view of the review as well as on this page you are able to change the status of the review as well as apply your own comment to
the review.
The status option allows you to select if the YR comment should be visible on the website. Available statuses are hidden and visible.
 
Moving the reviews
Rate & Review functionality allows you to move the existing reviews or future reviews from one product to another. Whenever a customer has placed a review on product X it will be moved to product Y. In the same way, it can be done for future reviews, so in the future, if the customer tries to post a review on product X it will be posted on product Y instead.
Visualization of the reviews moving page
In the reviews / moving tab you can find the following options:
Filters
Only visible tab by default. In this tab, you have to specify the product SKU you want to move the reviews from. After typing the SKU and applying the filter the other tabs will be visible.
Reviews list
The list of available reviews assigned to this product. Here it is possible to select the desired reviews that should be moved to another product.
Move selected reviews to another product
In this tab, you have to specify the product SKU to which you want to move the selected reviews. After pressing the "Move" button, the selected reviews will be moved.
Move invitations to another product
In this tab, you are able to specify the SKU of the product to which all future review invitations should be sent after a review was placed on the SKU in the Filters tab.
For example, if in the Filters tab, there is SKU 123456 and in Move invitations to another product tab SKU 654321 by purchasing the product 123456 customers will receive an invite to review the 654321 product.
 
 
 Rate & Review steps diagram
Rate & Review functionality has multiple steps and ways of handling, so to make it easier to follow and understand you can find below the diagram, which visualizes the functionality.
R&R diagram

Public JS API
Getting started
This article contains information regarding access to Public JS API and examples of its usage.
Table of contents:
 API methods
cart: TcApiCart
localization: TcApiLocalization
customer: TcApiCustomer
 Examples
 API methods
The API contains three main types of objects: cart, localization and customer. They are accessible through the window.tcApi. The object window.tcApi returns Promise with TcApi class instance.
cart: TcApiCart
getTotalValue(): Promise<number> - method returns total value of cart.
getProductsValue(): Promise<number> - method returns total value of all products in cart.
getProductsQuantity(): Promise<number> - method returns quantity of products in cart (product * quantity).
getGiftsQuantity(): Promise<number> - method returns quantity of gifts in cart.
totalProducts(): Promise<number> - method returns number of product rows in cart.
totalGifts(): Promise<number> - method returns number of gift rows in cart.
getProductsSummary(): Promise<ProductSummary> - method returns ProductsSummary object
interface ProductSummary {
totalValue: number;
productsValue: number;
totalProductsQuantity: number;
totalGiftsQuantity: number;
totalProducts: number;
totalGifts: number;
}
localization: TcApiLocalization
getLocale(): string - current env locale. For example: pl, cs or sk.
getCurrency(): string - current locale currency. For example zł in PL environment.
getCurrencyIso(): string - current locale currency in ISO 4217 standard. For example PLN.
getDecimalDigits(): number - number of decimal digits in prices.
getMinGiftPrice(): number - miminum price for a gift.
getMobileRegex(): string - mobile phone number regex pattern.
getMobileDefaultPrefix(): string - mobile phone number prefix. For example: +48.
getMobilePlaceholder(): string - mobile phone number placeholder. For example: +48000000000
getPostalCodePlaceholder(): string - postal code placeholder. For example: 00-000.
getPostalCodeRegex(): string - postal code regex. For example: ^([0-9]{2}-[0-9]{3})$.
customer: TcApiCustomer
isLoggedIn(): Promise<boolean> - method returns authentication state of current customer.
getFirstName(): Promise<string|null> - method returns first name of customer if logged in.
getState(): Promise<CustomerState> - method return CustomerState object.
interface CustomerState {
loggedIn: boolean;
firstName: string|null;
}
 Examples
Example usage of TC public JS API in CMS Blocks and CMS Pages.
Methods returning a Promise type may return the target value with a slight delay. This fact should be taken into account when designing views to avoid potential issues related to Cumulative Layout Shift or empty HTML elements.
Fetch and display current cart value in span element
<script>
window.tcApi().then(async (api) => {
if (api.localization === null) { /* Localization object can be null */
return;
}
const cartValue = await api.cart.getTotalValue(); /* Example: 14.99 */
const currency = api.localization.getCurrency(); /* Example: "zł" */
const cartValueElement = document.querySelector('.cart-value');
if (!cartValueElement) {
return;
}
cartValueElement.innerText = `${cartValue} ${currency}`;
});
</script>
The value of your cart is <span class="cart-value"></span>
Check if user is logged in and display the appropriate banner based on their status
<script>
window.tcApi().then(async (api) => {
const {loggedIn, firstName} = await api.customer.getState();
const loggedElement = document.querySelector('.logged');
const unloggedElement = document.querySelector('.unlogged');
if (!loggedElement || !unloggedElement) {
return;
}
if (loggedIn && firstName) {
loggedElement.style.display = 'block';
unloggedElement.style.display = 'none';
loggedElement.innerText = `Welcome ${firstName}`;
} else {
loggedElement.style.display = 'none';
unloggedElement.style.display = 'block';
}
});
</script>
<div class="logged" style="display: none;"></div>
<div class="unlogged" style="display: none;">Welcome guest!</div>

Catalog categorization
Getting started
In this article, you will learn about catalog categorization functionality, which allows you to create and edit categories. Categories are visible in the product catalog as well as during the product search (1), and allow customers to click on them in order to filter out products depending on products assigned to the selected category.
The default URL to the category page is constructed as: /c/category1[/category2][/category3], for example, /c/make-up/face/powders.
The prefix c can be modified by changing the category_url translation.
  Warning     It's not recommended to change the translation after some time of using the default one, as it will ruin SEO.   
Visualization of the product category page
The category page state consists of:
Category selection (part of category URL). Any filter functionalities never modify it.
Page number (`page` query parameter).
Items per page selection (`pp` query parameter).
Sort method selection (`sort` query parameter).
Features filter selection (`f` query parameter).
Price range selection (`pp` query parameter).
Store selection (`shop` query parameter).
*Only available in store* filter (`is` query parameter).
Filter to *New products* only (`news` query parameter).
Filter to *Bestsellers* only (`bestsellers` query parameter).
The following sections describe the behavior of all category page elements.
Table of contents:
 Category management
Filters section
Elements section
Editing and creating categories
 Changes made during the implementation of Categories functionality
Product page breadcrumb
Removal of the Tag page (`/tag`)
Features behavior
 
 
 Category management
All categories can be managed through the admin panel. The categories tab is located in:
Catalog > Categories / list
Categories can be additonally managed using the product catalog import / export.
  RememberYou can learn more about import / export of the catalog in the Product catalog export and import article.
  Warning   Up to three categories can be created in one path (excluding the default E-commerce one). 
For example, in the case of the path: 
E-commerce > Category1 > Category 2 > Category3 > Category4
Category4 won't be accessible on the e-commerce platform and trying to access it via URL will result in a 404 error.
Visualization of the categories / list tab
Filters section
In the filters section, you can see the current parent category, and switch to another one using the drop-down menu. You are additionally able to change the current filter by clicking on a category. This method is described in the Elements section.
Visualization of the filters section
Visualization of the categories drop-down menu
 
Elements section
In the elements section, you can see all categories in a selected parent category.
Visualization of the elements section
Below you will find a description of possible actions.
 Select the Show X entries (1) field to set the number of categories, displayed on one page (min 10 / max 100).
The names of the columns (2) that contain information about a given category. Each column is susceptible to sorting. To sort the records, click on the title of the column in question.
ID - An internal ID of a category
Name - A name of the category. These names are visible to the customers on a website. Category names can be opened by clicking on them (6), and it will open the elements tab with a selected category as a parent category.
Update time - Date and hour when the selected category has been updated last time.
Actions - An edit button, which allows editing a selected category. The main e-commerce category cannot be edited. You can read more about adding and editing categories in the Editing and creating categories section.
Select the Add category here (3) button to go to the adding the new category in a current parent category. You can read more about adding and editing categories in the Editing and creating categories section.
Search box (4) where you can search for the desired category by their category name.
Page buttons (5), which allows user to change the page of currently viewed categories.
 
Editing and creating categories
Whenever adding a new category or editing one you will be redirected to the following page.
Visualization of the editing of a category
Below you will find a description of possible actions.
Parent category - A field where the current parent category is displayed. This field
cannot be edited.
Name - A name of the category. This name will be visible to the customers.
Path (URL) - An URL of the category. This URL will be visible in the website URL whenever the customer selects this category or one under it.
Order - Number which defines the priority and order of this element. Lower the number, higher the priority, or higher position on the list.
Save - Button, which saves the changes made to the category.
Delete - A button that deletes a selected category and all the categories under it. It is only available when editing the category. In order to be able to press it you have to press the "I confirm delete" checkbox beforehand.
 
 
 Changes made during the implementation of Categories functionality
Product page breadcrumb
The breadcrumb has been modified to use the product's main category.
Removal of the Tag page (`/tag`)
The legacy way to create categories by links to selected feature sets has been removed.
Marketing links to, for example, product lines should be directed to promotion pages instead.
Features behavior
The existing behavior of features has been modified.
Previously, it never displayed features that were selected but did not exist in found products (after filtration). It generated scenarios when the user selected 3 filters but could remove only one or none of them.
Now, users always see all selected features, even if they returned 0 products. They can be seen and removed from the features filter menu and quick filter removal element.
It's useful when selected feature set results in an empty products list. Previously, the user could not see selected features nor remove them.
 

Expired elements deactivation
Getting started
In this article, you can learn about the expired elements deactivation functionality, which allows you to automatically deactivate CMS, promotion, and mobile app elements when the current date is after the end date. Deactivated elements save up server memory and increase website responsiveness. It also helps with better admin panel filtering and navigation, as unused elements won't be visible as "active" anymore, so it will be easier to find currently used ones.
Table of contents:
 Configuring the functionality
 
 
 Configuring the functionality
By default this functionality is disabled. In order to enable it you have to navigate to:
System > System / Settings > Built-in functions > Expired elements deactivation
Visualization of the functionality system settings
 
In the Expired elements deactivation tab you can find a single switch called Deactivation enabled, by enabling it you are enabling the automatic deactivation of elements with expired end date. Elements are deactivated 2 weeks after the end date expiration.
The affected elements are:
CMS blocks
CMS pages
Altshops
Product stickers
Cart promotion rules
Promotion pages
Opensets
Private offers
Sliders
Layout banners
Popups
Mobile app elements: articles, carousels, cms elements, current offers, homepage products, sub campaigns
The command is set to run every day at 2 am.
 

Delivery point widget
Getting started
In this article, you will find information about the delivery point widget. The delivery point widget allows selecting delivery services that deliver to parcels to be shown as one delivery option during the order process and will both be visible on the map at the same time with customization options.
Visualization of the delivery point widget functionality
Table of contents:
 Configuring the delivery point widget
Delivery types / list configuration
System / settings configuration
 Customer perspective
 
 
 Configuring the delivery point widget
Delivery types / list configuration
In order to add multiple delivery options to one delivery widget you have to navigate to delivery types and turn on the switches on the desired delivery options.
You can access delivery types tab in the:
System > Delivery types / list
Visualization of the delivery types / list
In the Delivery types / list expand your desired delivery option that delivers to the parcels and select the new Is in delivery point group? (1) switch. By turning this switch ON you are adding the selected delivery option to the group. Multiple delivery options can be in the group.
  RememberIn order for a delivery method to be visible for the customers it needs to be enabled both in the Delivery types / list and in the desired altshop. You can find more information about activating the delivery types in the altshops in the Delivery costs / list - browsing and managing delivery costs article.
System / settings configuration
For further configuration of the functionality you have to navigate to:
System > System / settings > Built-in options > Delivery point map
Visualization of the delivery point map settings
In the delivery point map you can find the following options:
 Default latitude - A default map center latitude when user location cannot be obtained
Default longitude - A default map center longitude when user location cannot be obtained
Default zoom - A default zoom level when user location cannot be obtained. This value can be set between 0 and 21, where 21 is the closest one, and 0 farthest away.
Clustering enabled - Enables clustering of delivery points on the map. It groups them when the map is zoomed out, but introduces a significant performance penalty.
 
 
 Customer perspective
The new delivery point widget can be accessed by the customers in the cart process on the "Select the delivery method" step
Visualization of the delivery method step in the cart process
When customer selects the delivery point map he will see points near his location if he allowed for a location sharing on their device or a default view configured in the System / settings.
Customer is able to search the map for their desired delivery point and if there are too many parcels to show them next to eachother they are being merged into one single icon with a number of parcels in this region (1).
Customers are also able to deselect the delivery companies they do not prefer (2).
Visualization of the delivery point map (desktop)
Visualization of the delivery point map (mobile)
Visualization of the delivery points (mobile)

Campaigns and titles
Getting started
In this article, you can find how campaigns are created and accepted after a certain period of time and the associated titles and qualifiers by which the application is able to promote consumers who have met the conditions.
Campaign is a process that works for a selected period of time. Campaigns count all the orders made with their value and according to qualifiers promote or demote customers that met 
set requirements.
Title is a customer rank that affects his used altshop and with that possibly products, promotions, and content on the website. A title can be possibly promoted or demoted depending on set qualifiers and the customer result of the campaign.
Qualifier is a JSON function that set various requirements in order to promote users if they are met.
Table of contents:
 Campaigns
Creating new campaign
Accepting completed campaign
 Titles
Creating new titles
Qualifiers
 
 
 Campaigns
Campaign as a process decides based on qualifiers what account will be promoted or demoted to the next title depending on customer purchase history.
Campaigns can be found in the admin panel under Campaigns > View.
  Warning    Campaigns were created with the intention to be handled regularly. Whenever a campaign is ready to be accepted and calculated it should be done as soon as possible. There shouldn't be a situation, where two campaigns at once are ready to be accepted and calculated.
Calculating both campaigns at once will result in an error and calculation freeze, which will result in the campaign system being unusable until fixed by Tau Ceti.
  
Visualization of the campaigns list
In the campaign view, You can filter campaigns whether they are active or not. The campaign is seen as active only when the current date is between the specified date range.
For example, if a campaign has a range of 1/11/2020 – 30/11/2020 it will be visible as active only if the current day is in this range.
In this view, you can see all past, currently active, and future campaigns with their information like:
ID – System ID of the campaign, it cannot be changed. The system recognizes various components on the website by their ID.
Short name – Short name of the campaign. It is specified automatically by the system. The name depends on the year and the number of the campaign.
Name – Full name of the campaign.
Start date – Date on which the campaign will start. The set time is always local time.
End date – End date of the campaign. After the end date is reached the campaign will receive “Campaign ready for acceptance” status, which will allow the user to accept the campaign and process user title changes. More on accepting the completed campaign can be found on Accepting completed campaign. The set time is always local time.
Status – Current status of the campaign. you have three statuses:
Not processed – Campaign did not end yet. This status will be visible on current and future campaigns in the admin panel.
Campaign ready for acceptance – Campaign ended and still hasn’t been processed by the Yves Rocher employee.
Campaign closed – Campaign ended and has been processed.
 
This page also has Add button (1) located in the top right corner of the Campaigns table. This button will create a new campaign. More on creating a new campaign can be read in Creating new campaign section.
 
Creating new campaign
In order to create a new campaign you need to click Add button (1).
Visualization of the creating of the new campaign
 
In order to create a new campaign you need to specify information like:
Name – A Long name of the campaign.
Campaign Year – Year of the campaign. This year will be visible on the short name of the campaign in the admin panel.
Campaign Number – Number of the campaign, it’s usually set to a current campaign month. This number will be visible on the short name of the campaign.
Start date – Start date of the campaign. The set time is always local time.
End date – End date of the campaign. After the end date is reached the campaign will receive “Campaign ready for acceptance” status, which will allow a user to accept the campaign and process user title changes. More on accepting the completed campaigns can be found on Accepting completed campaign. The set time is always local time.
Altshops – Altshops on which created campaign will gain orders information.
After you fill in all the necessery fields you can save our newly configured campaign by pressing the Save button (2).
With our campaign saved it’ll activate automatically on a set start date and end on the end date. A campaign that ended is not closed or processed and it needs to be accepted manually by the employee in order to grant customers promotions and demotions.
More on accepting the campaigns can be found in Accepting completed campaign section.
 
Accepting completed campaign
When the campaign is over, the user of the administration panel will be given the opportunity to move to campaign acceptance by selecting the Results acceptance button. After selecting the button, the application will start the operation of calculating and promoting the customers that participated in the campaign. 
  Warning   In case two campaigns are ready for acceptance at once, please accept only one campaign, wait for it to calculate (so the report for this campaign can be accessed), and then proceed with accepting the other campaign. Accepting both campaigns at once will result in an integration freeze and they won't get calculated until fixed by the Tau Ceti team.  
The campaign acceptance process consists of four stages, described below:
Commission
Visualization of the commision view
This step was used to determine what commission Member Club customers will get.
As Member club is mostly abandoned functionality, this step can be skipped.
Titles
Visualization of the titles view
In this step, you can see all customers that participated in the selected campaign.
From customer information, you can see their MC hash, first and last name, e-mail address, and phone number. you can also see their title statuses:
Status – Status of the title qualifier. It can be above qualifier, which will promote the customer, or below qualifier which won’t do anything if a customer meets current qualifier conditions. If a customer doesn’t meet current qualifier conditions he can be demoted if a title is configured like so.
Overdue – invoice payment status. That was MC functionality. Not used anymore.
Current title – Customer current title.
New title – Customer's new title, which will be assigned to him after acceptance of the campaign. It can be set or changed with “Change title”
In this step you can manually change the title of the customer just in case there is a need.
Hierarchy changes
Changes in the hierarchy are member club functionality that isn’t used anymore, this step can be skipped.
Confirmation
This step is the last step of campaign acceptance.
Visualization of the confirmation view
In this step, you can see the number of customers with the above and below statuses with their total percentage. After ensuring that the campaign is correct and promotions and demotions are correct, you can close the campaign with the Close campaign button (4).
With the campaign closed all the customers that had the Above status will be promoted depending on the qualifiers to the new title or demoted depending on the title settings.
 
 
 Titles
Titles as customer ranks allow us to set specific qualifiers for them in order to create a title hierarchy, which will give us more options to manage what customers will be able to see on the website based on their order history.
Titles can be found in the admin panel under Titles > View.
Visualization of the titles section
Titles can be filtered by their activity (if they’re active or not). Filtered activity is read from “is active?” field.
In the Titles tab you can see basic information about the title:
ID – The system ID of the title, it cannot be changed. The system recognizes various components on the website by their ID.
Title – Full title name
Short title – Short title name usually used in promotions and qualifiers options.
Is active? – check If the selected title is currently active.
Primary – Member club functionality that isn’t used anymore.
You can create new titles with Add button (1) located on the top right corner of the table. More on creating titles can be found on Creating new titles located on the page below.
Creating new titles
If there’s a need to create a new title you can do it by pressing Add button (1) located in the top right corner of the titles section.
Creating or editing the title is separated by sections. The first one is the Title section.
Visualization of the title section
In the Title section you need to specify:
Title – A name of the title
Short title – Short name of the title (e.g. T0, TS, TG)
Is active? – switch if the title is active
There’s also a Leadership switch. This was Member Club functionality, so it’s not used anymore. It should be left on OFF.
The next sections are Qualifiers and Promotion / demotion rules.
Visualization of the Qualifiers and Promotion / demotion sections
In the Qualifiers section, you  need to select our created qualifier and apply rules to it
(e.g. Orders count from 1 >= 1).
More on qualifiers can be found in the Qualifiers section.
In Promotion / demotion rules section you have various fields you can customize:
Number of campaigns – In this field, you can select a number of campaigns that will be used to check qualifiers. E.g. if it’s set to 2, the customer needs to meet qualifier requirements for 2 campaigns in order to promote / demote. This field is in most cases left on 1.
Demote to – Drop down menu which allows us to select other titles that are supposed to be lower in the hierarchy. That customer with this title will be demoted if doesn’t meet current title qualifier requirements.
Allow demotion to – In this field you can specify other titles that customers can be demoted.
  ExampleBased on the title promotion path set to T0 > TS > TG and with a customer that has current title TG.
If a Customer with a title TG doesn’t anymore meet the requirements for that title in the next campaign, he’ll be demoted to TS if Demote to is set to TS.
With set Allow demotion to: T0 when a customer also doesn’t meet requirements for TS title, he’ll be demoted to T0 title.
As normal demotion path would go TG > TS > T0 because on this campaign he doesn’t meet requirements for TG so the next check for TS qualifier requirement will be on the next campaign it’ll demote TG > T0 as system checks, that customer also doesn’t meet requirements for TS so it demotes him 2 titles at the same time to the T0 title.
Promote to – Drop-down menu which allows selecting titles that are supposed to be higher in the hierarchy. If that customer met the qualifier requirements for the next title,
he will be promoted.
Promote only if matches qualifiers of next title – Switch that will read the qualifiers of the next title. It can be used when in the current title there are no specified qualifiers, so when T0 title has no qualifiers and the next title in the hierarchy, TS has “Orders count from 1 >= 1” qualifier it will promote the customer to the TS title if he makes 1 or more orders in the selected campaign.
Allow promotion to – In this field you can specify other titles that customers can be promoted to. This work same as with Allow demotion to 
Current Title path – In this section, you can see the current title path. Current title will be bolded out. Example of the title path:
There are also sections:
Credit policy
Commission
Reports access
Dashboard tabs access
But as they’re Member club functionalities they’re not used or supported anymore, so they’ll be skipped in this documentation.
Qualifiers
Qualifiers are the requirements that need to be met in order to promote the customer to the next title or in case the customer does not meet the requirements he will be possibly demoted depending on the current title setup.
Qualifiers can be found in Titles > Qualifiers
Visualization of the qualifiers section
In the qualifiers section you can see basic information about qualifiers:
ID – System ID of the qualifier. It cannot be changed. The system recognizes various components on the website by their ID.
Type – Type of the qualifier. You currently have 3 qualifier types:
Orders count – This type will count the number of the orders
Orders value – This type will count the value of the orders
Dependent members count – This type is from Member Club functionality, which is not supported anymore.
Name – Name of the qualifier
Public name – Public name of the qualifier. It’s Member club functionality so it’s not visible anywhere anymore.
Public name (short) – Short public name of the qualifier. It’s Member club functionality so it’s not visible anywhere anymore.
Is active? – Check if the qualifier is currently active.
 
You can add new qualifiers with the Add button (2) or edit existing ones.
Visualization of the qualifiers section
 
The fields you can find while adding or editing qualifiers are:
Type – Type of the qualifier. You currently have 3 qualifier types:
Orders count – This type will count the number of the orders
Orders value – This type will count the value of the orders
Dependent members count – This type is from Member Club functionality, which is not supported anymore.
Name – Name of the qualifier
Public name - Public name of the qualifier. It’s Member club functionality so it’s not visible anywhere anymore.
Public name (short) - Short public name of the qualifier. It’s Member club functionality so it’s not visible anywhere anymore.
Description – Description of the qualifier. It’s Member club functionality so it’s not visible anywhere anymore.
Image (SVG) – Image of the qualifier. It was used by Member club functionality so It doesn’t do anything now.
Is active? – Switch if the selected qualifier is active.
Parameters – JSON parameters of the qualifier.
  ExampleWith parameter JSON set to: 
{    
 "orders_count_from": 1,     
 "only_orders_from_campaign": false 
} 
The qualifier counts all the orders from 1st created order as orders_count_from is set to 1 even those orders without the campaign because only_orders_from_campaign is set to false. So when you set this qualifier in Title settings to Qualifier >= 1 the customer will be promoted to the set title when he creates 1 or more orders and created campaign gets processed as titles are granted after the campaign is processed by the employee.
As qualifiers are wide in range of possibilities the documentation of the parameters is separate and can be found when editing or creating new qualifiers on the website below the parameters section.
Visualization of the parameter documentation

Omnibus price history
Getting started
In this article, you can learn about the omnibus price history functionality. This functionality allows showing the customers if the current product catalog price is the lowest catalog price in the last X days or not (1) when the promotion price is applied to the product. If the price is not the lowest one, there will be information about the lowest price in the last X days. The price check occurs every day at 01:05, 09:05, 16:05, and 23:30. This functionality also introduces a new price history report.
Visualization of the omnibus functionality on a product page (desktop)
Visualization of the omnibus functionality on a product page (mobile)
Table of contents:
 Configuring the integration
 Product price history
 Customer perspective
 
 
 Configuring the integration
In order to turn on the integration, you have to navigate to:
System > System / settings > Built-in functions > Omnibus price history
Below you will find a description of possible actions.
Visualization of the omnibus price history system settings
Display information about the lowest price - An ON / OFF switch that enables the integration on the website.
Show lowest price from [...] days - A field where you can define from how many days back the lowest price should be read. The price check occurs every day at 01:05, 09:05, 16:05, and 23:30.
Store prices for [...] days - A field where you can define for how many days the prices should be stored. Cannot be lower than the count of days used to detect the lowest price. Stored prices are used in the product's price history report. You can read more about this report in the  Product price history chapter.
 
 
 Product price history
With this integration, a new report has been created. The product price history report can be found in:
Reports > Products price history
  RememberPrices are updated four times per day. The report contains prices for every product which was active in the default altshop on a given day. If a product was not active in the default alt shop, there will be no row for a given product and day. Only default altshop prices are used. Prices history is stored for X days (configurable in the system settings). You can learn more about altshops in the Alt shops - Introduction article.
The SKU column in the report is just to allow for faster data analysis. Data is stored per product, not per SKU, as all SKUs assigned to a single product always have the same price.
Below you will find a description of possible actions.
Visualization of the products price history
Date range - A range of dates from which price history will be exported.
Product SKU - A list of SKUs separated by commas that will be exported.
You can export the report with an Apply filters button. It is possible to export the report without any filters applied, then all available SKUs will be generated in the report with a date range between the first time the integration was enabled and the current time.
Below, you will see all available columns in the exported XLSX file.
Visualization of the products price history xlx file
Product_id - An internal ID of a product
Product_sku - Products SKU.
Date - A date where a price was registered
Price - A registered price for a selected day.
 
 
 Customer perspective
With the functionality turned on, customers will see in every place on the website where products are visible (for example product catalog, promotion pages, in the cart) information if the current catalog price is the lowest one with a percentage of how much bigger / smaller it is to the current price (1).
This information is only visible when a selected product has applied a promotional price. Products without a promotional price will not have visible omnibus functionality.
Below you will see examples of the functionality on the website
Visualization of the omnibus functionality when current catalog price is higher than previous one
Visualization of the omnibus functionality when current catalog price is lower than previous one
Visualization of the products in the product catalog (desktop
Visualization of the products in the product catalog (mobile)

Simplified mobile top menu
Getting started
This article describes simplified mobile top menu functionality, that shows top menu categories in the mobile view (1). This functionality allows partners to decide, if they prefer to use top menu for mobile version of the website.
  RememberThe content visible in the top menu is configured in CMS > Top menu / list. More information regarding top menu can be found in [UNDER CONTRUCTION] article.
Visualization of the mobile view of the home page.
Table of contents:
Turning on the functionality
Customer perspective
 
 
 Turning on the functionality
When turned on, simplified mobile top menu will be visible at all times on the mobile version of the website. It can be turned on in the Admin panel > System > System / Settings > Built-in functions > Top menu.
Visualization of the top menu tab
In Top menu tab we can find Simplified mobile menu (1) switch, which will turn on the functionality when it’s turned on.
 
 
 Customer perspective
With the functionality turned off, customer will see the old top menu, where he needs to click on the menu in the top right corner in order to see available categories on the website
Visualization of the mobile top menu when functionality is turned off
With functionality turned on, the customer will see available categories in the top menu (1) and will be able to scroll through them and select the desired one, which will redirect him to that web page.
Visualization of the mobile top menu when functionality is turned on
 

Catalog

Product management
Getting started
In this article, you can find information about product management in the admin panel. There are two ways to manage products:
In the admin panel, described in this article. This method is recommended for singular product changes or smaller works.
Using product catalog import / export. This method is recommended for bulk product management. You can find more information about this method in Product catalog export and import article.
  RememberFor a product to be visible for the customer it needs to be enabled in the desired altshop. You can find information about activating products in altshops in the Products / list - browsing and managing products in altshop module article. 
  RememberYou can find information about catalog categorization in the Catalog categorization article.
 
  RememberThis article contains information about the products with their catalog pricing. If you wish to learn more about the promotion module, where these products can be used you can find more about it in the Promotion module introduction article.
 
Visualization of the product page on the e-commerce platform
Table of contents:
 Product page on the e-commerce platform
Catalog management
Filters
Tags mass assignment
Products list
Product creation
 Colors
Colors list
Color creation
 Properties and tags
Properties
Tags
 Images upload
 Mass product removal
 
 
 Product page on the e-commerce platform
Below you can find a visualization of how the product is visible to the customers on the e-commerce platform with the most important sections highlighted.
Visualization of the product page on the e-commerce platform (desktop view)
 
Visualization of the product page on the e-commerce platform (mobile view)
The product page contains the following sections:
(1) Product Name - A name of the product.
(2) Product rating. The average rating of the product that was rated by the customers. You can find more about Rate & Review functionality in the Rate & Review article.
(3) Color selection - Contains all of the created color variations for the selected product.
(4) Product capacity - The capacity of the product. Usually, the capacity is written in milliliters or grams (e.g. 200ml or 50g).
(5) SKU number - A unique product number in the product catalog.
(6) Main image - A main product image (e.g. 63154.png)
(7) Additional images - Additional product images (e.g. 63154_1.png). On mobile devices customers can swipe the image left or right to see additional images.
(8) Product Description - The following description fields will be visible here: Main description, Effects, Usage, Capacity and packaging and Additional information
(9) Product ingredients - Ingredients of the product. The following description fields will be visible here: Ingredients and Notes.
 
 
 Catalog management
All products that have been imported, or manually created in the admin panel can be found in
Catalog > Products / list
In this section, products can be created or edited with all of their core attributes.
  RememberProduct promotional prices can be modified in the product altshop configuration. You can find more about this section in the Products / list - browsing and managing products in altshop module article.
Filters
The product list can become vast, so to help with that you can use available filters, to slim down the product selection.
Visualization of the product filters
The following filters are available:
Product status - Current active status of the product. The available statuses are:
Active
Inactive
Product visibility - The status of product visibility on the e-commerce website. Available statuses are:
Hidden
Visible
Product tags - Tags assigned to the filtered products.
Product category - Categories assigned to the filtered products.
Product SKU - SKU lists separated by a comma.
Product price - The range of the catalog prices.
Gifts - A status of gift flag. Available options are:
Yes - Shows products that have gift flag activated.
No - Hides products that have gift flag activated.
New products - A status of Is_new flag. Available options are:
Yes - Shows products that have gift flag activated.
No - Hides products that have gift flag activated
Availability - Availability status of the filtered products. Available options are:
Out of stock
In stock
Stock value - A range of the current stock values.
Creation/update time - A range of dates, when the products were created or updated.
Tags mass assignment
Tag mass assignment allows to assign multiple tags to multiple products at once.
Visualization of the tags mass assignment section
When the desired tags are selected you are able to apply them to the selected products, or set for all products.
Set for selected only applies tags to all of the products that are checked in the products table.
Set for all applies the selected tags to all filtered tags. Please note, that searching the products in the products table does not filter products. Before using this option please make sure that all desired filters are applied, as misuse of this functionality might result in setting tags to more products than desired.
Products list
In the products list you can find all of the products currently present in the database.
Visualization of the products section
Below you will find a description of all possible actions you can perform in the Products section.
Select the Show X entries (1) field to set the number of products, displayed on one page (min 10 / max 100).
The names of the columns (2) that contain information about target products. Each column is susceptible to sorting.
To sort the records, click on the title of the column in question.
Selection checkbox - A checkbox used for the Set for selected options in tags mass assignment and activity status set.
SKU - Product SKU number
Name - Product name
Price - Catalog price of the product
Is active? - A switch that defines if the product is active in the product catalog or not. It can be turned on and off in this view.
Actions
An Edit button that edits the desired product. You can learn more about product editing and creation in the Product creation section.
A duplicate button, that duplicates the desired SKU. It duplicates all data.
Add product button (3), which creates a new product in the product in the product catalog. You can learn more about product creation in the Product creation section.
Search field (4), which allows searching for the desired products. Products can be searched by their name, friendly URL and SKU.
Page buttons (5), which allows users to change the page of currently viewed products.
Clear selection (6) button, which clears the selection of previously selected SKUs by their Selection checkbox.
Activity status change (7) for multiple products same as with tag mass assignment allows to change for selected products or all filtered products the catalog activity status. Please note, that searching the products in the products table does not filter products. Before using this option please make sure that all desired filters are applied, as misuse of this functionality might result in setting tags to more products than desired.
Product creation
This view edits or creates a new product in the product catalog. Some of the options are only visible, when the product is edited, and are not visible while creating a new product. It is possible to delete the product by pressing the Delete this product button at the bottom of the product page.
These options can be also be assigned and changed in the product mass import. If you want to learn more about product mass import please see the Product catalog export and import article.
In the top right corner of the edit product page, you can find Alt shops prices button, which redirects the user to Altshops > Products / list, where the promotion prices can be set for the product. You can learn more about it in the Products / list - browsing and managing products in altshop module article.
Visualization of the product edit form
The following options are available when creating or editing a product:
General Data - This section contains general information about the product
SKU - Product SKU
Name - Product name. This name is visible on the website
Friendly URL - URL of the product.
Title - Title of the product, that is visible in the browsers tab card.
Short description - A short description of the product visible directly under it's name on the website.
Price - Catalog price of the product.
Capacity - The capacity of the product. Usually, the capacity is written in milliliters or grams (e.g. 200ml or 50g). This option is visible on the website.
EAN - EAN number of the product in an EAN-9 or EAN-11 format. One product can have multiple EANs separated by a comma.
Main category - The main category the product is assigned to. You can learn more about catalog categorization in the Catalog categorization article.
Additional categories - Additional categories that the product is assigned to. You can learn more about catalog categorization in the Catalog categorization article.
Is active? - An activity flag, that defines if the product is available in the product catalog. When the product is disabled in the catalog it is disabled globally for the customers.
Is hidden? - A flag that defines if the product should be hidden in the product catalog on the website as well as in search options. Product with this flag turned on it is still possible to add the product to the cart with promotions or by adding directly the SKU in the cart.
Sort order - The sort order of the product. This functionality is no longer used.
Visualization of the colors section in product edit form
Colors section shows all of the created color variations for the selected product. Each color has a unique SKU number, color name, activity status and stock value. You can create a new color by pressing the Add button or edit the existing one by pressing the edit button. Delete button removes the color variation from the product.
Color name is not created while creating a new color variation. You can learn more about color name in the  Colors section.
Visualization of the color creation for a product
While creating a product you have to specify its:
SKU - A unique SKU number of the color variation for the product. When a product has at least 1 color, then one of the variations has to be set to the original product's SKU. This will define the main color. For example, if the product 55533 has 3 colors: Beige, blue and red, then at least one of them has to have SKU 55533 like that: Beige (55533), Blue (55534) and Red (55535).
Color name - Color name of previously created color. You can learn more about it in the  Colors section.
EAN (optional) - An EAN number. It is possible to have multiple EAN numbers for a single color variation by separating them with a comma ( ",").
Is active? - Activity status of the color variation. If it is disabled it won't be accessible and visible by any customer on any altshop in the e-commerce platform.
Additionally same as with normal products you are able to upload images that will be used with the selected color variation as well as you can edit the stock values. You can learn more about stocks further down this section.
Visualization of the stickers section in product edit form
Stickers - Stickers define different flags that can be applied to the products. Flags have different properties that apply to the product once they are active.
Green point - The green point flag marks the product with a green dot as well as information, that it is a green point product.
Bestseller - Bestseller flag gives the product "Bestseller" information on the website, as well as allows to find the product when filtering for bestsellers.
Outlet - Marks the product as an outlet.  By itself, this flag doesn't show any difference on the e-commerce platform for the customer. It is mostly used in promotions, that want to exclude product sets from them.
Limited edition - Marks the product as a limited edition product. This flag by itself doesn't change anything on the e-commerce platform, and this option is usually used in the generated product feeds.
Set - Marks the product as a set. Displays the SET sticker when enabled next to the product on the product page and in the cart - The sticker text can be changed in the translations under phrase Set. It is mostly used in promotions, that want to exclude product sets from them. 
Is New until date - A date to which the product will be marked as new. New products are marked on the website as new, as well as can be found when filtering for new products.
Gift - The gift flag marks the product as a gift. Gift products are not visible in the product catalog on the website and can be added to the cart only using promotions.
Gift of choice - The gift of choice flag marks the product as gift of choice allowing it to be used in the gift of choice promotions. Both Gift and Gift of choice flags need to be enabled at the same time for a product to be used in the gift of choice promotion.
Visualization of the photos section in product edit form
Photos - Displays all of the product images assigned to the selected product. This option is only visible when editing a product. The upload button redirects the user to  Images upload.
It is possible to remove all additional pictures by pressing the delete button. The main picture can only be changed by uploading a new product image in Images upload.
Visualization of the tags section in product edit form
Tags - Displays all assigned properties and tags to the product. It is possible to assign a new property and a tag by using the list of available properties, and then selecting the desired tags that are assigned to them.
Visualization of the description section in product edit form
Description - Contains all of the product descriptions that are visible to the customer on the e-commerce platform as well as the mobile app. This section is separated by the tabs.
Main description, Effects, Usage, Capacity and packaging and Additional information are all visible one after another in on the product page. It is a common practice to put the product description mainly in the main description section, as it doesn't change anything visually for the customer and makes it easier to manage one bigger chunk of description / code. Main description is visible for the customers directly below the product images on the e-commerce platform.
Ingredients and Notes - These sections are the only other sections that are visible to the customer, and are not in the same view as the description sections described above. They are visible on the e-commerce platform by pressing the ingredients text just below the product image.
Visualization of the product page on the e-commerce platform
Keywords - Product keywords that can be used in the search engine to find a product. For example by typing here "Beige, delicate" you will allow customers to find this product by searching for "Beige" or "Delicate" in the search engine.
Mobile app description - Product description that will be displayed in the mobile app. This field cannot contain any HTML or CSS code.
Mobile app ingredients - Product ingredients that will be displayed in the mobile app. This field cannot contain any HTML or CSS code.
Visualization of the stock section in product edit form
Stock - The stock tab stores information about current product stock availability as well as allows to set the fixed availability and minimum values for a product.
Fixed availability - Allows to set the fixed availability for a product. Available options are:
Empty field - Default option. When the stock is at minimum stock value it will not be available. When it is above this value it will be available for the customer.
Always in stock - The product will always be available for the customer no matter of it's stock value.
Always unavailable - The product will always be unavailable for the customers on the website, even if it is in stock.
Stock value - Current stock value of the product. Usually, this value is automatically updated by TC Logistics or JOY functionalities.
Minimum stock value - The minimum stock value above what the product will be available for the customer in case no fixed availability is used. When the stock value is set to 5 the product won't be available once it's stock value reaches 5.
Warning stock value - Warning stock value threshold after which Yves Rocher employee defined in the system settings will receive a warning, that the stock value is getting low.
Visualization of the herbarium section in product edit form
Herbarium - A section that allows to select ingredients from the Herbarium and displays them on the product page. You can learn more about herbarium in the [In progress] article
Visualization of the metadata section in product edit form
Metadata - Contains information about the products meta data that can be used in the product feeds.
META Title - Title of the product available in the meta data.
META description - Description of the product available in the meta data.
META keywords - Keywords of the product available in the meta data.
 
 
 Colors
Colors section in the admin panel located in Catalog > Colors / list allows to manage color names that are later on used by the color variations of the products.
Colors list
Visualization of the colors list
Below you will find a description of all possible actions you can perform in the colors section.
Select the Show X entries(1) field to set the number of colors, displayed on one page (min 10 / max 100).
The names of the columns (2) that contain information about target colors. Each column is susceptible to sorting.
To sort the records, click on the title of the column in question.
ID - Internal ID of the color.
Name - Color name
Creation/Update time - A date and an hour when the color was created or last updated.
Actions
An Edit button that edits the desired product. You can learn more about product editing and creation in the Color creation section.
View button allows to view the selected color without the ability to edit any fields.
Delete button allows to delete the desired color.
Add button (3), which creates a new color.
Page buttons (4), which allows users to change the page of currently viewed colors.
Color creation
Visualization of the color creation
Color creation contains simply a Name field, which contains the desired name of the color that should be visible for the customer.
 Properties and tags
Properties and tags help organize product catalog into a manageable sections, which allows customers to filter the catalog on the e-commerce platform by using the selected combination of properties and tags, that are assigned to the products.
Visualization of the product filter on the platform
Properties
Properties are entities that contain tags in them. Properties are assigned to the selected products when they contain any tag. Customers are able to filter products in the product catalog by the properties they are assigned to.
Visualization of the properties list 
Below you will find a description of all possible actions you can perform in the properties section.
Select the Show X entries(1) field to set the number of properties, displayed on one page (min 10 / max 100).
The names of the columns (2) that contain information about target properties. Each column is susceptible to sorting.
To sort the records, click on the title of the column in question.
ID - Internal ID of the property.
Name - Name of the property. This name is visible to the customers.
Is active? - Shows the property activity status.
Visible on frontend? - Shows if the product is visible on the frontend to the customers.
Sort order - Sort order of the properties. It defines in what order properties are visible on the e-commerce platform.
Update time - A date and an hour when the color was last updated.
Actions
Tags button redirect the user to Tags section in the admin panel with all of the tags that are assigned to the selected property.
An Edit button that edits the desired property. You can learn more about property editing and creation further down below.
View button allows to view the selected property without the ability to edit any fields.
Delete button allows to delete the desired property.
Add button (3), which creates a new property. You can learn more about property editing and creation further down below.
Search field (4), which allows searching for the desired properties. Properties can be searched by their Name.
Page buttons (5), which allows users to change the page of currently viewed properties.
Visualization of the property creation
When adding a new property or editing an existing one you have the following options:
Name - Name of the property. This name is visible to the customers.
URL name - A name of the property, that will be used in the URL when filtered.
Sort order - Sort order of the properties. It defines in what order properties are visible on the e-commerce platform.
Is active? - Shows the property activity status.
Visible on frontend? - Shows if the product is visible on the frontend to the customers.
Tags
Tags are filter options that can be assigned to the selected properties, and to the products. Assigning tags to the products will allow customers to filter by them in the product catalog allowing customer to customize, what type of product they would like to see.
Visualization of the tags list section
Below you will find a description of all possible actions you can perform in the properties section.
Select the Show X entries(1) field to set the number of tags, displayed on one page (min 10 / max 100).
The names of the columns (2) that contain information about target tags. Each column is susceptible to sorting.
To sort the records, click on the title of the column in question.
ID - Internal ID of the tags.
Name - Name of the tag. This name is visible to the customers.
URL name - A URL name that will be used in the URL when the tag is selected on the e-commerce platform filter.
Property name - A name of the property that the tag is assigned to.
Sort order - Sort order of the tag. It defines in what order tag are visible on the e-commerce platform.
Update time - A date and an hour when the color was last updated.
Actions
An Edit button that edits the desired tag. You can learn more about property editing and creation further down below.
View button allows to view the selected tag without the ability to edit any fields.
Delete button allows to delete the desired tag.
Add button (3), which creates a new tag. You can learn more about property editing and creation further down below.
Page buttons (4), which allows users to change the page of currently viewed tag.
Visualization of the tag edit form
When adding a new tag or editing an existing one you have the following options:
Property - A property name to which the tag is assigned to.
Name - Name of the tag. This name is visible to the customers.
URL name - A URL name that will be used in the URL when the tag is selected on the e-commerce platform filter.
META Title - Title of the tag available in the meta data.
META description - Description of the tag available in the meta data.
META keywords - Keywords of the tag available in the meta data.
 
 
 Images upload
Products require to have available images in multiple sizes and formats, which means, that manual image management would be hard to handle, and be prone to errors. Images upload section allows to automate this by having the user to upload the desired 1000x1000 PNG images, and the rest of the process is handled by the system.
Visualization of the product images import
First, you have to select the desired images you wish to upload. You can do it by pressing the Select files button, or drag & drop the files from your computer on the blue box.
All files named SKU.png will be saved as the main photo for this SKU. If you want to import additional photos for this SKU please name the file with the number suffix, f.x. SKU_1.png, SKU_2.png etc. Please remember that if you have already uploaded SKU_1.png and you would upload SKU_1.png again, a new file will overwrite the existing one.
Small color images name as SKU_COLOR.png. One SKU can only have one color preview.
If you want to upload more than 50 files please create a ZIP archive and upload it here. They have to be included directory inside an archive, otherwise, they will be ignored.
With the uploaded files you will receive a result if this file is correct or incorrect (e.g. the file format is not in a png format). With the files review you are able to select the Delete all existing images for imported SKUs, which will remove all product images assigned to the uploaded SKUs.
With all options reviewed, you can proceed with an image import by pressing the Import selected files button.
All imported product images are automatically converted to .webp format, so they are lighter and load faster for the customers on the e-commerce platform.
 
 
 Mass product removal
As product management in Catalog > Products / list allows to manually remove singular products, and product import doesn't support product removal a Mass product removal tab has been created to reduce the need for manual work. This section allows users to remove multiple products by providing their SKUs at once.
This section can be found in Catalog > Mass product removal
Visualization of the mass product removal
In the Mass product removal section, you can type the product SKUs that should be removed from the product catalog and separate them by comma (e.g. 55533,12345,54321).
If product SKU is provided, it will be deleted along with it's attributes / color variations.
A single attribute SKU can be provided to delete a single attribute. It applies only to non-primary attributes (attribute SKU is different than product SKU).
Please note, that this action is irreversible.

Catalog - Images upload
Getting started
This article describes uploading images for products, their sizes, format and how to find them in the gallery (The gallery article can be found here). 
  RememberEvery product image has to be added in the Catalog > Images upload
   Visualization of the Catalog, Images upload
Table of contents:
Images restrictions and guides
Guidelines
Images names
Product images sizes
Image upload
Select files to import
 
 Images restrictions and guides
Guidelines
Images upload already contain guides on how the images are processed:
All files named SKU.png will be saved as main photo for this SKU. If you want to import additional photos for this SKU please name file with number suffix, f.x. SKU_1.png, SKU_2.png etc. Please remember that if you have already uploaded SKU_1.png and you would upload SKU_1.png again, new file will overwrite existing one.
Small color images name as SKU_COLOR.png. One SKU can only have one color preview.
If you want to upload more than 50 files please create ZIP archive and upload it here. They have to be included directory inside archive, otherwise they will be ignored
  NoteThe above guide is not the only one, that uploaders should be aware of. Images for products should be in PNG format only, they should also be in a size of 1000x1000px 
 
Images names
Every product images have to be named in a specific, role-related method:
(1) - This is the main image of the product, first to be seen, its name has to be SKU.png In this example it's 88737.png
(2) - These are all images named SKU.png and SKU_X.png Where X is a digit suffix that determines the order in which these images are presented (from top to bottom). In this example, it's 88737.png, 88737_1.png, 88737_2.png, 88737_3.png
(3) - Color images are used when a product has other color variants. These are named SKU_COLOR.png In this example 88737_COLOR.png and 88737_3.png are the same image renamed and uploaded twice.
   Visualization of the Product page, SKU 88737
 
Products images sizes
The main product image SKU.png ones uploaded will be transformed into several sizes. These can be found in the gallery (The gallery article can be found here). The most common sizes are 101x101(1), 184x184(2), 260x260 and 500x500(3). Every folder for them is named product_catalog_SIZE where SIZE is the value presented previously for example /uimg/product_catalog_500x500/
 
   Visualization of the Product page, example of image sizes
  RememberAll sizes are created and used automatically by the application. Uploaded images should always be in the size of 1000x1000px and in png format.
 
 Images upload
Before uploading images make sure to follow guide (1) (or see Images restrictions and guides). Images can be uploaded by clicking the Select files button (2) or by dragging and dropping files directly from the file browser (3).
 
Visualization of the Catalog, Images upload
 
Select files to import
After selecting files, a new section will show up with the line of progress (4), Checkboxes to choose whether uploaded files should be transferred to the gallery or not (1). There is an option to Delete all existing images for imported SKUs(2), this will erase all previously existing images for products that receive new ones. When everything is set click Import selected files(3) to update products with new images. 
 
Visualization of the Catalog, Images upload- Select files to import

CMS

Configurable CMS block
Getting started
In this article, you can learn about configurable CMS block functionality, which will allow you to put and properly configure banners visible on a website. There are two defined CMS blocks:
above_cart_steps_banner - Displays a configured banner only in a cart page (/cart).
above_layout_content_banner - Displays a configured banner everywhere except the customer panel, cart page, and checkout.
As with every CMS block that is configured to be visible on a homepage it is important to make sure, that created CMS block has exactly the same name as provided above. If the CMS block has a different name it won't be displayed on a website.
Visualization of the above_cart_steps_banner in a /cart page
Visualization of the above_layout_content_banner on a homepage
  RememberYou can find more about CMS blocks creation and configuration in the CMS blocks article.
Table of contents:
 Configuration
 
 
 Configuration
The new banners are configured exactly like every CMS block, but they have one new field, which manages the properties of the block.
Visualization of the configurable block configuration
In order to see the new JSON field you have to select the configurable block type.
The  CMS block configuration is a JSON field, which allows to configure few properties of created banners:
visibility (string) - Sets if the selected block is visible for all users, only logged-in users, or only logged-out ones. Available options are: all, logged_in, logged_out
closeable.position (string) - Sets the position of the close (X) button. Available positions are: top-right, top-left, bottom-right, bottom-left
closeable.color (string) - Sets the close (X) button color. Available options are:
 primary - Green.
 secondary - Red.
closeable.time (integer) - Sets after how many hours the banner will be visible to the customers again after they closed it.
width (string) - A CMS block width option. There are three possible widths:
full - Banner is stretched to fit the entire width of the screen. Please remember, that a proper background image has to be prepared for it to fit.
full-bg - Banner has the same width as the container width, but the rest of the screen width is colored with a color set in the background parameter.
container - Banner width that fits the website layout. The banner width is set to 1248px for the desktop view - the same as the slider.
background (string) - A background color that is visible when a full-bg width is selected. This value should be in hex i.e. #0AA78F
bottomShadow (boolean) - A small shadow below the banner that is visible whenever widths full and full-bg are selected. This field accepts true and false values.
Example of a valid JSON:
{"visibility": "all", "closeable": {"position": "top-right", "color": "secondary", "time": 1}, "width": "full-bg", "background": "#0AA78F", "bottomShadow": true}
 
It is possible to configure these blocks to change their state according to users login status (logged in / logged out) and have them still visible for all groups in the visibility property. This needs to be coded in the CMS block HTML content.
  RememberYou can find examples of checking of the current cart value and verification of the user logged in / logged out status in the Public JS API article.
 

Featured products list
Getting started
In this article, you will learn about the featured products list. Featured products list functionality allows displaying new, selected, or Exponea products in the respective tabs on the home page of the website below the slider (1). This block is responsive, so products will be correctly visible both on desktop and mobile devices without additional input.
Featured products need to be activated in the desired altshop in order to be visible on the website. You can find more about activating featured products in the Featured products / list - browsing and managing featured products in altshop module article.
Visualization of the featured products on the home page (desktop view)
Visualization of the featured products on the home page (mobile view)
To open the Featured products / list view, in the admin panel, navigate to:
Alt shops > Featured products / list
All possible operations to perform on the Featured products / list view can be done in the Filters (2), and Featured products / list (3) tabs.
Visualization of the featured products / list
Table of contents:
 Filters section
 Featured products / list
 Adding new featured products
 Configuring featured products list
Custom
Bestsellers
News
Exponea recommendations
 
 
 Filters section
The Filters section allows sorting of the featured products in the CMS module, based on the available filters. Below you will find a description of available filters
Visualization of the filters tab in the Featured products / list module
Is active? - Featured products list activity status.
After defining the above filters, select the Apply Filters button to get a list of sites according to the applied filters.  
 
 
 Featured products / list
The Featured products / list section allows organizing the filtered featured products, edit them and create new ones, delete them, and search for the desired featured products list.
Below you will find a description of all possible actions you can perform in the featured products / list section.
      Visualization of the select list section in the Featured products / list module
 Select the Show X entries(1) field to set the number of featured products, displayed on one page (min 10 / max 100).
The names of the columns (2) that contain information about a target featured products list. Each column is susceptible to sorting.
To sort the records, click on the title of the column in question.
ID - An internal ID of the featured product list.
Name - The system name of the featured product list.
Public name - Name of the featured product lists that is visible to the customers.
Sort order - Featured products sort order. The active list will be displayed in order according to this value.
Is active? - Activity status of the featured products list.
Actions - List of buttons with possible actions that can be done to the desired featured product list:
Edit - Edit desired featured products list. You can find more about editing in the  Configuring featured products list chapter.
View - Allows to view the content of the featured products list without the ability to edit any fields in it.
Delete - Deletes the featured products list without the ability to restore it.
Select the Add (3) button to go to the adding the new featured products list. You can learn more about adding of the featured products in the Adding new featured products list chapter.
Search box (4) where you can search for featured products list by their system name.
Page buttons(5), which allows user to change the page of currently viewed featured products lists.
 
 
 Adding new featured products list
Add button allows users to create a new featured products list. While creating a new featured products list, you can only set key features about the list, without the ability to add or remove products. In order to add or remove products to the list, you have to edit the desired featured products list. More about editing of the featured products list can be found in the  Configuring featured products list chapter.
Below, you will find a description of all possible fields that can be edited while creating a new featured products list.
Visualization of the adding of the featured products list
Name - The system name of the featured product list.
Public name - Name of the featured product lists that is visible to the customers.
Is active? - Activity status of the featured products list.
Sort order - Featured products sort order. The active list will be displayed in order according to this value.
Type - A type of the featured products list. You can find more about information about types in the  Configuring featured products list chapter. The available types are:
Custom - Custom added products and their sort order
Bestsellers - Custom added products and their sort order with additional recommendation of bestselling products list
News - Newly added products
Exponea recommendations - Products configured in the Exponea. More about Exponea integration can be found in the [UNDER CONSTRUCTION] article.
With all necessary fields filled, you can save the changes using the save button, and add the products to your list by editing it. More about editing the featured products list can be found in the  Configuring featured products list chapter.
 
 
 Configuring featured products list
As users are unable to add products to their featured products list during its creation, it is needed to edit the desired list. Below you will find different types of product lists.
 
Custom
Custom type allows users to add their desired products to the list and change their sort order.
Visualization of the custom type
You can change the sort order of the products by using the drag & drop functionality.
Products will show alerts next ot their name in case of product having no stock, or being inactive. You can remove the products by pressing the "remove" buton.
 
Bestsellers
Bestsellers type works exactly like custom type, but has one additional tab, where products are visible with their sold quantity, which helps to decide which products should be visible. You can add products by pressing the "Add to list" button
Visualization of the bestsellers type
In the Bestsellers propositions tab you can also hide the unwanted products by pressing the hide button.
You can change the sort order of the products by using the drag & drop functionality.
Products will show alerts next ot their name in case of product having no stock, or being inactive. You can remove the products by pressing the "remove" buton.
 
News
News type automatically adds and changes the products visible in the featured products list. It shows only the newest products.
 
Exponea recommendations
Exponea recommendations tab allows to select an Exponea product block from
CMS > Exponea / Recommend Product Block
  RememberYou can learn about the Exponea functionality in the [UNDER CONSTRUCTION] article
Visualization of the adding of the exponea recommendations type
 

Friendly URLs
Getting started
This article describes Friendly URLs and their aliases. Friendly URLs are links that are assigned to created content for example CMS pages, products, promotion pages or opensets.
Friendly URLs can have assigned aliases, which will redirect the user to the selected friendly URL using the custom-made alias.
To open the Blocks / list view, in the admin panel, navigate to:
CMS > Friendly URLs / list
In the Friendly URLs / list view, we can find one tab: Friendly / URLs (1)
   Visualization of the Friendly URLs / list page
Friendly URL aliases are located in the:
CMS > Friendly URLs / Aliases
In the Friendly URLs / aliases view, we can find two tabs: Filters (2) and Friendly URLs / aliases (3)
   Visualization of the Friendly URLs / aliases page
Table of contents:
 Friendly URLs / list
 Friendly URLs / Aliases
Filters section
Friendly URL / aliases section
Adding a new alias
Importing aliases
 
 
 Friendly URLs / list
Friendly URLs / list section contains all the already assigned URLs from all the products, CMS pages, Opensets and Promotion pages.
Friendly URLs are created in their respective categories, for example creating a new CMS page with URL /New_CMS_Page will create and assign automatically a friendly URL /New_CMS_Page to the created CMS page.
Below you will find a description of all possible actions you can perform in the Select block section.
   Visualization of the Friendly URLs section
 Select the Show X entries(1) field to set the number of friendly URLs, displayed on one page (min 10 / max 100).
The names of the columns (2) that contain information about a target friendly URL. Each column is susceptible to sorting. To sort the records, click on the title of the column.
ID - An internal ID of the Friendly URL.
Request path - The URL of the friendly URL.
Related element - An element of the website assigned to the friendly URL (i.e., CMS block, promotion page, a product, openset).
Update time - Last update time of the friendly URL.
Actions - An Edit button that redirects the user to the selected element where the friendly URL is located (i.e. CMS block, promotion page, a product, openset).
Search box(3) where you can search for desired friendly URL by its request path.
Page buttons(4), which allows user to change the page of the friendly URLs.
 
 
 Friendly URLs / aliases
The Friendly URLs / aliases section allows organizing the filtered aliases, editing them, and adding the new ones.
Aliases are alternative URLs that will redirect to the source URL. For example, if the source URL is a
"/Source_URL", and we create an alias "/New_link" customer can access the /Source_URL through the /Source_URL link and /New_link, as it redirect to the source link.
 
Filters section
The Filters section allows sorting of the aliases, based on the available filters.
Below you will find a description of each filter.
   Visualization of the filters section in the Friendly URLs / aliases
Update time - A range of dates, that filters the available aliases by their update time.
After defining the above filters, select the Apply Filters button to get a list of sites according to the applied filters.  
 
Friendly URLs / aliases section
The Friendly URLs / aliases section allows organizing the filtered aliases, editing them, and removing of the unnecessary ones.
Below you will find a description of all possible actions you can perform in the Select block section.
   Visualization of the Friendly URLs / aliases section
 Select the Show X entries (1) field to set the number of aliases, displayed on one page (min 10 / max 100).
The names of the columns (2) that contain information about a target aliases. Each column is susceptible to sorting. To sort the records, click on the title of the column.
ID - An internal ID of the alias.
Request path - The URL of the alias.
Target path - The target URL.
Update time - Last update time of the alias.
Actions - List of buttons with possible actions that can be done to the desired alias:
Edit - Edit desired alias. Editing is exactly same process as adding a new alias.
View - Allows to view the content of the alias without the ability to edit it.
Delete - Deletes the alias without the ability to restore it.
Import (3) button, which imports the prepared aliases from an xlsx file. You can find more about it in the Importing aliases section.
Export (4) button, which exports all filtered aliases to an xlsx file.
Select the Add (5) button to go to the adding the new alias. You can learn more about adding of the aliases in the Adding a new alias chapter.
Search box (6) where you can search for desired alias by using their request or target path.
Page buttons (7), which allows user to change the page of the aliases list.
At the bottom of the page you will find a Mass removal tab, which contains the Remove all url aliases button.
   Visualization of the Friendly URLs / aliases section
By pressing this button you will remove all aliases in the environment database without an ability to restore them. Please use this option only if previously created aliases have been exported beforehand and are ready to be imported.
   Visualization of the Friendly URLs / aliases section
After pressing the Remove all url aliases button there is a pop-up that warns the user, that it is an irreversible process, and an additional confirmation is required by pressing the Yes, remove all button. This process at this point still can be cancelled by pressing the No button.
Adding a new alias
Add button allows users to create new aliases.
   Visualization of the adding of the new aliases.
While creating a new alias or editing an existing one, you have to specify the:
Request path - The URL of the alias.
Target path - The target URL.
For example, if you want customers to access the promotion page "/New_promotion" by URL "/New_link" we need to type "/New_link" to the Request path, and "/New_promotion" to the Target path.
After typing the necessary URLs you can save the changes with the "Save" button.
Importing aliases
Aliases can be imported using the import functionality. This can be done by pressing the import button in the CMS > Friendly URLs / Aliases, or by directly accessing Import / Export > Import and selecting the Aliases option.
   Visualization of the adding of the new aliases.
The prepared file needs to be in an xlsx format and it has to contain the following columns:
request_path - The URL of the alias.
target_path - The target URL. Must start with a slash ("/").
The request path and target path cannot contain exactly the same URL in the same row.
An example of an incorrect path:
request_path
target_path
/Webpage
/webpage
As both request_path and target_path contain exactly the same URL it will create a loop when accessing it. This option will result in an error when trying to import such an alias.
The import mechanism has validation, that automatically cancels the import of aliases if they contain the same URL in request_path and target_path as well as if the target_path doesn't start with a slash ("/").
The import mechanism can only add new aliases. For alias removal please remove the unnecessary aliases in CMS > Friendly URLs / Aliases by pressing the delete button next to the alias, or remove all aliases from the database by pressing the Remove all url aliases button, and import the correct aliases from an xlsx file.

Banner notifications
Getting started
This article describes Banners / list tab in the admin panel, which will allow users to create header and side notifications on the website. Notifications work like CMS blocks using HTML + CSS code, and can be activated on specific altshops.
There can be more than one header banner (1) visible at the same time. When the top banner is closed by the client, it will be not visible to the customer for configured in the System / Settings amount of days.
Only one side banner (2) can be visible, and it is determined by their sort order.
   Visualization of the banners on the homepage (Desktop view)
   Visualization of the banners on the homepage (Mobile view)
Table of contents:
Configuring the banners
System / settings configuration
 Customer perspective
 
 
 Configuring the banners
Top and side banners can be created and managed in the
CMS > Banners / list
  RememberEvery created banner needs to be activated in the desired altshop. More about activating banners in the altshops can be found in the Banners / list - browsing and managing banners in altshop module article.
   Visualization of the Banners / list tab
In the Banner / list tab,  it is possible to select the Show X entries (1) field to set the number of banners, displayed on one page (min 10 / max 100).
In this tab we can also find columns (2), that can be sorted, with basic information regarding the banners:
ID – Internal ID of the banner.
Location – Top or Side location.
Name – Internal name.
Start and End date - Range of dates when the banner should be visible.
Is Active? – Status if the banner is currently active.
Sort order – Sort order of the banner.
Update time – Last update time done by the user.
Actions - Three action buttons that allows to
Edit selected banner. Editing is the same action as Add, but with already existing element. More about it can be read below.
Duplicate selected banner. Duplicate creates exactly the same banner, but with a (x) at the end of the name (where X is a number).
Delete selected banner.
In order to create new banner, we need to click on the Add (3) button
It is possible to search for a desired banner by their name using the search box (4), change the pages when the number of banners is by default bigger than 10 (5), and see how many banners are currently visible on the page out of them all (6).
   Visualization of the new banner creation
When creating new banner, we can specify:
Name – Internal name.
Location – Top or Side location.
Sort order – Sort order of the banner.
Start and End date - Range of dates when the banner should be visible.
Is Active? – Status if the banner is currently active.
In the content tab, we need to type HTML code in order for it to be visible on the website for the customer.
Example code for Top banner:
<div style="width: 100%">
<p style="text-align:center;">Connectes-vouz our creez votre compte pour profiter de vos <strong>avantages exclusifs</strong></p>
</div>
Example code for side banner:
<style type="text/css">.side-banner-content {
    height: 100%;
    color: #fff;
    display: flex;
    justify-content: center;
    align-items: center;
  }
</style>
<div class="side-banner-content">
<p style="color: #fff;">Connectes-vouz our creez votre<br />
compte pour profiter de vos<br />
<strong>avantages exclusifs</strong></p>
</div>
With the correctly filled necessary fields and code, we can save the banner.
 
 
 System / settings configuration
Layout banners can be closed by the customers, and they will reappear after a configured amount of time. It can be configured in the
System > System / settings > Built-in functions > Layout banners
   Visualization of the Layout banners tab in the System / settings
There we can find two options, one for top banner and second one for side banners.
 
 
 Customer perspective
Created and configured banners will be visible on the website. Top banners (1) and side banners (2) are visible on every page.
   Visualization of the banners on the homepage (Desktop view)
   Visualization of the banners on the homepage (Mobile view)

Pseudo tags
Getting started
This article describes the pseudotag system that is used by the CMS blocks and CMS pages to dynamically display content in them. 
   Visualization of the example usage of a pseudotag
For pseudo tags to work, they need to be enabled in the selected CMS block or page by turning on the Use pseudo tags? button (1). When this button is turned off the pseudo tags won't be converted into dynamic content.
   Visualization of the use pseudo tags? button.
Table of contents:
Available pseudo tags
 Available pseudo tags
Pseudo tag is defined by name and parameters of the pseudo tag in double curly braces "{{ }}". The pseudo tag is defined in the following order: {{PseudoTag: SKU,SKU,SKU argument:true}}
Name
Available arguments
cmsblock
Title of a CMS block
addpayedgift
SKU number of a product
addproduct
productlink
productlist
reload:true - sets if the add to cart modal should be shown to the customer. If this argument is set to false customer will see add to cart modal, if it's set to true customer will remain on the page.
limit:6 - sets the limit how many products should be displayed at the same time
SKU list separated by comma (",")
blockproductlist
productlistsmall
productlistcolor
productlistsmallcart
productlistbig
treescounter
N/A
Example of a pseudo tag:
{{productlistsmall:69296,86429,47043,38421 limit:2}} - will show a list of products with buttons to add them to the cart. Only 2 products will be displayed, even when the number of specified SKUs is bigger than 2.
{{productlist: 55555,53212,12345 reload:true}} - Will show a product list of the selected SKUs with a button that allows customers to add these products to the cart. After pressing the "add to cart" button customers won't see a modal confirming that option, but they will remain on the webpage.

General

Customer e-mail flows
Getting started
In this article you can find a flow of every e-mail used on the Yves-Rocher websites.
  RememberRemember
  Warning   Warning  
(1) (2) (3)
Table of contents:
 
 
 
 A
 
 
Visualization of the
 
 
 
 
 B
 

TCAI search hints mechanism
Getting started
In this article, you will find information about the TCAI search hints mechanism (1). TCAI is standalone and separate from the TC administration panel platform that collaborates with the Elastic engine. The search engine was developed to address the need for quick access to relevant and more accurate query results. The TCAI search hints mechanism is a feature that helps users refine their search queries and find the desired product they need more efficiently. The search engine additionally checks for misspellings and searches for similar, words in case there is a mistake. The engine itself performs two searches at the same time using different phrase weights, which allows us to make sure the customer gets the best and most accurate results. This new version of the TC search engine allows for fast, scalable, and flexible full-text search and analytics. 
It is worth emphasizing that the mechanism allows for advanced analysis of what the customer is searching for.
  RememberElasticsearch is an external integrated engine that helps optimize, manage, and analyze search results.
Visualization of the TCAI search mechanism UI (desktop)
Visualization of the TCAI search mechanism UI (mobile)
Table of contents:
TCAI search engine configuration
 TCAI description of operation - front-end and business perspective
 TCAI keywords
 
 
 TCAI search engine configuration
All settings regarding TCAI you'll find in the admin panel, navigating to:
System > System / settings > Integrations tab > TCAI
You can easily search for TCAI settings by typing a dedicated phrase into the system settings browser (as shown in the screenshot). Below you will find a description of all visible settings:
Visualization of the TCAI admin panel settings
Enabled - a switch that decides if the TCAI function is enabled and whether TCAI is the primary search engine.
  RememberTC platform provides three types of search engines. TCAI has the highest priority, which means it works as the main search engine and ignores the SLI mechanism, which has a lower priority than TCAI. The standard version of the TC search engine has the lowest priority, which means it is ignored when any of the above two browsers are enabled.
Enabled suggested phrases - switch which enables the phrase suggestions during the search.
Host url - the URL where TCAI can be found.
Auth token - the identifier used to authenticate the TCAI platform to ensure proper collaboration with the TC admin panel. The parameter is sensitive, and any changes should be consulted with the TC team.
Search feed main category name - a parameter indicating the category based on which the search will be conducted. The parameter that is taken into consideration is the 
url_name It's the parameter, which appears, among others, in the mass import of products. You can find more information on the topic of mass import of products at Product catalog export 
and import. The parameter is sensitive, and any changes should be consulted with 
the TC team.
Search feed batch size - the parameter determining the number of products that are sent to TCAI at once, in one batch. The functionality is currently being expanded. The parameter is sensitive, and any changes should be consulted with the TC team.
Debug mode - a mode of operation for identifying and correcting errors in a program, allowing programmers to observe program behavior and track variable values. The parameter should be disabled in the production environment unless it is necessary for debugging purposes.
 
 TCAI description of operation - front-end and business perspective
 
 
In the following section, you will find a description of the mechanism's behavior from the frontend user's perspective and the main features of the search engine from the Yves Rocher business point of view. 
Front-end perspective
The search engine saves the user's last searches (1) in local storage. The view with the last searches is visible when the user clicks on the search field for the product.
These are searches that ended with the user pressing the enter key or clicking on the search button.
Visualization of the TCAI - last phrases UI (mobile&desktop)
TCAI intelligently matches search results based on the entered query. The search is performed by the main category (2) (defined in the Search feed main category name parameter), product name and properties. In the main search results (3), we will find a maximum of 8 products that have the best scoring. The mechanism also helps the user by predicting and generating suggested clickable phrases (4).
Clicking on the cart button (located in the product box) adds the product to the cart, while clicking on the product name will redirect the user to the page with the details of the selected product.
TCAI is able to track user clicks and group them accordingly for analysis purposes. For example, each click on a product name or image in the main search results (3) will be counted for the "hints_product_tile" tag, while a click on the cart icon will be counted for the "add_to_cart" tag.
Tracking and analysis of clicks also occur after submitting the search form on the target product list. In this case, clicking on the product name, image, or review will record a click for the "product_tile" tag, while clicking on the cart will increase the value for the "add_to_cart" tag.
 These tags are present in the TCAI analytics module.
Visualization of the Tau Ceti AI search mechanism UI (desktop)
Visualization of the Tau Ceti AI search mechanism UI (mobile)
Business perspective
The user experience is equivalent to that of current solutions on CEE websites
The TCAI platform is standalone and separate from the TC e-commerce platform.
It has the capability to integrate with various production and non-production sites. 
It's compatible with the current multi-language catalog product content obtained from different sources.
Open architecture allows for adaptation to future changes such as new catalog product schemas, additional dictionaries, and new sources. 
Search functionality based on Elasticsearch.
In terms of appearance and user experience, we are basing on the current layout and behavior of the existing Persoo solution for YR, allowing for minor improvements (among other things):
TCAI mechanism includes search phrase suggestions
The ability to add products to the cart directly from the suggestion window.
Business users have access to statistical information, it allows among other things:
how the search volume is distributed over weeks
when the highest traffic occurs during the day
which products and what phrases lead to which user clicks
Ability to add synonyms (there is a possibility of bulk importing synonyms (up to a maximum of 256 synonym groups).
The data of the search tool is based and recognized on: altshops, category, name, tag, property, keywords, EAN, SKU, and colors as search keywords. 
The search tool results are passed to the native results page.
Suggested categories will be displayed by the search box based on the identified keyword.
Products with zero stock aren't excluded from the search results as the user may be interested in seeing the details of the product. Such results are placed at the very end of the product list.
Ability to manually optimize the results directly in the search platform. The platform allows optimization based on the following parameters:
Product is new
Product is bestseller
Product is green point
Product is limited edition
Product is outlet
Product capacity
Product reviews rating
Product reviews count
 
 
 TCAI keywords
TCAI keywords functionality uses AI to generate product keywords that can be searched in the TCAI search. The keywords are generated based on the product description, and this process is fully automated and keywords are generated once a day, even when the product description has been updated.
 High-quality product descriptions aid in generating significantly better quality keywords, directly related to the product. Additionally, if keywords generated for a particular product aren't strictly related to it, the user doesn't lose anything. They may only gain the advantage that by entering one of the generated keywords, the product will still be found.
Generated keywords can be found in
Catalog > Products / list > Edit on the desired product > TCAI Search 
Visualization of the TCAI keywords
These keywords are added to the keywords in the Description > Keywords field, so when customers are searching by non-standard phrasing like "Anti-age global" (to find all of the anti-age global products) they will find all of the products that have "Anti-age Global" keyword generated.
Visualization of the searching of a keyword in the TCAI search

Admin panel alerts
Getting started
In this article you can find information about available alerts and how to enable them in TauCeti admin panel. These alerts will warn admin users via notification sent to their e-mail address regarding the issues with JOY.
Table of contents:
 Enabling the alerts
 
 
 Enabling the alerts
Users that have the following groups are able to enable the alerts for both their local account and GAC account:
MC business admin
Administrator
Super Administrator
Root
Visualization of the user preferences button location
Alerts settings can be accessed by pressing the users picture in top right corner (1) and pressing the Preferences (2) option.
Visualization of the alerts in the admin panel.
In the users preferences you can find alerts under Alerts tab (3).
In order to receive JOY alerts on your e-mail address you have to enable the Use own settings (4) option and then select the alerts that you want to receive. Available alerts are:
JOY stock synchronization errors – Reports problems with JOY stock synchronization
and problems when checking stocks in real-time.
JOY campaign code errors – Reports issues with checking if campaign code is
defined in JOY (real-time mailing code verification). Reporting includes sending
information that campaign code does not exist in JOY. Such a problem can also be
detected and reported during stock synchronization.
JOY API XML (WSDL) verification errors – Reports when JOY API definitions (WSDL
file) are unavailable or have changed. Unavailability of WSDL file means that the
entire JOY API is unavailable.
Orders export – Reports problems detected within following export mechanisms:
JOY Order Export - An alert is sent when at least one order has failed to be
exported or there is an issue with API connection initialization.
JOY Payment Export - An alert is sent when at least one payment has failed to be
exported or there is an issue with API connection initialization.
Rumanku Payment Export - An alert is sent when at least one payment has failed
to be exported.
EET Hungary (Stocker) Order Export - An alert is sent when there are some
problems with XML file generation or communication to Stocker's SFTP.
EET Czechia Order Export - An alert is sent in multiple scenarios, including invalid
configuration, API communication issues and multiple self-checks.
Orders invoice generation – Reports problems with import of invoices from EET
Hungary (Stocker) integration. This alert is only available for root users.
Orders check – Reports issues with internal order checks performed for every placed
order, before it is exported to any system that will take care of system processing
(JOY, TC Logistics, Rumanku). This alert is only available for root users.
Environment synchronization – Reports that someone scheduled a synchronization.
With alerts enabled you will receive a notification on your e-mail address. Notifications are sent only once every 30 minutes if a problem is persistent. Some notifications can be sent more frequently.
Every generated alert is always sent to system administrators (Tau Ceti internal e-mail
inbox). The system administrator also receives many more notifications based on internal
system checks.

Groups of users and rights in admin panel
Getting started
In this article, you will find information about all available user groups and their permissions and access on Yves Rocher admin panel. User groups define what viewing restrictions assigned employees will have when browsing the admin panel or what actions they can perform.
This list will go in order from the most powerful groups to the least.
Table of contents:
 Root
 Super administrator
 Administrator
 MC business admin
 MC business Analyst
 Content manager
 Content Editor
 BOK supervisor
 Customer care service
 External Call Center
 Herbarium editor
 POS admin
 Repository Manager
 
 
 Root
Dashboard
Contacts
Orders / list
Pending orders
New order
POS retail
Customer edit requests
Removed contacts
Alt shops / list
Campaign codes / list
Delivery costs / list
Payment types / list
Products / list
Pages / list
Blocks / list
Product stickers / list
Banners / list
Popups / list
Featured products / list
Promotion pages / list
Opensets / list
Sales channels / list
Slider / list
Promotion validity dates
Products / list
Colors / lit
Properties / list
Tags / list
Reviews / list
Ingredients / list
Reviews / moderation
Product stickers / list
Reviews / moving
Images upload
Mass product removal
JOY stocks
Conditions / list
Actions / list
Rules / list
Discount codes / list
Promotion pages / list
Opensets / list
Campaign codes / list
Products excluded from promotion (global)
Push messages / list
Vouchers / list
Customer / MC clients
Customers / list
Customer / leads
Customer / blacklist
Customer / data audit
Customer / opt-out mobile
Subscribers / list
Address Dictionary
Subscribers groups
Member get Member
Call center / new case
Call center / cases
Call center / contact ways
FIDEN2 / Search card
FIDEN2 / Change card balance
FIDEN2 / Automatic balance operations
FIDEN2 / Assign card
FIDEN2 / Card initialize
Forget requests / list
Customer / Redirect
Customer Private Offers
SMS Templates
Customer / Form
Customer / Contact Subject
Orders / list
Orders / to verify
JOY / Check order
Orders / Order payments
JOY / Waybill log
PayU refunds
Allegro
Allegro delivery methods
Allegro errors
Voucher / GiftCard
BaseLinker
Baselinker delivery
Baselinker errors
Refunds
Baselinker Catalog
Baselinker integrations
Reviews / products
Products / stock
Stock / statistics
Sales / Orders
Sales / MC orders
Customers / Registrations
Discount codes / sales
Promotions / orders
Personal discount codes
Error pages
Security incidents
PUSH messages / events
PUSH devices / registrations
Member Club / reports
Short link clicks
JOY / Failed orders
Search / top phrases
Password recoveries / list
Orders promotion rules
FIDEN2
Products price history
Top menu / list
Slider / list
Gallery / images
Pages / list
Blocks / list
Banners / list
Popups / list
Friendly URLs / list
Friendly URLs / aliases
Featured products / list
Beauty advices / list
Beauty advice attributes / list
Exponea / Recommended Product Block
Stores / list
Export / SALESmanago tags
Export / catalog
Import
Export / customers
Export / subscribers
Export / POS users
Export / Jumia
Import / FIDEN2 points
Export / sales
Export / FIDEN2 cards
Import / discount codes
Generator / discount codes
Export / Invoices
Export / contacts
Export / orders
Export / gift cards payment
Mass personal codes removal
Agreements
Admins / list
Available zip codes / list
Synchronization
Admins / Auth IPs
Admin / messages
Admin / banned IPs
Delivery types / list
Payment types / list
Delivery / payment exceptions
Translations / list
System / settings
Translations / missing list
SEO / settings
Tasks
Planned tasks
Public API / keys
APIv2 / Keys
Order status / list
SALESmanago / settings
Cross selling / settings
JOY / Real time validation
JOY Stock errors / list
Disabling site
Short links / list
Search / dictionary
Alternative authorization
Robots.txt
Redlink Messages
FIDEN2 / File history
FIDEN2 / Data flow dashboard
External imports / list
Delivery points / list
System log
POS / Monthly report
Export / Monthly report
Assigned cards / report
View
Qualifiers
Commission
Simulation
KPIs / list
View structure
Movements
New region
View regions
Leaders / targets
View
Add
Plants
Plant families
Regions
Carousel
Sub campaign
Boxes
Homepage products
Articles
Current offers
Cms elements
Cms categories
Catalog
Customer Private OFfers
 
 
 
 
 Super administrator
 
Dashboard
Contacts
Orders / list
Pending orders
New order
POS retail
Customer edit requests
Removed contacts
Alt shops / list
Campaign codes / list
Delivery costs / list
Payment types / list
Products / list
Pages / list
Blocks / list
Product stickers / list
Banners / list
Featured products / list
Promotion pages / list
Opensets / list
Sales channels / list
Slider / list
Promotion validity dates
Products / list
Colors / lit
Properties / list
Tags / list
Reviews / list
Ingredients / list
Reviews / moderation
Product stickers / list
Reviews / moving
Images upload
Mass product removal
JOY stocks
Conditions / list
Actions / list
Rules / list
Discount codes / list
Promotion pages / list
Opensets / list
Campaign codes / list
Products excluded from promotion (global)
Push messages / list
Vouchers / list
Customer / MC clients
Customers / list
Customer / leads
Customer / blacklist
Customer / data audit
Customer / opt-out mobile
Subscribers / list
Address Dictionary
Subscribers groups
Member get Member
Call center / new case
Call center / cases
Call center / contact ways
FIDEN2 / Search card
FIDEN2 / Change card balance
FIDEN2 / Automatic balance operations
FIDEN2 / Assign card
FIDEN2 / Card initialize
Forget requests / list
Customer / Redirect
Customer Private Offers
SMS Templates
Customer / Form
Customer / Contact Subject
Orders / list
Orders / to verify
JOY / Check order
Orders / Order payments
JOY / Waybill log
PayU refunds
Allegro
Allegro delivery methods
Allegro errors
Voucher / GiftCard
BaseLinker
Baselinker delivery
Baselinker errors
Refunds
Baselinker Catalog
Baselinker integrations
Reviews / products
Products / stock
Stock / statistics
Sales / Orders
Sales / MC orders
Customers / Registrations
Discount codes / sales
Promotions / orders
Personal discount codes
Error pages
Security incidents
PUSH messages / events
PUSH devices / registrations
Member Club / reports
Short link clicks
JOY / Failed orders
Search / top phrases
Password recoveries / list
Orders promotion rules
FIDEN2
Products price history
Top menu / list
Slider / list
Gallery / images
Pages / list
Blocks / list
Banners / list
Friendly URLs / list
Friendly URLs / aliases
Featured products / list
Beauty advices / list
Beauty advice attributes / list
Exponea / Recommended Product Block
Stores / list
Export / SALESmanago tags
Export / catalog
Import
Export / customers
Export / subscribers
Export / POS users
Export / Jumia
Import / FIDEN2 points
Export / sales
Export / FIDEN2 cards
Import / discount codes
Generator / discount codes
Export / Invoices
Export / contacts
Export / orders
Export / gift cards payment
Mass personal codes removal
Agreements
Admins / list
Available zip codes / list
Synchronization
Admins / Auth IPs
Admin / banned IPs
Delivery types / list
Payment types / list
Delivery / payment exceptions
Translations / list
System / settings
Translations / missing list
SEO / settings
Planned tasks
Public API / keys
APIv2 / Keys
Order status / list
SALESmanago / settings
Cross selling / settings
JOY / Real time validation
JOY Stock errors / list
Disabling site
Short links / list
Search / dictionary
Alternative authorization
Robots.txt
Redlink Messages
FIDEN2 / File history
FIDEN2 / Data flow dashboard
External imports / list
Delivery points / list
POS / Monthly report
Export / Monthly report
Assigned cards / report
View
Qualifiers
Commission
Simulation
KPIs / list
View structure
Movements
New region
View regions
Leaders / targets
View
Add
Plants
Plant families
Regions
Carousel
Sub campaign
Boxes
Homepage products
Articles
Current offers
Cms elements
Cms categories
Catalog
Customer Private OFfers
 
 Administrator
 
Dashboard
Contacts
Orders / list
Pending orders
New order
POS retail
Customer edit requests
Removed contacts
Alt shops / list
Campaign codes / list
Delivery costs / list
Payment types / list
Products / list
Pages / list
Blocks / list
Product stickers / list
Banners / list
Featured products / list
Promotion pages / list
Opensets / list
Sales channels / list
Slider / list
Promotion validity dates
Products / list
Colors / lit
Properties / list
Tags / list
Reviews / list
Ingredients / list
Reviews / moderation
Product stickers / list
Reviews / moving
Images upload
Mass product removal
JOY stocks
Conditions / list
Actions / list
Rules / list
Discount codes / list
Promotion pages / list
Opensets / list
Campaign codes / list
Products excluded from promotion (global)
Push messages / list
Vouchers / list
Customer / MC clients
Customers / list
Customer / leads
Customer / blacklist
Customer / data audit
Customer / opt-out mobile
Subscribers / list
Address Dictionary
Subscribers groups
Member get Member
Call center / new case
Call center / cases
Call center / contact ways
FIDEN2 / Search card
FIDEN2 / Change card balance
FIDEN2 / Automatic balance operations
FIDEN2 / Assign card
FIDEN2 / Card initialize
Forget requests / list
Customer / Redirect
Customer Private Offers
SMS Templates
Customer / Form
Customer / Contact Subject
Orders / list
Orders / to verify
JOY / Check order
Orders / Order payments
JOY / Waybill log
PayU refunds
Allegro
Allegro delivery methods
Allegro errors
Voucher / GiftCard
BaseLinker
Baselinker delivery
Baselinker errors
Refunds
Baselinker Catalog
Baselinker integrations
Reviews / products
Products / stock
Stock / statistics
Sales / Orders
Sales / MC orders
Customers / Registrations
Discount codes / sales
Promotions / orders
Personal discount codes
Error pages
Security incidents
PUSH messages / events
PUSH devices / registrations
Member Club / reports
Short link clicks
JOY / Failed orders
Search / top phrases
Password recoveries / list
Orders promotion rules
FIDEN2
Products price history
Top menu / list
Slider / list
Gallery / images
Pages / list
Blocks / list
Banners / list
Friendly URLs / list
Friendly URLs / aliases
Featured products / list
Beauty advices / list
Beauty advice attributes / list
Exponea / Recommended Product Block
Stores / list
Export / SALESmanago tags
Export / catalog
Import
Export / customers
Export / subscribers
Export / POS users
Export / Jumia
Import / FIDEN2 points
Export / sales
Export / FIDEN2 cards
Import / discount codes
Generator / discount codes
Export / Invoices
Export / contacts
Export / orders
Export / gift cards payment
Mass personal codes removal
Agreements
Admins / list
Available zip codes / list
Synchronization
Admins / Auth IPs
Admin / banned IPs
Delivery types / list
Payment types / list
Delivery / payment exceptions
Translations / list
System / settings
Translations / missing list
SEO / settings
Planned tasks
Public API / keys
APIv2 / Keys
Order status / list
SALESmanago / settings
Cross selling / settings
JOY / Real time validation
JOY Stock errors / list
Disabling site
Short links / list
Search / dictionary
Alternative authorization
Robots.txt
Redlink Messages
FIDEN2 / File history
FIDEN2 / Data flow dashboard
External imports / list
Delivery points / list
POS / Monthly report
Export / Monthly report
Assigned cards / report
View
Qualifiers
Commission
Simulation
KPIs / list
View structure
Movements
New region
View regions
Leaders / targets
View
Add
Plants
Plant families
Regions
Carousel
Sub campaign
Boxes
Homepage products
Articles
Current offers
Cms elements
Cms categories
Catalog
Customer Private OFfers
 
 MC business admin
 
Dashboard
Contacts
Customer edit requests
Removed contacts
Alt shops / list
Campaign codes / list
Delivery costs / list
Payment types / list
Products / list
Pages / list
Blocks / list
Product stickers / list
Banners / list
Featured products / list
Promotion pages / list
Opensets / list
Sales channels / list
Slider / list
Promotion validity dates
Products / list
Colors / lit
Properties / list
Tags / list
Reviews / list
Ingredients / list
Reviews / moderation
Product stickers / list
Reviews / moving
Images upload
Mass product removal
JOY stocks
Conditions / list
Actions / list
Rules / list
Discount codes / list
Promotion pages / list
Opensets / list
Campaign codes / list
Products excluded from promotion (global)
Push messages / list
Vouchers / list
Customer / MC clients
Customers / list
Customer / leads
Customer / blacklist
Customer / data audit
Customer / opt-out mobile
Subscribers / list
Address Dictionary
Subscribers groups
Member get Member
Call center / new case
Call center / cases
Call center / contact ways
FIDEN2 / Search card
FIDEN2 / Change card balance
FIDEN2 / Automatic balance operations
FIDEN2 / Assign card
FIDEN2 / Card initialize
Forget requests / list
Customer / Redirect
Customer Private Offers
Customer / Form
Customer / Contact Subject
Orders / list
Orders / to verify
JOY / Check order
Orders / Order payments
JOY / Waybill log
PayU refunds
Allegro
Allegro delivery methods
Allegro errors
Voucher / GiftCard
BaseLinker
Baselinker delivery
Baselinker errors
Refunds
Baselinker Catalog
Baselinker integrations
Reviews / products
Products / stock
Stock / statistics
Sales / Orders
Sales / MC orders
Customers / Registrations
Discount codes / sales
Promotions / orders
Personal discount codes
Error pages
PUSH messages / events
PUSH devices / registrations
Member Club / reports
Short link clicks
JOY / Failed orders
Search / top phrases
Password recoveries / list
Orders promotion rules
FIDEN2
Products price history
Top menu / list
Slider / list
Gallery / images
Pages / list
Blocks / list
Banners / list
Friendly URLs / list
Friendly URLs / aliases
Featured products / list
Beauty advices / list
Beauty advice attributes / list
Exponea / Recommended Product Block
Stores / list
Export / SALESmanago tags
Export / catalog
Import
Export / customers
Export / subscribers
Export / Jumia
Import / FIDEN2 points
Export / sales
Export / FIDEN2 cards
Import / discount codes
Generator / discount codes
Export / Invoice
Export / orders
Export / gift cards payment
Mass personal codes removal
Agreements
Admins / list
Available zip codes / list
Synchronization
Admins / Auth IPs
Admin / banned IPs
Delivery types / list
Payment types / list
Delivery / payment exceptions
Translations / list
System / settings
Translations / missing list
SEO / settings
Planned tasks
Public API / keys
APIv2 / Keys
Order status / list
SALESmanago / settings
Cross selling / settings
JOY / Real time validation
JOY Stock errors / list
Disabling site
Short links / list
Search / dictionary
Alternative authorization
Robots.txt
Redlink Messages
FIDEN2 / File history
FIDEN2 / Data flow dashboard
External imports / list
Delivery points / list
POS / Monthly report
Export / Monthly report
Assigned cards / report
View
Qualifiers
Commission
Simulation
KPIs / list
View structure
Movements
New region
View regions
Leaders / targets
View
Add
Plants
Plant families
Regions
Carousel
Sub campaign
Boxes
Homepage products
Articles
Current offers
Cms elements
Cms categories
Catalog
Customer Private OFfers
 
 MC business Analyst
 
Dashboard
Alt shops / list
Campaign codes / list
Delivery costs / list
Payment types / list
Products / list
Pages / list
Blocks / list
Featured products / list
Promotion pages / list
Opensets / list
Sales channels / list
Slider / list
Promotion validity dates
Products / list
Colors / list
Properties / list
Tags / list
Reviews / list
Ingredients / list
Reviews / moderation
Reviews / moving
Images upload
JOY stocks
Conditions / list
Actions / list
Rules / list
Discount codes / list
Promotion pages / list
Opensets / list
Campaign codes / list
Products excluded from promotion (global)
Push messages / list
Vouchers / list
Customer / MC clients
Customers / list
Customer / leads
Customer / blacklist
Customer / data audit
Customer / opt-out mobile
Subscribers / list
Address Dictionary
Subscribers groups
Call center / new case
Call center / cases
Call center / contact ways
FIDEN2 / Search card
FIDEN2 / Change card balance
FIDEN2 / Automatic balance operations
FIDEN2 / Assign card
FIDEN2 / Card initialize
Forget requests / list
Customer / Redirect
Customer Private Offers
Orders / list
Orders / to verify
JOY / Check order
Orders / Order payments
PayU refunds
Allegro
Allegro delivery methods
Allegro errors
Voucher / GiftCard
Reviews / products
Products / stock
Stock / statistics
Sales / Orders
Sales / MC orders
Customers / Registrations
Discount codes / sales
Promotions / orders
Personal discount codes
Error pages
PUSH messages / events
PUSH devices / registrations
Member Club / reports
Short link clicks
JOY / Failed orders
Search / top phrases
Password recoveries / list
FIDEN2
Top menu / list
Slider / list
Gallery / images
Pages / list
Blocks / list
Friendly URLs / list
Friendly URLs / aliases
Featured products / list
Beauty advices / list
Beauty advice attributes / list
Exponea / Recommended Product Block
Export / SALESmanago tags
Export / catalog
Import
Export / customers
Export / subscribers
Export / Jumia
Import / FIDEN2 points
Export / sales
Export / FIDEN2 cards
Import / discount codes
Generator / discount codes
Export / Invoices
Export / orders
Agreements
Admins / list
Available zip codes / list
Synchronization
Admins / Auth IPs
Admin / banned IPs
Delivery types / list
Payment types / list
Delivery / payment exceptions
Translations / list
System / settings
Translations / missing list
SEO / settings
Planned tasks
Public API / keys
APIv2 / Keys
Order status / list
SALESmanago / settings
Cross selling / settings
JOY / Real time validation
JOY Stock errors / list
Disabling site
Short links / list
Search / dictionary
Robots.txt
Redlink Messages
FIDEN2 / File history
External imports / list
Delivery points / list
POS / Monthly report
Export / Monthly report
Assigned cards / report
View
Qualifiers
Commission
Simulation
KPIs / list
View structure
Movements
New region
View regions
Leaders / targets
View
Add
Plants
Plant families
Regions
Carousel
Sub campaign
Boxes
Homepage products
Articles
Current offers
Cms elements
Cms categories
Catalog
Customer Private OFfers
 
 Content manager
 
Dashboard
Alt shops / list
Campaign codes / list
Products / list
Pages / list
Blocks / list
Banners / list
Product stickers / list
Featured products / list
Promotion pages / list
Opensets / list
Sales channels / list
Slider / list
Products / list
Colors / list
Properties / list
Tags / list
Product stickers / list
Images upload
Promotion pages / list
Opensets / list
Campaign codes / list
Subscribers / list
Subscribers groups
Top menu / list
Slider / list
Gallery / images
Pages / list
Blocks / list
Banners / list
Friendly URLs / list
Friendly URLs / aliases
Featured products / list
Beauty advices / list
Beauty advice attributes / list
Export / catalog
Admin / banned IPs
Translations / list
Translations / missing list
Carousel
Sub campaign
Boxes
Homepage products
Articles
Current offers
Cms elements
Cms categories
Catalog
Customer Private OFfers
 
 Content Editor
 
Dashboard
Banners / list
Product stickers / list
Product stickers / list
Gallery / images
Pages / list
Blocks / list
Banners / list
Friendly URLs / list
Translations / list
Translations / missing list
Carousel
Sub campaign
Boxes
Homepage products
Articles
Current offers
Cms elements
Cms categories
Catalog
Customer Private OFfers
 
 BOK supervisor
 
Dashboard
Reviews / list
Reviews / moderation
Vouchers / list
Customers / list
Customers / data audit
Member get Member
FIDEN2 / Search Card
FIDEN2 / Change card balance
FIDEN2 / Assign card
FIDEN2 / Card initialize
Orders / list
Orders / to verify
Admin / banned IPs
Carousel
Sub campaign
Boxes
Homepage products
Articles
Current offers
Cms elements
Cms categories
Catalog
Customer Private OFfers
 
 Customer care service
 
Dashboard
Customer / MC clients
Customers / list
Customer / blacklist
Customer / data audit
Customer / opt-out mobile
Subscribers / list
Call center / new case
Call center / cases
Call center / contact ways
FIDEN2 / Change card balance
FIDEN2 / Card Initialize
Orders / list
Orders / to verify
Products / stock
Stock / statistics
View structure
Carousel
Sub campaign
Boxes
Homepage products
Articles
Current offers
Cms elements
Cms categories
Catalog
Customer Private OFfers
 
 External Call Center
 
Dashboard
Customer / MC clients
Customers / list
Customer / leads
Customer / blacklist
Customer / data audit
Call center / new case
Call center / cases
Call center / contact ways
FIDEN2 / Search card
FIDEN2 / Assign card
Orders / list
Orders / to verify
BaseLinker
Baselinker errors
Sales / Orders
Sales / MC orders
Customers / registrations
Carousel
Sub campaign
Boxes
Homepage products
Articles
Current offers
Cms elements
Cms categories
Catalog
Customer Private OFfers
 
 Herbarium editor
 
Dashboard
Friendly URLs / list
Plants
Plant families
Regions
Carousel
Sub campaign
Boxes
Homepage products
Articles
Current offers
Cms elements
Cms categories
Catalog
Customer Private OFfers
 
 POS admin
 
Dashboard
POS / Monthly report
Carousel
Sub campaign
Boxes
Homepage products
Articles
Current offers
Cms elements
Cms categories
Catalog
Customer Private OFfers
 
 Repository Manager
 
Dashboard
Images upload
Carousel
Sub campaign
Boxes
Homepage products
Articles
Current offers
Cms elements
Cms categories
Catalog
Customer Private OFfers

Accesses on the platforms
Gettings started
This article describes various access information for Yves Rocher, EasyRedmine and GAC websites.
In this article we can find who to contact to request access to the website, how to log in into it, and how to reset user password.
Table of contents:
 Yves Rocher admin panel
Password reset
Logging in
 Global Authorization Center
Password reset
Logging in
EasyRedmine
Password reset
 Yves Rocher admin panel
Yves Rocher admin panel can be accessed on every environment by adding /baadmin at the end of the link (for example https://www.yves-rocher.pl/baadmin).
   Visualization of the /baadmin log in page 
To gain access to admin panel please contact your supervisor, so they can contact persons responsible for account creation. After confirmation that an account has been created, we need to reset the password.
In order to create new account Tau Ceti needs user:
Name
Surname
E-mail Address
Mobile number with country code
Permission group (i.e., Administrator, BOK supervisor etc.)
Environment names to which user will have access to (i.e., PL PROD, TEST)
Password reset
For the first login, the password needs to be reset. In order to reset the password, we need to click on the "Reset password" button.
   Visualization of the reset password page
On this page, we need to provide our email address and mobile number that supervisor provided to us in order to create the account.
Mobile number needs to be typed with the country code (for example, +48123456789).
After confirmation of the password reset, the user will receive an SMS message with a new, temporary password.
Logging in
After receiving having email address and password, we can log in into the platform by typing it in the designed fields.
   Visualization of the login /baadmin log in page
In the next step, we will see authorization options. By default, only the SMS message authorization method is available.
 RememberIn order to activate mobile authorization, it is needed to configure Google Authenticator after first log in. It is highly recommended to do so. You can find more about this authorization method in the Google Authenticator article.
   Visualization of the authorization page
After selecting SMS Code authorization method, the user will receive an SMS message with a short authorization code. This code needs to be typed in visible field.
   Visualization of the SMS authorization
Please take notice that SMS message may take up to 5 minutes to arrive depending on the network load on the SMS provider side.
After confirming the authorization, user after first login or once a month need to type new password for security purposes.
   Visualization of the password update process
After confirming the new password, the user will be logged in and the account will be ready to use.
 Global Authorization Center
Global Authorization Center (GAC in short) is a TauCeti platform that allows users to log in to various environments using only one account without need of relogging.
GAC can be accessed under link https://auth.tauceti.tech/.
   Visualization of the GAC log in page
In order to receive GAC access, please contact your supervisor. In order to create new account, Tau Ceti needs users:
Name
Surname
E-mail Address
Mobile number with country code
Permission group (i.e., Administrator, BOK supervisor etc.)
Environment names to which user will have access to (i.e., PL PROD, TEST)
Password reset
For the first login, the password needs to be reset. In order to reset the password, we need to click on the "Reset password" button.
   Visualization of the password reset process
In here, we need to type our e-mail address and mobile number (without country codes) and confirm it with “Reset password” button. This action will send us temporary password via SMS message.
Logging in
After having our e-mail address and password, we can log In to the platform through https://auth.tauceti.tech/ but also using "Log in using Tau Ceti account" button (1) on Yves Rocher website (e.g. Yves-Rocher.hu/baadmin)
   Visualization of the alternate way to log in to GAC
In the next step, we will see authorization options. By default, only SMS message authorization is available.
   Visualization of the GAC authorization methods
After selecting SMS Code authorization method, the user will receive an SMS message with a short authorization code. This code needs to be typed in visible field.
   Visualization of the SMS authorization
After confirming authorization, user after first login or once a month need to type new password for security purposes.
   Visualization of the password update process
After confirming the new password, the user will be logged in and the account will be ready to use.
 EasyRedmine
EasyRedmine is a helpdesk platform used by TauCeti Helpdesk. It can be used by users to create new tasks for the helpdesk team instead of sending requests on email address helpdesk@tauceti.email, as creating tasks on EasyRedmine platform allows user to see message history, task status and the message will arrive to helpdesk team faster.
EasyRedmine can be accessed under link https://tcteam.easyredmine.com/.
   Visualization of the EasyRedmine log in screen
In order to have access to EasyRedmine platform, Tau Ceti needs to receive a list of authorized users to send invitations to.
   Visualization of the EasyRedmine account activation e-mail
In the invitation, the user will see their login and temporary password. With this data, user will be able to log in to the platform.
   Visualization of the EasyRedmine password creation
After logging in, the user will be requested to type a new password. After that, account will be ready to use. Logged-in user can find useful documentation regarding EasyRedmine under link https://tcdev.easyredmine.com/projects/91/issues?set_filter=0
Password Reset
If there is a need to reset the password, the user can do it by selecting Lost password retrieve on the login screen.
   Visualization of the EasyRedmine log in screen
This option will open a lost password form in which the user needs to type an e-mail address.
   Visualization of the EasyRedmine password reset screen
After submitting an email address, the user will receive a new password via e-mail message and can proceed with it to log in.

Integrations

Express Relais integration
Getting started
In this article, you can find information about the Express Relais delivery option used in the Moroccan market. Express Relais is a delivery option available for customers, that allows them to deliver their products to a delivery point that they have selected on the interactive map. This integration is implemented in both the E-commerce platform and TC Logistics.
Table of contents:
 E-commerce
Configuration of the integration
Customer perspective
 TC Logistics
System Settings
Order Management
 
 
 E-commerce
Configuration of the integration
For the functionality to work properly on the E-commerce platform, it needs to be enabled and configured in the admin panel. Express Relais system settings can be found in:
System > System / Settings > Integrations > Express Relais API
Visualization of the Express Relais system settings
In the Express Relais system settings you can find the following options:
URL - URL of an Express Relais API. This URL shouldn't be changed.
Username - API username used to access the API.
Password - API password used to access the API.
Allowed mobile prefixes separated by comma - A list of mobile numbers separated by a comma, that is allowed to use the Express Relais delivery.
  RememberFor the delivery to be visible it needs to be enabled in System > Delivery types / list and Altshop > Delivery costs / list.
Customer perspective
When the delivery is configured and enabled in the admin panel it can be accessed during the order creation process.
Visualization of the Express Relais delivery
By selecting the Express Relais delivery customers will open an interactive map with a list of points provided by Express Relais that they can select to have their package delivered to. If the Express Relais is first on the delivery list it will open the map by default, once the customer proceeds with the order process.
Only customers with a mobile number starting with 2126 and 2127 (e.g. +2126123456789) will be able to use this delivery method, as Express Relais only accepts orders from these prefixes. This prefixes can be changed in the system settings.
Visualization of the delivery point widget
The Delivery point map contains basic point information, like its name, number, and address.
After the point is selected and the transaction is finalized the order will be exported to TC Logistics.
 
 
 TC Logistics
TC Logistics is used to overview and manage orders created with Express Relais delivery.
Express Relais delivery status is being checked periodically depending on how old the order is. The ranges are as follows:
up to 2 days old - every 1 hour
3 to 5 days old - every 2 hours
6 to 10 days old - every 6 hours
11 to 14 days old - every 12 hours
Orders older than 14 days do not receive automatic status checks from Express Relais. This value can be changed in integration settings as described in System Settings.
System Settings
Express Relais additionally needs to be configured on TC Logistics alongside E-commerce to ensure order communication and status exchange. Express Relais settings can be found in:
System config > Integrations > Express Relais
Visualization of the TC logistics system settings
In the Express Relais integration settings you can find the following options:
Functionality enabled - A switch enabling the functionality. When it's disabled the Express Relais orders won't be sent to the vendor and their status won't be updated.
API URL - URL of an Express Relais API. This URL shouldn't be changed.
API username - API username used to access the API.
API password - API password used to access the API.
Max check period (days) - Maximum number of days to check the order status in Express Relais. The default value is set to 14, which means that when the order is older than 14 days it won't anymore have automatic status checks. This value should be set to at least a number of days when the customer is allowed to return their product.
Mobile prefix - Prefix added to mobile phone numbers on Express Relais order creation.
Pickup city, address, contact, phone, email - Store or warehouse information from where the Express Relais orders should be received from. It is essential for these fields to be filled in.
Order Management
In the order details a new Delivery point table is visible when the Express Relais delivery is used (1). This table contains:
Delivery point ID - ID of the delivery point.
Delivery point name - Name of the delivery point.
Delivery point address - Address of the delivery point.
Visualization of the TC logistics order details (Details tab)
When the TC Logistics status is set to Packaging the Express Relais tab is visible (2). This tab contains detailed information regarding the Express Relais statuses.
Below you can find what Express Relais statuses are automatically mapped to TC Logistics statuses. The change of the Express Relais status will change TC Logistics status during the next status check.
Express Relais status
TCLogistics status
ER status description
NEW_ORDER
ID_PACKAGING
Initial status at order creation
ORDER_CONFIRMED
ID_READY_TO_SHIP
Order Confirmed
ORDER_CANCELED
ID_CANCELLED
The order was canceled by the client
ORDER_REFUSED
ID_DELIVERY_FAILURE
Order refused by Express Relais
MISSING_PARCEL
ID_DELIVERY_FAILURE
Missing parcel during pickup
PARCEL_PICKEDUP
ID_SHIPPED
Parcel picked up
PARCEL_IN_AGENCY
ID_SHIPPING_IN_PROGRESS
The package arrived at the regional agency
PARCEL_IN_TRANSIT
ID_SHIPPING_IN_PROGRESS
Parcel in transit
PARCEL_IN_DELIVERY
ID_SHIPPING_IN_PROGRESS
The parcel is delivered to the locker or destination address
DELIVERED_TO_LOCKER
ID_SHIPPING_IN_PROGRESS
Parcel delivered to the locker
PARCEL_RETRIEVED
ID_DELIVERED
Parcel received from Smartlocker
WAITING_IN_LOCKER
ID_SHIPPING_IN_PROGRESS
The package waiting for pickup from the automated locker
DELAY_IN_RETRIEVE
ID_SHIPPING_IN_PROGRESS
Package delayed for pickup at the destination locker
WAITING_COD
ID_SHIPPING_IN_PROGRESS
The package arrived at the destination locker and awaiting payment upon delivery
COD_PAID
ID_SHIPPING_IN_PROGRESS
Payment upon delivery at the locker completed, the recipient can retrieve their parcel
PARCEL_TO_RETURN
ID_RETURN
The client has initiated the return of the parcel in question
PARCEL_ABANDONED
ID_RETURN
The package was abandoned because the package was not delivered and the client did not initiate its return
PARCEL_RETURNED
ID_RETURN
Parcel returned successfully
PARCEL_IN_FINAL_AGENCY
ID_SHIPPING_IN_PROGRESS
Parcel has arrived at the final agency
RETURN_REQUEST_CONFIRMED
ID_RETURN
The requested return parcel has been confirmed
Visualization of the TC logistics order details (Express Relais tab)
In the Express Relais tab you can find the current status of the orders with the following information:
Parcel ID - ID of the order from E-commerce platform.
Status - Current Express Relais status of the order.
Status Description - Status description is taken from Express Relais.
Status comment - Status comment taken from Express Relais
Status update time - Last update them when the status was updated.
Below the table with order status, you can find a log of status changes that additionally contains a waybill column. Waybill is assigned to the order once it is present in the status update.
As mentioned in  TC Logistics the status update frequency depends on how the order is, but if there is a need to receive a new update even after an allowed 14 days by default it is possible by pressing the update status button located in the top right corner of the Express Relais tab. This button will immediately check the status of a desired order and update all data if there is a change.

BLIK integration
Getting started
In this article, you can find information about the BLIK integration used on a Polish website.
Blik is a payment system in Poland that allows users to make instant payments and withdraw cash using only the user's standard mobile banking app. The system allows to make online and in-store purchases and to transfer money in real time between bank accounts without the need for a payment card. BLIK is a typical T6 payment that uses 6 numbers long codes, that are randomly generated every 2 minutes to pair the payment request to their bank application.
This integration uses PayU integration, as PayU manages all BLIK payments as well as provides necessary keys and IDs.
Table of contents:
 Configuration
 Customer perspective
 
 
 Configuration
Blik doesn't have any internal options in System / Settings and is configured like every PayU payment method in System > Payment types / list.
Visualization of the BLIK configuration
Available settings are:
Is active? - A switch that definies if the selected payment method is active
Public name - A public name of a payment method. This name is visible on the website for the customers.
Public description - A description of a payment method. This description is visible on the website for the customers.
Export tag - A tag that will be exported to JOY. For BLIK it should be set to PAY_PP_CREDIT_CARD export tag.
Sort order - A sort order of the payment. It defines in which order payments should be sorted on the payment page. The higher the number the later in the list payment will be visible.
enable_optional_payu_payment - Enables a button on a BLIK page, which allows customers to use PayU instead. This option shouldn't be enabled if the transparent blik is enabled. Accepted values are 1 for true and 0 for false.
key1 - An integration key provided by a PayU panel.
key2 - An integration key provided by a PayU panel.
onlyBlik - Provides an option for an on-page blik handling instead of redirecting the users to a PayU page. In the case of transparent BLIK payment, it should be enabled. Accepted values are 1 for true and 0 for false.
posID - ID of a POS from a PayU panel.
ssl_receiver - An option to enable a Secure sockets layer receiver. It should be enabled.
use_sandbox - An option to enable a sandbox mode for a selected payment. This option should only be enabled on UAT environments.
With a BLIK payment option created and configured, it needs to be enabled in the altshops. You can find more about it in the Alt shop / payment types article.
  RememberBLIK payment option needs to be properly configured in the PayU panel beforehand. PayU themselves need to enable a transparent blik option for a selected payment method.
 
 
 Customer perspective
Enabled BLIK payment option will be instantly usable by the customers during the payment process
Visualization of the payment options in the order process
When the OnlyBlik option is selected the customers will be redirected at the last step into an order confirmation page where the field for a BLIK code is visible. Customers can put there their BLIK code and confirm it.
Visualization of the BLIK payment
If the BLIK code is correct the customer order will be instantly paid for. If the code is not correct customers will see information, that the typed code is incorrect and will be able to try once again. In case of expired or used codes customers will be able to type the code again as well.
Visualization of the incorrect BLIK code

Passmachine integration
Getting started
In this article, you can find information about the passmachine integration, which allows customers to add their FIDEN2 cards to their virtual wallets on iOS and Android devices.
Table of contents:
 Enabling the functionality
 Customer perspective
 
 
 Enabling the functionality
Passmachine integration is disabled by default and needs to be enabled in the
System / settings > Integrations > Passmachine
Visualization of the passmachine system settings
In the passmachine integration system settings there are the following options:
Enabled -A switch that enables or disables the functionality.
Display on the website - A switch that enables the integration for the website. If it's turned off, the functionality will only work in the mobile app.
Login (e-mail) - E-mail is used to log in to PassMachine account. It should have User-level privileges and should be limited to only one subproject.
Password - Password to the PassMachine account.
Template ID - Template ID from the PassMachine panel which should be used for new passes (virtual cards).
Endpoint URL - Absolute URL to PassMachine API. This URL should always point to https://api.passmachine.cz unless there are changes on the passmachine side.
With the functionality configured and enabled it is ready to be used by the customers.
 
 Passmachine passes
Passmachine assigns it's internal passes to the customers e-mail addresses. This way passmachine can connect which customer is which by their pass from the wallet, and then link it to the customer on the Yves Rocher application or website.
If there is a need to remove a singular customer pass or clear the entire pass database it is possible to do so in
System > Passmachine / passes
When the customer has their pass removed from the database a new one will be generated, when the customer logs in to their account.
  Warning   Removing the passes is irreversible. All the connections between Yves Rocher and Passmachine wallet integration will be severed, so customers no longer will be able to use or see their FIDEN2 points in their Google / Apple wallet.  
Visualization of the passmachine passes tab
In the Passmachine / Passes you can find the following options:
(1) Show X Entries allows to filter how many entries should be visible at once
(2) Various table columns. All of them can be sorted by clicking on them.
ID - Pass internal ID
E-mail - Customers e-mail address to which the selected pass is assigned to.
Pass ID - Identification of the pass used in the passmachine.
Update time - A date and hour when the last time pass was updated
Actions
Delete - A button, that allows to deletion of a selected pass. This action is irreversible.
(3) Clear database button allows to clear the whole pass database. Do not use this functionality unless it is absolutely necessary. This action is irreversible.
(4) Search field allows to search the passes by the customer e-mail address or their pass ID.
(5) Pages list allows to show the next batch of passes on the another page according to applied sorting option and filters.
 
 
 Customer perspective
With the functionality enabled, customers will be able to add their FIDEN2 cards to their virtual wallets. The new buttons can be found in the customer profile below the bar code and card number.
Visualization of the customer profile
These buttons redirect users to the passmachine website, where they can choose the platform they want to use.
Visualization of the passmachine website

Orlen delivery integration
Getting started
In this article you can find information about Orlen delivery service, which can be used by customers to deliver their packages to the selected pickup points.
Orlen delivery doesn't have system configuration, as all of it's content is provided and managed by Orlen. All needed to start using this delivery option is enabling it in System > Delivery / types and in a selected altshops.
  RememberYou can find more about enabling delivery options in Delivery costs / list - browsing and managing delivery costs article
Table of contents:
 Frontend overview
 
 
 Frontend overview
With enabled and configured delivery type customers are allowed to use the Orlen delivery pickup.
Visualization of the Delivery step in the order process
Visualization of the Orlen delivery window
In the delivery point popup customers are able:
(1) Search for their desire location. This option will move the map to the typed location
(2) Allow the device to share their current location. This option will center the map on the users location. Users approval to use the devices GPS is required for this functionality to work properly.
(3) Select one of the closest locations. This option shows customers the exact location of the pickup point as well as it's opening and closing hours. The delivery cost is taken from the Orlen Delivery Pickup delivery cost configured in Delivery costs / list - browsing and managing delivery costs.
  RememberOrlen delivery view is provided by Orlen, and Tau Ceti is unable to make any changes to the design and functionality at it's current state.
With selected delivery point customers are able to proceed with their order, and the order will be delivered to the selected Orlen pickup point.

Exponea
Getting started
Exponea is an external cloud-based e-commerce experience platform by Bloomreach. It specializes in B2B services in marketing automation, product discovery, and content management system.
Tau Ceti platform integrates with Exponea, allowing Yves Rocher employees to configure AI product recommendations and personalized content and inject it into desired places on the website.
  RememberIn order to use the Exponea panel under URL https://app.exponea.com/ you have to have an account with proper access. Yves Rocher provides access to Yves Rocher Exponea, so if you require access please get in touch with your superior.
  RememberYou can learn more about using the Exponea panel in Bloomreach documentation under URL https://documentation.bloomreach.com/engagement/docs
Table of contents:
 Configuration
 Exponea product recommendation
Creating a product recommendation
 
 
 Configuration
Exponea integration connects to the Yves Rocher website with a unique project token and keys. Every country using exponea has separate projects for each country, so their content is separated.
You can find the Exponea configuration in:
System > System / Settings > Integrations > Exponea
 
Visualization of the
In the Exponea configuration you can find the following options:
Functionality enabled - A switch that enabled the integration support.
Project token - An Exponea project key.
Public key - An Exponea public integration key
Private key - An Exponea private integration key
Exponea: Product view count weblayer id - An ID of an Exponea web layer, which is used to count the amount of times products on a website have been viewed. It is necessary for proper AI product recommendations.
Use non-flickering experiments snippet - A switch that defines if a non-flickering snippet for experiments should be used. You can find more about it under URL https://documentation.bloomreach.com/engagement/docs/flickering-effect-in-experiments
Webpush support enabled - A switch that defines if webpush support should be enabled. If this switch is turned on the built-in web push support should be disabled.
Show popup with webpush subscription proposal on all pages - A switch that defines if a newsletter subscription proposal web push should be displayed on all pages for the customer. Whenever it is disabled it will be visible only on a homepage.
With all necessary fields filled Exponea integration is ready to use and projects set up in the Exponea panel will affect the selected Yves Rocher website.
 
 
 Exponea product recommendation
Exponea can be configured to recommend customers products that might interest them based on their purchase history and view history. Bloomreach is using an AI technology, to find the most likely products that customer will purchase, when recommended.
In the Tau Ceti admin panel these recommendations can be configured in:
CMS > Exponea / Recommend product block
Below you will find a description of all possible actions you can perform in the Select block section.
 
Visualization of the
 Select the Show X entries (1) field to set the number of product recommendations, displayed on one page (min 10 / max 100).
The names of the columns (2) that contain information about a target product recommendation. Each column is susceptible to sorting. To sort the records, click on the title of the column.
ID - An internal ID of the Exponea product recommendation
Name -
Is active? -
Actions - List of buttons with possible actions that can be done to the desired recommendation:
Edit - Edit desired product recommendation. Editing has exactly same actions as adding new one, so the list of actions can be found in Creating a product recommendation chapter.
Select the Add (3) button to go to the adding the new Expoena product recommendation. You can learn more about adding of the recommendations in Creating a product recommendation chapter.
Search box (4) where you can search for desired recommendation by using their name.
Page buttons (5), which allows user to change the page of the recommendation list.
Creating a product recommendation
While creating or editing a new product recommendation we have to have prepared a correct recommendation ID from the Exponea panel. You can find more information about this topic and recommendation examples in the Bloomreach documentation under URL https://documentation.bloomreach.com/engagement/docs/recommendations#section-4-implement
Below you can find field descriptions in the Tau Ceti panel
 
Visualization of the
Name - An internal product recommendation name.
Recommendation ID - Exponeas recommendation ID
Size - A number of recommended items to return i.e. 5 will result in 5 items shown.
Items - Information about currently viewed product by the browsing user. Represented as dictionary 'product_id: weight.' Please use only single item in the dictionary with weight = 1.
Strategy - 
Picture - This field is only visible when creating a new product recommendation.
Category id - This field is only visible when creating a new product recommendation.
Block title - This field is only visible when creating a new product recommendation.
Anti - 
Similarity -  A switch that decides the similarity between two items. When it's turned on the AI will try to recommend similiar items to the customer.
Anonymous - 
Consider known items - 
Active - A switch which defines if a selected recommendation is active on the Yves Rocher website.
 

JOY webservice
Getting started
In this article, you can read about JOY integration and its options in the Tau Ceti panel.
JOY is an external integration Yves Rocher uses for order, stock, and campaign code management. Currently, during the order creation process at the last step, JOY validates if a current product stock in JOY and assigned to the altshop campaign code is correct. If it's not correct customer is unable to finish the order with a notification to try again later.
When the order is created in Tau Ceti it's going through an internal check process, which is followed by a JOY check process. After passing both checks the order is being sent to JOY.
Table of contents:
 JOY - TC communication
Configuration
 Orders to verify
 JOY stocks
 JOY / Failed orders report
 JOY / Real time validation
 
 
 JOY - TC communication
Communication between JOY and Tau Ceti happens in cycles or during certain events. Below you can find used communications between Tau Ceti and JOY:
Cyclic communication
Stock synchronization happens every hour at different times for every environment. Updates stock levels stored in the TC database based on values from JOY. Stocks are retrieved from JOY always using the regular altshop default campaign code. This value uses the Order API.
Stock synchronization schedule:
Polish environment synchronizes every hour at 
XX:00.
Czech environment synchronizes every hour at 
XX:12.
Slovak environment synchronizes every hour at 
XX:24.
Hungarian environment synchronizes every hour at 
XX:36.
Romanian environment synchronizes every hour at 
XX:48.
Import of invoice numbers happens every 30 minutes. Retrieves invoice numbers from JOY for orders that, when placed in JOY, did not generate an invoice. The invoice number is used in other processes (i.e.: invoicing, EET CZ). This value uses the Order API.
Export e-commerce orders happen every 3 minutes. Exports orders to JOY. When exporting orders in JOY, Tau Ceti creates and updates consumer data (this doesn't happen anywhere else). The order is exported regardless of the paid status. When exporting orders, Tau Ceti also performs a check to see if a city name definition exists in JOY for the postal code used. If it does not exist, the record is created. In this way, we automatically populate the address dictionary in JOY, because otherwise, JOY would not allow us to save multiple orders. This value uses the Order API.
Export e-commerce order payment information happens every 3min. Exports order payment information if such information was not available when the order was exported. Uses Invoice API.
Event-based communication
Export BaseLinker orders - when a positive validation of an order from BaseLinker is completed. Always creates new consumers in JOY. It does not use existing accounts. Orders with e-payments are exported to JOY only if they have already been paid. It uses Order API.
Import of order status changes and waybill numbers from JOY - when Tau Ceti gets a notification sent to TC API. Order status change information may include a waybill number, which is stored in the database for presentation to the consumer for order tracking. Waybill numbers are also sent to BaseLinker if the notification is for an order originating from BaseLinker.
Checking campaign code and inventory in real-time - at the time of order closing (approval of order placement by the consumer). Uses Order API.
  RememberTau Ceti service is waiting 5 seconds for a connection initiation. If the connection is not initiated it will result in a timeout.
If Tau Ceti doesn't receive a response to their request from the JOY service within 30 seconds it will result in a timeout.
 
 
 Configuration
Initial JOY configuration on a new environment requires joint cooperation between Tau Ceti developer team and the JOY team to set it up properly.
You can find the JOY configuration in the:
System > System / Settings > Integrations > JOY Webservices
Visualization of the JOY webservices tab in System / Settings
In the JOY configuration you can find the following options:
JOY Enabled - A switch that enables or disables JOY integration
Invoice API: WSDL URL - URL of Invoice API WSDL. This URL shouldn't be changed.
Invoice API: market code - Market code. This code is provided by JOY
Invoice API: login - Login provided by JOY, which allows connecting to the JOY API
Invoice API: password - Password provided by JOY, which allows connecting to the JOY API
Invoice API: Use Keep-Alive - Defines whether we reuse existing connections to the JOY API when we make more than 1 request to the API in a single process. This option is unstable and may cause issues, so it is recommended to leave it disabled.
Order API: WSDL URL - URL of Order API WSDL. This URL shouldn't be changed.
Order API: market code - Market code. This code is provided by JOY
Order API: login - Login provided by JOY, which allows connecting to the JOY API
Order API: password - Password provided by JOY, which allows connecting to the JOY API
Order API: Use Keep-Alive - Defines whether we reuse existing connections to the JOY API when we make more than 1 request to the API in a single process. This option is unstable and may cause issues, so it is recommended to leave it disabled.
Order API: skip order filters - If enabled, filters set in JOY are ignored. It should be enabled because it is very common to have filters set up in JOY that prevent orders from being placed. If skip orders filters are enabled, filters in JOY do not block order placement.
API: Technical breaks - Definies in a HH:MM-HH:MM;HH:MM-HH:MM (i.e. 08:00-10:00;22:00-23:00) format when the API technical break occurs. Please do not use e.g. 23:00-01:00 range, as the time is always checked for the current day.
Stock real time validation - A switch that defines if real-time validation for stocks is enabled when creating a new e-commerce order. If it is enabled, but JOY is unable to validate stocks because of i.e. connection issues customers won't be able to create new orders.
Campaign codes real time validation - A switch that defines if real-time validation for campaign codes is enabled when creating a new e-commerce order. If it is enabled, but JOY is unable to validate the campaign codes because of i.e. connection issues customers won't be able to create new orders.
Joy Export Logs: Lifetime (days) - Defines for how long JOY export logs will be stored.
Delete errors older than (days) - Defines after how many days system deletes JOY errors
Export company data - A switch that defines if customer company data in the Invoice table should be exported to JOY.
Please notice that JOY allows only for setting company data within customer records. It means that customers placing two orders using the same account, on the same day, with different invoice data will probably receive invoices with the same data as the person/company receiving the invoice. It applies not only to company data, it applies to entire billing data. They are overwritten during the export of every customer's order.
Additionally used fields were added to JOY for Romania only. It means that JOY may not support the usage of these fields for any other country than Romania.
Only billing address company data are transferred to JOY. There is no option to pass company data for delivery data.
 
 
 Orders to verify
Whenever an order fails an internal Tau Ceti check or JOY check it will be visible with an error message in the:
Orders > Orders / to verify
Visualization of the Orders / to verify tab
In the Orders / to verify tab there is an option to
Re-export the order - The system tries once again to verify the order and re-export it to the JOY. If the verification fails once again the order will be visible once again in Orders / to verify after a short time.
  RememberIn most cases whenever an error cannot be re-exported it should be handled by the JOY team on their side unless it's an error with incorrect customer invoice/delivery data, which needs to be fixed in the Tau Ceti panel.
The JOY support team can be contacted via email helpdesk-se@yves-rocher.se.
If you are not sure about the error please contact the Tau Ceti helpdesk team via 
email helpdesk@tauceti.email.
Mark the order as correctly exported - Severs the connection between Tau Ceti and JOY regarding this order and marks it as correctly exported in the Tau Ceti admin panel.
  Warning    Marking an order as correctly exported severs the connection between Tau Ceti and JOY regarding this order, which means any updates on both platforms won't be sent to the other platform. This means that the order will also not have a generated invoice.   
  RememberIn Orders / to verify there are also visible orders with errors from other integrations like Rumanku used in Click & Collect functionality. Rumanku errors can be recognized with a CC: at the beginning of the error message. The JOY team is not handling Rumanku errors. 
 
 
 JOY stocks
JOY stocks functionality can be used to verify a product stock available in JOY as well as it is a quick way to verify if a connection with JOY works correctly, as it will return an error whenever trying to check a stock.
You can find JOY stocks in:
Catalog > Joy stocks
Visualization of the JOY stocks
In the JOY stocks you are able to choose a desired campaign code and then type the SKU number of a desired product. By pressing the Check stock button you will be able to see how exactly many pieces of typed product are available for a selected campaign code. You are additionally able to see an XML request sent to JOY and its response.
If typed product is not available in JOY or the connection to JOY doesn't work properly you won't see any product information, but a message that the product couldn't be found.
 
 
 JOY / Failed orders report
It is possible to see all orders that have not been placed in Tau Ceti admin panel, because of failed JOY campaign code or stock validation. You can find such report with failed JOY orders in:
Reports > JOY / Failed orders
Visualization of the filter in JOY failed orders report
In the filters tab we have following options:
Error time - Defines a range of dates within the errors will be searched for
Order ID - Defines an order ID of a failed order
Customer ID - Defines a customer's internal ID.
Visualization of the filtered JOY failed orders
With an applied filter, you can see all of the orders in a selected date range that has failed. In the Error column, you can see what was exactly a source of an error.
If the order was placed afterward it's Order ID will be blue and clickable. By clicking the Order ID you will be redirected to the order page.
 
 
 JOY / Real time validation
Whenever there will be a planned maintenance of JOY webservice Yves Rocher can prepare for that by disabling the real-time validation for campaign codes and stocks. This can be done in JOY system settings described in  Configuration chapter, but it can also be automated in:
System > JOY / Real time validation
Visualization of the JOY real time validation tab
In the JOY / real time validation tab, we are able to select the:
Mode - A Enable / Disable choice. Whenever the mode is set to Disable it will disable both validations (stock and campaign code) for a selected execution time, whenever it's set to Enable it will enable them.
Execution time - A local time whenever the selected mode should be executed. Below the field, you are able to see a local time for a selected environment. As execution happens according to the local time please check if provided information by JOY applies to the environment local time i.e. if the JOY team has provided information that they have maintenance at 23:00 UTC+2 and the selected environment country is located in a UTC+3 timezone you have to select the hour 00:00.
The schedule applies only once for a selected mode, so there is no automatic way to enable the validation back whenever it's been disabled. In this case please remember to put another schedule, whenever you want to enable the validations back. For example:
29.07.2023 22:00 - Disabled mode
29.07.2023 23:00 - Enabled mode
This way JOY validation will be disabled for an hour on a selected environment.

Click and Collect
Getting started
In this article, you will find information about click and collect integration, which will connect the Yves-Rocher e-commerce website with selected local POS stores. By doing so, customers will be able to check products and their available stock for a selected store, order them online, and collect them in the store. This functionality allows to even further expand the user experience by giving them more options to handle the delivery as they please as well as verify if their desired product is available in the selected store before going there.
  RememberClick & Collect uses Rumanku integration in order to connect to the stores. Setting up Click & Collect on a website requires both configuring it in the Tau Ceti admin panel described in the  Configuration chapter as well as configuring the stores in Rumanku itself.
Table of contents:
 Configuration
 POS stocks configuration
 E-commerce perspective
 Configuration
Click & Collect functionality configuration can be found in the
System > System / Settings > Integrations > Click and collect
Visualization of the Click and Collect functionality
In the Click and Collect tab you can find the following options:
Functionality enabled - enables the click & collect functionality.
Debug mode - Enables expanded logging for communication between TC and Rumanku. This option should be turned off unless the TC team is verifying the functionality.
API URL - Rumanku API URL. This URL shouldn't be changed.
API Token - Rumanku API token
Non-exportable SKU - An array of SKUs that shouldn't be exported to Rumanku. In this list, there should be products that are virtual only and are not available in the POS stores like FIDEN2 points from a Gift of Choice promotion. Example of an array:
["40PKT","80PKT","TREE"]
Invoicing enabled - Enables invoice generation for C&C orders.
Cancel order after days - A numerical value that defines after how many days an order should get canceled automatically if not received by the customer.
Available in shop filter - Adds a filter in the product catalog, which allows customers to filter only products available in the selected POS store.
Show modal shop selector as list - Defines if the POS store list should be visible for customers as a vertical list or modal tiles. You can find a visualization of these options in the  E-commerce perspective chapter.
Force zero stock SKU list - An array of SKU numbers that will have forced a stock value of 0 for all C&C stores.
  RememberWith Click & Collect functionality enabled it is important to enable the Click & Collect delivery option in System > Delivery types / list (You can find more about this section in the [UNDER CONSTRUCTION] article), and enable it in the desired altshops in Altshops > Delivery costs / list. (You can find more about this section in the Delivery costs / list - browsing and managing delivery costs article).
 POS stocks configuration
As POS stocks are stored locally and are sent from the Tau Ceti platform to Rumanku this functionality needs to be enabled for Click & Collect to work properly. It can be found in:
System > System / Settings > Built-in functions > POS stocks
Visualization of the POS stocks system settings
In the POS stocks system settings you can find the following options:
Import enabled -Enables/disables automatic import of POS Stocks from the local directory.
Ignored SKU prefixes - List of SKU prefixes that are removed from SKU before checking real stock value. JSON array should be in the following format: 
["P", "F", "S"]
Fixed stock SKU - List of fixed stocks for point of sales. They are never checked against real values. JSON array should be in the following format: 
[{"sku":"40PKT","stock":1000},{"sku":"80PKT","stock":1000}
Stock buffer - Minimum stock value which allows customers to buy products. For example, value "3" means that the customer will be able to buy 2 pieces if stock is "5". It affects all orders referencing POS stocks (both Click&Collect and Beauty Advisor). Set to "0" to disable the buffer.
 E-commerce perspective
With Click & Collect functionality enabled customers are able while looking through the product catalog or searching for desired products to select a desired Yves Rocher store (1).
Visualization of the Click & Collect POS selection (desktop)
Visualization of the Click & Collect POS selection (mobile)
This filter option will open a pop up with a list of available POS stores that can be searched by their address, name, or POS number. The content of every modal or list is configured in Rumanku.
Visualization of the POS selection popup (modal tiles)
Visualization of the POS selection popup (list)
Visualization of the POS selection popup (mobile)
After customers select a desired POS store now they are able to filter all of the products in the search query or a product catalog by their availability in the store (2).
Visualization of the "Show only products available products in the store" filter
Additionally whenever customer enters a product page there will be an information about availability of the product in the selected store as well as their exact stock if they are available (3).
Visualization of the product stock information on the product page (desktop)
Visualization of the product stock information on the product page (mobile)
With the order ready customers are able to select the Click & Collect delivery option, which means they will get their order in person in the selected POS Store. If in the product catalog, no store was selected customers will be requested to choose a POS store at this step.
Visualization of the Click & Collect delivery option
If at least one selected product is not available in the POS store customer will receive an information about that when selecting the POS store
Visualization of the POS store list with unavailable products from the cart
As well as if a customer tries to proceed with the order they will be brought back to the delivery option selection in case one of the products are not available in the selected store with a popup which products are not available.
Visualization of the popup informing which products are not available in the selected store

Zbozi.cz integration
Getting started
In this article, you can learn about zbozi.cz integration. Zbozi.cz integration contains configuration in the system settings, feed, and API connection with zbozi, which exports order data to zbozi whenever it is paid for. The API export does not contain gifts from the order.
Zbozi.cz feed is located under /partner/feedZBOZI.xml URL
(i.e. https://www.yves-rocher.cz/partner/feedZBOZI.xml)
  RememberZboží.cz is an internet comparison engine providing information for shopping on the internet. It allows customers to sort, filter and compare prices of products, find out the stock availability of goods or locate a store near them. 
Visualization of the zbozi.cz feed
Table of contents:
Configuration of the integration
Zbozi API elements
 
 
 Configuration of the integration
In order for zbozi.cz integration to work properly it needs to be configured first. It's configuration settings are located in:
System > System / Settings > Integrations > Zbozi
Visualization of the zbozi configuration in the system / settings
In the Zbozi system settings you can find following fields:
Enabled - Enables the integration
Integration URL - URL Address where Zbozi application is available (sandbox: "https://sandbox.zbozi.cz", prod: "https://www.zbozi.cz/")
Company ID - Identifier of the company on the Zbozi platform (Establishment ID)
Sklik ID - Sklik conversion identifier.
Private Key - The authorization key for the integration (Secret Key)
Sandbox - Enables the test mode
 
 
 Zbozi API elements
With integration configured every order that has been paid for is being sent to zbozi API. Gifts are not being sent to the API.
Visualization of the example order sent to zbozi
Following order data is being sent to zbozi:
Order Number
Delivery Price
Other costs
Payment method
Calculated total price
List of products

Heureka integration
Getting started
In this article, you can find information about the Heureka integration. This integration prepares a product feed that can be used on the Heureka platform. The feed is available under 
/partner/feedHeureka.xml (i.e. http://www.yves-rocher.cz/partner/feedHeureka.xml) when it is enabled in the system settings. The feed is generated every two hours.
  RememberHeureka is a Czech e-commerce site. More than 38,000 online stores present their offers on the Heureka.cz platform, allowing portal users to choose offers and compare prices of more than 21 million products.
Visualization of the Heureka xml feed
Table of contents:
 Configuration of the integration
 Feed overview
 
 
 Configuration of the integration
In order for a feed to be available it needs to be enabled. You can find the feed configuration in the
System > System / Settings > Integrations > Heureka.
Visualization of the Heureka integration in the System settings.
In the Heureka tab in the system settings you can find the following options:
Feed enabled - A switch that decides whether the feed should be generated or not. Disabling the feed does not delete the file that has already been generated.
Altshop - A list of altshops you can choose a single altshop from which products should be downloaded and applied to the feed.
Manufacturer - The name of the manufacturer, appearing in the MANUFACTURER field in the generated feed.
Delivery days - information after what time the product will be delivered. This is the DELIVERY_DATE field in the feed.
Categories limit - the limit of categories displayed in the feed for one product (analogous to the limit on the product card).
 
 
 Feed overview
In the Heureka feed, we can find available products from the selected altshop.
Visualization of the Heureka xml feed
Every product in the feed has the following fields:
ITEM_ID - Product SKU number taken from the SKU field
PRODUCTNAME - Product name taken from a name field
DESCRIPTION - Product description taken from the Main description field
URL - Product URL starting with the website URL (i.e. https://www.yves-rocher.cz) and followed by the URL taken from the Friendly URL field.
IMGURL - URL of the image assigned to the selected product.
PRICE_VAT - Current price of the product
MANUFACTURER - Manufacturer name set in the Heureka configuration.
CATEGORYTEXT - Product properties and tag. Properties are separated by a vertical bar.
EAN - Product EAN number taken from the EAN field.
PRODUCTNO - Product SKU number taken from the SKU field
PARAM - List of parameters.
PARAM_NAME - Name of the parameter.
VAL - Value of the parameter.
DELIVERY_DATE - Delivery date value set in the Heureka configuration.
ITEMGROUP_ID - SKU of a parent product (applicable for example for color variations)

Login via Apple ID
Getting Started
Apple integration allows to register and log in using an Apple account with a simple click of a mouse (1). In order to enable the functionality, it is needed to provide the necessary keys from the Apple app, and enable it in the System / settings.
This integration allows customers to quickly log in or register to their accounts without the need to provide additional email and password information.
  RememberIt is also possible to register and log in using Google, Facebook, and Seznam accounts. You can find more about that in the Social login and Login via Seznam articles.
Visualization of the Apple ID authorization button on the log in page
Table of contents:
 Configuring the functionality
Customer perspective
 
 
 Configuring the functionality
Apple log-in can be configured in the:
System > System / Settings > Integrations > Apple Auth.
Visualization of the Apple.cz authorization tab
In this tab we can find following options:
Enabled - A switch that enables the functionality.
API URL - URL of the Apple API. Should always be set to https://appleid.apple.com.
Client ID - Client identifier which can be obtained from Identifiers / Services IDs section in Apple Developer website.
Mobile App client ID - Client ID parameter used by mobile applicaiton
Team ID - Apple team ID taken from Apple developer website.
Private key path - Absolute path to Apple p8 private key.
Private key ID - Apple p8 private key ID.
Locale (f.x. pl_PL) - Integration locale. F.x. pl_PL for Poland.
 
 
 Customer perspective
When functionality is enabled, the customer will be able to simply register and log in by pressing the Login with Apple button (1) and using his Apple ID on the log in page:
Visualization of the Apple authorization button on the log in page
The button is also located in the registration form:
Visualization of the Apple authorization button in the register tab
 
When a customer selects the option to log in via Apple ID, the Apple popup will appear, where the customer is able to log in to his Apple account or select logged in account and log in into it.
Visualization of the Apple authorization
After logging in customer will have to allow Yves Rocher website access to their Apple ID.
Visualization of the Apple authorization
After acceptance customer will be logged in if there is already a registered account using that
e-mail address.
In case there is no account with the customer's e-mail address in the database, he will be redirected to the registration web page, where he has to fill in the needed fields (2) for registration that are not provided by Apple.
Visualization of the Apple additional information page

Glovo feed
Getting started
In this article, you will find how to enable and download Glovo feed. Glovo is an on-demand courier service that purchases, picks up, and delivers products ordered through its mobile app.
By default, the feed is disabled on all countries except Romania.
Visualization of the Glovo feed
Table of contents:
 Enabling the feed
 Downloading the feed
 
 
 Enabling the feed
The feed switch can be found the
System / settings > Integrations > Glovo
Visualization of the Glovo system settings
Here you can change the Feed enabled switch state which will enable or disable the Glovo feed. The feed is updated every hour at XX:09.
Altshop option allows selecting from which altshop product list will be taken with their altshop prices.
 
 
 Downloading the feed
When the switch is enabled in the system settings the feed can be accessed through /partner/feedGlovo.xlsx URL for example https://www.yves-rocher.ro/partner/feedGlovo.xlsx.
Visualization of the Glovo feed
In the feed you can find the following columns:
External_ID - Contains product SKU.
Product_Name - Contains product name.
SuperCollection - This field is always empty.
SuperCollection_Order - This field is always empty.
SuperCollection_Image - This field is always empty.
Collection - This field is always empty.
Collection_Order - This field is always empty.
Collection_image - This field is always empty.
Section - This field is always empty.
Section_Order - This field is always empty.
Price - Contains the price of the product
Image - Contains URL of an image of the product in 500x500 format.
Extra_Images - Contains additional images if the product has them assigned to it.
Description - Contains description of the product
Is_Alcoholic - Is always set to NO
Is_Tobacco- Is always set to NO
Attribute_Groups - This field is always empty.
 

Data layer
Getting started
In this article, you will find information about available variables and events used in the data layer on a Yves Rocher websites. The data layer is a JavaScript object (array) that is used to pass data from a web page to the Google Tag Manager container. The data that the website passes to the data layer can then be used to create variables, rules, and tags.
  RememberThe data layer contains all of the data generated by visitors and customers engaging with the Yves Rocher website. 
Table of contents:
 Available variables in the data layer
yr_gtm_a
yr_gtm_a1
yr_gtm_ab
yr_gtm_b
yr_gtm_ac
yr_gtm_c
yr_gtm_ad
yr_gtm_d
yr_gtm_e
yr_gtm_f
yr_gtm_fa
yr_gtm_g
yr_gtm_h
yr_gtm_k
yr_gtm_l
yr_gtm_m
yr_gtm_n
yr_gtm_u
yr_gtm_aa
yr_gtm_ae
yr_gtm_ag
yr_gtm_x
yr_gtm_y
yr_gtm_z
ecomm_pagetype
ecomm_totalvalue
ecomm_prodid
ecomm_prodidpl
id_sekce
visitorLoginState
hashed_email
hashed_phone_number
email
phone_number
address_info
 Available data layer events
page_view
ecommerce / view_cart
ecommerce / add_to_cart
ecommerce / remove_from_cart
ecommerce / add_shipping_info
cart.change_address_data
ecommerce / add_payment_info
ecommerce / begin_checkout
ecommerce / purchase
ecommerce / view_item
ecommerce / view_item_list
website_error
type: '404_error'
type: 'wrong_discount'
type: 'missing_product_in_cart'
type: 'old_offer_error'
type: 'zero_search'
mgm.button_share
mgm.button_copy
wishlist_add
 
 
 Available variables in the data layer
yr_gtm_a
Shows URL parameter for current altshop (used also in ?yras=… URLs)
Example: default
Available on: All pages
yr_gtm_a1
Shows Offer_segment value from current altshop settings.
Example:  OfferSegment
Available on: All pages
yr_gtm_ab
Shows historic offer_segment values from the last 90 days in current altshop.
Example:
yr_gtm_ab
object
- .
object
.offer_segment
Old_offer
.total_visits
189
.total_orders
8
Available on: All pages
yr_gtm_b
URL parameter of a current campaign code in current altshop
Example: CC1546592845
Available on: All pages
yr_gtm_ac
History of URL parameters of the campaign codes active in user session in last 90 days in current altshop
Example:
yr_gtm_ac
object
         .0
CC1664286880
         .1
CC1661009512
         .2
CC1498480417
         .3
CC1658042828
Available on: All pages
yr_gtm_c
Current campaign code in current altshop
Example: 3CYLAWS11
Available on: All pages
yr_gtm_ad
URL parameters of a history of campaign codes active in user session in last 90 days
Example:
yr_gtm_ad
object
         .0
3CYLAWS11
         .1
3CYL8WS11
         .2
3CYGCWP01
         .3
3CYL7WS11
Available on: All pages
yr_gtm_d
User fingerprint (RLC) stored in long lasting cookie.
Example: b51Fx9u0VgKaVkkKz1P1nGqZZknbNYRk5
Available on: All pages
yr_gtm_e
Customer hash. Non-empty only for sessions that can be connected with some customers.
Example: 062f89de75ddf516484a
Available on: All pages
yr_gtm_f
User type. There are the following types:
"1" - Guest user, no information about a connection with any customer account
"2" - User who has subscribed to newsletter
"3" - Registered customer
"4" - Registered customer with active VIP Zone subaccount (Member Club account)
Example: 4
Available on: All pages
yr_gtm_fa
Current customer VIP zone MC title.
Example: T0
Available on: All pages
yr_gtm_g
Count of customer orders from last 360 days.
Example: 7
Available on: All pages
yr_gtm_h
Date of last customer order (YYYY-MM-DD), only orders up to 360 days are taken into account.
Example: 2022-08-04
Available on: All pages
yr_gtm_k
Value of last customer order in websites currency, only orders up to 360 days are taken into account.
Example: 1000
Available on: All pages
yr_gtm_l
Average value of customer orders from last 90 days.
Example: 750
Available on: All pages
yr_gtm_m
List of product SKUs present in customer orders from last 360 days, excluding gifts
Example:
yr_gtm_m
object
        .0
97701
Available on: All pages
yr_gtm_n
List of gifts SKUs present in customer orders from last 360 days.
Example:
yr_gtm_n
object
        .0
F02113
        .1
F94615
        .2
F67114
Available on: All pages
yr_gtm_u
Date of current visit (YYYY-MM-DD)
Example: 2022-10-25
Available on: All pages
yr_gtm_aa
Current visit status. There are the following statuses:
0 - standard visit (without order and abandoned cart).
1 - visit with an abandoned cart.
2 - visit with the placed order.
Abandoned cart - another cart than current, with at least one product.
Example: 2
Available on: All pages
yr_gtm_ae
Date of previous visit (YYYY-MM-DD)
Example: 2022-10-24
Available on: All pages
yr_gtm_ag
Count of visits in last 360 days
Example: 607
Available on: All pages
yr_gtm_x
List of SKUs that the user saw during the current visit. Only SKUs seen on product pages are used.
Example:
yr_gtm_x
object
        .0
05241
        .1
74084
        .2
74084
Available on: All pages
yr_gtm_y
List of tags seen by user during the current visit. Only tags used on tag pages (/tag*) are used.
Example:
yr_gtm_y
object
        .0
Kategorie: Vlasy > Masky a octy: Masky > Cílená péče: Detox vlasů
        .1
Kategorie: Vlasy
        .2
Kategorie: Vánoce
        .3
Kategorie: Vánoce
Available on: All pages
yr_gtm_z
Top X product SKUs in abandoned carts from last 90 days, without gifts.
Example:
-yr_gtm_z
object
        .0
22456
        .1
J0437
        .2
83020
Available on: All pages
ecomm_pagetype
A type of page. Available types are:
"home"
"product"
"category"
"purchase" (orderend = order thank you page)
"cart" (all other cart pages)
"siteview" (visit on any site not meeting above conditions)
Example: product
Available on: All pages
ecomm_totalvalue
Total cart/order value without delivery method cost
Example:  2000
Available on: Only on pages with ecomm_pagetype = purchase/cart
ecomm_prodid
On purchase/cart pages: list of SKUs in order/cart, without gifts.
On product pages: current product SKU.
Example:
On product page: "10399"
On other pages: ["10399","J0346"]
Available on: Only on pages with ecomm_pagetype = purchase/cart/product
ecomm_prodidpl
On purchase/cart pages: list of SKUs in order/cart, without gifts.
On product pages: current product SKU.
On category pages: top X top-rated products found by selected filters.
Example:
On product page: "10399"
On other pages: ["10399","J0346"]
Available on: Only on pages with ecomm_pagetype = purchase/cart/product/category
id_sekce
On category pages: list of selected tags IDs.
On product pages: list of tags IDs from the most important feature assigned to the product (eg. Category).
Example: ["1246","1252"]
Available on: Only on pages with ecomm_pagetype = product/category
visitorLoginState
Current state of user log in state. There are currently two states:
"0" = guest
"1" = logged in customer
Example: 1
Available on: All pages
hashed_email
SHA256 hash of normalized user e-mail address.
Methodology: https://developers.google.com/google-ads/api/docs/conversions/enhance-conversions?hl=en#normalization_and_hashing
Example:  "1b4f0e9851971998e7320785...edf7caa332359d6f1d83567014"
Available on: Only on the order thank you page (/cart/orderend, /cart/prepayment)
hashed_phone_number
SHA256 hash of normalized user mobile number.
Methodology: Google does not provide it. We normalize phone numbers to digits only and then hash them.
Example: "60303ae22b998861bce3...8a213c86c93c076dbe9f558c11c752"
Available on: Only on order thank you page (/cart/orderend, /cart/prepayment)
email
User e-mail address.
The field is generated only when unsafe user info is enabled within System > System / Settings > Integrations > Google Tag Manager
Example: "example@example.com"
Available on: Only on order thank you page (/cart/orderend, /cart/prepayment)
phone_number
User mobile number.
Field is generated only when unsafe user info is enabled within System > System / Settings > Integrations > Google Tag Manager
Example: "+48999999999"
Available on: Only on order thank you page (/cart/orderend, /cart/prepayment)
address_info
An object containing delivery address data of placed order. First and last names are hashed using SHA256.
Methodology: https://developers.google.com/google-ads/api/docs/conversions/enhance-conversions?hl=en#enhancement_adjustments
Fields "first_name" and "last_name" are generated only when unsafe user info is enabled within System > System / Settings > Integrations > Google Tag Manager
Example:
{
"hashed_first_name": "4f0e9851971998e...e59d6f1d83567014",
"hashed_last_name": "60303ae861bce3...8a213c86c9311c752",
"city": "Praha",
"postal_code": "11800"
}
OR
{
"hashed_first_name": "4f0e9851971998e...e59d6f1d83567014",
"hashed_last_name": "60303ae861bce3...8a213c86c9311c752",
"first_name": "Jan",
"last_name": "Kowalski",
"city": "Praha",
"postal_code": "11800"
}
Available on: Only on order thank you page (/cart/orderend, /cart/prepayment)
 
 
 Available data layer events
page_view
Event Generated automatically by Google Analitycs. All events handled by GA4 have anonymized IP (it's non-configurable).
Event parameters: (GA4 generated)
altshop
Triggered on every page if "Track page loads as "altshop" event" is enabled in GA4 system settings.
Event parameters:
{
name: 'alt shop name'
}
ecommerce / view_cart
This even is triggered on cart page (/cart).
Event parameters:
{
value: gross value of products,
currency: 'ISO currency code',
items: [{
item_name: 'product name',
item_id: 'product SKU',
item_variant: 'product attribute value / color name',
item_brand: 'YvesRocher',
item_category: 'Product category',
price: final price for 1pc,
discount: 'difference between catalog_price and final price',
currency: currency,
quantity: quantity
}],
shipping_tier: 'delivery method name'
}
ecommerce / add_to_cart
Triggered when a user adds an item to the cart. It applies only to regular 'add to cart' buttons. The value field contains the total row value after a change (determined by SKU). Items contain only elements with item_id equal to added SKU.
Event parameters:
{
value: gross value of products,
currency: 'ISO currency code',
items: [{
item_name: 'product name',
item_id: 'product SKU',
item_variant: 'product attribute value / color name',
item_brand: 'YvesRocher',
item_category: 'Product category',
price: final price for 1pc,
discount: 'difference between catalog_price and final price',
currency: currency,
quantity: quantity
}],
shipping_tier: 'delivery method name'
}
ecommerce / remove_from_cart
Triggered when the user removes an item from the cart using "X" in cart table at /cart. The value field contains the total row value after a change (determined by SKU). Items contain only elements with item_id equal to added SKU.
Event parameters:
{
value: gross value of products,
currency: 'ISO currency code',
items: [{
item_name: 'product name',
item_id: 'product SKU',
item_variant: 'product attribute value / color name',
item_brand: 'YvesRocher',
item_category: 'Product category',
price: final price for 1pc,
discount: 'difference between catalog_price and final price',
currency: currency,
quantity: quantity
}],
shipping_tier: 'delivery method name'
}
ecommerce / add_shipping_info
Triggered when user clicks on delivery method box on /cart/delivery (user changes delivery method).
Event parameters:
{
shipping_tier: 'delivery method name',
value: gross value of products,
currency: 'ISO currency code',
items: [{
item_name: 'product name',
item_id: 'product SKU',
item_variant: 'product attribute value / color name',
item_brand: 'YvesRocher',
item_category: 'Product category',
price: final price for 1pc,
discount: 'difference between catalog_price and final price',
currency: currency,
quantity: quantity
}]
}
cart.change_address_data
Triggered when the user clicks on "add new address" button on /cart/delivery page.
Event parameters: No parameters.
ecommerce / add_payment_info
Triggered when user clicks on the payment method box on /cart/payment (user changes payment method).
Event parameters:
{
payment_type: 'payment method name',
value: gross value of products,
currency: 'ISO currency code',
items: [{
item_name: 'product name',
item_id: 'product SKU',
item_variant: 'product attribute value / color name',
item_brand: 'YvesRocher',
item_category: 'Product category',
price: final price for 1pc,
discount: 'difference between catalog_price and final price',
currency: currency,
quantity: quantity
}],
shipping_tier: 'delivery method name'
}
ecommerce / begin_checkout
Triggered when "I confirm order" is clicked at the last step of the checkout process. Previously the event was triggered with every click of "next step" button.
Event parameters:
{
value: gross value of products,
currency: 'ISO currency code',
items: [{
item_name: 'product name',
item_id: 'product SKU',
item_variant: 'product attribute value / color name',
item_brand: 'YvesRocher',
item_category: 'Product category',
price: final price for 1pc,
discount: 'difference between catalog_price and final price',
currency: currency,
quantity: quantity
}],
shipping_tier: 'delivery method name'
}
ecommerce / purchase
Triggered on /cart/orderend page. The legacy implementation also triggered this event on /cart/prepayment page but it does not comply with GA4 e-commerce events.
Event parameters:
{
transaction_id: 'order id with prefix',
affiliation: 'VPI',
value: gross value with shipping,
shipping: gross delivery + payment method cost,
currency: 'ISO currency code',
items: [{
item_name: 'product name',
item_id: 'product SKU',
item_variant: 'product attribute value / color name',
price: final price for 1pc,
discount: 'difference between catalog_price and final price',z
currency: currency,
quantity: quantity
}],
shipping_tier: 'delivery method name'
}
ecommerce / view_item
This event is triggered on a product page.
Event parameters:
{
item_name: 'product name',
discount: 'difference between catalog_price and final price',
item_brand: 'YvesRocher',
item_category: 'Product category',
price: catalog price,
value: final price for 1pc,
}
ecommerce / view_item_list
Triggered on product list pages i.e. Category, Search result, Featured list.
Event parameters:
{
item_list_name: 'Name of list',
items: [{
item_name: 'product name',
item_id: 'product SKU',
item_brand: 'YvesRocher',
item_category: 'Product category',
price: final price for 1pc,
discount: 'difference between catalog_price and final price',
currency: currency
}]
}
website_error
Triggers whenever the user encounters an error on the website. Currently, there are 5 error types:
type: '404_error'
Triggered when a user enters 404 'not found' page.
type: 'wrong_discount'
Triggered when a user had activated the discount code that does not trigger any promotion rules. It's also triggered when the user had in the cart already used personal discount code.
type: 'missing_product_in_cart'
Triggered when some products were deleted from the cart due to low stocks.
type: 'old_offer_error'
Triggered when a customer is redirected to /auth/restricted.
type: 'zero_search'
Triggered when a customer entered search results page which did not return any results
mgm.button_share
Triggered when the user clicks on "share by e-mail" below the invitation link or code in a customer account.
Event parameters:
{
type: 'email'
}
mgm.button_copy
Triggered when user clicks on "copy" below invitation link or code in a customer account. This event triggers one of two parameters depending if the customer clicked copy below link or a code:
{
type: 'invitation_link'
}
or
{
type: 'invitation_code'
}
wishlist_add
Triggered when the user clicks on the wishlist button (small heart icon) which adds a product to the user's wishlist.
Event parameters:
{
item_name: 'product name',
item_id: 'product SKU',
item_brand: 'YvesRocher',
item_category: 'Product category',
price: final price for 1pc,
discount: 'difference between catalog_price and final price',
currency: currency
}

Magyar Posta delivery method
Getting started
In this article, you can find information about a new delivery method Magyar Posta Pickup. It is a pickup delivery method that displays near pickup points for the customers according to their delivery address set on the website, which can be used on a Hungarian Yves Rocher website.
Visualization of the Magyar Posta delivery pickup selection
Table of contents:
 Configuring the delivery method
 Customer perspective
 
 
 Configuring the delivery method
Magyar Posta delivery has to be activated and configured in the admin panel. You can find its configuration in the:
System > System / Settings > Integrations > Magyar Posta
Visualization of the Magyar Posta delivery system settings
in the Magyar Posta system settings, you have the following fields:
URL to XML file - this is a field where the Magyar Posta .xml file should be linked. This link should not be changed unless needed.
  RememberAs Magyar Posta is using Google Maps API to show their points on the map it is also required to have necessary frontend and backend keys in the System > System / Settings > Integrations > Google maps API
With all fields correctly filled remember to verify if the delivery method is correctly configured and set in the system > delivery types / list. You can find more about delivery types / list in the [UNDER CONSTRUCTION] article.
Visualization of the Magyar Posta delivery settings
It is also important to remember to enable the selected delivery methods in the Altshops > Delivery costs / list. You can find more about delivery costs / list in the Delivery costs / list - browsing and managing delivery costs article.
 
 
 Customer perspective
With the delivery method configured customers will see a new delivery method available in the delivery step of the purchase process ( /cart/delivery ).
Visualization of the magyar post delivery method in the delivery step
When the customer selects the Magyar Posta delivery method he will get a pop-up with all available pick-up points near them.
Visualization of the magyar Posta delivery pickup selection
  RememberAs Magyar Posta integration shows only available stores near customers' delivery addresses it can show no delivery points if the customer has his set address in a place, where Magyar Posta doesn't work. It is possible to change the customer's delivery address in another delivery method if the customer wishes to deliver to a different address than the default one.

Baselinker
Getting started
In this article, you can find information about BaseLinker integration, which allows Allegro and eMag orders to be processed directly into BaseLinker API and sent to JOY without the need to create orders in the Tau Ceti platform.
  RememberYou can find more about Allegro integration in the Allegro article
This integration allows employees to edit, if needed information on the BaseLinker panel and helps to identify Allegro and eMag orders.
This integration also provides constant communication between the Tau Ceti platform and BaseLinker API with automatic updates for products and stocks.
Table of contents:
 Configuring the BaseLinker
 BaseLinker product fields
 BaseLinker / Orders tab
Filters section
Orders section
Order details
Baselinker categories
 BaseLinker delivery mapping
Adding a new delivery method
 BaseLinker campaign codes
Creating a new campaign code
 BaseLinker errors
 
 
 Configuring the BaseLinker
BaseLinker configuration can be found in the
System > System / Settings > Integrations > BaseLinker
Visualization of the system settings integration location
Visualization of the BaseLinker settings
In the BaseLinker tab we can find the following options:
Functionality enabled – Switch that turns on or off the functionality.
Debug mode – Switch that turns on the debug mode. By default, it should be turned off.
Synchronize products - Turns ON/OFF products update executed daily. If disabled it will block the manual operation of products and categories creation. This switch does not affect stock updates.
Synchronize product attributes - Turns ON/OFF support for attributes within products add & update processes. Every attribute is exported as a variant within BaseLinker API.
Update stock - Switch which defines if the product's stock should be sent to the BaseLinker API. Stocks are updated every 15 minutes.
Waybill Enabled - Switch which defines if information about a waybill should be sent to the BaseLinker API.
Order prefix – Prefix of the orders made with BaseLinker.
Campaign code – Optional field of the campaign codes that will be used by orders made with BaseLinker API.
Sales Channel -A field that defines the sales channel used during order export to JOY
(field: salesChannel).
Default postal code - Postal code used during order export to JOY if the order has no postal code within BaseLinker API.
EasyBox parser - Turns ON/OFF decoding locker number for EasyBox service. Such locker number is placed within the address normally used for storing street names and numbers. EasyBox parcel numbers are not available within information about the "selected delivery point" within BaseLinker API.
JOY Export: Append state name to the city - Turns ON/OFF Appending the state name field to the value of the city field during order export to JOY. This switch alters both delivery and billing addresses.
BaseLinker altshop - Altshop that is used to get products that should be exported to the BaseLinker.
Remove diactrics - Turns ON/OFF removing diacritics from products name and description.
Product name: add "Yves Rocher" - Turns ON/OFF the addition of the ", Yves Rocher" to the product name.
Product name: add capacity - Turns ON/OFF adding ", {capacity}" to the product name. 
Warranty field value - Value for the "warranty" feature exported for every product.
Product price spread field value - Value used while calculating "min_sale_price" and "max_sale_price" features exported for every product. A value of 50 will mean that the minimum sale price will be set to 50% of the product promotion price and the maximum sale price will be set to 150% of the product promotion price.
Manufacturer name - Value used as manufacturer name during product synchronization.
Sex feature URL name - Value of field "URL name" which can be found within the e-commerce properties dictionary. This value is used to find the sex features which will be exported as the "sex" feature to BaseLinker.
Product image size - Image size identifier which will be used during exporting product images to BaseLinker. It must be an existing image size, eg. "500x500".
API url – API url. It should always be https://api.BaseLinker.com/connector.php
API Token – API token. This token can be found in the BaseLinker panel > User profile > My account > API > Your API token.
 Inventory ID - Inventory ID which should be gathered from the BaseLinker panel. It can be found in the lower-left corner of the Inventory edit form. Only inventory with this ID will be updated during product and stock synchronizations.
Warehouse ID - Warehouse ID which should be gathered from the BaseLinker panel. It can be found in the lower-left corner of the Warehouse edit form. All stocks will be exported only for this warehouse. If there are any other warehouses within BaseLinker API, they will be ignored.
Support company data - Turns ON/OFF considering company fields when importing orders from the BaseLinker. It also affects the export of billing data to the JOY as a result of BaseLinker order import with or without company data. It alters only BaseLinker orders and works regardless of the current value of the Company Fields switch (e-commerce related).
Company ID field identifier - The identifier of the extra field that contains the company ID. It can be found in BaseLinker panel section Orders > Settings > Additional fields > ID and should look like 
extra_field_64542.
Panel URL - It is used to generate buttons linking to the BaseLinker panel. Example: 
https://panel-e.BaseLinker.com.
With all necessary options set and saved, we can find export and update buttons in the
Orders > BaseLinker / Processes
Visualization of the BaseLinker processes
In BaseLinker Catalog we have 4 processes:
Adding new categories (1) – Export all the categories to the BaseLinker. The category tree is defined by the exisiting categories in Catalog > Categories / list. It is possible to define what categories should be exported to JOY in Orders > BaseLinker / categories ( You can find more about this section here  BaseLinker categories ) When this option is used again, we do not duplicate already exported categories, but only add new ones, and also old categories are not automatically removed.
Adding new products (2) – Exports products that are enabled on the selected in the System / Settings altshop and assigned to the categories. This option also does not duplicate already exported products, only adds new ones, and products with stock <= 0 are also ignored. It also controls the creation of product variants, which means that when Synchronize product attributes is active in the system settings, running product adding will add all active attributes to existing products. When one of the attributes is missing, it will be added. Product variants are created even if their stock value equals 0.
Please note, that only product main category will be assigned to it on the BaseLinker platform.
Below you will find supported fields:
Field name
Description
Data source
inventory_ID
Catalog ID
ID from TC system settings (BaseLinker_inventory_id)
product_ID
Product ID
Always null
is_Bundle
Is the product a part of a set
Always false
ean
EAN of a product
First found in the database EAN of the product. In case of multiple EAN codes, the first one taken from the database is exported.
sku
SKU of a product
Main SKU of the product. Attribute sku if data is generated for product variant.
tax_rate
VAT tax rate
Vat percentage taken from TC system settings from vat_percentage field.
weight
Weight of the product
Capacity field from the product page. This field is converted to a floating point number or 0.0.
height
Height of the product
Always 0.0
width
Width of the product
Always 0.0
length
Length of the product
Always 0.0
star
Star type (indication in the BaseLinker panel)
Always 0
manufacturer_id
Manufacturer ID
Manufacturer ID with a name that matches the BaseLinker_manufacturer_name system setting. Obtained from the getInventoryManufacturers method. If the manufacturer does not exist, it is created automatically.
category_id
Category ID
ID obtained from the API in the process of going through the categories to create a product. In the case of finding a product within several categories, it is the ID of the first category encountered
prices
The list of prices in the price groups.
id-price-group: price, where ID of the group is taken from the getInventoryPriceGroups method. Always default price group is used (is_default: true).
locations
Additional information regarding the location of the product in the warehouse
Always an empty table ([])
text_fields
descriptive fields with possible variants in different languages / for different integrations
Object with a set of fields compatible with the Supported text fields table.
images
Product pictures
List of images assigned to attribute if data is generated for product variant. The main photo is marked with index 0. We pass the photos as string url: {address}. If there are currently fewer photos than there were previously, the pre-existing object indexes are transferred with the value "" in order to force the deletion of the old photos. We are transferring photos in size 500x500px (system setting:
BaseLinker_product_img_size). The list is limited to 15 items.
Note: BaseLinker returns a list of photos with indexes increased by 1. When referring to these images, this index should always be decreased by 1. For update requests, the numbering is from 0, when retrieving product information, the numbering is from 1.
We only provide images related to the SKU set in the product, i.e. in the case of a SKU color variant, we will transfer only photos associated with a particular color.
links
Identifications of the product in the other warehouses.
Always an empty table ([])
stock
Stock value
{ "stock-id": { "stock-status" }
where ID of the warehouse comes from the system setting, while the stock is set according to the default altshop configuration. The logic is according to the cyclic process of updating stock levels.
Fields stock, parent_id, and bundle_products are not exported to BaseLinker.
Updating existing products (3) – Updates whole existing products and product variants with their picture, data, and stock. This method is performed cyclically every 24 hours for the RO market. All fields that are being updated by adding new products are updated except fields star, stock, parent_id, and bundle_products which are not updated.
When the products update process detects a product or variant which is inactive, it will set 
status feature to 
0.
Updating products stocks (4) –  Updates only existing product stocks and their variants without changing anything else. This method is performed cyclically every 15min for PL and RO markets. It excludes updating parent product stock as BaseLinker does not allow to set it. The stock of the parent product in BaseLinker is a sum of stocks assigned to all variants. The stock update process supports variants regardless the state of Synchronize product attributes switch. Depending on the product configuration, we send to BaseLinker:
The true value of the stock minus the minimum stock.
Value 99 in case of always in the stock setting.
Value 0 if set to never in stock.
For each process, we are able to see their current status, last usage time, and a button to run the selected process. Available statuses are:
started - the process is currently working.
not-working - the process is not currently running and is not scheduled to run automatically (it will run only when you click on the run now button).
disabled - the process is deactivated by system settings.
scheduled - the process is not currently running, but it is scheduled to run automatically.
  RememberBaseLinker communication is also automated with TC platform:
Orders are imported to the TC platform and they are updated every 5 minutes
We export the stocks to the BaseLinker every 15 minutes.
Products are exported and updated in the BaseLinker every 24 hours, every day at 01:10AM server time.
Export of Emag orders from TC platform to JOY is sent every 2 minutes.
Orders are exported from eMag to the BaseLinker every 10 minutes
Supported text fields in the product import:
Name of the field
Description
Data source
name
Name of the product
Product name. adds 
- {color name} if data is generated for product variant.
Value ", Yves Rocher" is added if the system setting BaseLinker_product_name_manufacturer is equal to 1.
Value ", {capacity}" is added if the system setting BaseLinker_product_name_capacity is equal to 1 and the product has a non-empty capacity field value.
Within the text, all diacritical characters are
converted to characters in the ASCII range if the setting of the BaseLinker_remove_diactrics system setting has a value of 1.
description
Description of the product
combined text of all descriptions in order: main, effects, usage, ingredients, capacity, additional_info, notes.
Within the text, all diacritical characters are
converted to characters in the ASCII range if the setting of the BaseLinker_remove_diactrics system setting has a value of 1.
description_extra1
Additional description 1
Always an empty string ("")
description_extra2
Additional description 2
Always an empty string ("")
description_extra3
Additional description 3
Always an empty string ("")
description_extra4
Additional description 4
Always an empty string ("")
features
Features of the product
List of product features with additional features (please see Supported Features section).
status is 
0 when the product is globally inactive (disabled in product definition).
status is 
0 if the product is active but data is generated for the inactive product variant.
 
Supported features
Within the features field within the product data, we upload:
A warranty feature with a value derived from the system setting BaseLinker_warranty_field_value.
The part_number feature with the product's main SKU.
The min_sale_price feature with a value calculated according to the formula {spread} * {promotion price} / 100, where {spread} is the value of the system setting BaseLinker_price_spread_field_value.
Feature max_sale_price with a value calculated according to the formula (100 + {spread}) * {promotion price} / 100*, where {spread} is the value of the system setting BaseLinker_price_spread_field_value.
The base_price feature with the promotional price of the product.
The sale_price feature with the value calculated according to the formula {price} - {vat percentage} * {promotion price} / 100.
Status feature with a value of 1 if the product is active in BaseLinker's alt shop, 0 otherwise.
Feature sex with the value of the feature assigned to the product within the
e-commerce database.
The link is after the SEO (url friendly) name of the feature. The SEO name comes from the
BaseLinker_sex_feature_url_name system setting. If a product has more than one value assigned to the feature, they are separated by a comma with a space.
All values are cast to a string type
 
 
 BaseLinker product fields
Updating the product changes almost the same amount of fields as importing the new ones.
Visualization of the BaseLinker product edit
In the first tab “General Information” we have fields:
Product name – The name of the product which is taken from the product “Name” field on the Yves Rocher platform. We add to this field automatically after the comma “Yves Rocher” and after another comma the capacity of the product from the product “capacity” field
Category – The category of the product.
Manufacturer – default value that will always be “Yves Rocher Romania” for RO website, other values will be visible for other countries
Quantity in storage – The quantity of the product taken from the “Stock value” field on the Yves Rocher platform product page.
Gross price – Base price of the product. If the product doesn’t have a promotion price it will be the catalog price taken from the “Price” product field. If the product has a promotion price it will take from the Altshop “Price” field from a specific product
Purchase price – Same as Gross price
EAN – EAN of the product which is added in the import process of the products to the Yves Rocher platform.
Catalog number – SKU – SKU of the product taken from the “SKU” field.
VAT rate – fixed value set in the BaseLinker settings
Weight – The weight of the product taken from the “Capacity” product field.
Visualization of the BaseLinker product edit description
In the descriptions tab, we can see product descriptions. The product description is taken from all description fields on Yves Rocher platform and put in one Description field on the
BaseLinker platform.
Visualization of the BaseLinker product edit photos
In the Photos tab, we can see exported photos of the products. If the product has additional pictures they will be visible in Additional photo 1, Additional photo 2 etc. fields.
Visualization of the BaseLinker product edit parameters
In the parameters tab we can see all product parameters:
Status – Status of the product. 1 equals active, 0 equals that product is inactive. The default value is 1, but if the stock of the product falls to 0 the product status will change also to 0, so customers won’t be able to buy it. Disabling the product in the altshop also will change the status value to 0.
Min_sale_price – Minimal sale price for the product. It is equal to 50% of the base price of the selected product.
Max_sale_price – Maximal sale price for the product. It is equal to 150% of the base price of the selected product.
Base_price – Base price of the product. It is taken from the product catalog or promotional price, same as in the “gross price” in the general information tab
Sale_price – Sale price of the product. Base price minus VAT percentage.
Warranty – The fixed value of 12 month
Part_number – Product SKU number is taken from the SKU field.
Sex – Male / Female values. It is only taken and read from the products that have the “sex” tag assigned to them.
 
 
 BaseLinker / Orders tab
The BaseLinker / orders tab allows us to see all successfully exported orders made in the Allegro or eMag platform and imported to BaseLinker API. This tab can be found in
Orders > BaseLinker / Orders
All possible operations to perform on the BaseLinker view can be done in the Filters (1), and Orders (2) tabs.
Visualization of the BaseLinker orders tab
 
Filters section
The Filters section allows sorting of the BaseLinker orders, based on the available filters. Below you will find a description of available filters
Visualization of the filters tab in the BaseLinker page
Creation time - Range of dates when filtered orders have been created.
Status - Current status of the BaseLinker orders. Possible order statuses are:
Order created
Order data validation & mapping success
Order data validation & mapping failure
JOY export success
JOY export failure
Order canceled
Order unpaid
After defining the above filters, select the Apply Filters button to get a list of sites according to the applied filters.  
 
Orders section
The Orders section allows for organizing the BaseLinker orders and searching for the desired ones.
Below you will find a description of all possible actions you can perform in the orders section.
Visualization of the orders tab in the BaseLinker orders page
Select the Show X entries(1) field to set the number of BaseLinker orders, displayed on one page (min 10 / max 100).
The names of the columns (2) that contain information about target orders. Each column is susceptible to sorting.
To sort the records, click on the title of the column in question.
ID - TauCeti internal ID of the order
External ID – Allegro / eMag ID of the order
First/last name – First and last name of the customer
E-mail – Customers email address
Mobile – Customers mobile number
Creation Time – Creation time of the order
Order ID – BaseLinker ID of the order
Status – Current status of the order. Possible statuses are:
Order created
Order data validation & mapping success
Order data validation & mapping failure
JOY export success
JOY export failure
Order canceled
Order unpaid
Actions - A show more button, which will open the selected order. Order details are described in the Order details section
Search box (3) where you can search for orders by customers e-mail address, mobile number, name and surname, order ID, and External ID.
Page buttons (4), which allows user to change the page of currently viewed BaseLinker orders.
 
Order details
When pressing the show more button you will get redirected to the selected order details.
Visualization of the order tab
The first tab is the Order tab. In the Order tab we can check the order:
ID – Internal ID of the order.
Import date - Date of the order import to the TauCeti platform.
Order ID – BaseLinker platform order ID. This field has three additional actions:
View button allows to see the order as a customer in the BaseLinker
View in BaseLinker button allows to check particular order in BaseLinker.
Cancel button is only visible when order is not exported to JOY (i.e. because it has an error). It allows to cancel the selected order in TC and BaseLinker.
Order Status – Current status of the order.
First/last name – First and last name of the customer.
E-mail – Customers E-mail address.
Mobile – Customers mobile number.
Creation Time – Date of creation of the order.
Confirmation time – Date of confirmation time. This date is provided by BaseLinker API.
The next tab is with Delivery Address data.
Visualization of the delivery address tab
In this tab we can see delivery address data provided by the customer with postal code and city. Right below the delivery address data we can find company data fields. These fields are only visible if the Support company data switch in system / settings is enabled.
Visualization of the Company tab
In the Company data tab we have listed the provided name of the company, its tax ID, and Company ID.
The next visible tab is the Order data tab. The order tab shows basic information about the order.
Visualization of the order data tab
In this tab we can see Order information like:
Status – BaseLinker status number. This number is provided by BaseLinker
Delivery – The selected delivery method by customer.
Delivery cost – Cost of the delivery
Delivery point – Delivery post identification. It’ll be only filled when customer selects delivery to certain delivery point.
Delivery point name – Full name of the delivery point.
Delivery point address – Street name and number where selected delivery point is located
Delivery point postcode – Postal code of the delivery point
Delivery point city – City name, where delivery point is located.
Visualization of the payment tab
In Payment tab, we can see what payment method has been selected and how much customer paid using this payment method.
Visualization of the order lines tab
In the Order lines tab we can see all purchased products with their SKU, name, price, quantity and total value. If voucher was used in the order on the e-mag platform it will be also visible here with it's amount that has been deducted. When the order is exported to the JOY platform the amount of the discount is deducted from the order value, as JOY doesn't accept product negative
product values.
Last visible tab is the Events tab.
Visualization of the events tab
In the Events tab, we can see all events that happened in a particular order. If one order is edited in BaseLinker panel, the change will be visible in that order in the Events tab.
 
 
 
 BaseLinker categories
In this section, you can select the desired product categories, that should be exported to the Baselinker platform. The categories are created according to the existing category tree, that is configured in Catalog > Categories / list.
Visualization of the Baselinker categories section
This table contains the following columns:
Name - The name of the category. The categories are displayed as a tree. It means that it is impossible to select a subcategory without selecting the category higher in the branch.
BaseLinker Inventory ID - The internal BaseLinker inventory ID of the category. It is only displayed once the category has been successfully exported to BaseLinker
Synchronized to BaseLinker - The date and time when the category was exported to BaseLinker.
Update time - The date and time when the category status has been last updated. Changing the is active? tickbox will update the update time.
Is active? - A tickbox that defines if the category should be exported to BaseLinker. Only selected tickboxes will be exported. It is possible to deselected or selected all categories using the Deselect all categories or Select all categories buttons at the top of the table.
When the changes to the category selection are done they need to be saved using the Save button located in the top right corner of the table.
 
 
 BaseLinker delivery mapping
In this section, we can edit, delete or add new BaseLinker delivery methods and map them to the Yves-Rocher delivery methods. In order to map BaseLinkers delivery method with available Yves-Rocher delivery methods we need to navigate to:
Orders > BaseLinker / Delivery mapping
Below you will find a description of all possible actions you can perform in the BaseLinker / Delivery mapping tab.
Visualization of the BaseLinker delivery tab
Select the Show X entries (1) field to set the number of BaseLinker delivery methods, displayed on one page (min 10 / max 100).
The names of the columns (2) that contain information about target delivery methods. Each column is susceptible to sorting.
To sort the records, click on the title of the column in question.
BaseLinker Name – Name of the delivery method provided by BaseLinker
Joy name – Export tag of the delivery method sent to JOY. Export tags can be found in System > Delivery types / list. Based on that mapped name JOY sends to us waybill number which our system imports it to BaseLinker.
Courier Code – Courier Code provided by BaseLinker.
Name – System name of the delivery method.
Actions - There are two available actions:
View - View created a delivery method
Delete - Delete the selected delivery method
Select the Add delivery method (3) button to go to the adding the new delivery method. You can learn more about adding of the new delivery method in the Adding a new delivery method chapter
Search box (4) where you can search for delivery methods by their BaseLinker name, JOY name, or courier code.
Page buttons (5), which allow users to change the page of currently viewed delivery options.
 
Adding a new delivery method
To link the new delivery method we need to fill all the fields according to the columns described above. After saving the new delivery method with correct data our delivery method will be automatically linked and all Allegro / eMag orders will be exported to JOY with delivery according to Joy name column.
Visualization of the adding of the new delivery method
 
 
 BaseLinker campaign codes
Campaign codes used by the BaseLinker need to be created in the
Orders > BaseLinker / Campaign codes
Without a proper campaign code, BaseLinker orders won't be able to be exported to JOY.
Below you will find a description of all possible actions you can perform in the BaseLinker / Campaign codes tab.
Visualization of the BaseLinker campaign codes tab
Select the Show X entries (1) field to set the number of BaseLinker campaign codes, displayed on one page (min 10 / max 100).
The names of the columns (2) that contain information about target campaign codes. Each column is susceptible to sorting.
To sort the records, click on the title of the column in question.
ID - An internal identification number of the created campaign code
Name – Name of the integration. This name must match a source of the order (i.e. Allegro).
Campaign code – Campaign code value. This value has to match the campaign code created in the JOY platform.
Actions - There are two available actions:
Edit - Edit selected campaign code.
Delete - Delete the selected campaign code.
Select the Add integration campaign code (3) button to go to the adding of a new campaign code. You can find more information about editing and creating of campaign codes in the Creating a new campaign code chapter.
Search box (4) where you can search for campaign codes by their Name, JOY name, or campaign code.
Page buttons (5), which allow users to change the page of currently viewed campaign codes.
Creating a new campaign code
When editing or creating a new campaign code user has to define two values
Visualization of the campaign code creation
Name - Name of the integration. This name must match a source of the order (i.e. Allegro).
Campaign Code  - Campaign code value. This value has to match the campaign code created in the JOY platform.
With both fields filled in we can save the changes by pressing the Save button.
 
 
 BaseLinker errors
BaseLinker / errors is the tab where we can see all errors regarding importing orders made on Allegro / eMag platform. This tab can be found in
Orders > BaseLinker / Errors
Visualization of the BaseLinker errors tab
In this tab we can find various individual JOY errors similar to Orders / To Verify tab.
When error has been fixed we can try to re-import the order by clicking Force re-export (1) button.

Allegro
Getting started
Allegro is the biggest Polish e-commerce platform with over 11 million users. This integration allows the Yves Rocher e-commerce platform to receive orders made on an Allegro platform and process them like an order made on the website.
  Remember Romanian Yves Rocher website is also using a Baselinker integration in a more expanded version, which works as a bridge between Emag.ro and Yves-rocher.ro websites. More about Baselinker can be found in the Baselinker article.
Table of contents:
 Allegro
 Allegro delivery methods
 Adding new Allegro delivery method
 Mapping Allegro delivery method
 Allegro errors
 
 
 Allegro
Allegro tab displays all successfully exported orders made in the Allegro platform. You can find this tab in
Orders > Allegro.
   Visualization of the Allegro orders tab
In this tab we can see basic information like:
First and last name of the customer
Customer’s city
Customer’s Street
Customer’s Postal code
Customer’s Mobile number
Order creation time
Yves Rocher order ID
We can see more details regarding the selected order by selecting Show more button (1).
   Visualization of the order tab in the order details
In Order tab, we can check order
ID – Allegro module specific ID of the order
Allegro order ID – Allegro platform order ID
Order ID – Yves Rocher Order ID. By clicking “See” button (2) we can check it in the Orders > Orders / list section like rest of the e-commerce orders.
Creation time – Creation time of the order
Update time – Update time of the order (if updated)
Message – Customer message to the seller
The next tabs are Customer Data and Delivery Address
   Visualization of the Customer data and Delivery address tabs in the order details
These tabs display detailed customer data and delivery address data.
They will have different data only when delivery address data is different from customer invoice data on the Allegro platform.
In the last tab we can see is Order data tab.
   Visualization of the Order data tab in the order details
This tab displays order information like:
Status – Order status. It should be set to “READY_FOR_PROCESSING” if imported correctly to the Yves Rocher e-commerce platform.
Delivery method – Selected delivery method by customer
Payment method – Selected payment method by customer. If delivery method is with COD, it’ll be empty
Price – Price, that customer paid. If the delivery method is COD, it’ll be empty.
 
 
 Allegro delivery methods
In order to map allegro’s delivery method on Yves-Rocher website, we need to navigate to
Orders > Allegro delivery method.
   Visualization of the Allegro delivery method page
 
In this section we can edit, delete or add new Allegro delivery methods and map them to the Yves-Rocher delivery methods.
Adding new Allegro delivery method
To add a new delivery method, we need to press the "Add Allegro delivery method" button.
   Visualization of the adding new Allegro delivery method
Required fields to fill are:
Allegro ID – ID of the delivery method provided by the Allegro platform
System Name – Name of the method read by the system. Has to be unique.
Public name – Visible name of the delivery method on the backend
Public Description – Visible description of the delivery method on the backend
   Visualization of the added Inpost24 delivery method
With the newly added Allegro delivery method, we can proceed to map it.
Mapping Allegro delivery method
In order to map delivery methods, we need to press the "Add delivery method mapping" button.
   Visualization of the mapping delivery method
We need to select from the list our desired Allegro delivery method created earlier and Yves Rocher delivery method defined from System > Delivery types / list.
After selecting desired delivery methods, we need to press Save button to map them.
   Visualization of the mapped delivery method
With configured mapping, we can see which allegro delivery methods corresponds with already existing methods for e-store.
 
 
 Allegro errors
Allegro errors is the tab that displays all errors of the imported orders made on Allegro platform. This tab can be found in the Orders > Allegro errors.
   Visualization of the Allegro errors tab
Two most basic import errors we can find here are:
Allegro product from order not found – this import error appears, when someone buys a product with certain SKU on allegro, that doesn’t exist on Yves Rocher e-commerce platform product catalog.
Order Rejected: Address (delivery) does not match requirements – This error appears when customer buys products on allegro and types (in this case) a postal code that isn’t in the postal code dictionary on e-commerce platform. Works only when postal code dictionary is activated in the admin panel.
When the error has been fixed on the Allegro side, we can try to re-import the order by clicking the Force re-check button (1).
 

Orders

Orders managment
Getting started
In this article, you can find information about orders and their management in the admin panel. There are a few types of orders currently supported in the application:
E-commerce orders - Orders created via the Yves Rocher e-commerce platform. Mobile app orders also fit in this section. This order management will be described within this article.
Beauty Advisor orders - For more information about Beauty Advisor and order creation in the BA platform, please see Beauty Advisor - getting started
Allegro / Baselinker orders - For more information about Allegro or Baselinker orders please see Baselinker article.
Table of contents:
 Order system settings
Orders API
Carts / Orders
Order cancellation
 Orders list
Filters
List of orders
Order details
 Orders to verify
 JOY check order
 Orders payment
 PayU refunds
Creating a refund
Importing multiple refunds
 
 Order system settings
Order-related settings are configurable in the admin panel's system settings.
Orders API
JOY accepts only product names without prefixes. In this case it is necessery to define, which prefixes should be removed from the products in the order when they are for example a gift. This option can be found in:
System > System / Settings > Built-in functions > Orders API
Visualization of the Orders API tab
In this tab you can define the prefixes in an array format. Example of such array:
["P","F","H","G","D","Q","X"]
In this case every product that contains one of the defined prefixes will have it's prefix removed when exporting the order to JOY. For example if the product SKU is F54321 JOY will receive 54321.
Carts / Orders
General Cart / order options can be found in the:
System > System / Settings > E-commerce > Cart / orders
Visualization of the Cart / orders tab
In this tab you can find the following options:
Disable onetime orders - A switch that defines if customers are able to create one-time orders without creating an account on the e-commerce platform. When this switch is enabled customers have to create an account on the website to create an order.
Minimum order value - The minimum order value that is needed to create an order.
Maximum order value - The maximum order value that is allowed to create an order.
Free shipment from - A value from which customer won't have to pay for an shipment.
Order ID prefix - A prefix that will be applied to all order numbers.
Consider order closed after - After how many days orders should be automatically closed.
Payment fee visibility for zero - A switch, that defines if the payment fee should be visible in the order process for the customer if it's value is equal 0. In case of it enabled if the payment method "PayU" has a fee of 0, the customer will see below the PayU method, that they won't pay any fee for this payment method. Nonetheless if this switch is enabled or disabled the payment fee is always visible if it's above 0.
Order cancellation
Order cancellation tab allows defining if orders can be cancelled in the admin panel if they were already exported to JOY or TC Logistics system.
Visualization of the Order cancellation tab
This tab only contains Allow to cancel already exported orders switch. When it's disabled the order cannot be cancelled in the admin panel once it is exported.
 
 
 Orders list
Every created order on the e-commerce platform is visible and accessible in the admin panel. In the Orders / list tab it is possible to filter out neccessery criteria, verify order details as well as manage the order itself. Orders / list sectiion is available in the
Orders > Orders / list
Filters
By default orders are not loaded due to their amount. It is necessery to apply any filter criteria to show the available orders.
Visualization of the filter tab in orders / list
There are the following filters available:
Order ID - The internal ID of the order. This ID doesn't contain the order ID prefix, so the correct value would be 5840318, not CZVPI5840318.
Processed on - A range of dates when the order was processed by the system.
Order value - A range of total value of the orders.
Alt shop - A list of altshops that the selected orders were created at.
Status - Current status of the order. Statuses change automatially according to the received information regarding the order. The available statuses are:
New
Processing
Sent
Delivered
Returned
Cancelled
Delivery failure
Shipping in progress
Delivery method - A list of delivery methods used in the orders.
Payment method - A list of payment methods used in the orders.
Deffered payment status - A current status of a deferred payment. Available statuses are:
Paid
Overdue
Pending
Check status - Current order verification status. Available statuses are:
New (1/4) - The order was just created, and it wasn't yet checked by our internal verification system nor JOY.
Successfully checked internally (2/4) - The order has passed our internal verification system, and is ready to be exported to JOY
Internal check failed (2/4) - The order has failed our internal verification system. The error will be visible in the order details, or in the  Orders / to verify tab.
Successfully exported (3/4) - The order has passed the JOYs order verification system and has been exported to the JOY platform.
Export failed (3/4) - The order has failed in the JOYs order verification system, and was not exported to the JOY platform. The error will be visible in the order details, or in the  Orders / to verify tab.
Successfully processed (4/4) - The order has been correctly verified and exported, and no other actions are required for it.
Paid? - A yes / no selection, which defines if the order was paid for.
Customer ID - ID of the customer that has created an order.
Only with vouchers - A switch that displays only orders that contain vouchers.
Status (Balikobot) - A status of the order in the Balikobot. Available statuses are:
Pending
Unpaid
Confirmed
Created
Picked
Delivered
After applying filters by pressing the Apply filters button the list of orders will be shown.
List of orders
After applying a filter an Orders / list table will be visible with the filtered content
Visualization of the orders / list table
Below you will find a description of all possible actions you can perform in the orders / list section.
Select the Show X entries(1) field to set the number of orders, displayed on one page (min 10 / max 100).
The names of the columns (2) that contain information about target orders. Each column is susceptible to sorting.
To sort the records, click on the title of the column in question.
ID - Internal ID of an order
Processed on - A date and an hour when the order was processed.
Value - A total value of an order.
First name - Customers first name
Last name - Customers last name
E-mail - Customers e-mail address
Paid? - A yes / no option, if the selected order is paid for.
DP status - Delivery point status received from the API.
Status – Current status of the order. Statuses change automatically according to the received information regarding the order. Possible statuses are:
New
Processing
Sent
Delivered
Returned
Cancelled
Delivery failure
Shipping in progress
Actions
A Show button, which will open the selected order details.
A Cancel button, which cancels the selected order after a confirmation.
Search box (3) where you can search for orders by customers e-mail address, mobile number, name and surname, order ID.
Page buttons (4), which allows users to change the page of currently viewed orders.
Order details
In the order details view you can find every aspect of the selected order.
Visualization of the order details
In the order details main table you can find all important data regarding the selected order. There are the following fields:
Processed on - A date when the order was processed.
Order Value - A total order value.
Alt shop - An altshop from which the order has been made.
Campaign code - A campaign code assigned to the selected altshop that has been used for the selected product.
Paid? - A status if the order has been paid for.
Invoice - A generated invoice. If the invoice was not generated it will show such information. If the invoice was generated the button will be available to download the invoice.
Check status - Current order verification status. When a status is set to a failed internal check, or export failed a re-export and mark as correctly exported buttons are available. You can find more about these buttons in the  Orders to verify section. Available statuses are:
New (1/4) - The order was just created, and it wasn't yet checked by our internal verification system nor JOY.
Successfully checked internally (2/4) - The order has passed our internal verification system, and is ready to be exported to JOY
Internal check failed (2/4) - The order has failed our internal verification system. The error will be visible in the order details, or in the  Orders / to verify tab.
Successfully exported (3/4) - The order has passed the JOYs order verification system and has been exported to the JOY platform.
Export failed (3/4) - The order has failed in the JOYs order verification system, and was not exported to the JOY platform. The error will be visible in the order details, or in the  Orders / to verify tab.
Successfully processed (4/4) - The order has been correctly verified and exported, and no other actions are required for it.
JOY status - A button that redirects to  JOY check order. 
JOY response - A response for a selected JOY order. It is also available in  JOY check order.
Status – Current status of the order. Statuses change automatically according to the received information regarding the order. In this row, it is possible to change the status manually, check the history of status changes as well as cancel the order. Possible statuses are:
New
Processing
Sent
Delivered
Returned
Cancelled
Delivery failure
Shipping in progress
Delivery method - Shows which delivery method was selected by the customer
Delivery fee - Shows the delivery fee that the customer has paid for the order. This fee is added to the order's total value.
Payment fee - Shows the payment fee that customer has paid for the order. This fee is added to the orders total value.
Payment method - Shows which payment method was selected by the customer.
Payment date - A date when the payment has been registered.
Paid amount - An amount of money that has been paid for the order.
Payment tries - A button that shows all of the payment tries for the selected order. From this view, you can create a PayU refund. More about it can be found in the  PayU refunds tab.
Visualization of the payment tries
E-mail - Customers e-mail address
ID - Customers internal ID
JOY customer ID - Customers JOY ID
Invoice data - All the data provided by the customer for their invoice. It is possible to edit this data by pressing the Change button.
Shipment data - Customers shipment data provided by the client. It is possible to edit this data by pressing the Change button.
Balikobot - Data provided by Balikobot regarding the selected order. Balikobot provides with:
Status - Balikobot delivery status.
JOY invoice ID - Invoice ID in the JOY platform.
Order date - Date of the order.
Discount code - This section contains the main code and personal code (if applicable) that has been used by the customer in the selected order.
The order details table contains in the top right corner an Order e-mails button, which opens a new window containing all system e-mails related to this order sent to the customer
Visualization of the generated e-mails for a selected order
You can find the following fields in the E-mails generated for the order window:
Type - Type of a sent e-mail.
Status - Status of a sent e-mail.
Title - Title of a sent e-mail.
Content - A show hyperlink, which shows an e-mail content.
Creation time - A date when the e-mail sent functionality was initiated.
Last changed - A date when there was a last change to the selected type (e.g. status change).
Below the order details table, there is an Order lines table containing all of the products contained in the selected order.
Visualization of the order lines table
In the order lines table you can find the following data:
ID - Products SKU number
Product name
Type - A type of a product. The usual types are PRODUCT and GIFT.
Price - A price of a singular piece of a product
Quantity - The amount of the same SKU purchased
Value - The overall price of a row (e.g. product with a price of 259 and quantity of 2 will result in a value of 518)
Set SKU - If the product is part of a set, the SKU of the set will be visible here.
Below this table, there is a Promotion rules analysis (by order row) table, which contains all of the products (both type PRODUCT and GIFT) and lists all of the discount promotions that have affected the selected product.
Visualization of the Promotion rules analysis (by order row) table
The last available table is the Promotion rules analysis (by promotion rule), which contains all of the promotion rules that have been applied to the selected order. By selecting promotion rule name or blue promotion action name you will get redirected to the selected rule or action in a view mode.
Visualization of the Promotion rules analysis (by promotion rule) table
Depending on the type of promotion that has been applied the content of this table can vary. For example, if the applied promotion is a gift, then it will list which SKU has been added as a gift. If the applied promotion is a gift of choice, it will list which product has been chosen by the customer in this promotion.
 
 Orders to verify
Whenever an order fails an internal verification or JOY verification process it will be visible in
Orders > Orders / to verify
Visualization of the orders to verify
In this section are listed all of the orders that have an Internal check failed (2/4) or Export failed (3/4) statuses with their error messages. These orders can be searched or filtered by their Order ID.
For these orders two options are available
Mark as correctly exported - Marks an order as correctly exported in the TC admin panel. This option severs the connection between JOY and Tau Ceti for this order. Only use in cases where order exists in JOY with all correct data. Please note as this option severs the connection it means that JOY won't be able to send to Tau Ceti the necessary invoice information.
Force re-export / Force re-check - Tries to re-check or re-export the order. When an issue that caused an internal check fail, or export fail has been resolved this option will go through the process of verifying the order and correctly importing it to JOY. In case the issue still persists the order will return to Orders / to verify with an error code.
The buttons at the top of the page apply an action to all orders that are currently blocked, while the buttons to the right of the error code only apply an action to the specified order.
In most cases, errors Export failed (3/4) are related to issues from the JOY side, and contacting the JOY team is necessary. If you are unsure what to do or who to contact with a certain error message feel free to contact our helpdesk at helpdesk@tauceti.email
Examples of possible errors:
CRITIAL ERRORS:
1) Testing order failed: SOAP fault: Mailing 3PYL8WO61 not found, code: MAILING_NOT_FOUND
This error message informs that the campaign code 3PYL8W061 does not exist or is unavailable in the JOY system. Please verify, if the campaign code is available in JOY.
CRITIAL ERRORS:
1) Testing order failed: SOAP fault: Error Fetching http headers 
There was a connection issue with JOY while trying to export this order. Please re-export the order.
CRITIAL ERRORS:
1) Testing order failed: SOAP fault: Transaction line contains invalid product: Error on line 2 Can't find: Product alias country "G30626", code: TRANSACTION_INVALID_PRODUCT
Product G30626 doesn't exist in the JOY system. Please verify if such SKU is available in JOY, and if not, please create it. After the creation try to re-export the order.
CRITIAL ERRORS:
1) Testing order failed: SOAP fault: Order number already exists, code: ORDER_NO_ALREADY_EXISTS
Order number already exists in JOY. Please verify if the exists in JOY, and contact the JOY support, so they can look into it from their side.
 
 
 JOY check order
It is possible to check the information that JOY returns to us regarding the specific order in
Orders > JOY check order
Visualization of the joy check order
In this tab, after providing the order ID you will send a request to JOY to check the order status and receive a response from JOY. The response is accessible in both the Result tab in a clear form as well as the Raw requests tab, where the raw XML response is visible.
The following information can be found in the JOY response:
Order ID - Tau Ceti order ID
Status - Current order status in the JOY system
Customer code - Customer ID
Order amount - Total order amount
Invoice ID/no - Invoice ID or number in the JOY system
 
 Orders payment
A list of all orders with their payment information can be found in the
Orders > Orders / Order payments
Visualization of the Order payments tab
 
Below you will find a description of all possible actions you can perform in the Order payments section.
Select the Show X entries(1) field to set the number of orders, displayed on one page (min 10 / max 100).
The names of the columns (2) that contain information about target orders. Each column is susceptible to sorting.
To sort the records, click on the title of the column in question.
Order number - Internal ID of an order
Processed on date - A date and an hour when the order was processed.
Order value - A total value of an order.
Customer ID - Internal customer ID.
MC Customer ID - Member club internal customer ID. Member club functionality is no longer supported.
JOY customer ID - Customer ID in the JOY system.
Payment method - A method of payment that was used for the selected order.
Payment date - A date when they payment was created
Payment status - Current status of the payment
DP order payment due date- no longer supported.
DP order payment status- no longer supported.
DP order payment accepted by - no longer supported.
Export button (3), which exports all of the filtered orders to the .xlsx file. The content of this file is exactly the same as the content on the page.
Search box (4) where you can search for orders by the order ID, customers ID, and payment method.
Page buttons (5), which allows users to change the page of currently viewed orders.
 
 PayU refunds
When a customer has paid using the PayU platform and wishes to return a product, cancel the order or there is another reason for them to request a refund it can be finalized in the
Orders > PayU refunds
Visualization of the PayU refunds page
In the PayU refunds table you can find all already created refunds. Below you will find a description of all possible actions you can perform in the PayU refunds section.
Select the Show X entries(1) field to set the number of refunds, displayed on one page (min 10 / max 100).
The names of the columns (2) that contain information about target refunds. Each column is susceptible to sorting.
To sort the records, click on the title of the column in question.
ID - An internal ID of the refund.
Creation time - A date when the refund request was created.
Order - Internal order ID. By clicking it you will be redirected to the Order details
Payment ID - PayU payment ID.
Amount - An amount that has been refunded to the customer
Status - Current status of the refund. This value is received from PayU
Operator e-mail - E-mail address of an employee who requested a refund.
Reason - A reason of the refund.
Import button (3), which imports the prepared .xlsx file with refunds. You can find more about this in the Importing multiple refunds section.
Create refund button (4) which allows to create a new refund. You can find more about it in the Creating a refund section.
Search box (5) where you can search for refunds by their internal ID, order number, PayU payment ID and operator e-mail.
Page buttons (6), which allows users to change the page of currently viewed refunds.
Creating a refund
Upon pressing on the Create refund button you will be redirected to the refund creaction page.
Visualization of the refund creation
To begin the process first you have to provide the internal order ID that should be refunded. After providing such ID you will see all of the payments that have been made for the selected order. If the payment has been rejected it will be greyed out. Other payment tries can be selected
Visualization of the selection of refund amount
After selecting the payment you wish to refund you will see two new fields:
Amount - An amount of money that should be refunded to the customer. It is possible to do a partial refund.
Reason - The reason why the refund was processed.
Upon pressing the Return funds to customer the refund request will be sent to PayU and money will be returned to the customer.
 
Visualization of the created refund
You can create a new refund directly from the refund confirmation page by pressing the Create next refund button.
 
Importing multiple refunds
If there are multiple refund requests it is possible to import the xlsx file with them.
Visualization of the refund import
XLSX file must contain the following columns:
Order_id - Internal order ID
Order_amount - A total order amount. This value has to match the total amount of the order in the admin panel.
Refund_amount - An amount that should be refunded to the customer. It cannot be higher than a Order_amount.
Refund_reason - A reason of the refund.
Visualization of the refund import
When imported all of the refunds from the file will be displayed with their information, payment ID and import status.
If there are mistakes or errors you can return to the first step by pressing the Change file button.
If everything is correct you can proceed by pressing the Create refunds for valid rows button.
Visualization of the refund import
When the file gets processed the status will update with an information, that the refund has been created, or with an error, that there was some kind of issue.

Promotion module

Promotion entities import / export
Getting started
In this article, you can find information about the entities import / export, which allows admin panel users to export already prepared promotion conditions, actions, or rules and import them on different Yves-Rocher websites or environments. The export extracts the selected promotions "as is", which means they export them without the ability to modify them on the computer and the downloaded .zip file can only be imported. Whenever the user exports the promotion rule the entities functionality automatically exports all conditions and actions used in the selected rule.
  RememberYou can find more about the promotion module in the Promotion module introduction article. More detailed description of conditions, action and rules can be found in their respective articles: Conditions, Actions and Rules. 
Table of contents:
 Exporting entities
 Importing entities
 
 
 Exporting entities
Promotion conditions, actions, and rules can be exported in their respective tabs while editing them. It is possible to export multiple promotions at once, and by exporting the promotional rules all conditions and actions that are active in them are also automatically exported, so whenever a rule is exported there is no need to manually add the used in this rule actions and conditions.
Visualization of the export button in the rule edition view
By clicking the button Add to export (1) you add this promotion part to the export stash (2).
Visualization of the export stash
In the export stash, you can see all added entities with an option to clear the list or export them. By clicking the Export button the entities will be available to download.
  RememberThe export stash holds all the added entities even after exporting them. You can clear the stash by selecting the clear button, or it will get cleared itself whenever the browser is closed. 
Visualization of the entities export
The exported .zip file shouldn't be unpacked or modified, as it contains all the necessary information for our system to reproduce these conditions, actions, and promotions whenever they are imported.
 
 
 Importing entities
With a ready exported .zip file with entities, we are able to import it to any environment and country. This process consists of three steps:
Select file - Selection of a .zip file with entities
Data mapping - mapping entities to the existing promotions or creating new ones
Import - importing the entities and viewing the report.
This is done in:
Import / Export > Import / entities
Visualization of the import / entities tab
In the import entities tab, we have to choose the previously downloaded .zip file with promotions and then select the import file button. This will proceed with the import process to the second step, which is data mapping.
Visualization of the data mapping step
In the data mapping step, there are listed all conditions, actions, and rules that are imported into a selected environment. In this step you can find the following columns:
Entity - Entity type (condition / action / rule), name, and external ID.
Status - Status of the entity after our internal check. If everything is correct the status will be set to Valid. If there is an issue with an entity it won't get imported.
Local data link - The system is verifying existing promotions on the environment and if there is a match between the imported one it automatically matches it to the existing one. If no matches were found it will create a new condition / action / rule. In this column users are able to choose if they want to match the import to the existing promotion, and if so which one, or to create a completely new promotion. Two buttons are available:
View - Is only visible whenever there is a selected match for an entity. This button opens the matched entity, so the user can verify it.
Search - Allows users to search available promotions and select them, so the system will match the imported promotion to the selected one.
Visualization of the search functionality
With all entities verified, we can proceed to the third step by selecting the Accept mapping & import file.
  Warning    Please verify thoroughly the mapping process, as it is not possible to revert the overwritten mapped conditions / actions / rules.    
In the last, third step - Import we can see the result of the entity import.
Visualization of the import step
In this step we can see a table with three columns:
Entity - Entity type (condition / action / rule), name, and external ID. Additionally in this step, we will see information regarding the selected entity if some actions couldn't be executed i.e. If the imported entity is imported from PL PROD to CZ PROD there might be a mismatch with used altshops, so in the information tab, we will see information that manual assignment of correct altshops is required for such rule.
Status - Status of the import. If a new entity was created it will show Created and if an entity is updating the matched promotion it will say updated.
Link - Direct link to created or updated condition / action / rule.
If there are any unexpected errors while importing an entity please contact the Tau Ceti helpdesk 
at helpdesk@tauceti.email.

Examples of popular promotions
Getting started
In this article, you will find an example of the promotions that are used most frequently on multiple Yves Rocher websites. This article will only show you possible combinations of conditions and actions without the details, of how to create such promotions. You can find articles about condition, action, and rule creation with all their possibilities in the following articles:
Promotion module introduction
Conditions
Actions
Rules
Table of contents:
 Gift of choice after set cart value is exceeded
 Discount on 2 most expensive products when discount code is added to the cart 
 Free delivery over set cart value
 Two products for one when selected products are in the cart
 Third product from the list for free when selected discount code is used
 Additional FIDEN2 loyalty points when customer exceeds set cart value
 
 
 Gift of choice after set cart value is exceeded
Gift of choice is a list of gifts that customers can choose from. In this example, the customer will be able to do that after his cart value is over 290Kc
To create such a promotion, you have to create an Order Value condition. In this example, we used the following JSON:
{"prices":"promotion","include_payed_gifts":"TRUE","use_default_excluded_list":"FALSE","consider_discounts":"TRUE"}
Additionally, you have to create a Gift of choice action with example JSON:
{"sku_list": ["F31623","F94615","F01989","250PT","NOGIFT"],"min_cart_value_for_description":"290"}
For a promotion to work, you have to assign the above condition and action to the rule.
Visualization of the rule configuration of the promotion.
For an Order value condition to activate above 290Kc, we have to set the logic operator to >= (1) and the value to 290 (2). The action doesn't require any operator, or value, as it doesn't use any parameters except the ones written in the JSON.
Below, you can see how a customer sees the Gift of choice (3) promotion, whenever he has more than 290Kc of products in his cart.
Visualization of the gift of choice promotion on the website
 
 
 
 Discount on 2 most expensive products when discount code is added to the cart
One of the most common promotion types uses discount codes as a condition with various actions. In this case, when the customer types the discount code to the cart, his two most expensive products will get discounted by -40%.
Such promotion uses the Discount code in cart condition. This condition doesn't use any parameters.
To discount the most expensive products in the cart, we have to create a discount most expensive product action. In this example, we will use the following JSON parameters:
{"type":"percentage","prices":"catalog","exclude_products":["green_point_flag"],"quantity_limit":"2"}
For a promotion to work, you have to assign the above condition and action to the rule.
Visualization of the rule configuration of the promotion.
For a Discount code in cart condition to activate, we have to set the logic operator to = (1) and value to desired promotion code (2) - in this case, we will use MAILING11_22points one. In the action field, we have to specify the percentage discount customers will receive on the two most expensive products, as the type parameter in the action is set to percentage. In this example, we set it to 40 (3).
Below you can see how the customer can see this discount in his cart (4).
Visualization of the applied promotion
 
 
 
 Free delivery over set cart value
One of the most common promotions in the e-commerce platforms is free delivery. In TauCeti panel, we can set it up in two different ways:
Changing the price range for set delivery methods in Altshops > delivery costs / list
Creating a promotion with a free delivery action
The first method can be read about in the Delivery costs / list - browsing and managing delivery costs article.
The second method requires creating a rule that contains a selected condition and a free delivery rule. In this example, we will use an order value condition with JSON parameters:
{"prices":"promotion","consider_discounts":"TRUE","exclude_products":["green_point_flag"]}
For an action, we have to create a new action with a Free delivery type. This action type doesn't require any JSON parameters.
For a promotion to work, you have to assign the above condition and action to the rule.
Visualization of the rule configuration of the promotion.
For an Order value condition to activate above, for example, 499Kc, we have to set the logic operator to >= (1) and value to 499 (2). Free delivery action doesn't require any operator, or value, as it doesn't use any parameters except the ones written in the JSON.
Below, you can see how customers can see this discount in their cart (3).
Visualization of the applied promotion
 
 
 Two products for one when selected products are in the cart
One of the most often promotions used are two for one promotions. Such promotion can be easily configured using the two products for one action.
In this example, the promotion will work only when selected products are in the cart. For this, we need to create a condition with check if SKU(s) exist condition type. We are using the following JSON:
{"sku":["55794","55665","55692","55751","55724","81503"],"required_quantity":"2","consider_quantity":"TRUE"}
For an action, we have to create a two products for one action with the following JSON:
{"allowed_products":["55794","55665","55692","55751","55724","81503"]}
In order for a promotion to work, you have to assign the above condition and action to the rule.
Visualization of the rule configuration of the promotion.
For a check if SKU(s) exist condition, we have to set the logic operator to = (1) and value to TRUE (2). Two products for one action doesn't require any operator, or value, as it doesn't use any parameters except the ones written in the JSON.
Below, you can see how customers can see this discount in their cart (4).
Visualization of the applied promotion
 
 
 Third product from the list for free when selected discount code is used
This promotion allows customers to select three products from the list and one of them (usually the cheapest one) will be for free. In order to activate such promotion customers will be required to apply a discount code in the cart.
For conditions, we need a simple Discount code in cart condition. This condition doesn't use any parameters.
In order for promotion to apply 3rd product for free to a certain list of products we need a Set of products action. Set of products can be used in various different ways according to their parameters. In the case of this promotion, we need the action with the following JSON parameters:
{"allow_same_sku":"TRUE","allowed_products":["55794","55665","55692","55751","55724","81503"],"set_size":3}
In order for a promotion to work, you have to assign the above condition and action to the rule.
Visualization of the rule configuration of the promotion.
For a Discount code in cart condition to activate, we have to set the logic operator to = (1) and value to desired promotion code (2) - in this case, we will use Discountcode one. In the action field, we only have to specify a newly created action, as it doesn't require additional values.
Visualization of the applied promotion
 
 
 Additional FIDEN2 loyalty points when customer exceeds set cart value
Sometimes it is a good idea to reward customers with more FIDEN2 points whenever they spend more money on their order. In this case, it is possible to use a promotion module to automatically apply such promotion.
For this type of promotion, we require a condition that will activate an action whenever the cart value exceeds the set price point. For this, we can use Order value condition with the following JSON parameters:
{"prices":"promotion","consider_discounts":"TRUE","exclude_products":["green_point_flag"]}
In the above case promotion price of products and other promotional discounts will be counted.
For an Action, we have to use Add or multiply loyality points action. This action requires to set if we want to add or multiply by percentage the loyalty points, so we can do that like in the example below:
{"type":"amount"}
In this case, we will add a set amount of additional FIDEN2 points to the customer.
For a promotion to work, you have to assign the above condition and action to the rule.
Visualization of the rule configuration of the promotion.
For an Order value condition to activate above, for example 499Kc, we have to set the logic operator to >= (1) and value to 499 (2). Add or multiply loyality points action requires to specify the amount of points we want to add to the order. In our case as the action is set to the amount of points if we type for example 500 points, the customer will receive additional 500 FIDEN2 points with their order.

FIDEN2
Getting started
FIDEN2 is a loyalty point system, where customers can earn FIDEN2 points by purchasing products on the e-commerce platform, reviewing products, or using configurated promotions. With enough FIDEN2 points customers are able to use them to receive a one-per-order FIDEN2 voucher (1), which discounts one, selected product in the cart by a selected amount (2). When the customer has more than one of the selected products in the cart the price of the products will be reduced by the selected amount.
FIDEN2 works additionally in retail stores using physical loyalty cards thanks to the JANTAR and WINSHOP integrations, so customers are able to gain FIDEN2 points by purchasing products in the stores locally.
FIDEN2 is a system that works with four separate databases to ensure correct data flow:
TauCeti platform - Stores e-commerce customer data and handles all e-commerce orders. Ensures that customers will receive points for all their e-commerce orders and reviews.
JANTAR - Manages retail cards as well as stores customer card numbers and amount of points. sends to TauCeti platform data with the above-mentioned information.
ISAM - Manages customer personal data assigned to the cards and connects customers to the cards according to their customer data on the TauCeti platform.
WINSHOP - Manages retail transactions and point management whenever FIDEN2 points were used for a discount in the retail store. It additionally initiates retail cards whenever they are created.
All above mentioned systems work together, so we ensure that the FIDEN2 system is omnichannel, which allows customers to have multiple retail and e-commerce FIDEN2 cards and all of them will be assigned to certain customer and have the same amount of points.
Visualization of the FIDEN2 location in the cart (desktop)
Visualization of the FIDEN2 location in the cart (mobile)
Visualization of the adding of the discount through FIDEN2 functionality (desktop)
Visualization of the adding of the discount through FIDEN2 functionality (mobile)
 
Table of contents:
 FIDEN2 system settings
General
Loyalty Points
Webservices
Balance operations export
Free cards
Vouchers
Notifications
ISAM file export
FIDEN2 functions
FIDEN2 loyalty card registration
Card Balance Checking
JANTAR API parameters
ISAM Parameters
 FIDEN2 Card management
FIDEN2 search card
FIDEN2 change balance
FIDEN2 automatic balance operations
FIDEN2 assign card
FIDEN2 / Card initialize
 FIDEN2 import and export operations
Import points
Export cards
 FIDEN2 report
 Configuring the FIDEN2 promotion
 
 
 FIDEN2 system settings
All necessary tabs to configure the FIDEN2 functionality can be found in
System > System / Settings > FIDEN2 (1)
In the FIDEN2 tab, you can find the necessary settings (2). Each of them and their options are described in the chapters below.
Visualization of the FIDEN2 tab in System / settings
General
In the general tab, you can find general functions described below
Visualization of the General tab
Functionality enabled - Switch that decides if the FIDEN2 function is enabled.
Debug mode - Enables debug mode for testing purposes. NEVER use on the production environment, as this mode irreversibly anonymizes customer data.
Header icon enabled - Enables a header icon that redirects customers to the NewLoyalityClub page. The page URL can be set in Loyalty Points tab
Loyality Points
In the Loyalty Points tab, you can set values connected to loyalty points and their earnings.
Visualization of the Loyalty points tab
Amount of points for each 1Kc - Amount of points customers will receive for every currency spent on the website. For example, if customers buys 700kc worth of products, they will receive 700 FIDEN2 points.
Currency base - Low-level setting, that changes the number of points customers will receive per spent price. This value works with a mathematical operation:
( Total price / currency base ) * multipler
So, for example, changing this value to 2, and the multiplier to 1 will result in customers receiving a number of points equal to 50% of their order value.
Points Lifetime - Value, which sets the lifetime of the points in days. If this setting is set to 365 it means that points earned in 01.01.2021 will disappear from the customer's account 01.01.2022.
Info page url - URL of the page that customer is redirected to, by icon in the header.
Amount of points for review - Amount of points customers will receive per product review.
Webservices
In the webservices tab, you are able to change the WSDL URL.
Visualization of the Webservices tab
WSDL URL - Jantar service URL. This setting should be left on a default URL.
Balance operations export
In the Balance operations export, you can change the operations settings described below
Visualization of the Balance operations export tab
Delay for point gain since order placement - Delays the points that customers will receive by X days from the date of order placement.
Count of tries if export fails - The number of tries the system will try to assign FIDEN2 points to the customer before it stops the action.
Notify about failed operations - A switch that when turned on sends daily e-mails (once per day) to all local administrators and business admins with information on how many FIDEN2 operations have failed in the last export. It doesn't send e-mails to GAC accounts.
Free cards
In the Free cards tab, you can set the following option:
Visualization of the Free cards tab
Reserve size - Count of cards that will be initialized and ready for assignment to customers.
Vouchers
In the Vouchers tab, you are able to configure the values and cost of the FIDEN2 promotion.
Visualization of the Vouchers tab
Configuration - JSON field, which configures the FIDEN2 promotion visible in the cart. JSON must contain:
"name" - Visible name of the option.
"value" - How much of a currency will be discounted. For example "100.00"
"points_cost" - How many FIDEN2 points customers will lose by selecting the discount option in the cart.
"description" - description of the option. This field is not visible to the customer.
Example of the JSON:
[{"name":"150Kč","value":150.00,"points_cost":2000,"description":"Věrnostní kupon"},{"name":"400Kč","value":400.00,"points_cost":4000,"description":"Věrnostní kupon"},{"name":"700Kč","value":700.00,"points_cost":6000,"description":"Věrnostní kupon"}]
Lifetime - A lifetime in days of a coupon added to the cart. For example, if a customer adds a coupon to the cart and then leaves the website the coupon will be in the cart for another X days. After X days the coupon will get canceled and the customer will receive points back.
Notifications
The notifications tab allows configuring if customers should receive notifications regarding their FIDEN2 card.
Visualization of the Notifications tab
Send SMS after card assignment in WAITING status - Switch that decides if the customer receives an SMS message after their card receives WAITING status.
Send SMS after car assignment in ASSIGNED status - Switch that decides if the customer receives an SMS message after their card receives ASSIGNED status.
ISAM file export
The ISAM file export settings allow configuring the following option:
Visualization of the ISAM file export tab
Include agreements - The setting that decides if ISAM customer export to ISAM should include their agreements.
FIDEN2 functions
In the FIDEN2 functions tab, you can set up the basic FIDEN2 functionalities described below
Visualization of the FIDEN2 functions tab
Points enabled - Switch, which enables the FIDEN2 points functionality. With this option disabled, customers won't be able to use FIDEN2 discounts and won't earn FIDEN2 points
Customer register card enabled - Switch, which enables the creation of new FIDEN2 cards whenever a new account is created on the website. Without a FIDEN2 card, customers won't be use FIDEN2 functionalities.
Vouchers: exclude discounted products - Switch, which when enabled, excludes already discounted products from the FIDEN2 discount functionality.
Fidelite CSV files import enabled - Switch, which enables import of the Fidelite .csv file sent from ISAM.
FIDEN2 loyalty card registration
In the FIDEN2 loyalty card registration, you can turn ON/OFF an option for customers that will allow them to assign their retail FIDEN2 cards to their newly created accounts during the registration process in the mobile app.
Visualization of the FIDEN2 loyalty card registration tab
In this tab you can set up the following options:
Enable loyalty card registration on account creation form - A switch that enables the functionality. When it is turned on customers will have an additional field in the registration form in the mobile app that will allow them to type their retail FIDEN2 card number and confirm it. The selected FIDEN2 card number must have a mobile number assigned to 
it in ISAM.
Max IP address requests per hour -  API setting, which defines how many IP address requests are allowed per hour before blocking the user.
Max IP address requests per day - API setting, which defines how many IP address requests are allowed per day before blocking the user.
Max card number requests per hour - API setting, which defines how many card number requests are allowed per hour before blocking the user.
Max card number requests per day - API setting, which defines how many card number requests are allowed per day before blocking the user.
Max nonexistence card number requests per day - API setting, which defines how many nonexisting in the database card number requests are allowed per day before 
blocking the user.
Max token check requests per day - API setting, which defines how many token requests are allowed per day before blocking the user.
Max token check requests per hour - API setting, which defines how many token requests are allowed per hour before blocking the user.
 
Card Balance Checking
In the card balance checking, you can change the following option:
Visualization of the Card balance checking tab
Enabled - Disables or enables pooling checking balance for cards that needs to be checked as a result of registered Webhooks
JANTAR API parameters
In the JANTAR API parameters, you can set up the following options:
Visualization of the JANTAR API parameters tab
Country ID - ID of a country that is used in the JANTAR application.
Commercial Language ID - ID of a commercial language that is used in JANTAR.
ISAM Parameters
In the ISAM parameters, you can set up the following options:
Visualization of the ISAM parameters tab
Origine shop nb - A value that is placed in the TCtoISAM file as origine shop nb.
Export customers without address - Switch, which decides if customers should have their main address exported to ISAM.
 
 
 FIDEN2 Card management
Customers cards can be verified, and their balance can be changed in the admin panel. Whole card management is located in the Customers tab (1).
Visualization of the FIDEN2 card management location
FIDEN2 search card
You are able to search for a card by its number in the FIDEN2 / Search card tab, which is located in:
Customers > FIDEN2 / Search card
Below you will find all possible fields in the FIDEN2 / Search card tab.
Visualization of the FIDEN2 / search card page
FIDEN2 / Search card - a field where you have to type the FiDEN2 card number. Without the card number, other options won't be visible.
General information - Contain general information about selected FIDEN2 card:
Exists in FIDEN2 API - A Yes/No field that returns the value if the selected card exists in the FIDEN2 API.
Exists in e-shop database - A Yes/No field that returns the value if the selected card exists in the e-shop database.
Card type - Type of a card. There are two types:
Internet - a card that has been assigned during the account creation on the e-shop.
Retail - a card that has been created and assigned in the physical retail store.
API export status - Status of the API export
Is free? - a yes/no field that shows if the selected card is assigned to any customer or not.
Mobile (from ISAM) - Customers mobile numbers imported from ISAM.
Data from API - Contains card balance on FIDEN2 API.
Assigned customers - List of customers that have selected cards assigned to them. This field contains columns:
ID - Customer internal ID
E-mail - Customers e-mail address
Mobile - Customers mobile number
Status - Assignment status.
Cards using the same loyalty account - a list of FIDEN2 cards that assigned customers have also assigned to them.
Operations (from API) - A list of operations taken from API.
Operations (from Fidelite Operation files) - A list of operations taken from Fidelite import file provided by JANTAR.
Below you will see all fields in the Operations tabs.
Visualization of the operations tab
 Select the Show X entries(1) field to set the number of operations, displayed on one page (min 10 / max 100).
The names of the columns (2) that contain information about target operations. Each column is susceptible to sorting.
To sort the records, click on the title of the column in question.
Date - A date and hour of an operation.
Card number- The card number used in the operation
Point type - A type of points. There are two point types:
AMT - Standard points for an order. This value is also visible with a point burn
BON - Bonus points. This value was used in the past. Currently, all values are set to AMT point type.
Operation type - Type of operation. There are two operation types:
BEN - Gain points
TKB - Burn points
Points change - The number of points added, or removed from the card.
Origin - The channel from which the point transaction originated from. There are currently two origin types:
SHP - Retail stores
NET - E-commerce e-shop
Reference part 1 - A first reference number taken from JANTAR.
Reference part 2 - An second reference number taken from JANTAR.
Keypuncher -  A keypuncher value is taken from JANTAR. This value is usually constant.
Search box (3) where you can search for featured products list by their card name, reference part 1, 2 and keypuncher.
Page buttons (4), which allow users to change the page of currently viewed operations.
 
FIDEN2 change balance
You are able to manually change certain card balances in:
Customers > FIDEN2 / Change card balance
Below you will find all possible fields in the FIDEN2 / Change card balance tab.
Visualization of the FIDEN2 / Change card balance page
Card number - a field where you have to type the FiDEN2 card number. Without the card number, other options won't be available.
Balance - Current balance on the card. This field cannot be edited.
Waiting points - The current amount of points that are waiting to be assigned to the card. This field cannot be edited.
Operation type - Option that allows selection of if points should be added or removed from the current balance.
Points count - The number of points that will get added / removed.
Change reason - A reason why points have been added or removed.
Balance after change - Displays a balance after adding / removing the points. This field cannot be changed.
With all fields filled you are able to confirm the operation using the Save points operation button.
 
FIDEN2 automatic balance operations
Automatic balance operations contain all FIDEN2 automatic operations, like points gained because of the newly created order. You can access FIDEN2 automatic balance operations in:
Customers > FIDEN2 / Automatic balance operations.
Below you will find a description of all visible fields.
Visualization of the automatic balance operations page
 Select the Show X entries(1) field to set the number of balance operations, displayed on one page (min 10 / max 100).
The names of the columns (2) that contain information about target balance operations. Each column is susceptible to sorting.
To sort the records, click on the title of the column in question.
ID - An internal ID of the balance operation.
Card number - A card number associated with the selected operation.
Reference - Reference number where that operation occurred. It can be an e-shop order number, which can be entered, or a reference number for use in the retail store.
Type - Type of operation. Available types are Gain points(+) and Burn points(-).
Value change - Value by how many points get added or removed from the card.
Status - Status of the operation.
Operation time - The time when the operation occurred.
Creation time - The time when the operation was created.
Search box (4) where you can search for balance operations by their card number and reference number.
Page buttons(5), which allow users to change the page of currently viewed operations.
 
FIDEN2 assign card
You are able to assign created FIDEN2 cards to selected customers in
Customers > FIDEN2 / Assign card
Below you will find a description of all visible fields.
Visualization of the FIDEN2 / assign card page
Card number - a field where you have to type the FiDEN2 card number.
Customer - A search field for an e-shop customer. You can search for customers by their e-mail address, name, and surname or mobile number.
With both fields filled you can assign the selected FIDEN2 card to the selected customer by pressing the "I confirm data validity" button.
 
FIDEN2 / Card initialize
You are able to initialize a new FIDEN2 card number in the
Customers > FIDEN2 / Card initialize
Below you will find a description of all visible fields.
Visualization of the FIDEN2 / card initialize page
Card number - a field where you have to type the FiDEN2 card number that is not in the system and FIDEN2 API.
Card status - A status check, that shows if the selected card number is taken or not. If the number is taken by another card it cannot be initialized.
With a valid card number entered that isn't yet initiated you can create a new e-commerce FIDEN2 card using the Create card button.
 
 
 FIDEN2 import and export operations
Import points
You are able to import FIDEN2 points using the .xlsx file to the selected cards
You will find FIDEN2 points import in the:
Import/Export > Import / FIDEN2 points
Visualization of the FIDEN2 / card initialize page
In this tab you will find fields:
File - button which allows to select the .xlsx file from the computer.
Reason - Reason for a points change
Options - optional test import tick box, which will test the imported file without doing any changes to the customer points.
With all necessary fields filled, you can import the FIDEN2 points using the import file button
Visualization of the FIDEN2 points import file
 
Export cards
You are able to export all FIDEN2 cards to the .csv file in the:
Import/Export > Export / FIDEN2 cards
Visualization of the FIDEN2 / card initialize page
In the Export / FIDEN2 cards you can select a card type, and export all the cards with a selected type to the .csv file using the Export button.
Visualization of the FIDEN2 / card initialize page
The exported .csv file contains:
Card number - Customers FIDEN2 card number
Type - Type of a FIDEN2 card
Mobile (from vpm_customers) - Customers mobile number taken from ISAM.
Status - FIDEN2 card status
Customers - e-mail address assigned to the selected FIDEN2 card.
 
 
 FIDEN2 report
FIDEN2 system has its own report, where you can see statistics about the voucher and points.
You can find FIDEN 2 report in the:
Reports > FIDEN2
Visualization of the FIDEN2 / card initialize page
In the FIDEN2 report you can find four tabs:
 Generated vouchers - the amount of generated available vouchers. In this tab you can find columns with:
Overview - The type of generated FIDEN2 vouchers.
Number - The number of generated FIDEN2 vouchers.
 Already used vouchers - The number of used vouchers. In this tab you can find columns:
Overview - The type of used FIDEN2 vouchers.
Number - The number of used FIDEN2 vouchers.
 Points gains by origin (last 30 days) - The origin from which customers gained points. In this tab you can find columns:
Overview - Type of origin. Available origins are NET and SHP.
Number - Number of points gained.
Transactions - Number of transactions.
Avg Points/Transaction - Average points gained per transaction.
 VPI Points gains by status - The number of points gained by their status. In this tab you can find the following columns:
Overview - Type of gain.
Number - Number of points gained
Transactions - Number of transactions
Avg Points/Transaction - Average points gained per transaction.
 
 
 Configuring the FIDEN2 promotion
In order for a FIDEN2 system to work properly on the front end for the customers the target environment has to have configured promotion rule.
  RememberYou can find more information about the promotional module and how to configure promotions in the Promotion module introduction article.
To create a FIDEN2 promotion first you have to create a FIDEN2 condition. Condition name and description can be set to whatever fits the user as it's not visible on the front end. You can learn more about promotion module conditions in the Conditions article.
Visualization of the FIDEN2 condition
FIDEN2 condition has to be set to type Voucher in the cart. Parameters can be left empty, as FIDEN2 parameter is a default one.
With the created condition, we have to create an action for a FIDEN2 promotion. Action name can be set to whatever fits the user as it's not visible on the front end. You can learn more about promotion module actions in the Actions article.
Visualization of the FIDEN2 action
In the FIDEN2 action we have to set the type of action to Apply voucher discount. Here you can configure parameters according to your needs. Available parameters are:
use_default_excluded_list: TRUE (default) / FALSE – use the global excluded SKU list
include_payed_gifts: FALSE (default) / TRUE - apply discount also to paid gifts
exclude_products: array, f.x. ["12345","12346"] - list of SKUs that should be excluded from this discount. You can use "green_point_flag", "bestseller_flag", "limited_edition_flag", "set_flag" and "outlet_flag" as SKU which will include all SKUs with selected flag into an excluded list. F.x. ["green_point_flag", "set_flag", "01234"].
allowed_products: array, f.x. ["12345","12346"] - list of SKUs which CAN be discounted, it disabled excluded products settings (only products from this list can be discounted).
With created condition and action we can make them work together by creating a new rule. You can learn more about creating promotion module rules in the Rules article.
Visualization of the FIDEN2 rule
In the FIDEN2 rule, you have to set Start date and End date within a broad range of dates, so the promotion doesn't expire anytime soon. Please remember to also be in the Alt shops list to enable the rule in all desired altshops, which customers have access to.
It is important to set Sort order to 0, so the FIDEN2 discount will be calculated and applied before any other promotion in the system. FIDEN2 is the only promotion type that can have sort order set to 0.
In the Conditions tab select your created FIDEN2 condition and set it to = TRUE, then in the actions tab select your FIDEN2 action, which doesn't take any other input.
With a properly configured rule, you can save it using the "Save" button, and the promotion rule should work right away on an e-commerce platform allowing users to use their FIDEN2 points on products in the cart.

Discount codes
Getting started
In this article, you will learn about the discount codes. Discount codes are codes that are used by the customers in the cart on the website (1) in order to get benefits from the configured promotional rules. We distinguish two types of discount codes:
Main code - a custom-made code created by the administrator with unlimited amount of uses (unless specified otherwise in the promotional rule).
Personal code - a code assigned inside the main code with one time use. When the main code has assigned at least one personal code, the main code itself doesn't work, and only the personal codes can be distributed among customers for it to work.
  RememberImported discount codes that were imported without assigning them to the main codes are added to the public personal code pool, which can be used to add personal codes to the selected main codes. You can check the current amount of public personal codes in the Reports > personal discount codes. You can find more about assigning public personal codes in the  Personal codes chapter.
Visualization of discount code field in the cart
To open the Featured products / list view, in the admin panel, navigate to:
Promotions > Discount codes / list
All possible operations to perform on the Discount codes / list view can be done in the Filters (2), and Discount codes / list (3) tabs.
Visualization of the discount code / list
Table of contents:
 Filters section
 Discount codes / list
 Creating a new discount code
 Personal codes
Generating new personal codes
Importing of the personal codes
 Discount codes cart translations
 
 
 Filters section
The Filters section allows sorting of the discount codes in the promotion module, based on the available filters. Below you will find a description of available filters
Visualization of the filters tab in the discount codes / list module
Is active? - Featured products list activity status.
Personal code search - A tick box that allows to search for personal codes inside the main codes, when using the search functionality in discount codes / list.
After defining the above filters, select the Apply Filters button to get a list of sites according to the applied filters.  
 
 
 Discount codes / list
The Discount codes / list section allows organizing the filtered discount codes, edit them and create new ones, delete them, and search for the discount codes.
Below you will find a description of all possible actions you can perform in the discount codes / list section.
      Visualization of the discount codes / list section in the discount codes / list
 Select the Show X entries (1) field to set the number of discount codes, displayed on one page (min 10 / max 100).
The names of the columns (2) that contain information about a target discount codes. Each column is susceptible to sorting.
To sort the records, click on the title of the column in question.
ID - An internal ID of the main code.
Name - The main code name. This name can be used to apply the promotion, if the promotion is set to use a main code, unless the selected main code has a personal code assigned to it. When a main code has assigned personal codes to it by writing the main code into the promotion, it will take personal codes from that main code.
Is active? - Activity status of the main code.
Actions - List of buttons with possible actions that can be done to the desired main code:
Edit - Edit desired discount code. As editing has exactly same actions as creating the new code, you can find more about editing in the  Creating a new discount code chapter.
View - Allows to view the content of the main code without the ability to edit any fields.
Import - A button that redirects to import / export > import / discount codes. In this module, it is possible to import personal codes to the selected main code. More about importing codes can be found in the Importing of the personal codes chapter.
Delete - Deletes the main code without the ability to restore it.
Select the Add (3) button to go to the adding the new main code. You can learn more about adding of the discount codes in the  Creating a new discount code chapter.
Search box (4) where you can search for discount codes by their system name, or if the Personal code search tick box is selected in the  Filters section, it also searches for a personal codes assigned to the main codes.
Page buttons (5), which allows user to change the page of currently viewed discount codes.
 
 
 Creating a new discount code
Add button allows users to create a new main code. During the creation of the main code, you won't have access to the Personal codes tab (1). This tab can be only accessed while editing the main code. You can read more about personal codes in the  Personal codes chapter
Below, you will find a description of all possible fields that can be edited while creating a new main code.
Visualization of the adding of the featured products list
Discount code - The main code name. This name can be used to apply the promotion, if promotion is set up to use main code, unless the selected main code has a personal code assigned to it.
Mailing code - Value of the discount code. This field is exported to ISAM inside MAILING_KEY field. It can contain up to 6 characters.
Is active? - Activity status of the main code.
  RememberISAM is an external system that manages customer personal data used in the FIDEN2 system, and connects customers to the cards according to their customer data on the TauCeti platform. You can find more information about FIDEN2 functionality in FIDEN2 article.
With all necessary fields filled, you can save the changes using the save button.
 
 
 Personal codes
Personal codes are codes assigned inside the main code with one time use. When the main code has assigned at least one personal code, the main code itself doesn't work, and only the personal codes can be distributed among customers for it to work.
Below you will find a description of all possible actions you can perform in the personal codes section and available fields.
Visualization of the adding of the featured products list
In the Assign new personal code tab we can find information about main code how many personal codes are assigned to it, how many are reserved by the customers and how many of them are used. Except that we can assign personal codes from the public personal code pool by typing the quantity (1), which we want to assign and press the Assign button (2).
In the Personal codes (main code) tab, you can find:
Select the Show X entries (3) field to set the number of discount codes, displayed on one page (min 10 / max 100).
The names of the columns (4) that contain information about a target discount codes. Each column is susceptible to sorting.
To sort the records, click on the title of the column in question.
ID - An internal ID of the main code.
Discount code - The personal code value. This is a code that customer uses in the cart in order to get the promotion.
Reserved - status that shows if the selected personal code has been reserved to the customer or not. Reserved personal codes cannot be assigned to other customer.
Used on - A date when the selected personal code was used.
Customer - Customers e-mail addresses, that code is assigned to.
Select the Export (5) button to export all personal codes assigned to the selected main code.
Search box (6) where you can search for discount codes by their name.
Page buttons (7), which allows user to change the page of currently viewed discount codes.
 
Generating new personal codes
In the Generator / discount codes module, you are able to generate personal codes and download them in the .txt file.
Personal codes can be generated in a high volume in
Import / export > Generator / discount codes
Visualization of the personal code generator
In this tab, you can select:
(1) Personal codes number - Number of generated personal codes.
(2) Personal code min length - The minimum length of the generated code
(3) Personal code max length - The maximum length of the generated code
With all fields filled, you can generate the codes by pressing the Generate and export button (4). You will be able to download the .txt file with all the codes in it. These codes can be imported to the public pool of the codes, or to the specific main code. More about importing of the personal codes can be found in the Importing of the personal codes chapter.
 
Importing of the personal codes
Generated personal codes, located in the .txt file can be imported to the public pool of personal codes, or to the selected main code. You can import personal codes in the:
Import / export > Import / discount codes
Visualization of the personal code import
In the import / discount codes section, you can:
Select a .txt file to import by pressing the browse... button (1).
Select a main code to import the personal codes into (2). If this field is empty the codes will be imported to the public personal code pool.
Select the tick box to do a test import (3). Test import checks the correctness of the file without adding the selected personal codes.
By pressing the Import file button (4), you will import the .txt file.
 
 
 Discount codes cart translations
When customers adds, or tries to add a discount code to the cart he will see one of the pop-ups with a message adequate to current promotion or discount code state. The content of these pop-ups can be set in the:
System > Translations / list
  RememberYou can learn more about translations in the [UNDER CONSTRUCTION] article.
Currently, there are four pop-up messages that customer will be able to see in the cart:
Correct discount code - This pop-up will appear when promotion is active, has correct start and end dates and not used personal code. This message can be found under phrase Discount code added to cart
Visualization of the correct discount code message
 Incorrect discount code - This pop-up occurs as the promotion is not active, has a start date in the future or is inactive in the selected altshop. This message can be found under phrase Improper discount code removed from cart
Visualization of the incorrect discount code message
Inactive discount code - It occurs as the end date of the promotion is in the past, so promotion is no longer valid. This message can be found under phrase Promotion with this discount code is no longer valid
Visualization of the inactive discount code message
Used personal code - This message occurs as the given personal code has already been used and the promotion is still active. This message can be found under phrase You provided improper discount code
Visualization of the used personal code message
 
 
 

Promotion pages
Getting started
Promotion pages are easy to make and maintain pages with a list of products, where customers are able to select the desired products and add them separately to the cart on the website.
Promotion pages are usually created in order to hold categories of products that have discounts assigned in the Products / list - browsing and managing products in altshop module.
  RememberYou can learn about the promotion module in the Promotion module introduction article.
  RememberIn order for the promotion page to be visible on the website, it needs to be activated in the desired altshops. You can find more about activating the promotion pages in the Promotion pages / list - browsing and managing promotion pages in altshop module  article
   Visualization of the promotion page (desktop view)
   Visualization of the promotion page (mobile view)
To open the Promotion pages / list view, in the admin panel, navigate to:
Promotions > Promotion pages / list.
In the Actions / list view, we can find two tabs: Filters (1) and Actions / list (2)
   Visualization of the promotion pages / list section in the administrator panel
Table of contents:
 Filters section
 Promotion pages / list section
Adding a new promotion page
Editing of a promotion page
Assigning the CMS block to the promotion page
 
 
 Filters section
The Filters section allows sorting promotion pages by using the available filters.
   Visualization of the filters section in the promotion pages / list.
Is active? - Filters by the "is active?" status of the promotion page.
After defining the above filters, select the Apply Filters button to get a list of pages according to the applied filters.  
 
 
 Promotion pages / list section
The Promotion pages / list section allows organizing the filtered pages, edit them, and add the new ones.
Below you will find a description of all possible actions you can perform in the promotion pages / list section.
   Visualization of the promotion pages / list section in the promotions pages / list
 Select the Show X entries (1) field to set the number of promotion pages, displayed on one page (min 10 / max 100).
The names of the columns (2) that contain information about a target promotion page. Each column is susceptible to sorting. To sort the records, click on the title of the column.
ID - An internal ID of the promotion page.
Name - The name of the promotion page. The value is displayed on the e-commerce platform for the customer in the breadcrumb.
Is active? - Promotion page activity status.
Start date - date from which the promotion page will be visible on the e-commerce platform for the customers.
End date - date from which the promotion page will not be visible on the e-commerce platform for the customers.
Actions - List of buttons with possible actions that can be done to the desired page:
Edit - Edit desired promotion page. Editing allows editing the promotion page parameters and changing the products visible on the promotion page. You can find more about editing the promotion page in the  Editing of a promotion page chapter.
View - Allows to view the content of the promotion page without the ability to edit it.
Delete - Deletes the promotion page without the ability to restore it.
Select the Add (3) button to go to the adding the new promotion page. You can learn more about adding of the CMS blocks in the  Adding a new promotion page chapter.
Search box (4) where you can search for desired promotion page by using their name.
Page buttons (5), which allows user to change the page of the promotion pages list.
 
 
 Adding a new promotion page
Add button allows users to create a new promotion page. While creating a new promotion page, you can only set key features about the promotion page, without the ability to add or remove products. In order to add or remove products to the promotion page, you have to edit the promotion page. More about editing of the promotion pages can be found in the  Editing of a promotion page chapter.
Below, you will find a description of all possible fields that can be edited while creating a new promotion page.
   Visualization of the promotion page creation.
Name - The name of the promotion page. The value is displayed on the e-commerce platform for the customer in the breadcrumb.
Friendly URL - URL address where the promotion page is located.
Is active? - Promotion page activity status.
Start date - date from which the promotion page will be visible on the e-commerce platform.
End date - date from which promotion page will not be visible on the e-commerce platform.
Short description -  No longer supported field, as the CMS blocks have replaced it. You can find more about adding the CMS blocks to the promotion pages in the  Assigning the CMS block to the promotion page chapter.
Display colors as separate products - A switch that decides if the products with multiple colors should be displayed separately or not. This switch can only be set when creating a promotion page, and cannot be changed later.
Default product sort order - Default sort order of the products in the list. You can select:
Newest - Products will be sorted by their add date.
Customer order - Products will be sorted by their sort order in the products field. You can read more about products field in the editing of a promotion page chapter.
Meta title - Title of the page used in the metadata.
Meta keywords - Keywords for a specific promotion page used in the metadata.
Meta Description - Description of the page used in the metadata
Description - No longer supported field, as the CMS blocks have replaced it. You can find more about adding the CMS blocks to the promotion pages in the  Assigning the CMS block to the promotion page chapter.
With filled necessary fields, users can save the changes using the save button to save the changes and go back to the pages list, or save and continue button which will save the changes and redirect the user to the editing of a promotion page.
 
 
 Editing of a promotion page
As products cannot be added during the creation of the promotion page they have to be configured using the edit functionality.
Below, you will find a description of all possible fields.
   Visualization of the additional edit actions
Add product - in this tab, you can search for a single product by its SKU and add it to the promotion pages product list.
Add many products - In this tab you can add multiple products to the promotion page product list by typing their SKUs separated by comma (for example 12345,54321,55443)
Remove many products - In this tab you can remove multiple products to the promotion page product list by typing their SKUs separated by comma (for example 12345,54321,55443)
Products - A list of products that are currently assigned to the promotion page. They can be moved by using the "Drag and drop" functionality, and their order will be visible on the website when the "customer order" sort order is selected. Products that are out of stock or inactive will have corresponding information next to their name. You are able to remove the products using the remove button.
In order to save the changes, press the Save button above the add product tab.
 
 
 Assigning the CMS block to the promotion page
Promotion pages by default do not have banners - they have to be added by assigning the CMS block into a promotion page.
In order for a CMS block to be visible on a promotion page, you have to set it's title to "promotion banner {ID}" where ID is a promotion's page internal ID. For example, correctly assigned CMS blocks have names:
promotion banner 1
promotion banner 552
promotion banner 1066
As with every CMS page and CMS block, these CMS blocks contain code for both desktop and mobile banners using the responsive web design.
It is possible to add a dedicated category navigation, that is generated on all available categories from added products. Category Navigation CMS block has to be named in the following format:
promotion category navigation {ID}
Where ID is a promotion page's internal ID. For example, correctly assigned CMS blocks have names:
promotion category navigation 1
promotion category navigation 552
promotion category navigation 1066
You can find an example code used in promotion category navigation at the bottom of this article
  RememberYou can learn about the CMS blocks and their creation in the CMS blocks article.
Example promotion category navigation {ID} code:
<link href="https://cdnjs.cloudflare.com/ajax/libs/tiny-slider/2.9.3/tiny-slider.css" 
rel="stylesheet" />
<style type="text/css">.selected {
        color: #ffffff !important;
        background-color: #8b9620 !important;
    }
    .tns-outer [aria-controls],
    .tns-outer [data-action] {
      display: none;
    }
    .onglet-slider a:hover {
      color: #8c951e;
      border-color: #8c951e;
    }
    .onglet-slider a {
      box-sizing: border-box;
      text-transform: uppercase;
      text-decoration: none;
      color: #000000;
      padding: 7px 10px;
      border-radius: 25px;
      margin: 5px;
      text-align: center;
      font-size: 12px;
      line-height: 12px;
      margin: 1px 10px 0 0;
      box-shadow: 0 2px 6px 0 rgba(0, 0, 0, 0.2);
      border: solid 1px #868686;
      background-color: #ffffff;
      justify-content: center;
      align-items: center;
      display: flex;
      width: 100%;
      font-weight: bold;
      height: 40px;
    }
    @media (min-width: 780px) {
      .onglet-slider  {
        width: 100% !important;
      }
    }
    .onglet-slider {
      display: flex;
      gap: 10px;
      margin: 10px 0px;
    }
    .onglet {
      min-width: 100px;
    }
</style>
<script src="https://cdnjs.cloudflare.com/ajax/libs/tiny-slider/2.9.2/min/tiny-slider.js">
</script><script>
    var slider = tns({
        container: '.onglet-slider',
        navAsThumbnails: false,
        "edgePadding": 15,
        "swipeAngle": false,
        slideBy: 1,
        "mouseDrag": true,
        autoplay: false,
        gutter: 1,
        nav: true,
        items: 3,
        center: false,
        loop: false,
        responsive: {
            480:{
              items: 5,
              loop: true
            },
            640:{
              "edgePadding": 25,
              loop: true
            },
            780:{
              items: 7
            },
            1024:{
              items: 10
            }
        }
    });
</script>

Actions
Getting started
From this article, you will learn about promotion module actions. Actions are promotions that are applied to the products after selected conditions in the action are met.
  RememberYou can learn about the promotion module in the Promotion module introduction article.
To open the Actions / list view, in the admin panel, navigate to:
Promotions > Actions / list.
In the Actions / list view, we can find two tabs: Filters (1) and Actions / list (2)
  Visualization of the actions / list module in the administrator panel
Table of contents:
Filters section.
Actions list section.
Adding a new action.
Action types.
Discount from order value
Discount the cheapest product
Discount the most expensive product
Gift 
Gift of choice
Payed gift
Free delivery
Free payment
Show rule description
Two products for one 
Enrollment set
Product as gift 
Prima port discount 
Apply voucher discount 
Add or multiply loyalty points 
Set of products
Product value multiplication
Product value multiplication - most expensive
Product value multiplication - cheapest
 
 
 Filters section
The Filters section allows sorting of the actions in the promotion module, based on the available filters. Below you will find a description of each filter.
Visualization of the filters tab in the actions / list
Is active? -  Defines the activity date of the visible list of actions.
Type - Type of the action. More about rule types can be found in the  Action types chapter.
After defining the above filters, select the Apply Filters button to get a list of actions according to the applied filters.  
 
 
 Actions list section
The Actions list section allows organizing the filtered actions, as well as editing, duplicating and deleting the desired actions.
Below you will find a description of all possible actions you can perform in the actions list section.
Visualization of the Actions / list tab in the Actions / list.
 Select the Show X entries(1) field to set the number of actions, displayed on one page (min 10 / max 100).
The names of the columns (2) that contain information about target actions. Each column is susceptible to sorting. To sort the records, click on the title of the column in question.
ID - Internal ID of the action.
Type - Type of the action. You can read more about types in the  Action types chapter.
Name - Name of the action.
Is active? - Activity status of the action.
Actions - List of buttons with possible actions that can be done to the desired action:
Edit - Edit desired action. Editing has exactly the same actions as adding a new action, so the list of actions can be looked up at  Adding a new action chapter.
Duplicate - Duplicates the actions with all its properties and content.
View - Allows to view the content of the action without the ability to edit any fields in it.
Delete - Deletes the action without the ability to restore it.
Select the Add (3) button to go to the adding the action. You can learn how to add an action in the  Adding a new action chapter.
Search box (4) where you can search for the desired action by its name.
Page buttons (5), which allows user to change the page of currently viewed actions.
 
 
 Adding a new action
Add button allows users to create a new promotion action, which can be configured and prepared for very specific needs.
Below, you will find a description of all possible actions you can perform.
Visualization of the adding of the new action.
Type - Type of the action. You can see more about action types in the  Action types chapter
Name - Internal name of the promotion action.
Description - Description of the promotion action. This field is visible to the customer if the action "Show description" is assigned to the action.
Parameters - JSON code used for parametrization of the action.
Is active? - Activity status of the action.
  RememberYou can learn about promotion conditions in the Conditions article.
  RememberYou can learn about promotion rules in the Rules article.
 
 
 Action types
The type of action defines what activity will apply to the products when the condition is met.
 
Discount from order value
Discounts entire order using percentage or amount.
Parameters:
base_prices - promotion (default) / catalog - which prices should be affected by discount.
type: percentage (default) / amount - the value of the discount is percentage or amount to remove from order value?
use_default_excluded_list: TRUE (default) / FALSE - use global SKUs that have been excluded globally in Promotions > Products excluded from promotion (global) 
include_payed_gifts: FALSE (default) / TRUE - apply discount also to paid gifts
exclude_products: array, f.x. ["12345","12346"] - list of SKUs that should be excluded from this discount. You can use "green_point_flag", "bestseller_flag", "limited_edition_flag", "set_flag" and "outlet_flag" as SKUs which will include all SKUs with selected flags in excluded list. F.x. ["green_point_flag", "set_flag", "01234"].
allowed_products: array, f.x. ["12345","12346"] - list of SKUs which CAN be discounted, it disabled excluded products settings (only products from this list can be discounted)
required_quantity: "all" (default) / any number - number of SKUs from list which has to be present in the order, "all" means all SKUs from list has to be present
multiplier_sku_list: array, e.g. ["12345","12346"] - list of SKUs which quantities should be summed; result number will multiply discount value
multiple: FALSE (default) / TRUE - if discount value will be multiplied
JSON example:
{"type":"amount","base_prices":"promotion","allowed_products":["J0322","J0323","J0324","J0325","J0326","J0327"],"use_default_excluded_list":"FALSE","required_quantity":3}
 
Discount the cheapest product
Discounts only the cheapest products in the cart. In case there are two cheapest products in the cart with exactly the same price the promotion module chooses the first one on the list.
Parameters:
type: percentage (default) / amount - the value of the discount is percentage or
amount to remove from order value?
prices: "promotion" (default) or "catalog" (use one of the values) - define which
product price (catalog or promotion) is to be granted a discount
use_default_excluded_list: TRUE (default) / FALSE - use global SKUs that have been excluded globally in Promotions > Products excluded from promotion (global)
exclude_products: array, f.x. ["12345","12346"] - list of SKUs which should be
excluded from this discount
allowed_products: array, f.x. ["12345","12346"] - list of SKUs which CAN be
discounted, it disabled excluded products settings (only products from this list
can be discounted)
quantity_limit (default 1): integer - quantity which should be discounted. It can
be 3 of 5 pieces of the cheapest product or 3 cheapest products (every with
1pcs) depending on the cart.
JSON example:
{"type":"percentage", "prices":"promotion","exclude_products":["I1695","I1696","BB003","BB004","BB005","BB006","BB008","BB007"],"quantity_limit":2}
 
Discount the most expensive product
Discounts for the most expensive single or multiple products are currently added to the cart. In case there are two most expensive products in the cart with exactly the same price the promotion module chooses the first one on the list.
Parameters:
type: percentage (default) / amount - the value of the discount is percentage or amount to remove from order value?
prices: "promotion" (default) or "catalog" (use one of the values) - define which product price (catalog or promotion) is to be granted a discount
use_default_excluded_list: TRUE (default) / FALSE - use global SKUs that have been excluded globally in Promotions > Products excluded from promotion (global)
exclude_products: array, f.x. ["12345","12346"] - list of SKUs which should be excluded from this discount
allowed_products: array, f.x. ["12345","12346"] - list of SKUs which CAN be discounted, it disabled excluded products settings (only products from this list can be discounted)
quantity_limit (default 1): integer - quantity which should be discounted. It can be 3 of 5 pieces of the most expensive product or 3 most expensive products (every with 1pcs) depending on the cart.
JSON example:
{"type":"percentage", "prices":"catalog","exclude_products":["BB012","BB011","I1695","I1696","BB003","BB004","BB005","BB006","BB008","BB007"]}
 
Gift 
Adds gift to the cart. Product that will be added to the cart must have the GIFT flag
activated. If the product has at the same time activated GIFT and GIFT OF CHOICE flags
product won’t be visible.
This action doesn’t have any parameters. The price of the gift is taken from the product price.
You can find more about product flags in the [Under construction] article
 
Gift of choice
Adds to the cart the list of the gifts, that customers can choose one from.
Those gifts must have GIFT and GIFT OF CHOICE flags. The price of the gift of choice is
taken from the product price.
Parameters:
sku_list: array, e.g. ["12345","12346"] - list of gifts SKUs (they have to be gifts). The list may also contain SKU "EMPTYGIFT", which allows the configuration of variants: gift or discount.
min_cart_value_for_description: float (default: 0.00) - minimum cart value to activate these gifts, used to inform the customer and to group gifts of choice to one set (box)
condition_description: string (default: "") - condition description used instead of minimum cart value information
show_inactive: 0|1 (default: 0) - show inactive gifts group in cart
multiplier_sku_list: array, e.g. ["12345","12346"] - list of SKUs which quantities should be summed; result number will multiply this list of choice
multiplier_divider: integer (default: 1) - divider used in calculation of how many lists should be presented, result number is always rounded down
empty_gift_description: if in sku_list there is a gift that is not available in the catalog anymore (i.e. got removed, wrong SKU number was typed) this description will be displayed instead of the product.
empty_gift_picture: if in sku_list there is a gift that is not available in the catalog anymore (i.e. got removed, wrong SKU number was typed) this picture will be displayed
instead of the product.
show_missing_amount_when_active_is_rule: RULE_ID - the rule will be visible (without the option to select, with the missing amount to be achieved) when the RULE_ID rule is active. For example show_missing_amount_when_active_is_rule: 6 will result in a GOC promotion to be grayed out when promotion rule 6 is active when the promotion itself is not active yet.
sku_list_stock_track_: QUANTITY - quantity of products from sku_list below which warning email about low stock should be sent (if service of informing about stock levels of promotional products is enabled). This functionality needs to be enabled and e-mail address has to be set in System > System / Settings > Admin > Promotion stock warning. Stock values are set in System > System / Settings > E-commerce > Stocks.
fallback_sku_list : array - array with list of SKUs that will be used as fallback when product from sku_list is not available. Products from fallback list are not associated with specific products from sku_list, they will be used in order they are on the list and in quantity corresponding to quantity of products from sku_list, which stock level dropped to 0.
JSON example:
{"sku_list": ["F06881","F94615","F44972","250PT","NOGIFT"],"min_cart_value_for_description":"290"}
 
Payed gift
Shows in the cart product that can be optionally bought by the customer usually in the promotional price (1). The price of the payed gift is taken from the product price.
Parameters:
sku_list: array, e.g. ["12345","12346"] - list of gifts SKUs
min_cart_value_for_description: float (default: 0.00) - minimum cart value to activate these gifts, used to inform the customer
condition_description: string (default: "") - condition description used instead of minimum cart value information
JSON example:
{"sku_list": ["OI0811"],"min_cart_value_for_description":"899.00"}
  Visualization of the payed gift in the cart
 
Free delivery
Makes that every delivery option is free of charge. This action doesn’t have any parameters.
 
Free payment
Makes that every payment option is free of charge. This action doesn’t have any parameters.
 
Show rule description
Shows the description of the promotion from rules / list in the cart (2).
Visualization of the show rule description action.
  RememberYou can learn about promotion rules in the Rules article.
 
Two products for one 
Takes the product from the allowed_products parameter, and if it is in the cart, adds another same product, but for free
Parameters:
use_default_excluded_list: TRUE (default) / FALSE - use global SKUs that have been excluded globally in Promotions > Products excluded from promotion (global)
exclude_products: array, f.x. ["12345","12346"] - list of SKUs that should be excluded from
this discount
allowed_products: array, f.x. ["12345","12346"] - list of SKUs which CAN be discounted, it disabled excluded products settings (only products from this list can be discounted)
catalog_price: TRUE / FALSE (default) - set catalog price for main product
limit: 0 (default) - limit of actions per cart
cheapest: TRUE / FALSE (default) - priority actions from the cheapest product
JSON example:
{"catalog_price":"TRUE","exclude_products":["green_point_flag","set_flag"],"limit":"50"}
 
Enrollment set
Exact same functionality as Gift of Choice, but with bigger product images. Adds a list of products that customers can choose one.
Parameters:
sku_list: array, e.g. ["12345","12346"] - list of gifts SKUs (they have to be gifts)
must_to_buy: TRUE (default) | FALSE - one product must be purchased
min_cart_value_for_description: float (default: 0.00) - minimum cart value to activate these gifts, used to inform the customer and to group gifts of choice to one set (box)
condition_description: string (default: "") - condition description used instead of minimum cart value information
JSON example:
{"sku_list": ["P26885","P27300","P27714","P28172"],"must_to_buy": "TRUE"}
 
Product as gift 
Creates the button with text from the “text” parameter and puts it in the product catalog right next to the “add to cart” button. With this button, customers can buy selected products from the “sku_list” parameter in the promotional price from the “price” parameter.
  Warning    Only one action of this type should exist in the altshop. Having more than one product as gift action active in the same altshop may result in unexpected behaviour.   
Parameters:
sku_list: array, e.g. ["12345","12346"] - list of product SKUs that can be chosen as a gift
limit: integer (default: 1) - how many products can be chosen as a gift
price: float (default: 0.00) - the price of gift added to cart
text: string (default: "Choose as gift") - text on a button
JSON example:
{ "sku_list" : ["36454","87816","77108","37086","26091","20410","87476","27899","70215","66318","05006","84299",],"limit":"1", "price" : "0", "text" : "Vybrat jako dárek"}
 
Prima port discount 
This type of action is no longer supported since the Prima port is no longer used.
 
Apply voucher discount 
Applies the FIDEN2 Voucher to the product. This functionality only works when FIDEN2 functionality is turned on in system / settings. You can learn more about FIDEN2 in the FIDEN2 article.
Parameters:
use_default_excluded_list: TRUE (default) / FALSE – use global SKUs that have been excluded globally in Promotions > Products excluded from promotion (global)
include_payed_gifts: FALSE (default) / TRUE - apply discount also to payed gifts
exclude_products: array, f.x. ["12345","12346"] - list of SKUs that should be excluded from this discount. You can use "green_point_flag", "bestseller_flag", "limited_edition_flag", "set_flag" and "outlet_flag" as SKUs which will include all SKUs with selected flags in the excluded list. F.x. ["green_point_flag", "set_flag", "01234"].
allowed_products: array, f.x. ["12345","12346"] - list of SKUs which CAN be discounted, it disabled excluded products settings (only products from this list can be discounted)
JSON example:
{"exclude_products":["85949","set_flag"]}
 
Add or multiply loyalty points 
Replaces the amount of points per product set in FIDEN2 system / settings with the new value. You can learn more about FIDEN2 in the FIDEN2 article.
Parameters:
type: "amount" (default) / "percentage" - add points by the amount or multiply by the selected percentage
JSON example:
{"type":"percentage"}
 
Set of products
Allows to create sets of products. In those sets, it can be set that if for example, we have three products from the “allowed product” parameter the third product will be for free as a gift or for reduced price. It is possible to set "set_size" and "discounted_amount" to the same value, so every product in the set will be discounted to the "discounted_price" value.
Parameters:
prices: "promotion" (default) or "catalog" (use one of values) - define which product price (catalog or promotion) is to be granted a discount
discounted_price (default "0.01"): string - discounted product price
allow_same_sku: FALSE (default) / TRUE - allow to create pair of products with the same SKU
sticker (default none): string - cms block name
quantity_limit (default 999): integer - max sets that can be created by the customer within the promotion in the cart.
exclude_products: array, f.x. ["12345","12346"] - list of SKUs that should be excluded from this discount. You can use "green_point_flag", "bestseller_flag", "limited_edition_flag", "set_flag" and "outlet_flag" as SKUs which will include all SKUs with selected flags into the excluded list. F.x. ["green_point_flag", "set_flag", "01234"].
allowed_products: array, f.x. ["12345","12346"] - list of SKUs which CAN be discounted, it disabled excluded products settings (only products from this list can be discounted)
include_payed_gifts: FALSE (default) / TRUE - apply discount also to payed gifts
use_default_excluded_list: TRUE (default) / FALSE - use global SKUs that have been excluded globally in Promotions > Products excluded from promotion (global)
set_size (default 2): integer - The size of the set
discounted_amount (default 1): integer - The amount of products that will be discounted when the set is created.
cmsblock (default ''): optional title of cms block with the content of promotion
description pop-up
JSON example:
{"prices":"catalog","discounted_price":"75","allow_same_sku":"TRUE","quantity_limit":"1","allowed_products":["76938","92335","62967","60160","61731"],"cmsblock":"shampoo_desc"}
 
Product value multiplication
Product value multiplication discounts the product according to a multiplication of its current catalog or promotional price i.e. if the multiplication is set to 10 and discount to 2 euro, the promotion will discount 2 euro for every 10 euro in the product, so a product that costs 50 euro will have 10 euro of discount.
Parameters:
multiplication_value: value from which multiplication discount will be calculated
every_sku_separately: TRUE/ FALSE (default) - value defines if the discount should be calculated separately for every SKU or summed up from all allowed SKUs
prices: "promotion" (default) or "catalog" (use one of values) - define which product price (catalog or promotion) is to be granted a discount
use_default_excluded_list: TRUE (default) / FALSE - use global SKUs that have been excluded globally in Promotions > Products excluded from promotion (global)
exclude_products: array, f.x. ["12345","12346"] - list of SKUs that should be excluded from this discount. You can use "green_point_flag", "bestseller_flag", "limited_edition_flag", and "set_flag" as SKUs which will include all SKUs with selected flags into the excluded list. F.x. ["green_point_flag", "set_flag", "01234"].
allowed_products: array, f.x. ["12345","12346"] - list of SKUs which CAN be discounted, it disabled excluded products settings (only products from this list can be discounted)
JSON example:
{"multiplication_value":10,"prices":"catalog","allowed_products":[""36454","87816","77108","37086","26091","20410"]}
 
Product value multiplication - most expensive
Product value multiplication discounts the most expensive product according to the multiplication of its current catalog or promotional price i.e. if the multiplication is set to 10 and discount to 2 euro, the promotion will discount2 euro for every 10 euro in the product, so a product that costs 50 euro will have 10 euro of discount.
Parameters:
multiplication_value: value from which multiplication discount will be calculated
prices: "promotion" (default) or "catalog" (use one of values) - define which product price (catalog or promotion) is to be granted a discount
use_default_excluded_list: TRUE (default) / FALSE - use global SKUs that have been excluded globally in Promotions > Products excluded from promotion (global)
exclude_products: array, f.x. ["12345","12346"] - list of SKUs that should be excluded from this discount. You can use "green_point_flag", "bestseller_flag", "limited_edition_flag", "set_flag" as SKU which will include all SKUs with selected flags into the excluded list. F.x. ["green_point_flag", "set_flag", "01234"].
allowed_products: array, f.x. ["12345","12346"] - list of SKU which CAN be discounted, it disabled excluded products settings (only products from this list can be discounted)
JSON example:
{"multiplication_value":10,"prices":"catalog","allowed_products":[""36454","87816","77108","37086","26091","20410"]}
 
Product value multiplication - cheapest
Product value multiplication discounts the cheapest product according to a multiplication of its current catalog or promotional price i.e. if the multiplication is set to 10 and discount to 2 euro, the promotion will discount 2 euro for every 10 euro in the product, so a product that costs 50 euro will have 10 euro of discount.
Parameters:
multiplication_value: value from which multiplication discount will be calculated
prices: "promotion" (default) or "catalog" (use one of values) - define which product price (catalog or promotion) is to be granted a discount
use_default_excluded_list: TRUE (default) / FALSE - use global SKUs that have been excluded globally in Promotions > Products excluded from promotion (global)
exclude_products: array, f.x. ["12345","12346"] - list of SKUs that should be excluded from this discount. You can use "green_point_flag", "bestseller_flag", "limited_edition_flag", "set_flag" as SKU which will include all SKUs with selected flags into the excluded list. F.x. ["green_point_flag", "set_flag", "01234"].
allowed_products: array, f.x. ["12345","12346"] - list of SKUs which CAN be discounted, it disabled excluded products settings (only products from this list can be discounted)
JSON example:
{"multiplication_value":10,"prices":"catalog","allowed_products":[""36454","87816","77108","37086","26091","20410"]}

Rules
Getting started
From this article, you will learn about promotion module rules. Rules are whole promotions that contain in themselves conditions and actions and make them work together in selected altshops and date ranges. They are essential parts for a promotion to work.
  RememberYou can learn about the promotion module in the Promotion module introduction article.
To open the Rules / list view, in the admin panel, navigate to:
Promotions > Rules / list.
In the Rules / list view, we can find two tabs: Filters (1) and Rules / list (2)
  Visualization of the rules / list module in the administrator panel
Table of contents:
Filters section
Rules list section
Adding a new rule
 
 
 Filters section
The Filters section allows sorting of the rules in the promotion module, based on the available filters. Below you will find a description of each filter.
Visualization of the filters tab in the rules / list
Is active? -  Defines the activity date of the visible list of rules. By default, "Yes" is selected.
Alt shop - Defines to which alt shop, you want to limit the list of rules.
After defining the above filters, select the Apply Filters button to get a list of rules according to the applied filters.  
 
 
 Rules list section
The Rules list section allows organizing the filtered rules, as well as editing, duplicating, and deleting the desired rules.
Below you will find a description of all possible actions you can perform in the rules list section.
Visualization of the Rules / list tab in the Rules / list.
 Select the Show X entries(1) field to set the number of rules, displayed on one page (min 10 / max 100).
The names of the columns (2) that contain information about target rules. Each column is susceptible to sorting. To sort the records, click on the title of the column in question.
ID - Internal ID of the rule.
Name - Name of the rule.
Start / end date - Range of dates where the rule is active.
Is active? - Activity status of the rule.
Sort order - Sort order of the rule. Sort order defines the order in which the rules will be applied in the customer cart, starting from 1.
Actions - List of buttons with possible actions that can be done to the desired rule:
Edit - Edit desired rule. Editing has exactly the same actions as adding a new rule, so the list of actions can be looked up in Adding a new rule chapter.
Duplicate - Duplicates the rules with all their properties and content. By default, duplicates are inactive.
View - Allows to view the content of the rule without the ability to edit any fields in it.
Delete - Deletes the rule without the ability to restore it
Select the Deactivate expired rules button (3) to set the is active? status on all the rules that have start / end date range outside the current date.
Select the Add list (4) button to go to the adding the rule. You can learn how to add a rule in the  Adding a new rule chapter.
Search box (5) where you can search for desired rule by its name.
Page buttons (6), which allows user to change the page of currently viewed rules.
 
 
 Adding a new rule
Add button allows users to create a new promotion rule, which can be configured to very specific needs.
Below, you will find a description of all possible actions you can perform while creating a new rule.
Visualization of the adding of the new rule.
Name - Internal name of the promotion rule.
Rule code - Value that is visible in the API. This value doesn't change anything, how the selected rule works on the website.
JOY club member discount percentage - Value sent to JOY at the order line level. This value doesn't change anything, how the selected rule works on the website.
Description - Description of the promotion rule. This field is visible to the customer if the action "Show description" is assigned to the rule.
Rule type -  Type of the rule. There are two types to choose from:
Standard - standard rule type that doesn't make any specific changes. This is the default type that should be used in most cases.
ETD - is used for backward analytics of ETD (End of ticket discount) discounts and how many of them were added. Selecting this type requires JOY club member discount percentage to be filled.
Start / end date -  Range of dates where the rule is active.
Is active? - Activity status of the rule.
Sort order - Sort order of the rule. Sort order defines the order in which the rules will be applied in the customer cart, starting from 1.
Altshops - List of altshops where the rule will be active. You can assign the altshop by selecting them from the list on the left side, and pressing the arrow buttons. The double arrow button will move all the altshops
Conditions - In the conditions field you can assign created conditions to the rule, assign operators to them, and the values. It is possible to change the order of the conditions using the arrows on the left side of the condition. Additionally, you are able to create a new condition from this window using the "Create new condition" button (1) and edit existing, selected conditions using the "Edit" button (2) next to the desired condition.
At the bottom of the conditions list you will find brackets and logic connectors. They can be used to create more complicated promotions
Brackets - Brackets can be used with logic connectors to separate certain conditions, and run them together. For example, conditions can look like: X or {Z and Y}, where X condition will run the promotion OR combination of Z AND Y.
Logic connectors - Logic connectors allow you to create complicated promotions where multiple conditions must be fulfilled by using AND connector, or to select that the rule will be activated by multiple, independent conditions using the OR connector.
Actions -  In the actions field, you can select multiple actions from the list of available ones. Actions will run, whenever selected conditions are met. You are additionally able to create a new action from this window using the "Create new action" button (3) and edit existing, selected action using the "Edit" button (4) next to the desired action.
Visualization of the condition creating window
Visualization of the action editing window
  RememberYou can learn about promotion conditions in the Conditions article.
  RememberYou can learn about promotion actions in the Actions article.
In the example below, you can see a promotion with:
Conditions that need to be fulfilled: Order value (catalog price) more or equal 50 euro OR 
{ Discount code in basket = CODE AND Order items count more or equal 2 }.
If the conditions are met, the customer will receive 50 euro discount on the most expensive product and 25% discount on the cheapest one.
Visualization of the example promotion rule configuration
 

Conditions
Getting started
This article will teach you about conditions, their types, and how to configure them. Conditions are used to determine whether a customer is eligible to get a promotion.
Conditions can be found in the
Promotions > Conditions / list
At the Conditions / list window Filters (1) can be found which will help search for a specific type of conditions, and the list of Conditions (2) itself, which allows for searching conditions by name, editing, deleting, and adding new ones. 
Visualization of the Promotions, Conditions / list
 
  RememberConditions and Actions are integral to Promotion Rules. All three can't be used individually. You can learn more about actions and rules in the Actions and Rules articles
Table of contents:
Conditions / list
Filters
Conditions
Creating new condition
Condition types
Discount code in cart
Discount code is empty in cart
Order value
Check if SKU(s) exist
Active alt shop
Sum of quantities from SKU list
Prima port ID in cart
Count of orders
Days from last order
Voucher in cart
Empty gift of choice in the cart
Delivery method
Payment method
Customer title
Regular account
Order items count
Promotion rules active in cart
 
 Conditions / list
Filters
Filters are the first tab in Conditions / list. It is used to narrow the results in the Conditions list.
(1) Is active? - Shows only active or inactive conditions.
(2) Type - Shows only active or inactive conditions.
(3) Two buttons:
Apply filters - Applies chosen filters to Conditions
Clear filters - Clears chosen filters and refreshes Conditions
Visualization of Filters, Conditions / list
 
Conditions
The conditions list is the main tab in this module. Here new conditions can be added (1), bellow there is a search field (2) that will filter out conditions names to typed letters. The table list itself (3) contains several columns, these are:
ID - The number given after the creation of the condition, it cannot be changed. Used only for database listing.
Type - Type of condition that determines its behavior (more about types in this section[LINK])
Name - Name of the condition, used as the main identification. Its name is used for rules and in the search bar.
Is active? - Mark that shows whether a condition is active or inactive
Actions - Four buttons:
Edit - Edit condition, its name, description, whether it's active, and parameters.
Duplicate - Duplicates condition with exact same parameters, the name will be edited by gaining (copy) as a suffix and changing its activation status to inactive.
Show - Shows details of the condition without permission to edit.
Delete - Erase condition, it won't be recoverable.
Visualization of Filters, Conditions / list
 
 Creating new condition
The condition has three fixed options that will stay the same (1), these are:
Name - Name of the condition, used as the main identification. Its name is used for rules and in the search bar. 
Description - Description serves as an additional source of information about the condition and its mechanics
Is active? - ON/OFF - switch to turn the condition active or inactive.
There are also two (2) configurable options that determine its behavior, these are:
Type - Determines the main target of verification. Types are:
Discount code in cart (link do każdego, scrollujący do danego typu)
Discount code is empty in cart
Order value
Check if SKU(s) exist
Active alt shop
Sum of quantities from SKU list
Prima port ID in cart
Count of orders
Days from last order
Voucher in the cart
Empty gift of choice in the cart
Delivery method
Payment method
Customer title
Regular account
Order items count
Promotion rules active in cart
Parameters - JSON code used for parametrization of the condition.
Visualization of Filters, Conditions / list
 
  RememberJSON is a light-weighted format to exchange data. More about this format you can learn from here.
 
 Condition types
The type of condition defines what it's supposed to look for when calculating cart items and values. Here are described all types of conditions and their parameters
 
Discount code in cart
This condition checks if there is a discount code in the cart (more about discount codes can be found in the Discount codes article).
Parameters:
None
Logic operators:
=
!=
Logic values:
Discount code name
  Remember
Since this condition type is so general and lacks any parameters. There is usually one of this type in the environment.
 
Discount code is empty in cart
This condition checks if there isn't a discount code in the cart.
Parameters:
Discount code name - it is not used in the condition itself since adding this type of condition to the rule will require naming it.
Logic operators:
=
!=
Logic values:
TRUE
FALSE
  RememberSince this condition type is so general and lacks any parameters. There is usually one of this type in the environment.
 
Order value
This condition checks the current cart value.
Parameters:
prices:
promotion - used by default, counts the value of products by promotion prices
catalog - counts values of products by their standard prices 
consider_discounts:
FALSE - used by default, counts the value before all discounts
TRUE - calculate order value after all discounts
use_default_excluded_list:
TRUE - used by default, uses global excluded SKU list
FALSE - excluded SKUs will also be counted toward the cart value
include_payed_gifts:
TRUE - consider the value of payed gifts
FALSE - used by default, do not count payed gifts
include_opensets:
TRUE - opensets count into the cart value
FALSE - used by default, do not count value of opensets
exclude_products:
Array - SKU numbers, these will be excluded from the order value. This parameter is above and will exclude products regardless of use_default_excluded_list parameter.
exclude_fid_discounted_products:
TRUE - Products discounted by the fidelity program will not be counted.
FALSE - used by default, do not count value of products discounted by fidelity points
Logic operators:
=
!=
>
<
>=
<=
Logic values:
Number - cart value
Example:
{"prices":"catalog","consider_discounts":"TRUE","exclude_products":["12345","54321"]}
 
Check if SKU(s) exist
This condition checks if the product SKUs from the selected array are present in the cart.
Parameters:
SKU:
Array - SKU numbers, without this parameter the condition won't work.
required_quantity:
all - All SKUs from the SKU parameter have to be present in the cart
number - Number of SKUs from the SKU parameter that has to be present.
consider_quantity:
TRUE - The number of pieces counts towards the SKU parameter (for example if the SKU parameter has 3 SKU's in the list then one of these SKU's added 3 times to the cart will return TRUE value in the promotion rule)
FALSE - Used by default, doesn't count the number of pieces
Logic operators:
=
!=
Logic values:
TRUE
FALSE
Example:
{"SKU":["12345","54321"],"required_quantity":"5"}
 
Active alt shop
This condition checks the altshop. This type is deprecated and unused. Promotion rules already are able to filter altshops.
 
Sum of quantities from SKU list
This type sums up all pieces from the SKU list set in the parameters.
Parameters:
SKU:
Array - SKU numbers, without this parameter the condition won't work.
Logic operators:
=
!=
>
<
>=
<=
Logic values:
Number - Quantity of products
Example:
{"SKU":["54321","12345"]}
 
Prima port ID in cart
This type of condition is no longer supported since Prima port is no longer used.
 
Count of orders
This type count the number of orders in the customer account.
Parameters:
orders:
all - All orders from the customer account will be counted (still regulated by the rest of the parameters)
all_mc - All orders are counted but since the date of gaining a title. You can learn more about customer titles in the Campaigns and titles article.
current_title - Orders are counted since the date of gaining the current customer title.
active_rule - Orders are counted only if they used certain promotion rules (list from parameter rule id)
campaigns:
Array - List of campaigns short names (more about campaigns in this article [UNDER CONSTRUCTION]
date_from:
date - The format for the date is YYYY-MM-DD (for example 2018-12-31). Orders will be counted from this date onwards.
date_to:
date - The format for the date is YYYY-MM-DD (for example 2018-12-31). Counted will be orders placed only before this date.
titles:
Array - List of title short names. Orders will be counted only if they were placed while the customer had these titles. Only used when parameter "orders":"current_title"
rule_id:
Array - List of Rules id's. This parameter only works with "orders":"active_rule"
only_paid:
TRUE - Only COD or fully paid orders are counted.
FALSE - Orders with pending payment are also counted
altshop_id:
id of altshop only from which orders are considered. The parameter value can only be one altshop/one ID. You can't use an array of altshop ID's. 
Syntax example:
{"altshop_id":"122"}
Logic operators:
=
!=
>
<
>=
<=
Logic values:
Number - Orders
Example:
{"orders":"all_mc","campaigns":["Campaign1","Campaign2"],"date_from":"2023-01-12","date_to":"2023-02-22"}
 
Days from last order
This condition count passed days from the last order.
Parameters:
orders:
all - All orders from the customer account will be counted (still regulated by the rest of the parameters)
all_mc - All orders are counted but since the date of gaining a title. You can learn more about customer titles in the Campaigns and titles article.
current_title - Orders are counted since the date of gaining the current customer title.
active_rule - Orders are counted only if they used certain promotion rules (list from parameter rule id)
campaigns:
Array - List of campaigns short names (more about campaigns in this article [UNDER CONSTRUCTION]
date_from:
date - The format for the date is YYYY-MM-DD (for example 2018-12-31). Orders will be counted from this date onwards.
date_to:
date - The format for the date is YYYY-MM-DD (for example 2018-12-31). Counted will be orders placed only before this date.
Logic operators:
=
!=
>
<
>=
<=
Logic values:
Number - Orders
Example:
{"orders":"all_mc","campaigns":["Campaign1","Campaign2"],"date_from":"2023-01-12","date_to":"2023-02-22"}
  Warning    If there are no order-matching rules defined by parameters, the condition will return 999 days. We strongly recommend pairing this condition with "Count of closed orders > 0"   
 
Voucher in the cart
This condition verifies whether there is applied promotion code in the cart.
Parameters:
type:
1 - Fiden2 code, this type is set as default.
2 - Promotion code from Promotions > Discount codes / list. You can learn more about discount codes in the Discount codes article.
Logic operators:
=
!=
Logic values:
TRUE
FALSE
Example:
{"type":"2"}
 
Empty gift of choice in cart
This condition will check if the customer chooses a certain, empty gift from the Gift of choice action type. You can learn more about actions in the Actions article.
Parameters:
rule_id:
1 - Fiden2 code, this type is set as default.
2 - Promotion code from Promotions > Discount codes / list (More about codes in this article[UNDER CONSTRUCTION])
Logic operators:
=
!=
Logic values:
TRUE
FALSE
Example:
{"rule_id":"2"}
 
Delivery method
This type checks chosen delivery method.
Parameters:
name:
Array - List of delivery method names.
Logic operators:
=
!=
Logic values:
TRUE
FALSE
Example:
{"name":["Delivery1","Delivery2"]}
 
Payment method
This type checks chosen payment method.
Parameters:
name:
Array - List of delivery method names.
Logic operators:
=
!=
Logic values:
TRUE
FALSE
Example:
{"name":["Payment1","Payment2"]}
 
Customer title
This type checks current customer title.
Parameters:
include_title:
Array - List of shortcut title names that will count into the TRUE value during calculation.
exclude_title:
Array - List of shortcut title names that will count into the FALSE value during calculation.
Logic operators:
=
!=
 
Logic values:
TRUE
FALSE
Example:
{"include_title":["T0","TS"]}
 
Regular account
This type checks if a customer is logged in to a registered account (not one-time).
Parameters:
None
Logic operators:
=
!=
Logic values:
TRUE
FALSE
 
Orders item count
This type checks the number of items in the cart.
Parameters:
consider_quantity:
TRUE - Set by default, every piece in each row will be counted.
FALSE - Only unique SKUs will be counted.
consider_gifts:
TRUE - Gifts will be counted to this condition.
FALSE - Set by default, gifts won't be counted to this condition.
consider_sets:
TRUE -  All sets will be counted.
FALSE - Set by default, sets won't be counted.
consider_outlet:
TRUE -  Discounted products with the flag outlet will count toward this condition.
FALSE - Set by default, products with the flag outlet won't be counted.
consider_greenpoint:
TRUE - Products with the flag greenpoint will count toward this condition.
FALSE - Set by default, products with the flag greenpoint won't be counted.
Logic operators:
=
!=
>
<
>=
<=
Logic values:
Number - Products in a cart
Example:
{"consider_quantity":"FALSE","consider_greenpoint":"TRUE"}
 
Promotion rules active in cart
This type checks if a set of rules is active in a cart. A rule is considered an active one when its conditions are met. A rule with no conditions is always considered as active. It is important to remember to set a sort order in a rule with this condition to a high value, so it is read last by the promotion module.
Parameters:
rule_ids:
Array- list of rules' IDs that are checked for activity. Set by default, every piece in each row will be counted.
mode (Default "all"):
"all" means all of the rules must be active, 
"any" means any of the rules must be active.
Logic operators:
=
!=
Logic values:
TRUE
FALSE
Examples:
Rule 123 is active:
{"rule_ids": [123]}
All the rules 123 and 321 are active:
{"rule_ids": [123, 321]}
Any of the rules 123 and 321 is active:
{"rule_ids": [123, 321], "mode": "any"]}

Promotion module introduction
Getting started
In this article, you will learn about a promotion module, and what can you do by using that module.
Promotion module is a complex group of categories that together create a base for all the promotions on the website. By using the promotion module, you can create and configure your own promotions, or create a ready promotion pages and opensets for customers to select from.
Promotion module consists of many parts, described below:
Visualization of the promotion module
Promotion logic (1), which is a main, and most important part of promotion module, which consists of conditions, actions, and rules that together create a promotion that is usable on the website (2).
Discount codes
Promotion pages
Opensets
Excluded products tab
Push messages
FIDEN2 vouchers
Visualization of the promotions in the cart on the website
Table of contents:
 Promotion logic
Excluded products
 Discount codes
 Promotion pages
 Opensets
 FIDEN2 vouchers
Push messages
 
 
 Promotion logic
Promotion logic allow creating custom promotions that will be applied according to the customer's cart value on the website. As an example of the promotion rules, we can distinguish:
20% catalog price discount on all products in the cart when customer's cart value is greater than 50 euro.
Two for one promotion on selected products
Buy 30 euro of selected products and get a gift product for free
Select a product for free from a list when cart value is over 20 euro.
When a discount code is applied in the cart, the most expensive and cheapest products are discounted by 50% of the promotional product value.
Promotion logic consist of three parts:
A condition
An action
A rule
Condition is a backbone of the promotion, as it dictates what conditions need to be fulfilled in order for the promotion to work. For example, in this section the "Order has to be greater than 50 euro" condition will be located.
An action applies the selected promotional action to the customer's cart, when the selected condition is met. In this section, the "discount 20% off catalog price of all the products in the cart" action will be located.
Rules are whole promotions that contain in themselves conditions and actions and make them work together in a selected altshops and date ranges.
You can find articles about these three parts in the following articles:
Conditions
Actions
Rules
 
Excluded products
Products excluded from promotion (global) is a tab where users are able to exclude the list of SKU's globally, so these products won't be affected by any created promotions until they are excluded in this list.
Visualization of the products excluded from promotion (global) tab.
 
 
 Discount codes
Discount codes are codes that are used by the customers in the cart on the website in order to get benefits from the configured promotional rules. We distinguish two types of discount codes:
A main code
A personal code
Main code is a custom-made code created by the administrator with unlimited amount of uses (unless specified otherwise in the promotional rule).
Personal code is a code assigned inside the main code with one time use. When the main code has assigned at least one personal code, the main code itself doesn't work, and only the personal codes can be distributed among customers for it to work.
 
You can find more about discount codes in the Discount codes article
 
 
 Promotion pages
Promotion pages are easy to make and maintain pages with a list of products, where customers are able to select the desired products and add them separately to the cart on the website.
Promotion pages are usually created in order to hold categories of products that have discounts assigned in the Products / list - browsing and managing products in altshop module.
Visualization of the promotion page
You can learn more about promotion pages in the Promotion pages article.
 
 
 Opensets
Opensets are a set of products that are bundled into a single package.
We distinguish three types of opensets:
Normal openset
DIY openset
DIY catalog price openset
Normal openset is a webpage where all the products are visible and selectable. The customer is able to select a configured amount of products and then bundle them together into an openset and added to the cart.
Visualization of the normal openset
DIY (Do it yourself) openset and DIY catalog price openset are webpages that use the JSON of products and categories and shows them this way on the openset page. Customer is able to select a product from a category and is being moved automatically to another one. Once customer select at least one product in all available categories, the products will get bundled into an openset and added to the cart.
Visualization of the DIY openset
You can find more about opensets in the Opensets article.
 
 
 FIDEN2 vouchers
FIDEN2 vouchers are vouchers that use FIDEN2 points and assign a configured discount to the selected product and remove the configured amount of points from the customer's account.
Customer is able to earn FIDEN2 points by buying products on the website, creating reviews or inviting its friends to create an account on the website and creating a new order on it.
Visualization of the adding of the discount through FIDEN2 functionality
You can learn more about FIDEN2 in the FIDEN2 article.
 
 
 Push messages
Push messages functionality allows creating and send push messages to the customers. This functionality  is no longer used and maintained as for YR5 version of the web application

Opensets
Getting started
This article describes openset promotion functionality, which allows users to create a web page with set of products, where the customer is able to select desired products from the list, and add them to the cart as a set.
We distinguish three types of opensets – “Normal”, “DIY” and “DIY catalog price”, which are described in the following chapters.
   Visualization of the DIY openset
Table of contents
Creating an Openset
Creating a normal openset (tab “General”)
Creating a normal openset (tab “CMS blocks”)
Creating a DIY or DIY catalog prices openset
JSON construction
 
 
 Creating an Openset
In order to create an Openset, in the administration panel navigate to the Admin panel > Promotions > Opensets / list section and click Add button (1), that will redirect you to the Openset creation page.
   Visualization of the opensets / list tab
 
Creating a normal openset (tab “General”)
Below you will find a description of all parameters needed to create an Openset.
   Visualization of the normal openset creation.
SKU – automatically generated unique openset product code.
Name – displayed name of the openset. The value is displayed on the e-commerce platform for the customer.
Friendly URL – URL address where openset is located.
Type – type of openset.
Price – Target price for the created set. The superior prices of products placed in the openset (Products SKU list field) are not taken into account.
Products number - number of products you can choose from the available list (Products SKU list field). After selecting 3 products, you will receive a popup with the possibility of adding the chosen set to the cart.
Allow to choose single product quantity - A switch that enables customers to select more units than 1 of the same product, instead of the need to select different products.
Products SKU list - list of products (SKU product code). Must be separated by comma.
Cart minimum value - archive field, currently not used.
Start date - date from which the openset will be visible on the e-commerce platform.
End date - date from which openset will not be visible on the e-commerce platform.
Is active - a switch that determines whether the openset is active or not on the e-commerce platform.
After filling in all the above parameters, select Save button to save the changes or Cancel button to cancel adding an Openset.
  RememberIn order for the element to be fully activated and visible on the e-commerce platform, remember to activate the openset in the Altshops module.
Below you’ll find the visualization of normal openset on the e-shop website.
   Visualization of the normal openset on desktop
   Visualization of the normal openset on mobile
 
Creating a normal openset (tab “CMS blocks”)
CMS Blocks tab allows us to see header CMS blocks (automatically created by the application) that will be used by the openset.
CMS block is required to have openset ID in its name, for example:
openset / header / 47 (where 47 is openset ID)
We can press “add” button, which will create a new CMS block for us with the appropriate block name.
Search button will search the CMS blocks in order to find blocks that meet the required name (openset / header / ID). Mobile openset header is no longer used as the website is in a responsive design, so desktop and mobile headers should be located in the openset / header / ID CMS block
   Visualization of the CMS blocks tab
  Remember The header of the openset cannot be wider than 1248px.
Section CMS block is the same for Normal as well as DIY opensets. And it looks as in the example displayed below (1).
   Visualization of the openset CMS block
 
Creating a DIY or DIY catalog prices openset
The process of creating a DIY opener is identical to a Normal type openset. The only differences between normal and DIY sets are:
Type field, where we have to indicate DIY or DIY catalog prices openset.
Product SKU list construction where we have a JSON record.
Product price value indicated in the JSON is superior value in relation to Price. In case of DIY catalog prices openset the price value takes the catalog prices of the product instead of promotion prices.
Products number - means the number of steps of which openset DIY is composed of.
   Visualization of the DIY openset in the admin panel
 
JSON construction
Below you can find an example JSON that can be used in the openset
[{"name":"Krem do rąk","products":[["27300","8.60"],["27714","8.60"],["28172","8.60"],["26885","8.60"]]},
{"name":"Mydło","products":[["05764","7.15"],["44059","7.15"],["42871","7.15"],["43332","7.15"],["43643","7.15"]]},
{"name":"Balsam do ust","products":[["00174","7.15"],["00392","7.15"],["00599","7.15"],["01030","7.15"],["01881","7.15"],["02092","7.15"],["89856","7.15"]]}]
Name parameter sets the name of the category. (1)
Products array sets the product SKU and product price (2) in the set name .
The number of categories (3) is taken from the Products number field of the openset.
Below you’ll find the visualization of DIY openset on e-shop website.
   Visualization of the DIY openset

System

User access control
Getting started
In this article, you can find information about admin panel user control, which allows to set up after how many days of inactivity the admin panel account will be blocked. Blocked accounts will be unlocked using the built-in unblocking process.
The supervisor will also receive e-mails after the selected amount of days with a list of users that are currently expired.
Table of contents:
 System settings
 Functionality overview
 
 System settings
The functionality can be configured in the
System > System / Settings > Admin > Expired accounts access control
Visualization of the system settings
In the Expire accounts access control section we can find the following settings:
Functionality Enabled - Switch that defines if the functionality is enabled or not.
Days to expire - Number of days after which the administrator is considered expired.
Self reactivation email domains - List of email domains that can reactivate the account themselves. Separate with commas. e.g. "example.com,example2.com"
Excluded email domains - List of email domains that wont be expired automatically. Separate with commas. e.g. "example.com,example2.com"
Supervisor email recipients - List of supervisor email addresses to which the admin reactivation request and info mail is sent. Separate with commas. e.g. "supervisor@mail.com,supervisor2@mail.com". Please make sure that an account that has at least super administrator role is set up here, as reactivating the account requires permissions to Settings > Admins / list > Edit
Info mail interval - Number of days after which the info mail is sent to the administrator.
 
 Functionality overview
After the selected number of days of inactivity specified in the system settings users account "is active?" parameter switches from ON to EXPIRED. When the selected user tries to log in when their status is set to Expired they will receive one of twe two notifications:
1. "Your account has expired after X days of inactivity. An e-mail with a request to re-activate the account has been sent to the supervisor" - This message is visible when the selected domain is not in the self-activation list, and the supervisor has to re-active the account manually.
2. "Your account has expiired after X days of inactiivty. An e-mail has been sent you to with a link to re-active the account" - this message is visible when the selected e-mail domain is in the Self reactivation email domains field in the system / settings. User will be able to re-active the account themselves.
Visualization of the error message when the account is expired
The user or the supervisor will receive the following e-mail. This e-mail contains the expired user e-mail address, after how many days it was blocked and when was the last activity of the user. It also contains a button that will allow to re-active the user. Self re-activation will just re-active the account, while supervisor e-mail redirects to the users admin panel profile.
  RememberSupervisor should be a person who has at least Super Administrator permissions in the admin panel in order to access System > Admins / list > Edit.
Visualization of the example re-activation e-mail.
When the supervisor gets redirected to the users profile in the admin panel they will notice that their is active? field is set to Expired. In order to unblock the user the value has to be changed from Expired to On.
Visualization of the user profile in the admin panel

Synchronization
Getting started
With the synchronization process, you are able to merge the contents of one environment with another without the need to make manual changes. The content you want to synchronize can be set at the process configuration phase, and the process itself is automatic.
  RememberSynchronization is the ongoing process of synchronizing data between two environments, and updating changes automatically between them to maintain consistency within them.  It is a perfect way to prepare for example campaign on TEST environment and then synchronize all the changes in tho PROD environment at once.
  NoteSynchronization process works only between PROD and TEST enviroments, and can be activated only from PROD environment. Data can only be synchronized one way at the time, for example: PROD > TEST, or TEST > PROD.
Not all data is synchronized between the environments. Below you will find data and settings that are not synchronized:
System settings (except mobile app JSONs described below)
Translations
Promotion codes
Campaigns
Titles
Users
Payment types
Delivery types
SEO settings
Orders
Reviews
Beauty Advisor module
Synchronization module is located in:
System > Synchronization
   Visualization of the synchronization tab
Table of contents:
 Description of the synchronization process
Changes review - description of the view and possible actions
Result of a synchronization
 
 
 Description of the synchronization process
In the synchronization module, you can find many synchronization options described below
   Visualization of the synchronization tab
(1) - Select the synchronization direction (PROD <--> TEST).
(2) - Choose whether you want to synchronize all records or only new ones.
Synchronize all records - the application will take all records available in the database into account, including also modification of the current records in the environment from which the synchronization process is performed.
Synchronize only new records - The application will only take newly created records into account in the environment from which the synchronization is performed.
  Example1. In the TEST environment, you have created a new CMS page.
2. On the PROD environment, you have changed the graphics in the currently existing Slider
3. You use the synchronize function in the TEST > PROD direction
The result:
The application will only move a new CMS page to the production environment (point 1).
  Warning    If you create a new CMS page on the TEST and PROD environments at the same time, and then synchronize the environments, there is a risk (if the status of the environments is not identical) that the synchronized pages will overwrite the currently existing pages on the environment in which the synchronization is performed because synchronization system is using the internal element IDs to fit the data together, and if the IDs are different that will result in conflict.   
(3) - button enabling selection of all records from section (4)
(4) - switches defining which application modules should be involved in the synchronization process. After selecting the Gallery folders switch, and specifying the synchronization process direction, you will be able to choose which folders from the gallery should take part in the synchronization process. System config option allows to synchronize mobile app JSONs located in System > System / Settings > Integrations > Mobile app.
  RememberSelecting mobile app synchronization options forces to additionally synchronize Gallery folders, as mobile app has mandatory images. Please remember to synchronize gallery folders that are used for a mobile app graphics (in most cases it's a mobile_app folder).
(5) - button initiating the synchronization process.
After selecting Start comparing environments (5) button, the process of environment comparison will start, and you’ll receive the following statement.
   Visualization of the e-mail message
 
 
 Changes review - description of the view and possible actions
After the system compares the enviroments you will see all changes and conflicts that will occur. You can find description of all changes below
   Visualization of the changes review tab
(1) - statement announcing in which direction the synchronization will be performed
(2) - tabs with the possibility to select the records you want to synchronize. In the above screenshot, an example of New records is attached. The selected record will be synchronized, an unmarked record will not be synchronized.
Conflicts - list of conflicts that occurred during synchronization. Conflicts can happen when synchronized data doesn't match internal ID. In this case, the user will receive a conflict warning with an option to ignore the conflict and overwrite the data. To avoid conflicts, it is recommended to not create same content on both enviroments at the same time, as this is the most common reason of a conflict.
New records - list of new records created on the source environment from which synchronization is performed to the target environment.
Modified records - list of modified records on the environment from which synchronization is performed. It is a list of records that have matching ID between PROD and TEST environment, and by selecting them the synchronization will overwrite the content of the data.
Deleted records - list of records deleted from the environment from which synchronization is performed. It is a list of records that doesn't exist on source environment, because they got deleted, but they still exist on a target enviroments. Same as with other actions, it is being compared using the IDs.
(3) - in this section you can schedule the date when the synchronization will be performed and choose the possibility of test import for a verification purposes (changes will not be saved).
  Warning    After scheduling a synchronization, it is advised to not make any changes to the source and target enviroments until the synchronization is finished or canceled. This may cause unexpected behavior in the synchronization process.   
After setting up the settings, select the Schedule synchronization button to initiate the synchronization process.
 
 
 Result of a synchronization
You can check the result of the synchronization by choosing the Messages (1) button.
 
   Visualization of the messages tab
While synchronization is still in process, you will see Synchronization process message. When you click on the message you will see detailed information:
   Visualization of the synchronization process message tab
Synchronization process message will show you at what day and hour the synchronization is scheduled, and you will be able to cancel the synchronization by pressing the HERE text.
After the synchronization process is complete, you will see in the Messages tab a Success: Synchronization process or a FAILURE: Synchronization process message.
   Visualization of the success: synchronization process message tab
In the Success: Synchronization process message you will see an information, that your synchronization was completed successful, and planned changes has been applied.
FAILURE: Synchronization process message will show you an error pointing out why the synchronization was unsuccessful.
A user who has initiated the synchronization process will additionally receive an email message on successful synchronization.
   Visualization of the e-mail message