What Is VDP?
Variable-data printing concepts, controlled data preparation and actual legacy processing limits.
Variable Data Printing populates reusable artwork with record-specific values, such as names, addresses, product codes or ticket identifiers. It describes a method, not a guarantee that any number of files can be generated instantly.
The current public legacy canvas and VDP Bulk surface are disabled. This guide is conceptual and a reference for an explicitly authorized compatible workflow. Remaining utility code is not an enabled product page.
Basic Concept
A source master, a validated dataset and explicit mappings produce record-specific output to inspect. Common artwork stays stable while configured values change. Keep the source revision, dataset revision and output identity associated.
VDP vs Traditional Printing
| Concern | Static job | Variable-data job |
|---|---|---|
| Content | Common approved artwork | Configured values may differ by record |
| Review | Inspect the approved version | Also validate mappings and record-specific results |
| Production | Agreed quantity/process | Agreed quantity/process plus data/output handling |
Minimum quantity, cost and time depend on the actual product and supplier. There is no universal 500-piece static minimum, one-piece VDP price or instant completion promise.
Use Cases
Marketing and Sales
Personalized letters, addressed mail and coupons can use a controlled recipient/offer dataset. Outcomes and campaign ROI are not guaranteed by personalization alone.
Event Management
Badges, tickets and certificates can vary by person. A printed code still needs a valid external ticket/verification system; uniqueness and authority are not created by a template example.
Industrial Use
Product labels, serial numbers and lot information are possible briefs. Match code format, source data and production material requirements explicitly.
VDP Benefits
Personalization
Names, roles and offer values can change while shared artwork remains stable.
Efficiency
Reuse can reduce repetitive source editing, but incorrect data/mapping can repeat an error across the whole batch. Inspect representative cases and verify required records.
Traceability
Keep a stable record identifier and output association. A code by itself is not an automatic analytics, scanning or ROI service.
Cost Effectiveness
Discuss setup, validation, quantities and delivery with the producer. No blanket lower-cost, stock-free or free-plan promise is established.
VDP Process
- Prepare authorized UTF-8 data with a header and explicit string identifiers.
- Retain a licensed source master and define the supported variable fields.
- Map columns exactly and specify missing-value/conditional behavior.
- Inspect long, empty, special-character and code cases, including correct recipient association.
- Use only a renderer proven to support the document; review output before sharing or production handoff.
Technical Details
Supported Data Formats
The retained helper parses CSV/TSV. Excel (.xlsx/.xls) requires an explicitly supplied workbook adapter and reads its first sheet; it does not guarantee spreadsheet recalculation or live Google Sheets import. Export resolved values to UTF-8 CSV when needed.
Maximum Limits
The protected batch API accepts at most 500 rows in a 5 MiB JSON request and bounds results at 50 MiB. Its fallback additionally defaults to 50 pages and 5,000 objects per document and rejects unsupported object types. These are technical admission bounds, not a current public entitlement or a print-quality guarantee.
FAQ
Is there an extra VDP charge?
The public VDP surface is closed. A plan label or absence of recurring membership fee does not enable it or make all tools/services free. Check terms for any explicitly offered authorized workflow.
Which output formats are available?
Do not assume the old PDF/PNG/JPG/PDF-X menu exists. The retained local batch path produces PDF files in a ZIP; it does not certify PDF/X or offer all formats.
Can VDP include images?
The mapping model includes image references, but the local fallback refuses images, QR and barcode objects. Actual image/code rendering requires a compatible renderer and separate verification; URL acceptance is not successful loading or a safe production result.
Was this article helpful?