Feefo’s preferred format for importing sales information is a tab-delimited data file encoded in UTF-8. If you're unsure about encoding, see Saving UTF-8 Sales Files.

A sales file can contain many thousands of order lines, with each order line for a given sale having its own separate line in the file. For example, if a sale contains four items, the file needs to contain a header line with four order lines, one for each item, with each line featuring several required fields plus, if needed, any optional ones too.

The following sale file example shows two sales entries with only the required fields listed:

merchant identifier name
order ref
product search code
examplesupplier-com John Smith johnxxxxxx@xxxxxx.com 11/01/2010 Falcon Mach V 92888 132
examplesupplier-com Harriet Jones harrietxxxxxx@xxxxxx.com 11/01/2010 Konica Minolta Z20 92896 133

The column headers in the shaded row in the table above need to be included in every sales file but the column order is not important. Clicking on the green text will take you to a more detailed description of each field. The table above lists the required fields and for completeness, the table below lists the optional fields for the same example: 

parent product ref
feedback date
customer ref
product link
product attributes
+447748123456 laptop 12/01/2010 Reference1 10 GBP http://www.examplesupplier.com/product_info.php?products_id=132 store=Cardiff,department=Computers en Performance,Value,Usability
+447805654321 camera 12/01/2010 Reference2 15 GBP http://www.examplesupplier.com/product_info.php?products_id=133 store=Petersfield,department=Photography fr Performance,Value,Usability

Where optional fields are included in a file, as for the required fields, the column headers need to be included but the order is not important. Again clicking on the green text above will take you to a more detailed description of each field.

A full explanation of the required and optional fields is given in Sales File Fields Summary.

Sales files can also be sent to Feefo in XML (Extensible Mark-Up Language) format, the structure being similar to the below example. For comparison purposes, this example shows the same data as the combined required and optional sales file example above. Note that ‘locale’ is not an option in XML files and so is not included in the XML example.

        <name>John Smith</name>
        <description>Falcon Mach V</description> 
        <product_link>http://www.exampleretailmerchant.com/product_info.php?products_id=132 </product_link>
    <item><name>Harriet Jones</name>
        <description>Konica Minolta Z20</description>
        <tags> store=Petersfield,department=Electrical</tags> 
        <product_link>http://www.exampleretailmerchant.com/product_info.php?products_id=133 </product_link> 
        <product_attributes>Value,Appearance</product_attributes> <amount>15</amount>

Once the sales file is in the correct format, it can be uploaded to Feefo by:

Introduction To Sending SalesSaving UTF-8 Sales Files