Integrations

Express Relais integration

Screenshot_2020-04-29_at_19.12.41.png 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:

  1. E-commerce
    1. Configuration of the integration
    2. Customer perspective
  2. TC Logistics
    1. System Settings
    2. Order Management

 

 

Screenshot_2020-04-29_at_19.12.41.png 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

POWERPNT_ONmagValxu.png
Visualization of the Express Relais system settings

In the Express Relais system settings you can find the following options:

info2.svg  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.

POWERPNT_khqdy1gbTw.png
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.

POWERPNT_GjUEVtNmOn.png
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.

 

 

Screenshot_2020-04-29_at_19.12.41.png 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:

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

POWERPNT_LDZ0otfCNI.png
Visualization of the TC logistics system settings

In the Express Relais integration settings you can find the following options:

Order Management

In the order details a new Delivery point table is visible when the Express Relais delivery is used (1). This table contains:

POWERPNT_ERPJBH687G.png
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
POWERPNT_6uIJi8GpDx.png
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:

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

Screenshot_2020-04-29_at_19.12.41.png 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:

  1. Configuration
  2. Customer perspective

 

 

Screenshot_2020-04-29_at_19.12.41.png Configuration

Blik doesn't have any internal options in System / Settings and is configured like every PayU payment method in System > Payment types / list.

POWERPNT_vijbDARDNE.png
Visualization of the BLIK configuration

Available settings are:

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.

info2.svg  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.

 

 

Screenshot_2020-04-29_at_19.12.41.png Customer perspective

Enabled BLIK payment option will be instantly usable by the customers during the payment process

POWERPNT_SJxvUbKfru.png
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.

POWERPNT_zcZCptchPK.png
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.

POWERPNT_itxmbstLcG.png
Visualization of the incorrect BLIK code

Passmachine integration

Screenshot_2020-04-29_at_19.12.41.png 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:

  1. Enabling the functionality
  2. Customer perspective

 

 

Screenshot_2020-04-29_at_19.12.41.png Enabling the functionality

Passmachine integration is disabled by default and needs to be enabled in the

System / settings > Integrations > Passmachine

Ttpuymf5MS.png
Visualization of the passmachine system settings

In the passmachine integration system settings there are the following options:

With the functionality configured and enabled it is ready to be used by the customers.

 

Screenshot_2020-04-29_at_19.12.41.png 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.

caution.svg  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.

POWERPNT_bENrs4jbei.png
Visualization of the passmachine passes tab

In the Passmachine / Passes you can find the following options:

 

 

Screenshot_2020-04-29_at_19.12.41.png 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.

POWERPNT_44v9E3rN8h.png
Visualization of the customer profile

These buttons redirect users to the passmachine website, where they can choose the platform they want to use.

POWERPNT_ZLCsjHKeQU.png
Visualization of the passmachine website

Orlen delivery integration

Screenshot_2020-04-29_at_19.12.41.png 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.

info2.svg  RememberYou can find more about enabling delivery options in Delivery costs / list - browsing and managing delivery costs article

Table of contents:

  1. Frontend overview

 

 

Screenshot_2020-04-29_at_19.12.41.png Frontend overview

With enabled and configured delivery type customers are allowed to use the Orlen delivery pickup.

POWERPNT_q7n86zHYDr.png
Visualization of the Delivery step in the order process
POWERPNT_XM6uvC7WMH.png
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.

info2.svg  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

Screenshot_2020-04-29_at_19.12.41.png 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.

info2.svg  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.

info2.svg  RememberYou can learn more about using the Exponea panel in Bloomreach documentation under URL https://documentation.bloomreach.com/engagement/docs

Table of contents:

  1. Configuration
  2. Exponea product recommendation
    1. Creating a product recommendation

 

 

Screenshot_2020-04-29_at_19.12.41.png 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:

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.

 

 

Screenshot_2020-04-29_at_19.12.41.png 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

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

 

JOY webservice

Screenshot_2020-04-29_at_19.12.41.png 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:

  1. JOY - TC communication
  2. Configuration
  3. Orders to verify
  4. JOY stocks
  5. JOY / Failed orders report
  6. JOY / Real time validation

 

 

Screenshot_2020-04-29_at_19.12.41.png 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:

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.

info2.svg  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.

 

 

Screenshot_2020-04-29_at_19.12.41.png 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

Screenshot 2024-10-28 at 15-44-56 System _ settings - Admin module.png
Visualization of the JOY webservices tab in System / Settings

In the JOY configuration you can find the following options:

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.

 

 

Screenshot_2020-04-29_at_19.12.41.png 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

POWERPNT_xJYDYNBxFb.png
Visualization of the Orders / to verify tab

In the Orders / to verify tab there is an option to

info2.svg  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.

caution.svg  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.

info2.svg  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.

 

 

Screenshot_2020-04-29_at_19.12.41.png 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

POWERPNT_iWPDTWvcW6.png
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.

 

 

Screenshot_2020-04-29_at_19.12.41.png 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

POWERPNT_N6mrQ9fe36.png
Visualization of the filter in JOY failed orders report

In the filters tab we have following options:

POWERPNT_77pZj2ZE83.png
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.

 

 

Screenshot_2020-04-29_at_19.12.41.png 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

POWERPNT_FY8zj7Qvfp.png
Visualization of the JOY real time validation tab

In the JOY / real time validation tab, we are able to select the:

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

Screenshot_2020-04-29_at_19.12.41.png 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.

info2.svg  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:

  1. Configuration
  2. POS stocks configuration
  3. E-commerce perspective

Screenshot_2020-04-29_at_19.12.41.png Configuration

Click & Collect functionality configuration can be found in the

System > System / Settings > Integrations > Click and collect

POWERPNT_ggz8U3e3ze.png
Visualization of the Click and Collect functionality

In the Click and Collect tab you can find the following options:

info2.svg  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).

Screenshot_2020-04-29_at_19.12.41.png 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

POWERPNT_gLcdVQVwzq.png
Visualization of the POS stocks system settings

In the POS stocks system settings you can find the following options:

Screenshot_2020-04-29_at_19.12.41.png 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).

POWERPNT_JqE7Y6uE2E.png
Visualization of the Click & Collect POS selection (desktop)
POWERPNT_pSBN8AqV3J.png
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.

POWERPNT_LabWbPC9Nq.png
Visualization of the POS selection popup (modal tiles)
POWERPNT_2SUG9YvipV.png
Visualization of the POS selection popup (list)
POWERPNT_AiQViuXCwQ.png
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).

POWERPNT_XuKZyaRWwR.png
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).

POWERPNT_xD5BZXCJtD.png
Visualization of the product stock information on the product page (desktop)
POWERPNT_ivWDjDTzf7.png
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.

POWERPNT_gWgnZ7S5ap.png
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

POWERPNT_qyxpRY2vuB.png
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.

POWERPNT_PCHjVE6BgT.png
Visualization of the popup informing which products are not available in the selected store

Zbozi.cz integration

Screenshot_2020-04-29_at_19.12.41.png 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)

info2.svg  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.

POWERPNT_m9jFxcayfX.png
Visualization of the zbozi.cz feed

Table of contents:

  1. Configuration of the integration
  2. Zbozi API elements

 

 

Screenshot_2020-04-29_at_19.12.41.png 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

POWERPNT_GX3Lnt2ZCB.png
Visualization of the zbozi configuration in the system / settings

In the Zbozi system settings you can find following fields:

 

 

Screenshot_2020-04-29_at_19.12.41.png 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.

POWERPNT_7hWXt7DA2n.png
Visualization of the example order sent to zbozi

Following order data is being sent to zbozi:

Heureka integration

Screenshot_2020-04-29_at_19.12.41.png 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.

info2.svg  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.

POWERPNT_47hRkE4LkA.png
Visualization of the Heureka xml feed

Table of contents:

  1. Configuration of the integration
  2. Feed overview

 

 

Screenshot_2020-04-29_at_19.12.41.png 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.

POWERPNT_vetfnAf7WP.png
Visualization of the Heureka integration in the System settings.

In the Heureka tab in the system settings you can find the following options:

 

 

Screenshot_2020-04-29_at_19.12.41.png Feed overview

In the Heureka feed, we can find available products from the selected altshop.

POWERPNT_47hRkE4LkA.png
Visualization of the Heureka xml feed

Every product in the feed has the following fields:

Login via Apple ID

Screenshot_2020-04-29_at_19.12.41.png 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.

info2.svg  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.

POWERPNT_jJQ3HUW9S6.png
Visualization of the Apple ID authorization button on the log in page

Table of contents:

  1. Configuring the functionality
  2. Customer perspective

 

 

Screenshot_2020-04-29_at_19.12.41.png Configuring the functionality

Apple log-in can be configured in the:
System > System / Settings > Integrations > Apple Auth.

POWERPNT_quZNBnNxNk.png
Visualization of the Apple.cz authorization tab

In this tab we can find following options:

 

 

Screenshot_2020-04-29_at_19.12.41.png 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:

POWERPNT_irZsaHV3Wx.png
Visualization of the Apple authorization button on the log in page

The button is also located in the registration form:

POWERPNT_mGXYaDKx96.png
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.

POWERPNT_9DyNHjqEWm.png
Visualization of the Apple authorization

After logging in customer will have to allow Yves Rocher website access to their Apple ID.

POWERPNT_Vu6KiNTw7R.png
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.

POWERPNT_qKdWPjdWTZ.png
Visualization of the Apple additional information page

Glovo feed

Screenshot_2020-04-29_at_19.12.41.png 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.

POWERPNT_nTf8j7pXfJ.png
Visualization of the Glovo feed

Table of contents:

  1. Enabling the feed
  2. Downloading the feed

 

 

Screenshot_2020-04-29_at_19.12.41.png Enabling the feed

The feed switch can be found the

System / settings > Integrations > Glovo

POWERPNT_FpFLpSv9LQ.png
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.

 

 

Screenshot_2020-04-29_at_19.12.41.png 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.

POWERPNT_nTf8j7pXfJ.png
Visualization of the Glovo feed

In the feed you can find the following columns:

 

Data layer

Screenshot_2020-04-29_at_19.12.41.png 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.

info2.svg  RememberThe data layer contains all of the data generated by visitors and customers engaging with the Yves Rocher website.

Table of contents:

  1. Available variables in the data layer
    1. yr_gtm_a
    2. yr_gtm_a1
    3. yr_gtm_ab
    4. yr_gtm_b
    5. yr_gtm_ac
    6. yr_gtm_c
    7. yr_gtm_ad
    8. yr_gtm_d
    9. yr_gtm_e
    10. yr_gtm_f
    11. yr_gtm_fa
    12. yr_gtm_g
    13. yr_gtm_h
    14. yr_gtm_k
    15. yr_gtm_l
    16. yr_gtm_m
    17. yr_gtm_n
    18. yr_gtm_u
    19. yr_gtm_aa
    20. yr_gtm_ae
    21. yr_gtm_ag
    22. yr_gtm_x
    23. yr_gtm_y
    24. yr_gtm_z
    25. ecomm_pagetype
    26. ecomm_totalvalue
    27. ecomm_prodid
    28. ecomm_prodidpl
    29. id_sekce
    30. visitorLoginState
    31. hashed_email
    32. hashed_phone_number
    33. email
    34. phone_number
    35. address_info
  2. Available data layer events
    1. page_view
    2. ecommerce / view_cart
    3. ecommerce / add_to_cart
    4. ecommerce / remove_from_cart
    5. ecommerce / add_shipping_info
    6. cart.change_address_data
    7. ecommerce / add_payment_info
    8. ecommerce / begin_checkout
    9. ecommerce / purchase
    10. ecommerce / view_item
    11. ecommerce / view_item_list
    12. website_error
      1. type: '404_error'
      2. type: 'wrong_discount'
      3. type: 'missing_product_in_cart'
      4. type: 'old_offer_error'
      5. type: 'zero_search'
    13. mgm.button_share
    14. mgm.button_copy
    15. wishlist_add

 

 

Screenshot_2020-04-29_at_19.12.41.png 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:

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:

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:

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:

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:

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:

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)

 

 

Screenshot_2020-04-29_at_19.12.41.png 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

Screenshot_2020-04-29_at_19.12.41.png 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.

POWERPNT_2wBvJgixxu.png
Visualization of the Magyar Posta delivery pickup selection

Table of contents:

  1. Configuring the delivery method
  2. Customer perspective

 

 

Screenshot_2020-04-29_at_19.12.41.png 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

POWERPNT_iSvLuTGpNJ.png
Visualization of the Magyar Posta delivery system settings

in the Magyar Posta system settings, you have the following fields:

info2.svg  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.

POWERPNT_C8SG5zyveN.png
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.

 

 

Screenshot_2020-04-29_at_19.12.41.png 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 ).

POWERPNT_KfaVsydrUX.png
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.

POWERPNT_2wBvJgixxu.png
Visualization of the magyar Posta delivery pickup selection

info2.svg  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

Screenshot_2020-04-29_at_19.12.41.png 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.

info2.svg  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:

  1. Configuring the BaseLinker
  2. BaseLinker product fields
  3. BaseLinker / Orders tab
    1. Filters section
    2. Orders section
    3. Order details
  4. Baselinker categories
  5. BaseLinker delivery mapping
    1. Adding a new delivery method
  6. BaseLinker campaign codes
    1. Creating a new campaign code
  7. BaseLinker errors

 

 

Screenshot_2020-04-29_at_19.12.41.png Configuring the BaseLinker

BaseLinker configuration can be found in the
System > System / Settings > Integrations > BaseLinker

POWERPNT_atwMtNyFR3.png
Visualization of the system settings integration location
S1creenshot 2024-05-08 at 11-12-26 System _ settings - Admin module.png
Visualization of the BaseLinker settings

In the BaseLinker tab we can find the following options:

With all necessary options set and saved, we can find export and update buttons in the
Orders > BaseLinker / Processes

POWERPNT_yTmdCL2Cqr.png
Visualization of the BaseLinker processes

In BaseLinker Catalog we have 4 processes:

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:

info2.svg  RememberBaseLinker communication is also automated with TC platform:

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:

All values are cast to a string type

 

 

Screenshot_2020-04-29_at_19.12.41.png BaseLinker product fields

Updating the product changes almost the same amount of fields as importing the new ones.

Screenshot_2022-07-26_160145.png
Visualization of the BaseLinker product edit

In the first tab “General Information” we have fields:

Screenshot_2022-07-26_163414.png
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.

Screenshot_2022-07-26_165026.png
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.

Screenshot_2022-07-27_140029.png
Visualization of the BaseLinker product edit parameters

In the parameters tab we can see all product parameters:

 

 

Screenshot_2020-04-29_at_19.12.41.png 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.

POWERPNT_8shzkC6BDm.png
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

POWERPNT_TeujXACHKX.png
Visualization of the filters tab in the BaseLinker page

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.

POWERPNT_KAjbqmVAGL.png
Visualization of the orders tab in the BaseLinker orders page

 

Order details

When pressing the show more button you will get redirected to the selected order details.

POWERPNT_riQ7NTXpdG.png
Visualization of the order tab

The first tab is the Order tab. In the Order tab we can check the order:

The next tab is with Delivery Address data.

POWERPNT_AutNNr8Nb8.png
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.

POWERPNT_gWADfxNTd9.png
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.

POWERPNT_Q3XgUAmmLE.png
Visualization of the order data tab

In this tab we can see Order information like:

POWERPNT_6JG2JQdvRh.png
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.

POWERPNT_V8xq8aXB2R.png
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.

POWERPNT_ZxWFxeBkgF.png
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.

 

 

 

Screenshot_2020-04-29_at_19.12.41.png 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.

POWERPNT_BZZksreM2N.png
Visualization of the Baselinker categories section

This table contains the following columns:

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.

 

 

Screenshot_2020-04-29_at_19.12.41.png 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.

POWERPNT_WpkMnsUK8M.png
Visualization of the BaseLinker delivery tab

 

Adding a new delivery method

POWERPNT_i7Jj7St8Q3.png
Visualization of the adding of the new delivery method

 

 

Screenshot_2020-04-29_at_19.12.41.png 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.

POWERPNT_fbn33vXtKa.png
Visualization of the BaseLinker campaign codes tab

Creating a new campaign code

When editing or creating a new campaign code user has to define two values

POWERPNT_c5M3XS6vpB.png
Visualization of the campaign code creation

With both fields filled in we can save the changes by pressing the Save button.

 

 

Screenshot_2020-04-29_at_19.12.41.png 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

POWERPNT_FRUVPkNEqY.png
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

Screenshot_2020-04-29_at_19.12.41.png 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.

info2.svg  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:

  1. Allegro
  2. Allegro delivery methods
    1. Adding new Allegro delivery method
    2. Mapping Allegro delivery method
  3. Allegro errors

 

 

Screenshot_2020-04-29_at_19.12.41.png Allegro

Allegro tab displays all successfully exported orders made in the Allegro platform. You can find this tab in
Orders > Allegro.

POWERPNT_EDt6Ww6YFK.png
   Visualization of the Allegro orders tab

In this tab we can see basic information like:

We can see more details regarding the selected order by selecting Show more button (1).

POWERPNT_Fs3yTJdw88.png
   Visualization of the order tab in the order details

In Order tab, we can check order

The next tabs are Customer Data and Delivery Address

POWERPNT_zjiMYVsQTT.png
   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.

POWERPNT_M5Fs8J5cy3.png
   Visualization of the Order data tab in the order details

This tab displays order information like:

 

 

Screenshot_2020-04-29_at_19.12.41.png Allegro delivery methods

In order to map allegro’s delivery method on Yves-Rocher website, we need to navigate to
Orders > Allegro delivery method.

POWERPNT_MKQ3hWXLCE.png
   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.

POWERPNT_vR9eydfUir.png
   Visualization of the adding new Allegro delivery method

Required fields to fill are:

POWERPNT_kq6tSyYwje.png
   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.

POWERPNT_KprfzSQw8P.png
   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.

POWERPNT_HB5Bgm3Nzg.png
   Visualization of the mapped delivery method

With configured mapping, we can see which allegro delivery methods corresponds with already existing methods for e-store.

 

 

Screenshot_2020-04-29_at_19.12.41.png 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.

POWERPNT_RAcQkRPAv5.png
   Visualization of the Allegro errors tab

Two most basic import errors we can find here are:

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).