Feefo’s preferred format for importing sales information is a tab-delimited (TXT) or comma-separated (CSV) data file encoded in UTF-8. We have a sample sales file available for you to download within the Feefo Hub - When you're logged in, via the left-side navigation bar head to Sales > Upload Multiple Sales, and on the right hand side of the page you'll see the download link there.
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 sales file example shows two sales entries with only the required fields listed:
merchant identifier | name | email | date | description | 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.
The table above lists the required fields and for completeness, the table below lists both the required and optional fields for the same example:
gtin | mpn | mobile | parent search code | feedback date | customer ref | amount | currency | product link | image link | tags | locale | product attributes | |
721864985325 | GO12345OOGLE | +447748123456 | laptop | 12/01/2010 | Reference1 | 10 | GBP | http://www.exampleretailmerchant.com/product_info.php?products_id=132 | http://www.exampleretailmerchant.com/product_info.php?products_id=132 | store=Cardiff,department=Computers | en | Performance,Value,Usability | |
323456789012 | F9A6C544321EBOOK | +447805654321 | camera | 12/01/2010 | Reference2 | 15 | GBP | http://www.exampleretailmerchant.com/product_info.php?products_id=133 | http://www.exampleretailmerchant.com/product_info.php?products_id=133 | store=Petersfield,department=Photography | fr | Performance,Value,Usability |
Where optional fields are included in a file, the column headers need to be included but the order is not important.
A full explanation of the required and optional fields is given in the Sales File Fields Summary article.
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 example above. Note that ‘locale’ is not an option in XML files and so is not included in the XML example.
<items> <item> <name>John Smith</name> <email>johnxxxxxx@xxxxxx.com</email> <date>11/01/2010</date> <mobile>+447748123456</mobile> <feedback_date>12/01/2010</feedback_date> <description>Falcon Mach V</description> <merchant_identifier>examplesupplier-com</merchant_identifier> <tags>store=Cardiff,department=Computers</tags> <product_search_code>132</product_search_code> <order_ref>92888</order_ref> <product_link>http://www.exampleretailmerchant.com/product_info.php?products_id=132</product_link> <product_attributes>Value,Appearance</product_attributes> <amount>10</amount> <currency>GBP</currency> <customer_ref>Reference1</customer_ref> <gtin>721864985325</gtin> </item> <item><name>Harriet Jones</name> <email>harrietxxxxxx@xxxxxx.com</email> <date>11/01/2010</date> <mobile>+447805654321</mobile> <feedback_date>12/01/2010</feedback_date> <description>Konica Minolta Z20</description> <merchant_identifier>examplesupplier-com</merchant_identifier> <tags> store=Petersfield,department=Electrical</tags> <product_search_code>133</product_search_code> <order_ref>92896</order_ref> <product_link>http://www.exampleretailmerchant.com/product_info.php?products_id=133</product_link> <product_attributes>Value,Appearance</product_attributes> <amount>15</amount> <currency>GBP</currency> <customer_ref>Reference2</customer_ref> <gtin>323456789012</gtin> </item> </items> |