Return or Order ID
- Requirement
- Required
- Example
- ID-10042
- Purpose
- Needed for the core workflow
Upload order and return data to analyze returned units, returned orders, refund values, return reasons, products, channels, regions, and return rates.
Supports structured .csv and .xlsx files. Public examples use synthetic data. Review VizMint's current privacy and retention policy before uploading sensitive information.
Use the fixed preview below to switch between the source spreadsheet and a dashboard sample. Open the full demo in a new tab for every KPI and chart type.
Ecommerce Returns Dashboard
Interactive preview from the sample returns and refunds dataset
Switch preview
Total Records
48
rows in sample
Total Original Revenue
558,970
sum of Original Revenue
Total Refund Amount
29,624
sum of Refund Amount
Bin width 1,000 · 48 observations
Full dashboard with all KPI details and 6 charts is on the demo page.
Open full demoThe sample tracks 435 returned units and $29,624 refunded across 4 products and 3 channels.
Sample results: 6% unit return rate, Everyday Sneaker and Cloud Hoodie responsible for 72% of returned units, with return reasons and denominators published beside each KPI.
Identify products, reasons, channels, and periods driving returns and refund value.
Ecommerce exports often mix orders, line items, discounts, refunds, customers, and fulfilment records. Reliable analysis makes the aggregation level explicit so orders, units, customers, and line items are not confused.
The sample produces a 6% unit return rate, $29,624 refunded, and Everyday Sneaker and Cloud Hoodie responsible for 72% of returned units.
The workflow is designed around visible aggregation rules and source-level evidence for every headline metric.
Returns and refunds affect revenue, margin, operations, and customer experience. The workflow distinguishes return counts, refunded value, and true return rates. A returns-only file cannot produce a valid rate without corresponding sales or order denominators. Analyze returned orders, returned units, refund value, return reasons, products, channels, and rates.
The result brings the most important metrics, trends, and exceptions into one view, while keeping the supporting records available for review.
Follow the same dataset from source rows to the generated dashboard preview. The spreadsheet table, KPI cards, and charts all come from one JSON sample, so every visible result can be checked against the source.
The source preview highlights the exact columns and representative rows used by the workflow.
| Date | Quarter | Category | Product | Original Revenue |
|---|---|---|---|---|
| 2025-07-01 | Q3 2025 | Footwear | Everyday Sneaker | 16,366 |
| 2025-07-01 | Q3 2025 | Apparel | Cloud Hoodie | 12,546 |
| 2025-07-01 | Q3 2025 | Bags | City Backpack | 8,066 |
| 2025-07-01 | Q3 2025 | Accessories | Desk Mat | 3,354 |
| 2025-08-01 | Q3 2025 | Footwear | Everyday Sneaker | 18,228 |
The finished output includes the KPI cards, charts, tables, and report views described below.
Grouped by Date
VizMint works best when every column has one clear heading and each row represents one consistent record. Fields that are not available should not be invented; dependent outputs should be hidden or clearly marked as unavailable.
| Column | Requirement | Example | Purpose |
|---|---|---|---|
| Return or Order ID | Required | ID-10042 | Needed for the core workflow |
| Return Date | Required | 2026-06-01 | Needed for the core workflow |
| Product or SKU | Required | SKU-1042 | Needed for the core workflow |
| Returned Quantity or Refund Amount | Required | 12 | Needed for the core workflow |
| Sold Quantity or Orders File | Recommended | 167 | Adds an important comparison or breakdown |
| Return Reason | Recommended | Size / Fit | Adds an important comparison or breakdown |
| Channel | Recommended | Online Store | Adds an important comparison or breakdown |
| Region | Recommended | North America | Adds an important comparison or breakdown |
| Customer ID | Optional | CUST-2048 | Adds detail when present |
| Return Status | Optional | Approved | Adds detail when present |
| Original Revenue | Optional | 12500.00 | Adds detail when present |
| Category | Optional | Footwear | Adds detail when present |
Count of physical units returned in the reporting period, with exclusions documented beside the result.
Count of distinct returned orders in scope after deduplication and status rules are applied.
Sum of valid refund values for the defined period and population, with currency stated.
Returned units divided by sold units, expressed as a percentage with the denominator shown.
Returned orders divided by total orders when unique order IDs are available.
Refund amount divided by the selected sales denominator, with gross vs net scope documented.
The product or variant with the highest returned-unit count in the selected scope.
The return reason with the highest associated returned-unit or refund volume.
| Chart or Output | Required Fields | Business Question |
|---|---|---|
| Returns Trend | Return date and returned quantity or refund amount | How are returns changing over time? |
| Returns by Product | Product or SKU and returned quantity | Which products drive the most returns? |
| Returns by Reason | Return reason and returned quantity | What are the main return reasons? |
| Returns by Channel | Channel and returned quantity or refund amount | Which channels create the most returns? |
| Refund Value by Category | Category and refund amount | Where is refund value concentrated? |
| High-Return-Rate Products | Product, sold quantity, and returned quantity | Which products exceed the average return rate? |
Upload the workflow-specific sample or a user file.
Select the correct worksheet when the workbook contains multiple sheets.
Confirm the detected header row and field mapping.
Review the data preview, exclusions, and validation warnings.
Generate the dashboard, chart, report, presentation, or answer.
Review KPI values, calculations, charts, and source traceability.
Save, share, or export using capabilities available on the active plan.
| Metric | Formula or Method | Required Fields | Important Rule |
|---|---|---|---|
| Unit Return Rate | Returned units / sold units × 100 | Returned quantity and sold quantity | Requires sold-unit data. |
| Order Return Rate | Returned orders / total orders × 100 | Return count and order ID | Use unique order IDs. |
| Refund Rate | Refund amount / selected sales denominator × 100 | Refund amount and revenue denominator | State whether the denominator is gross or net sales. |
| Problem | Recommended Fix |
|---|---|
| Returns not linked to orders | Document the rule, standardize the source data, and validate the corrected result before generation. |
| Returned units exceeding sold units | Document the rule, standardize the source data, and validate the corrected result before generation. |
| Refunds without returns | Document the rule, standardize the source data, and validate the corrected result before generation. |
| Different product identifiers | Document the rule, standardize the source data, and validate the corrected result before generation. |
| Inconsistent reason labels | Standardize labels so the same entity or category uses one consistent value. |
Available sharing and export options depend on the live VizMint plan. Publish only capabilities confirmed in production, such as saving the analysis, downloading images or PDF files, exporting PowerPoint, creating private links, refreshing a saved report, or removing branding on eligible plans.
Do not hardcode plan limits, file-size limits, privacy promises, or export features until product and billing owners confirm them.
VizMint analyzes exports; it does not replace the accounting, CRM, help-desk, HR, warehouse, advertising, or project-management system that produced them.
Upload a structured CSV or Excel file to generate the supported metrics, charts, and comparisons for this workflow.