How to Use This Tool
Use this inventory aging report analyzer when you have receipt-level inventory rows and need to review remaining stock by age and cost value. Paste CSV or select one local CSV file; the browser groups receipt cohorts into editable age buckets, flags invalid rows, and creates a downloadable report.
How to use
- Prepare one header row containing
sku,received_date,quantity, andunit_cost. - Paste the CSV, choose a local file, or select Load sample to see the complete workflow immediately.
- Set the report date and increasing age cutoffs. The default cutoffs create 0–30, 31–60, 61–90, 91–180, and over-180-day buckets.
- Select Analyze inventory. Review the summary first, then inspect any row marked “Needs review.”
- Export only after the reported row count and total value reconcile with the source.
Required columns
sku identifies the item. received_date must be an ISO date such as 2026-08-20. quantity is the number of units from that receipt cohort still on hand at the report date, and unit_cost is its per-unit cost on one consistent valuation basis and currency. This input is important: the analyzer does not subtract later sales or transfers for you. Column order may vary and extra columns are ignored, but all four required names must appear in the first row.
Inventory aging formula and example
For each valid row, age in whole days is the selected report date minus received_date. Row value is remaining quantity multiplied by unit cost; the report sums those values into your chosen age buckets. With the sample report date of November 10, 2026, a receipt dated September 15 is 56 days old and belongs in the 31–60 day bucket. The sample has four cohorts: three valid rows total 130.00 in value, and 60.00 (46.2%) is more than 90 days old. One deliberately invalid date is kept as a review row rather than silently included.
How to read the aging report
The oldest-bucket card shows where the maximum valid age falls. “Value over 90 days” is the sum of quantity multiplied by unit cost for valid cohorts older than 90 days, divided by total valid value for the percentage. Rows processed includes valid and rejected data rows, while the detailed table preserves source-row numbers so a correction can be made in the original CSV.
Common mistakes
- Uploading a current SKU total without separate receipt cohorts: one aggregate row cannot reveal when its units arrived.
- Using a date after the report date: future receipts are rejected instead of being assigned a negative age.
- Mixing currencies or valuation bases in
unit_cost: the displayed total is only meaningful when costs are comparable. - Entering unordered or duplicate cutoff days: bucket limits must increase from left to right.
Limitations
Age is an investigation signal, not proof that inventory is obsolete or should be discounted. This page does not forecast demand, consume sales history, allocate outbound orders, choose an accounting method, or recommend write-downs. It also does not join lots or warehouses unless those distinctions already appear as separate receipt rows. Preserve the source file and reconcile the exported totals before making operational or accounting decisions.
Privacy and local processing
The CSV is read and calculated in this browser tab. The tool does not send file contents, filenames, SKU values, dates, quantities, costs, or results to an ecech calculation service. The 2 MB and 5,000-row limits keep the interaction bounded on phones and ordinary laptops.
Sources & assumptions
Formula and interface checked 2026-11-10. The page uses a transparent receipt-cohort calculation; it does not claim to reproduce a platform’s native report.
Official references
- Shopify Help Center — Inventory reports (checked 2026-11-10) — reference for inventory snapshot and on-hand terminology, not for this page’s receipt-date formula.
Model assumptions
- Dates are ISO calendar dates without time zones.
- Quantity and unit cost share one valuation basis and currency.
- Each row is a receipt cohort and its remaining on-hand quantity, not a current SKU aggregate.
- The report date minus receipt date gives age; quantity multiplied by unit cost gives row value. All rows must use comparable costs in the same currency.
- There is no direct Shopify, D365, SAP, or Oracle Fusion connector or vendor-specific column mapping. Reshape an export to the four documented columns and check that its quantities represent remaining units by receipt cohort.
- It does not forecast sales, value inventory under an accounting policy, merge outbound allocations, identify lots or recommend write-downs.

