Step 1
Upload your inventory CSV
Each part receives a coverage score — days of stock on hand divided by daily usage — and is classified against its supplier lead time. Results fall into seven categories: Urgent Stockout Risk, Stockout Risk, Healthy, Excess Inventory, Potential Dead Stock, No Usage Data, and Invalid.
Export your inventory to CSV from your ERP and upload it below.
Common column names — Part No, QTY ON HAND,
Avg Daily Usage, Lead Time — are recognized
automatically. Lead Time must be in calendar days.
Maximum file size: 5 MB.
If your ERP exports Unicode (UTF-16) files, open in Excel first and re-save as
File → Save As → CSV (Comma delimited) (*.csv).
File requirements & supported formats
Required columns — common ERP names are recognized automatically:
- Part Number — Part No, Item, SKU, Material, Component
- Quantity on Hand — QTY ON HAND, Stock, Balance, Unrestricted
- Daily Usage — Avg Daily Usage, ADU, Consumption, Demand/Day
- Lead Time — LT, LT Days — must be in calendar days
File format
- Comma-delimited CSV (.csv) only, maximum 5 MB
- UTF-8 or Windows-1252 encoding (standard ERP exports)
- Up to 20 metadata rows above the header row are skipped automatically
Not supported: UTF-16 / Unicode files, semicolon or tab-delimited exports, CJK encodings (Shift-JIS, GB2312). For any of these, open in Excel and re-save as CSV (Comma delimited) (*.csv).
No file yet? to see a demo, or download the sample CSV as a format reference.
Common upload errors and fixes
Error: “missing required columns”
The file doesn’t contain a column name the tool recognises. Open File requirements & supported formats above to see accepted names, or download the sample CSV as a naming reference.
Error mentions semicolons, tabs, or pipes
Your ERP exported a non-comma-delimited file. Open it in Excel and re-save as File → Save As → CSV (Comma delimited) (*.csv).
Error mentions UTF-16 or Unicode
Some ERP Unicode exports cannot be read directly. Open the file in Excel and re-save as File → Save As → CSV (Comma delimited) (*.csv), then upload again.
Error: file is too large
Maximum is 5 MB. Filter the ERP export to a smaller scope — a single site, product family, or planner group — and re-export.
Error: “no data rows”
The file was read but contained no usable rows. Confirm the export includes data below the column headers and is not an empty or filtered-out report.
What do the result categories mean?
- Urgent Stockout Risk — Coverage is below 50% of the supplier lead time. A standard replenishment order may not arrive before stock runs out at current usage rates.
- Stockout Risk — Coverage is below the full lead time. Open purchase orders should be reviewed and expedited if needed.
- Healthy — Coverage is within the normal replenishment window. No action required.
- Excess Inventory — Coverage exceeds twice the lead time. More stock than needed for the current replenishment cycle.
- Potential Dead Stock — Coverage exceeds six times the lead time. The part may be obsolete or severely over-procured. Disposition review warranted.
- No Usage Data — Daily usage is zero or not recorded. Coverage cannot be calculated for this part.
- Invalid — One or more required fields are missing or contain non-numeric values. Review the Reason column in the detail table to see exactly which fields need correction.
Classification uses fixed rules applied uniformly to every row. Coverage = on-hand ÷ daily usage (days of stock remaining). The thresholds and column mapping used are shown in the Triage Summary classification basis after each analysis.