Both are accepted, and a cut list can be as long as the job needs. Column mapping is the only set-up.
Product · Cut list import
Import the cut list you already have.
No CAD export, no new file format, no re-keying. Upload the spreadsheet your estimator already maintains, map your columns once, and every row is checked before a second of solver time is spent.
The upload
Spreadsheet in, validated demand out.
An import that accepts anything and then fails halfway through a run is worse than one that refuses the file. Validation happens first, in full, and reports every problem at once.
Span, width and quantity per grating. Map them once to the columns your sheet already uses, rather than reformatting the sheet to suit the tool.
Numeric span, width and quantity; positive quantities; span within the panel bounds; width producible after classification. Errors are returned per row and per column with a stable code, so a fix is a spreadsheet edit rather than a guess.
Each piece is classified as fine, needing an extra load bar, or needing a split, with the delivered width shown against the requested one. You see this before committing a run from your allowance.
What a validation report looks like
Errors you can act on.
Every problem carries a stable code, so the same defect always reads the same way and a recurring import can be corrected at source.
| Row | Column | Problem | What to do |
|---|---|---|---|
| 14 | width | Not numeric | Remove the unit suffix from the cell |
| 27 | quantity | Zero or negative | Delete the row, or correct the quantity |
| 31 | span | Exceeds the panel bounds in the profile | Split the piece, or raise the maximum span |
| 48 | width | Off the load-bar pitch grid | Accept the extra bar, or adjust to a grid width |
Row-level errors are capped with an overflow count, so a badly formed file reports its first several hundred problems rather than producing an unreadable wall of text.
Two steps, not one
Parse, then commit.
An import is reviewed before it becomes demand. Nothing enters a batch until you have seen what the file actually contained.
-
Parse
The file is read, the columns are mapped and every row is validated. You get the row count, the error list and the preflight classification, and nothing has been saved as demand yet.
-
Commit
Accept the parse and the rows become the batch demand, ready to run. Reject it, fix the spreadsheet and parse again; the run allowance is untouched either way.