Variable Data Print Tools

I owned a print house. I know what kills a job at 3am.

About this work

I owned and operated a print production facility. Every VDP tool I ship has been tested against a real press -- not simulated, not approximated, but run through prepress and printed. That's not something you get from a SaaS vendor or a developer who's never seen a press room. My tools are print-rigorous: every output is press-correct by construction.

VDP tools built by someone who knows what print-rigorous actually means.

Variable Data Printing is the practice of generating large runs of printed material where every piece is unique — personalized names, addresses, QR codes, prices, individual offers, unique barcodes.

The enterprise solutions — EFI Fiery, Kodak PRINERGY, XMPie — are powerful, battle-hardened, and priced accordingly: €15,000–50,000+ in licensing, specialist operator required, annual maintenance contracts.

For mid-size print houses, agencies, and brands that need VDP capabilities without the enterprise overhead, I build custom lightweight VDP tools that do exactly what you need, correctly, without the price tag.

Enterprise VDP (EFI, XMPie, PRINERGY):
- €15,000–50,000+ licensing/year
- Specialist operator required
- Annual maintenance contract
- Vendor lock-in on formats and workflows
- You adapt to the tool

Custom VDP tool (from me):
- From €120/h — you own the code outright
- Your team can run it after handover
- No subscription, no price increases
- Your data format, your workflow, your rules
- Tool adapts to you

The QR code ink problem (and the fix)

A QR code printed in standard rich black — C:75 M:68 Y:67 K:90 — uses approximately 300% total ink coverage on press.

The same QR code in K=100 (pure black separation only) uses 100% coverage. Three quarters less ink. Scans identically. Carries zero risk of color registration error causing scan failures.

This sounds trivial until you're printing 50,000 loyalty cards and your ink bill comes back 40% higher than expected — or your QR rejection rate spikes because the four CMYK plates didn't register within tolerance on a fast press run.

Every VDP tool I build uses K=100 for all black elements by default. Not as a preference — as a production standard.

Rich black QR (common mistake):
- C: 75% M: 68% Y: 67% K: 90%
- Total ink coverage: ~300%
- 4-plate registration risk: real
- Scan failure risk: elevated at scale
- Ink cost: 3× higher than necessary

K=100 QR (print-correct):
- K: 100% only
- Total ink coverage: 100%
- 4-plate registration risk: zero
- Scan failure risk: minimal
- Ink/toner cost: ~75% lower
- And it looks sharper.

Real numbers

50,000 loyalty cards. K=100 QR codes. Ink coverage down 75%. Zero scan failures. No misregistration. No reprints. That's what print-rigorous actually means in production.

What I build

QR code and barcode generation — vector, print-correct, K=100 black by default, with proper ink optimization for any press type
Personalized print runs — names, addresses, variable copy and offer text across thousands of unique units from a single data source
Variable image composition — per-unit product shots, headshots, maps, location-specific graphics, charts from live data
Data-driven layouts — prices, specs, dimensions, availability that update from spreadsheet, database, or API feed
Multi-page variable documents — personalized catalogs, custom reports, individualized proposals, event booklets
Postal compliance — address formatting, postal barcodes, automated sortation mark placement, country-specific standards

What 'print-correct' means in practice

Proper CMYK separations — not RGB-converted-to-CMYK at the last step
Correct overprint settings — black text overprints, light elements knock out, no surprises at prepress
Accurate bleed and safe zones — 3mm bleed minimum, critical content never in the danger zone
Fonts embedded, not substituted — PDF/X-1a or PDF/X-4 compliant output
K=100 for all black elements — ink coverage that doesn't surprise anyone at the printing stage
ICC profile-aware color — output matched to your press profile, not generic sRGB

Why custom instead of SaaS

You own the tool outright — no subscription, no vendor lock-in, no price increases next year
It handles your specific data format and workflow, not a generic approximation of what most customers need
Print-correct by default — I've run a press, I know what causes stop calls and reprints
Significantly less expensive than enterprise licensing for the same end capability
Ongoing modifications as your needs change — add a new format, a new data source, a new compliance requirement

Show me your print run. I'll show you what's possible.

EUR120/h. Print-rigorous. First session includes a review of your current output quality -- I'll spot your press problems before they become reprints. You own the code.

madeby.mex.com