Template + data
A PDF positioning template can be paired with spreadsheet data so variable information can be generated against the intended artwork positions.
PROJECT STUDY / MERGEFORGE
Turning repeat print-production steps into a focused tool.
MergeForge is a UNKNOT-built variable print production engine designed around recurring PDF, spreadsheet and output-preparation work.
The problem was not one big task. It was a pile of small repeated ones.
Production files often arrive with variable information, positioning requirements, output limits and finishing rules that have to be checked before anything useful can happen. A spreadsheet may drive names, numbers or barcodes. A PDF template needs to stay visually intact. Large jobs may need to be split into practical batches. The same checks happen again and again.
MergeForge was built around that reality. Instead of asking operators to bend every job into a generic workflow, it provides focused processors for recurring production tasks.
The principle is simple: preserve the artwork, preserve the data order, automate the repeated handling around them.
What the current workflow handles
Output splitting
Large output can be divided into practical batches while keeping the original record order intact.
Preflight checks
Checks include POS sequence validation and duplicate reporting for review without silently dropping records.
Local processing
PDF processing stays on the machine. Artwork is not downsampled, and test and production use the same renderer.
Why the implementation matters
A production tool can look correct on screen and still create downstream problems if it changes page geometry, strips useful data or handles one test differently from the real run. MergeForge therefore treats production behaviour as part of the product, not as an afterthought.
The project continues to grow through specific processors for recurring jobs rather than by turning into a sprawling general-purpose design application.
FROM INTERNAL TOOL TO MARKET PRODUCT
MergeForge is being prepared for wider use.
The product grew from real production problems rather than from a feature checklist. The next stage is packaging that capability for other teams without losing the practical, task-specific approach that made it useful in the first place.
We are planning several access levels so smaller operators do not have to buy a large enterprise package simply to automate a few recurring jobs.
Planned tier structure
StarterProBusiness
Exact features, usage limits and pricing are still being defined. We would rather publish those once they are properly tested than put placeholder numbers on the page.
RELATED THINKING
Automation should remove repeated effort, not understanding.
That same principle appears across UNKNOT’s workflow work: define what must stay visible, automate what keeps repeating, and keep the handover practical.