Reporting
      Back to home
      1. Loupe - Help & Support
      2. Reporting

      Sales Data File Upload Columns

      Find the format and accepted inputs for all columns in the Sales Data upload file

      The columns included in the Sales File are: 

      Note: You can download the Sales and Inventory File Templates here.

       

       

      Sales File Start Date 

      Sales File Start Date is the date in which the data you are sending in the Sales file starts. For example, if you are sending sales data for Sunday to Saturday of last week, the Sales file start date should be Sunday's date. If you are sending us your sales file in Loupe, the Sales File Start date must match what you have selected in the upload process. 

      If you are a store only business and there are days that you do not trade at all, please remember to include these in the time periods you send to Loupe. You do not need to have sales for all of the days in the time period you send to Loupe. 

      The data in this column is:

      • Required - you cannot leave the cell blank 
      • The same for all rows in the file 
      • Entered in the format YYYY-MM-DD - Where YYYY is Year, MM is Month and DD is Day

      Example:

      2023-03-26

       

      Sales File End Date

      Sales File End Date is the date in which the data you are sending in the Sales file ends. For example, if you are sending sales data for Sunday to Saturday of last week, the Sales File End Date should be Saturday's date. If you are sending us your sales file in Loupe, the Sales File End Date must match what you have selected in the upload process. 

      If you are a store only business and there are days that you do not trade at all, please remember to include these in the time periods you send to Loupe. You do not need to have sales for all of the days in the time period you send to Loupe. 

      The data in this column is:

      • Required - you cannot leave the cell blank 
      • The same for all rows in the file 
      • Entered in the format YYYY-MM-DD - Where YYYY is Year, MM is Month and DD is Day

      Example:

      2023-04-01

       

      Transaction ID

      A transaction ID is a unique identifier that POS systems give to every transaction. In the Sales Data File, multiple rows can contain the same transaction ID if they were all bought in the same transaction (i.e. all on the same receipt). However, it should never be the case that the same combination of Transaction ID and Atelier code appear in more than one row. 

      The data in this column is:

      • Required - you cannot leave the cell blank 
      • 1 to 100 characters long
      • Allowed to contain numbers, letters and special characters (e.g. -,/.*#)

      Example:

      T-0001

       

      SKU

      A SKU (Stock Keeping Unit) is a unique code given to a specific product to help track inventory and identify products. Two products with different specifications should not share the same SKU. 

      The data in this column is:

      • Optional - you can leave the cell blank 
      • 1 to 37 characters long
      • Allowed to contain numbers, letters and special characters (e.g. -,/.*#)

      What is an example value expected in this column?

      YGLD-DIA-18CT-001

       

      Atelier Code

      The Atelier Code is a code that Loupe gives to every unique product in your assortment. Two different products in Loupe cannot share the same Atelier Code. You can find the Atelier Code of each product either on the Linesheet inside of Loupe or in any of the Linesheet exports. 

      The data in this column is:

      • Required - you cannot leave the cell blank 
      • 1 to 15 characters long
      • Numbers, letters only - Atelier Codes never contain special characters

      What is an example value expected in this column?

      AZ12345

       

      Date of Transaction

      Date of Transaction should be the date in which the transaction took place. Please note that whichever date is sent to Loupe is the date that will be shown - we will not convert dates or times depending on your time zone. 

      The data in this column is:

      • Required - you cannot leave the cell blank 
      • Entered in the format YYYY-MM-DD - Where YYYY is Year, MM is Month and DD is Day

      What is an example value expected in this column?

      2023-03-28

       

      Sell Price

      The sell price is the price at which the product was actually sold. For example, if the retail price is $999.99 and you are running a promotion where customers get 10% off, the sell price of the product in the transaction would be $899.99. 

      The data in this column is:

      • Required - you cannot leave the cell blank 
      • A currency value - do not add the currency symbol when loading the data. Loupe will add that for you in the UI  (e.g. you load 899.99 and we will show $899.99 in Loupe)
      • Up to 2 decimal places 

      What is an example value expected in this column?

      899.99

       

      Retail Price

      The retail price is the ticket price for any given product. For example, if the ticket price is $999.99 and you are running a promotion where customers get 10% off, the retail price of the product in the transaction would be $999.99. 

      The data in this column is:

      • Required - you cannot leave the cell blank 
      • A currency value - do not add the currency symbol when loading the data. Loupe will add that for you in the UI  (e.g. you load 899.99 and we will show $899.99 in Loupe)
      • Up to 2 decimal places 

      What is an example value expected in this column?

      1099.98

       

      COGS (Cost of Goods Sold)

      COGS (Cost of Goods Sold) is the value of the direct expense incurred in producing the product. It includes raw materials, labour, and overhead costs. You will usually use COGS to calculate total profit. 

      The data in this column is:

      • Required - you cannot leave the cell blank 
      • A currency value - do not add the currency symbol when loading the data. Loupe will add that for you in the UI  (e.g. you load 238.87 and we will show $238.87 in Loupe)
      • Up to 6 decimal places

      What is an example value expected in this column?

      268.47

       

      Transaction Type

      Transaction Type tells Loupe whether the transaction was a Sale or whether the transaction was a Return. We then use this information to generate and calculate your report values accurately. 

      The data in this column is: 

      • Required - you cannot leave the cell blank 

      • One of the following 2 options:

        • Sale - a customer purchased the product

        • Return - a customer returned the product

      What is an example value expected in this column?

      Sale

       

      Units Sold

      Units sold is the quantity of units of that particular product that were sold or returned in any given transaction. We expect sales to be a positive integer (e.g. 1) and returns to be a negative integer (e.g. -1).

      The data in this column is:

      • Required - you cannot leave the cell blank 
      • An Integer - the value must be a whole number, no decimal places 
      • Either positive or negative - depending on whether it is a sale or return

      What is an example value expected in this column?

      1

       

      Store ID

      When you have multiple stores, there is sometimes an identifier used to determine which store the sale came from. These IDs can be words or numbers but are always unique per store.

      The data in this column is: 

      • Optional - you can leave the cell blank  
      • 1 to 50 characters long
      • Allowed to contain numbers, letters and special characters (e.g. -,/.*#)

      What is an example value expected in this column?

      1001