TABLE OF CONTENTS
Introduction
Feefo provides a straightforward method for importing sales information through tab-delimited (TXT) or comma-separated (CSV) data files, both of which should be UTF-8 encoded. This article aims to explain the various sales file fields you can use when uploading your sales data to Feefo's platform. Understanding these fields will ensure the smooth processing of your sales information, allowing you to collect valuable feedback from your customers.
Field names are in tab-delimited and comma-seperated files. All files must be UTF-8 encoded.
Required Fields
The following fields are required in your sales file:
Merchant Identifier: Your unique Feefo identifier. This informs the system which account the data should be uploaded to. To find your Merchant ID, click on your name in the top right corner of the Feefo Hub, where you'll find this information.
Field name for a TXT or CSV file | Brief description | Key points | Required or Optional |
merchant identifier | Your unique Feefo identifier | This column tells the system which account to upload the data to. This will be the same for each line of data. To find your Merchant ID, click on your name in the top right corner of the hub where you'll find this information. | Required |
name | The customer's name | N/A | Required |
The customer's email address | N/A | Required | |
date | The date of the sale/transaction | N/A | Required |
description | The description of the item purchased | This column can be left blank if it’s not needed, although the header of the column will still need to be present. | Required |
order ref | Your order reference number | This is where you enter the unique order reference for that customer's transaction/interaction. The order reference dictates which sale items are grouped into a feedback request email. If five entries share the same order reference, a single feedback request would be sent to the consumer, requesting feedback on all five items at once. | Required |
product search code | An identifier for the product | This is the SKU or ID number that you use to identify the product in your business. This is used to categorise the product reviews together and ensures that the right reviews are displayed on your website’s product pages. (If you’re only collecting service reviews, you can copy and paste the description). You can’t leave this field blank. | Required |
Optional Fields
In addition to the required fields, you have the option to include the following fields, based on your data needs:
Field name for a TXT or CSV file | Brief description | Required or Optional |
gtin | The Global Trade Item Number (GTIN) | Required if assigned |
mpn | The Manufacturer Part Number (MPN) | Optional (not needed if gtin supplied) |
mobile | The customer's mobile phone number. This should be in the international format starting with a ‘+’, e.g. +447111111111 (UK, US, IE and ZA numbers only). If used, this column must be formatted as 'Text' to ensure the + symbol remains. | Required if assigned |
parent search code | An identifier for the product's parent search code | Optional |
feedback date | A specific date on which the feedback for this order should be sent out | Optional |
customer ref | Your customer's reference number | Optional |
amount | The price paid for the item bought | Optional |
currency | The currency of the amount field | Optional |
product link | The URL to the product page for the product | Optional |
tags | A list of service levels for analysing the data | Optional |
locale | The customer’s locale | Optional |
product attributes | A list of additional product attributes that the customer can rate for a product. Read more | Optional |
image link | The full URL starting with http or https to the product's main image | Optional |
Further Reading
This defines the language of the Feefo emails that you send to a customer including the feedback request email, the merchant response emails and any follow-up emails.
As each line in a sales file can have a single locale defined, one sales file can upload sales data for customers with different locales resulting in the correct language emails being sent to each customer. If a sale does not have a locale defined or the value entered is not supported or is invalid, then those sales will use the language and country defined by a campaign, via Campaign Preferences.
If you're adding a locale value, be sure that the relevant language template within the campaign has also been updated, so your customers can see the emails as intended.
Locales supported for defining the language of Feefo emails are:
Language | Local |
Bulgarian | bg |
| Chinese (Simplified) | zh_CN |
| Chinese (Traditional - Hong Kong) | zh_HK |
| Czech | cs |
| Danish | da |
| Dutch | nl |
| English | en |
| English (US) | en_US |
| Finnish | fi |
| French (Canadian) | fr_CA |
| French (European) | fr |
| German | de |
| Greek | el |
| Hungarian | hu |
| Indonesian* | in |
| Italian | it |
| Japanese | ja |
| Korean | ko |
| Lithuanian | lt |
| Norwegian | no |
| Polish | pl |
| Portuguese (Brazilian) | pt_BR |
| Portuguese (European) | pt |
| Romanian | ro |
| Russian | ru |
| Slovak | sk |
| Spanish | es |
| Swedish | sv |
| Thai | th |
| Turkish | tr |
Conclusion
By understanding the sales file fields and including the required information in your tab-delimited or comma-separated data files, you can effectively import sales data into Feefo's platform. This process enables you to collect valuable feedback from your customers, allowing you to analyse the data and make informed decisions to enhance your products and services. If you have any questions or need assistance, Feefo's support team is available to guide you through the process and ensure a successful sales data upload.