Inventory Triage

Deterministic rules  ·  No AI inference
Inventory Triage Engine

Stop stockouts before
they stop the line

Upload your ERP export. Get a ranked risk assessment in seconds.

Stockout & gap detection Deterministic rules, zero hallucination Results in under 3 s
Step 1

Upload your ERP inventory export

Parts are scored by days-of-stock vs. lead time — seven categories, zero guesswork.

Fastest way to see value

Run a bundled sample first to see the full triage flow, then upload your own ERP export once the output format is clear.

Built for repeat reviews

The first upload finds today’s risk. Pro turns it into the baseline for next week.

  1. TriageRank shortage and excess exposure.
  2. SaveKeep an audit trail for the run.
  3. CompareShow what improved next cycle.

Columns auto-detected: Part No, QTY ON HAND, Avg Daily Usage, Lead Time (calendar days). Max 5 MB CSV.

File requirements & supported formats

Required columns — common ERP names 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, semicolon / tab-delimited, or CJK-encoded files. Open in Excel and re-save as CSV (Comma delimited) (*.csv).

Prefer to validate your file format first? Download sample CSV
Common upload errors and fixes

Error: “missing required columns”

No recognised column name found. Check accepted names in File requirements above, or download the sample CSV as a reference.

Error mentions semicolons, tabs, or pipes

Non-comma delimiter detected. In Excel: Save As → CSV (Comma delimited) (*.csv).

Error mentions UTF-16 or Unicode

UTF-16 exports cannot be read directly. In Excel: Save As → CSV (Comma delimited) (*.csv), then re-upload.

Error: file is too large

Max 5 MB. Narrow the ERP export to a single site, product family, or planner group and re-export.

Error: “no data rows”

File parsed but no data rows found. Confirm the export contains rows below the column header and isn’t an empty 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.

Fixed rules, applied uniformly. Coverage = on-hand ÷ daily usage. Thresholds and column mapping are shown in the Triage Summary after each analysis.

OpsCopilot-Lite  ·  Deterministic Inventory Triage for Manufacturing Materials Teams