Skip to content
  • There are no suggestions because the search field is empty.

Upload Revenue Dollars

Overview

The “Revenue Dollars” interface is where you will upload revenue by particular source (ERP System, SPINS, Nielsen, etc). Once uploaded, this data flows through the system and appears in multiple interfaces: Forecasting, Promotion Analytics, Budgeting, Finance Analytics, and Profitability (P&L). This is an integral component of Vividly as it assists with computing trade rates, understanding ROI and forecast actuals. 

Steps on How To Upload Revenue Dollars 

 

  1. Log into Vividly and click on the Business icon in the left-hand navigation menu.

  2. Click on Revenue Dollars from the submenu.

  3. You'll arrive at the Revenue Dollars homepage showing a table of any previously uploaded revenue data.

  4. At the top of the Revenue Dollars page, you'll see several action buttons.

  5. Click the "Load from File" button to open the upload interface.

  6. A panel will appear with upload instructions and options.

  7. In Step 1, locate and click the "Download Sample File" link.

  8. An Excel file will download to your computer, typically named something like "Revenue_Upload_Template.xlsx" or "Revenue_Sample_File.xlsx".

  9. Save this template in an accessible location on your computer (e.g., Desktop, Documents folder, or a shared drive).

  10. Open the downloaded template in Microsoft Excel or Google Sheets.

  11. Add and adjust the data you want to upload.

    • DO NOT delete the header row (Row 1) which contains column labels, this will be needed for the mapping process later.

  12. Once you are done with the file, save it and upload it to Vividly by dragging and dropping it in the upload box in the Step 1 of the Upload process.

  13. Select the type of source. They depend on what Data Sources  you have set up on your account. Two of the most common ones are: 

    1. Accounting Source Data (ERP/Shipment Data): Revenue data from your internal accounting system or ERP showing what you invoiced/shipped to customers (NetSuite, QuickBooks, SAP, Oracle, Microsoft Dynamics, Sage, or custom ERP systems).

    2. Syndicated Data (POS/Consumption Data): Point-of-sale data from syndicated data providers showing what consumers actually purchased at retail (SPINS, Circana (formerly IRI), Nielsen, or direct retailer POS feeds)

  14. Click on Next Step when done

  15. In Step 2, Vividly will attempt to auto-map columns based on the header names in your file, review each mapping to ensure correctness.

  16. After confirming all column mappings, click on Next Step

  17. In Step 3, review and correct errors displayed in the Errors and Warnings lists.

    1. Use our AI insights for suggestions on how to correct these errors and warnings. 

  18. You might need to correct these errors within Vividly or your own file depending on the error or warning. Because of that, once you correct, you'll need to repeat all this process.

  19. Click on Next Step when done correcting these errors and warnings and you are done.

Considering Your Data Source

 

Mapping is highly dependent on the type of data source that you select.:

Accounting Source: 

  • Customer Name/Code: Must match a customer name or alternative customer code/number mapped in the Manage > Customers section; accepts Vividly customer name or any configured alt names.

  • Product Name/Code: Must match a product name, UPC, or alternative product code mapped in the Manage > Products section; accepts Vividly product name or any configured product codes.

  • Revenue Dollar: The actual dollar amount of revenue generated for the customer-product transaction; represents shipment revenue from your ERP system.

  • Date: The date associated with the revenue transaction; Vividly groups data by month, so any date within a given month (e.g., 10/07, 10/14, 10/21) will aggregate into that month's revenue totals.

    Syndicated Data:

    • Customer Name: Retailer name as it appears in syndicated data reports; must be mapped to Vividly customer profile (often requires adding syndicated-specific alt names like "Publix Corp-RMA").

    • Product Code/UPC: Product identifier from syndicated data; must be mapped in Manage > Products section with corresponding UPC or product code.
    • Actual Units: Number of units sold at retail (scanned at POS); replaces "Revenue Dollar" field for syndicated uploads.
    • Date: Date when the syndicated data was captured; typically aligns with weekly syndicated reporting periods.
    • Stores (Optional): Number of stores where the product was sold; not required but provides additional context.
    • Region (Optional): Geographic region for the sales data; not required but can be included for segmentation.

       

      Tips & Best Practices

      • Establish a data source strategy early: During implementation, decide whether you'll upload ERP data, syndicated data, or both—and stick to a consistent approach.

      • Document your data sources: Create internal documentation noting which data sources you're using, how often you upload, and who is responsible.