1. Using CSV without headers

You must comply with the following rules to ensure successful product.csv integration:

1. The file must be accessible through HTTP.
2. The file must be zip compressed.
3. The file must be updated at least once a day.
4. There must not be a header in the first line.
5. The file must be UTF-8 encoded without BOM (byte order mark).
6. Use semicolon to separate columns.
7. If a product goes out of stock, stock column must be declared as 0 (zero) or the entire line must be removed from the file.
8. If there is no discounted price, the original price must be written in the discounted price column as well, ensuring that both columns contain the same value.
9. All product codes must be unique. 
10. A product can have only 1 category. If a product is linked to multiple categories use only the default category.
11. Product codes you sent from web site or mobile app must be the same as product codes in the Product Feed.

Columns must be ordered in the following way:

Once you have prepared the required file based on the rules and standards mentioned above, follow these steps below to validate it and schedule an automatic upload:

1. Go to  Personalize > Settings > Product Integration.
   
   
2. Enter the URL for the CSV file you have created. 
   
   
3. Click “Test URL” to validate the URL and file.
   
   
4. If you have no error in your Test Detail, click “Save URL”. 
   
   
5. Click “Add Trigger” to schedule product data uploads. We also recommend that you synchronize the product data generation and upload frequency.
   
   

2. Using XML

Uploading and Validating the Data 

To verify your product file format and content, you can use the Product File Integrator.

Choose; Cog Icon > Personalization Center > Recommendation > Product Integration

3. Product Integration for Multi-Language, Multi-Currency and Location 

3.1. By Using CSV;

In this section, you can find the rules to be followed in product integration in order for the products recommended in the widgets of RMC Recommend to work responsively with websites that support multi-language and multi-currency.

Visilabs CSV product integration service has a structure that does not have header information, and fixed column order in CSV. Additions have been made to the existing integration file standards so that the products to be proposed in widgets on sites that support multi-language and multi-currency can be displayed in the language and currency preferred by the visitor.

The changes are briefly as follows:

1. Including header information in CSV product integration file is mandatory for multi-language support. Details are explained in the "CSV File Header Information" section.
2. The site's localization options (currency, product availability and language) and standard product information should be  provided.In other words, it is necessary to provide the correspondence of the standard columns according to the supported location options. Details are explained in the "Customizing Product Data" section.
3. Consistency must be maintained in the product information, provided for localization. Details are explained in the "Consistency in Localized Product Information" section.

CSV File Header Information:

Customizing Product Data

We mentioned that product information can be customized on the basis of language, currency and availability (location) in the “CSV File Header Information” section above.

Product information that can be customized with language:

The columns of the CSV product integration file that can be customized to the language are as follows:

Product information that can be customized with currency:

The columns of the CSV product integration file that can be customized to the currency are as follows:

Consistency in Localized Product Information

In order for widgets to be displayed on the site, the visilabs JavaScript library must be placed on all pages to be displayed.  This library sends some of the information that the visitor obtains during their browsing while requesting suggestions from visilabs internet services. At the same time, due to the implementation to be made on the site, some knowledge other than this information can be sent by the site coders on the related pages through some methods in the library. 

For multi-language and multi-currency support, 3 parameters must be added to the parameter array collected by the visilabs library, before the desired method is called.

These parameters are: OM.p_lng, OM.p_loc, OM.p_dc

In the light of this information, while the visilabs suggestion service is sending the recommended products, the service provides the delivery of the entire information that can be used in the design compatible to the user's localization settings.

At this point, to avoid undesirable situations, the information that is used for localization should be compatible.

For example, when requesting a suggestion for a visitor, let the submitted parameter value be:

OM.p_lng = de

OM.p_loc = DE

OM.p_dc = EUR

Let the fields localized for the product "ABC" in the product file be as follows:

Inventory_DE  = 1

Let originalPrice_EUR = empty or "". In this case, if the suggested product is "ABC", the price information that can be used while creating the widget on the site will not be sent and will be displayed as 0.

The same can be true for the product view link (TargetUrl). If "TargetUrl_de" is not sent or if it is sent blank while Inventory_DE = 1 is submitted,  there will be no link that can be accessed because the product is clicked on the widget.

Based on this, in order for the widgets to work in harmony in a site that supports 3 languages, 3 currencies and 3 locations, while the widgets are rendered besides the standard fields, the customized columns of the most required fields should be sent in the product integration.

These fields are as follows:

ProductName, TargetURL,  (SmallImageURL veya MediumImageURL veya LargeImageURL) en az bir tanesi, OriginalPrice, Currency, DiscountedPrice, DiscountCurrency ,Inventory

In this case, the number of columns that should be in the product file:

• Standard number of column: 20

• Number of customized field: ProductName_[language]  * 3 + TargetURL_[language]  *3 + MediumImageURL_[language] *3 + OriginalPrice_[currency] * 3 + OriginalPriceCurrency_[currency] * 3 + DiscountedPrice_[currency] * 3 + DiscountPriceCurrency_[currency] * 3 + Inventory_[location] * 3 = 24

• There should be minimum of 44 (20 + 24) columns in total.

3.2. By Using Single XML

You can find the rules to follow for the product integration to allow the widgets in the RMC Product Recommend product to run smoothly on the websites that support multi-language and multi-currency.

3.2.1. Product information customizable with LANGUAGE

The naming of the colons to be used on the data to be customized with language should be done accordingly: The character “_” and the 2-character ISO 639-1 code should be entered at the end of the original name of the relevant field.

Following are the XML product integration file colons that can be customized with language.

3.2.2. Product information customizable with CURRENCY

The naming of the colons to be used on the data to be customized with currency should be done accordingly: The character “_” and the 3-character ISO-4217 code should be entered at the end of the original name of the relevant field.

Following are the XML product integration file colons that can be customized with currency.

3.2.3. Product information customizable with LOCATION 

The naming of the colons to be used on the data to be customized with location should be done accordingly: The character “_” and the 2-character ISO 3166-1 country code should be entered at the end of the original name of the relevant field.

Following are the XML product integration file colons that can be customized with location:

3.3. By Using Multiple XML

Parent Topic: Sending Data to RMC