The following sales file fields can be used in tab-delimited (TXT) and comma-separated (CSV).
Note that field names are case-insensitive in tab-delimited and comma-separated files that all sales files supplied to Feefo must be UTF-8 encoded
|Field name for a TXT or CSV file ||Required or optional||Brief description|
|merchant identifier||Required||Your unique Feefo identifier |
|name||Required||The customer's name |
|email||Required||The customer's email address |
|date||Required||The date of the sale |
|description||Required||The description of the item purchased |
|order ref||Required||Your order reference number |
|product search code||Required||An identifier for the product |
|gtin||Required (if assigned)||The Global Trade Item Number (GTIN)|
|mpn||Optional (not needed if gtin supplied)||The Manufacturer Part Number (MPN)|
|mobile||Optional||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. |
|parent search code||Optional||An identifier for the product's parent search code|
|feedback date||Optional||A specific date on which the feedback for this order should be sent out |
|customer ref||Optional||Your customer's reference number |
|amount||Optional||The price paid for the item bought |
|currency||Optional||The currency of the amount field |
|product link ||Optional||The URL to the product page for the product |
|tags||Optional||A list of service levels for analysing the data |
|locale||Optional||The customer’s locale |
|product attributes||Optional||A list of additional product attributes that the customer can rate for a product. Read more|
|image link||Optional||The full URL starting with http or https to the product's main image|
Locale. 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.
Supported locale values are:
|Chinese (Traditional - Hong Kong)||zh_HK|