How to Combine Multiple Sales Excel Files into One Dashboard

 

How to Combine Multiple Sales Excel Files into One Dashboard

At the end of every month, or after every campaign, the same situation plays out. A Shopify export lands in your downloads folder. An Amazon sales report arrives by email. A regional sales file from your ops team shows up in Slack. A vendor performance file sits on someone's desktop. You need one consolidated view of revenue and KPIs, but before any analysis can start, someone has to figure out how to combine all of it.

This post walks through how to consolidate multiple sales Excel files into an analysis-ready dataset. It covers the difference between simply appending rows and doing it correctly, and what to check before you merge anything.


Why You End Up with Multiple Files

Spreadsheet fragmentation happens for three predictable reasons.

Different platforms export differently. If you sell on Shopify, Amazon, and your own storefront, each platform produces its own export. Column names differ. Date formats differ. Order ID schemes have nothing in common.

Time periods get split. Systems often limit how far back you can pull in a single export, so teams end up managing a January file, a February file, a March file. Over a year that becomes twelve separate workbooks covering the same metrics.

Teams manage their own files. Sales, marketing, and operations each maintain spreadsheets that only come together at quarter-end, when someone has to merge them under deadline pressure.

The data exists. The problem is that it lives in separate files, and decisions require a single view.


What to Check Before You Merge

Appending rows without checking the structure first is where most consolidation errors begin. Go through these checks before combining anything.

1. Do the column names match?

File A might have Order Date. File B might have Purchase Date. File C might have order_date. These three columns carry the same information, but if you stack the files without aligning them, you end up with three separate columns — most of them mostly empty. Map each file's columns to a shared schema before merging.

2. Are the date formats consistent?

Date format mismatches are extremely common in exported spreadsheets. One file stores dates as 2025-01-15, another as 01/15/2025, another as January 15, 2025. Inconsistent formats break time-series aggregations. Standardize to one format before stacking.

3. Are currency and numeric columns clean?

Platform exports frequently store revenue as text. A cell containing $1,234.56 or 1,234,567원 will not sum correctly until the currency symbol and formatting are stripped and the column is converted to a numeric type. Check every revenue and quantity column before merging.

4. Are the order ID schemes compatible?

Every platform uses its own order numbering system. Order 1001 from Shopify and order 1001 from Amazon are two completely different transactions. If you do not add a source column identifying which file each row came from, you lose the ability to trace data back to its origin after the merge.

5. Do any files cover overlapping time periods?

This is the most common source of double-counted revenue. A January–March file and a March–May file, stacked without deduplication, will count March twice. Identify overlapping ranges before combining and define your deduplication key — usually a combination of order ID and source.


Common Mistakes

Pasting rows with mismatched headers. Copy-paste in Excel will not warn you when column alignment is off. The rows append, but the data lands in the wrong columns. Pivot tables built on top of that will silently produce wrong numbers.

Numbers stored as text. If a revenue column contains values like "1,234" (with quotes or comma-formatted as text), Excel and most tools will not sum them. The column looks correct visually, but aggregations return zero or skip those rows entirely.

Including canceled and returned orders in revenue. Many platform exports include cancellations, returns, and exchanges in the same file as completed orders, distinguished only by a status column. If you do not filter or handle those rows before aggregation, your gross revenue figure will be wrong.


A Step-by-Step Consolidation Workflow

Follow this sequence to reduce errors.

Step 1. Profile each file. Open each file and note the column list, row count, data types, missing value rates, and date range. This step feels slow when you have many files, but skipping it costs more time later.

Step 2. Define a column mapping. Write down which column in each source file corresponds to which column in your unified schema. If your unified schema uses order_date, specify the exact column name for that field in each file.

Step 3. Apply cleanup rules. Standardize date formats, convert text-encoded numbers to numeric types, normalize currency, and remove header or footer rows that the export appended automatically. Document these rules so you can reuse them next month.

Step 4. Add a source column. Before stacking the files, add a column that records which file or platform each row came from. This preserves the ability to break the consolidated dataset back down by channel after the fact.

Step 5. Deduplicate. Remove duplicate rows using order ID combined with source as the deduplication key. If the deduplication criteria are unclear, pull the duplicates into a separate sheet and review them before deciding.

Step 6. Validate against known numbers. After building the consolidated dataset, cross-check at least one metric you already know. If you know January revenue was $48,000 from Shopify alone, verify the consolidated file produces the same number when filtered to Shopify and January. If it does not, go back to the column mapping or deduplication step.

Step 7. Build the dashboard. Once the dataset is validated, build KPI views, time-series charts, channel breakdowns, and product rankings on top of clean, trusted data.


Metrics to Review After Consolidation

Once the consolidated dataset is ready, these are the first metrics worth checking.

  • Gross revenue and net revenue. After accounting for cancellations and returns, what did you actually collect?

  • Revenue by channel. Which platform drove the most volume? How has that mix shifted over time?

  • Weekly and monthly trends. Is revenue growing? Are there weeks or months with unexplained drops or spikes worth investigating?

  • Average order value (AOV) by channel. If AOV differs significantly between channels, it usually points to differences in discount policy, product mix, or customer segment.

  • New vs. returning customers. If customer IDs are available across channels, the ratio of first-time buyers to repeat buyers tells you something about retention at the channel level.


How Kiolix Xel Handles Multi-File Consolidation

Kiolix Xel is a local-first desktop app for Mac and Windows that ingests Excel and CSV files and turns them into dashboards, KPI views, and exportable reports. It supports up to 100 files in a single project.

When you import files, a DuckDB-based local analysis engine automatically profiles each file: column names, data types, missing value rates, and date ranges. From there, the Data Prep panel lets you define column mappings, apply cleanup rules, and choose between union, merge, or join workflows — without writing SQL or copying rows between spreadsheets.

Your workbooks are not uploaded to Daolix servers as part of normal analysis. Processing and aggregation happen on your device. If you use the AI follow-up feature with a cloud LLM (OpenAI, Claude, or Gemini), the prompt and context sent to that provider follow that provider's data policy. For sensitive files, Kiolix Xel supports local model inference through Ollama, which keeps everything on-device. Note that Ollama requires a separate installation.

Once the dashboard is ready, you can export to PowerPoint, XLSX, PDF, or PNG.


Pre-Merge Checklist

  • Have you reviewed the column list and data types for each file?

  • Are date columns in a consistent format across all files?

  • Are revenue and quantity columns stored as numbers, not text?

  • Is currency consistent, or do you have a plan for normalizing it?

  • Have you identified overlapping date ranges and defined a deduplication key?

  • Have you decided how to handle canceled, returned, and exchanged orders?

  • Does each row have a source column identifying which file it came from?

  • Do you have a known number to validate the consolidated output against?


Download Kiolix Xel

If you are combining sales Excel exports every month and the prep work is taking longer than the analysis, Kiolix Xel is built for that workflow.

Comments

Popular posts from this blog

Moltbook: The AI-Only Social Network Taking the World by Storm

UAE Exits OPEC After Six Decades, Reshaping Global Oil Order

Iran's Death Sentences Against Women Protesters: What We Know, What Remains Unclear