Start with one question
“Which product categories brought in the most revenue this month?” is more useful than “make a dashboard.” Write down the period, what counts as revenue and who will use the result. Decide whether refunds, tax and shipping belong in the total before calculating anything.
Inspect the export first
Open it in the CSV viewer. Check the delimiter, headings, date range and a few records against the original system. Search for blanks in fields you expect to be present, and inspect cells containing unexpected values.
Product,Category,Orders,Revenue
Notebook,Stationery,124,868.00
Desk lamp,Home,38,1140.00
Coffee beans,Food,96,1536.00
In this synthetic sample, Food has revenue of 1,536.00. The total is 3,544.00. Those numbers give you a small check case when you build a spreadsheet formula or reporting script. QuickDataView displays and filters the data; it does not calculate these totals for you.
Separate identifiers from measurements
An order ID such as 00124 is an identifier, not a quantity. Preserve leading zeros when importing into an editor. Check decimal separators and date formats explicitly. A text value such as 1,536.00 can be interpreted differently under different regional settings.
Build the smallest useful report
- Import a copy into your spreadsheet or reporting tool.
- Set the types for dates, identifiers and amounts.
- Group by category and total revenue.
- Reconcile the total with the source export.
- Add one chart only if it makes the comparison easier to read.
If the total does not match, investigate duplicated rows, missing categories, negative amounts, refunds and filters. Fix the reason before polishing the chart.
Make next month easier
Keep a short checklist: export location, period, expected headings, transformations, validation total and output location. A reusable template may be enough. Automating a process makes sense once the input and checks are stable; otherwise it can repeat the same mistake faster.
A PROMICRO TOOL
Doing the same export every month?
Discuss your reporting or automation workflow with the people behind QuickDataView. Start with the business question and a description of the process. Keep confidential source files out of an initial inquiry.
Talk to Promicro Our own business
Keep control of the files
QuickDataView processes the file on your device. Exporting creates a local download. If you move the data into another service or send it to a consultant, that is a separate sharing decision. Use synthetic or anonymized examples while discussing a project.
For choosing an editor, read View or edit a spreadsheet. For nested API exports, try the JSON viewer.
Credit to the format’s makers
CSV owes its usefulness to decades of spreadsheet and data-export practice rather than a single creator. Yakov Shafranovich’s RFC 4180 documents a common comma-separated convention. That simplicity makes a small export easy to move between tools.
Format reference: RFC 4180’s CSV documentation. Reference checked 7 October 2026. These links acknowledge the format; they do not imply endorsement or a partnership.