PReS Language

PReS is a procedural, domain-specific scripting language created by PrintSoft for the design, composition, and high-speed production printing of personalized documents. Where general-purpose languages aim to do anything, PReS was built for one demanding job: ingesting raw data and turning it — at industrial volumes — into precisely laid-out, individually personalized documents such as bank statements, insurance policies, utility bills, and direct mail. The name is commonly expanded as “Print Description Script,” reflecting a language “dedicated to the processes of data manipulation, editing, and formatting associated with production printing.”

PReS belongs to the world of variable-data printing (VDP), where every page in a run can differ — a different name, a different balance, a different set of inserts — yet all must flow through the same composition logic and out to the same high-speed press. For decades it was marketed as one of the most powerful and flexible document-composition languages available for that task.

History and Origins

PReS comes from PrintSoft, a company founded in 1989 in Melbourne, Australia. PrintSoft described itself as a pioneer of PC-based high-speed variable-data composition technology, building tools that let organizations compose, process, deliver, and store business documents in both paper and digital form. PReS became the core scripting engine of that product line.

The exact year PReS first appeared is not well documented publicly. The evidence points to the early 1990s, shortly after PrintSoft’s 1989 founding: by the late 2000s the language had reached version 6.x, reportedly with earlier 3.x and 4.x releases preceding it, which is consistent with an origin around the early-to-mid 1990s. Because no authoritative first-release date is published, the dates here are given approximately and the year shown should be read as an estimate rather than a verified milestone.

The company’s technology was, according to Australia Post, originally created to help a major financial institution consolidate its desktop mail-production processes — a fitting origin for a language whose entire reason for existing is high-volume, rules-driven correspondence.

Design Philosophy

PReS reflects the priorities of the production print room rather than those of general software engineering:

• Data in, documents out. The language is organized around reading structured input data, manipulating and editing it, and formatting it onto pages — the full pipeline of variable-data composition.
• Personalization at scale. Conditional logic and rules let a single script branch on each record, so one program can produce thousands or millions of distinct, individually correct documents.
• Production-grade output. PReS was designed to feed high-speed presses directly, emitting the page-description and print-stream formats those devices expect rather than generic on-screen documents.
• Precision layout. Exact placement of text, graphics, barcodes, and logos on the page is a first-class concern, because the output is physical mail subject to inserter and postal constraints.

Key Features

• Variable-data composition — the central capability: merging data with templates so that each output document is personalized to its recipient.
• Multiple output formats — the PReS suite is documented as supporting print and image formats including AFP/AFPDS, PCL, PostScript, IJPDS, PDF, EPS, PNG, TIFF, and JPEG, letting the same composition logic drive many device types.
• Business rules and conditions — built-in conditional logic to add or suppress content, insert barcodes and graphics, control page numbering, and manage envelope-inserter instructions.
• High-volume orientation — the engine was built for the throughput of production bureaus; later versions (PReS 6.0 onward) took advantage of multi-threading on Windows to improve performance on large runs.

Note: PReS is proprietary commercial software, and a full, openly published language specification is not available; the feature descriptions above are drawn from vendor and user documentation rather than a formal standard.

Evolution

PReS evolved both as a language and through a long chain of corporate ownership:

The most significant technical pivot came in 2015, when Objectif Lune launched PReS Connect — described as the result of four years of R&D after acquiring PrintSoft. PReS Connect re-platformed the PReS heritage onto Objectif Lune’s Connect architecture, pairing a design tool with a PReS Workflow automation engine that dispatches data, controls plugins, and routes output for print, email, or fax. Under Upland, this lineage continues as OL Connect.

Current Relevance

The classic PReS scripting engine belongs to an earlier generation of variable-data tools, but its lineage is very much alive. Today the technology lives on through PReS Connect / OL Connect under Upland Objectif Lune, which continues to serve customer-communications management (CCM) needs — composing, automating, and delivering transactional and promotional documents. Organizations with long-running PReS deployments — particularly in financial services, insurance, utilities, and mailing bureaus — have in many cases carried that investment forward into the Connect platform.

PReS is proprietary Windows software, not an open-source or freely distributable language, so there is no official public Docker image or open toolchain. Its audience has always been print-production professionals rather than general developers.

Why It Matters

PReS is a window into a specialized but economically important corner of computing: the industrial production of personalized documents. Long before “customer communications management” was a marketing category, languages like PReS were solving the hard problem of turning a database of customers into millions of individually correct, press-ready pages. PrintSoft’s early bet on PC-based variable-data composition helped move that work off expensive specialized hardware and onto commodity machines.

Its story also illustrates how a focused domain-specific language can outlive its original creator through acquisition: born at a Melbourne software company in the early 1990s, passed to a national postal service, then to a Canadian document-automation firm, and finally into a large enterprise-software portfolio — yet still recognizable, decades later, in the composition engine behind today’s customer-communications platforms.