Octo for variable data in CorelDRAW
CorelDRAW's Print Merge generates one page per record from a spreadsheet, with text, image and QR for subscribers. Octo validates the spreadsheet before merging, builds labels with barcodes by macro when imposition is needed, controls numbering and checks the PDF by reading each code back. People's names and photos are personal data: the data protection officer decides.
Six possible deliverables, drawn from the survey. All of them work on a copy, check by content and end in the hands of whoever releases the print run.
Unique code, name within the layout's length, category from the list, EAN-13 with the correct check digit, URL in the standard format, existing photo and recorded consent.
Deliverable: pendencias.csv and pronto_para_mesclar.csvTemplate with text, image and QR fields; a merge that creates the merged document, one page per person, published as PDF.
Deliverable: badge PDF and batch reportEAN-13 with a verified check digit and QR per record, in SVG and PNG, with open libraries (segno and python-barcode).
Deliverable: code folder with an indexSeveral labels per sheet, with positions calculated from the layout and an imported vector barcode, without relying on Print Merge.
Deliverable: sheets built on a copy of the templateReserved range recorded before generating; the PDF is checked number by number; a reprint keeps the same number and goes into the log.
Deliverable: log of the range and reprintspdfinfo, pdftotext, pdftoppm and zbarimg count pages, find names and read each code back against the spreadsheet.
The same Octo cycle, applied to variable data. Each arm has a narrow role; people decide on personal data and release the print run.
Where the spreadsheet comes from, which CorelDRAW version is in use and whether there is a subscription (Print Merge with QR depends on it).
Columns, rules and encoding defined; validation happens before the merge, not after printing.
Nothing leaves the network without review by the data protection officer (LGPD); the working spreadsheet is deleted within the agreed period.
Print Merge for one piece per page; a macro when there is imposition, vector code or controlled numbering.
Each spreadsheet rule noted with its reason; each sheet measurement taken from the layout.
Code read back, page count and names in the PDF. Seeing the code on screen is not a check.
PDF, report and sha256 together. A person releases the print run.
Numbering ranges, batches, reprints and who approved each one.
Octo validates before and checks after; it does not decide which personal data go on the piece or release the print run.
The criteria Octo uses to choose, with the documented limit of each path.
| Task | Path | Note |
|---|---|---|
| One piece per record, text only | Print Merge (classic flow) | TXT, CSV, RTF or ODBC in the 2019 help |
| Badge with photo and QR | Print Merge (subscriber flow) | September 2023; bitmap images only |
| Spreadsheet in .xlsx | Print Merge (subscriber flow) | Subscribers only, according to Corel |
| Fix after merging | Template and a new merge | The merged document does not keep the source |
| Standalone barcode | Object > Insert > Barcode | CorelDRAW wizard on Windows |
| Several labels per sheet | VBA macro on a copy of the template | Object model names to be tested on the version in use |
| EAN-13 and QR in batch | segno and python-barcode | BSD and MIT; SVG and PNG |
| Find each code in the PDF | pdftotext -layout | Text per page |
| Prove the code scans | pdftoppm + zbarimg | Reads back what was printed |
| Validate the spreadsheet | validar_planilha.py | Before the merge, with pending items separated |
Three steps. Each one only makes sense after the previous one has shown results on your team.
A proposal, not a promise
Octo validates the spreadsheet before the merge the team already does, without changing the template.
Each PDF read back against the spreadsheet, with a report attached to the batch.
Numbering ranges, imposition by macro and reprints recorded.
Each point below has a source published by Corel, Microsoft, the open-source project or the responsible body. Object and method names are checked in the Object Browser of the installed version. The sources are in the next section.
3
points with a published source, each with its reference shown alongside.
Octo prepares everything, but it does not sign. The document of record stays with whoever is accountable for it.
Surveys, calculates, organizes and generates the documents: files, PDFs, variable data spreadsheets, proofs and reports.
Deliverable: material ready to checkThe client or the art director checks what Octo delivered before approving. If something doesn't add up, it goes back to Octo with the correction.
Step: review by the approverOcto does not approve the artwork. Artwork carries no legal signature: approval of the artwork and the proof stays with the client or the art director.
Approval: client or art directorCorel help, tutorials and update pages, documentation for the open libraries and tools, and the LGPD, consulted on Oct 31, 2026.
The assessment starts with a read-only validation of a spreadsheet and a PDF from a batch already printed, with the personal data reviewed first by the data protection officer. You get what the check would find, what depends on your CorelDRAW version and the questions only your team can answer.
