Home / Data Merge Production / Cut-and-Stack CSV Sequencer

Variable print · source preparation

Cut-and-Stack CSV Sequencer

Turn an approved source table into one row per physical sheet, with separate field sets for each cell and an auditable after-cut collection sequence.

Files stay on this device. No upload or account required.

Enter the source and job settings, then run the check.

What this calculator solves

Sequential source records normally merge across sheets in reading order. Cutting a pile of those sheets can leave each smaller pile out of sequence. This tool changes the source structure before merging: one CSV row describes an entire physical sheet, with a separate set of fields for each numbered cell. It preserves names and every other source column alongside the IDs. It does not position artwork, calculate bleed or impose a PDF. Those remain template and printer responsibilities.

How to choose the inputs

Begin with an approved source CSV and resolve structural faults first. Across and down are whole counts, not millimetres; their product is the number of cells on one sheet. Maximum sheets per lift is the number the operator intends to cut and collect together. Select row-major or column-major pile collection and whether each cut pile is read in emitted-first or emitted-last sheet order. Measure actual press delivery rather than assuming face-up and face-down stacks behave identically. File input overrides pasted data until cleared.

How the calculation works

For each lift, sheet count H is the smaller of the entered maximum and the ceiling of remaining records divided by cells per sheet. Collection pile k receives the next H source records. Emitted sheet s receives depth s for first-sheet-first order or H minus 1 minus s for reversed depth. Each source column is expanded into field sets ending __C1, __C2 and so on. Image headers keep their leading @. Out-of-range source positions become empty cells; no real record is dropped to fill a sheet.

Worked production example

For eight records, two cells across, one down and two sheets per lift, the first emitted sheet contains source records 1 and 3. The second contains 2 and 4. Cutting that lift and collecting the left pile before the right produces 1, 2, 3, 4. The next lift emits 5/7 and 6/8. If only seven records exist, the final cell is blank and is explicitly counted. Reversing sheet-read order reverses the emitted depth within each lift while preserving the intended collected sequence.

How to interpret the result

Download both the production CSV and the cell map. Build one physical-sheet template whose cell 1 uses ID__C1, Name__C1 and the remaining C1 fields; cell 2 uses C2 fields. Merge one record per complete sheet. Do not apply a second multiple-record arrangement. The map identifies lift, emitted sheet, grid position and original source-record number, allowing the cutter operator to prove the route with a numbered paper dummy. Blank cells require a spoilage/blank-removal instruction, not silent deletion of the sheet record.

Common production mistakes

A correct numerical map cannot compensate for collecting piles in a different order, reversing a delivered pile unexpectedly or letting the RIP impose the sheet again. Another common error is sequencing only a number column and leaving names or QR payloads in their original order. This tool keeps complete source records together. Do not re-sort the expanded CSV by ID after export. Do not use the multiple-record merge option on an already expanded full-sheet template. Recheck the last partial lift, not only the first full lift.

Production assumptions and limitations

Across and down are limited to twelve each and lift height to one thousand sheets; expanded output is capped at two thousand fields. The source limit is 2 MiB, twenty thousand records and one hundred columns. The model assumes one consistent artwork orientation and a declared collection path; it does not handle duplex front/back matching, NCR interleaving, booklet signatures or mechanical turn-over operations automatically. Export is lossless CSV text. Formula-like source values or @ headers require explicit acknowledgement before production download because spreadsheet opening can execute or reinterpret them.

Related production workflow and sources

Use CSV Preflight before reordering and Print Imposition separately for physical sheet fit. The Data Merge Production Preflight Guide covers proof and handoff. The source-preparation approach is described in Colecandoo's cut-and-stack explanation; final application setup follows the compositor documentation. Last reviewed: 2026-10-26.