← All case studies

A multi-brand web-to-print platform

A custom print-management platform for a specialist print business that produces payment cards, gift cards and packaging. It handles the whole job in one system: a customer places an order, artwork and variable data are processed, print-ready press sheets are built automatically, files go to print suppliers, and quotes, invoices and purchase orders are raised in the accounting software. Several branded storefronts run on one codebase, each with its own look, customers and rules.

The challenge

Industrial print has very little room for error. One misplaced card on a press sheet, one barcode that doesn't match its data row, or one wrong colour space can waste a full print run. The business needed to:

  • Take orders from several branded sales channels, each with its own pricing, workflows and customer-specific rules
  • Turn customer artwork and large variable-data files (unique numbers, barcodes, QR codes) into press-ready PDFs
  • Treat card data under strict security rules
  • Send jobs to several print suppliers, each wanting its own file format and delivery method
  • Keep finance in sync without anyone re-keying data

The solution

A hybrid PHP and Java architecture

The core application is built on Laravel 11 (PHP 8.4) with a Vue 3 front end. PHP isn't the best fit for the heavy PDF work, so the platform includes a dedicated Java imposition and PDF engine built on Apache PDFBox. It is made up of around 13 purpose-built programs that handle:

  • Data-driven imposition: arranging hundreds or thousands of unique cards onto press sheets, with layouts specific to each press and finishing format
  • Variable-data merging: placing each record's numbers, Code 128 barcodes and QR codes onto its own card
  • Spot-colour and layer handling for embellishments such as foils and special finishes, imposed on their own layers
  • Proof generation, page extraction, concatenation and raster previews

PHP orchestrates the work and hands off to Java through a controlled process bridge, with memory limits, exit-code handling and full logging. Each language does the job it is best at. The platform also uses several PHP PDF libraries for documents like delivery notes, job bags, labels and order forms.

An asynchronous production pipeline

Proofing and imposition run in queued background jobs. The pipeline waits for proofs, only then builds impositions, and only once those exist does it mark a job as sent to print. Real-time websocket updates show users progress as it happens, so nobody watches a spinner while a large job processes.

Multi-brand from one codebase

The platform detects which branded storefront a visitor is on from the subdomain. It validates that storefront and applies its own stylesheet, which the build pipeline compiles automatically. Adding a new brand means adding a stylesheet, with no change to the build configuration.

Layered, inheritable business rules

Instead of hard-coding rules for particular customers, the platform has a typed settings engine with inheritance. A rule can be set globally or for a client, a customer, an order or a single batch, and the most specific setting wins. A separate chain does the same for print suppliers. Behaviour that once needed a developer can now be configured for an individual order.

Batches, quotes and approvals

One order can contain several batches, each with its own artwork, data file, delivery addresses and approvals. Re-quoting resets only the quote approval. Uploading new artwork resets only that batch's approvals. Print is blocked until the data rows exactly match the approved quantities.

Security-first data handling

Card data files are encrypted at rest. They are only decrypted for the moment they are being processed, and an hourly purge removes any plaintext that remains. Shared library artwork is soft-deleted, then removed overnight once no order uses it any more.

Supplier and finance integration

  • Print files go to each supplier in its own format (XML or JSON) over SFTP, and transfers outside production are blocked
  • Purchase orders are created automatically: one per supplier across batches, with deliveries combined per address
  • A full integration with Xero (OAuth, automatic token refresh, status sync) creates quotes, invoices, purchase orders and contacts, applies each brand's invoice styling, and links supplier bills back to batches for financial reporting

A rich, international interface

  • A canvas-based artboard editor (Konva.js) for laying out cards and positioning data fields visually
  • About 150 Vue components covering ordering, proofing, approvals, dashboards and charts
  • Four languages, with an in-app translation editor so staff can edit wording without a deployment
  • Bulk order import through a separate, token-secured REST API that processes uploads in chunks and reports errors for each row
  • SMS and email notifications, plus barcode and QR generation in both PHP and Java

Production-grade operations

The platform runs in Docker with Apache, PHP-FPM, PostgreSQL 16, Redis, Postfix, websockets and supervised queue workers. Around 30 maintenance commands handle data migrations, backfills, health checks and purges. Errors are tracked centrally and alerts go out in real time.

AI-assisted engineering

AI-assisted development played a large part in moving the platform forward. Working alongside an AI coding assistant made it possible to:

  • Refactor safely at scale: moving the system from single-artwork orders to a multi-batch model, and auditing and removing old order-level fields across the whole codebase
  • Replace hard-coded customer rules with the configurable settings engine
  • Diagnose performance and infrastructure issues in proof generation, cache-key collisions between web and background processes, and stale queue workers
  • Strengthen security, including the encrypted-at-rest pipeline for card data
  • Speed up delivery of new features, such as single-column EAN-13 barcodes in data files and consolidated purchase orders

The AI didn't replace engineering judgement. It extended it, so a small team could handle architectural changes that would normally need a much larger one.

Results

  • End-to-end automation from order to press-ready file, supplier hand-off and accounting
  • Production lead time reduced by more than 3 weeks, with customers across the world
  • Several brands served from one maintainable codebase
  • Fewer print errors, because the system checks data and approvals before anything reaches a press
  • Customer-specific rules moved from code into configuration
  • Security-conscious handling of sensitive card data

Need a production pipeline that just works?

If your business runs on complex orders, files or integrations, get in touch to talk through what an automated platform could do.

hello [at] firestormdigital [dot] net