Automated preflight: stop fixing files, start printing them

Infigo checks every customer file against the job that was actually ordered, before they reach checkout. Errors get caught, corrected or flagged automatically. Your prepress team only ever sees print-ready files.

Pitstop warning on Infigo MegaEdit interface
Problem

The job is fine until it isn't

A job makes it through checkout, into the queue and onto the press. Then someone notices the artwork was RGB, the bleed was missing, or the fonts were never embedded. The reprint costs money and the delay costs a customer.

 

It is getting harder. More customer artwork now comes from tools like Canva and Adobe Express, built by people who have never prepared a file for print. Prepress touch time, not press time, is what caps output in most shops running real volume.

 

Infigo moves that check upstream. Because the storefront already holds the product specification, every file is validated against the job that was actually ordered, not against a generic profile.

Print operator reviewing printed material
How it works

File in. Print-ready file out. No prepress step in between.

Industrial Print Operator working on print machinery
  1. 01

    Warnings while the customer designs

    In MegaEdit, the editor flags problems during the design session itself. Low-resolution images, content sitting outside crop marks, and colour space issues surface while the customer is still working. Colour space handling passes through to Enfocus PitStop, since MegaEdit builds the layout rather than processing colour profiles itself.

  2. 02

    The check at submission

    When a customer uploads a print-ready PDF, or finishes a MegaEdit layout, Infigo runs the assigned Enfocus PitStop profile. This happens before checkout completes. The customer gets a pass or fail result, a warning, or an auto-corrected file, on screen.

  3. 03

    Correction and routing

    Where PitStop can fix an issue, it fixes it without an operator. The validated file routes through Infigo Sync to the correct output device, and the order status carries the preflight result into your management information system (MIS).

Capabilities

Every check built for production, not just presentation

Preflight is not one feature. It is a set of components you configure to match how your operation runs.

01

Catch it while they are still designing

MegaEdit flags low-resolution images and content outside crop marks during the design session, before the customer reaches an upload step. Colour space handling passes through to Enfocus PitStop.

Why it matters: Problems fixed during design never become support tickets or reprints.
Hexcodes floating around designer reviewing artwork
02

The check runs before they pay

Infigo runs the assigned PitStop profile at submission, before checkout completes. Supported on Multipart Upload products and on MegaEdit in both Editor and Upload configurations.

Why it matters: A broken file never becomes a paid order you have to unpick later.
Cloud Icon floating above laptop
03

Fixed without an operator touching it

Where PitStop can correct an issue, it does. RGB to CMYK conversion, adding missing bleed, and similar problems with one correct answer are handled automatically. A Check profile validates, a Fix profile corrects.

Why it matters: Routine fixes stop consuming skilled prepress time.
Infigo favicon and warning on a block on a laptop
04

One profile instead of one per variant

Sell booklets in A5, A4 and A3 and the static approach needs three profiles to build and maintain. Infigo passes the ordered dimensions into one profile at runtime through a Job Ticket XML file, so A4 validates against 210 by 297 and A5 against 148 by 210. Change the rule once and every size inherits it.

Why it matters: Your catalogue grows without your profile maintenance growing with it.
Floating human icon on laptop with finger about to touch it
05

A record of what happened to the file

Infigo can generate a PDF report for the customer to download, or a PDF and an XML report together, listing every warning raised, error found and fix applied.

Why it matters: Customers can see what was wrong and what was fixed, so they stop asking you.
Floating PDF icon above laptop
06

Do not re-check what already passed

A storefront reorder references the already-validated file and skips the check. Products categorised as approved reprint items can have preflight suppressed altogether.

Why it matters: Repeat buyers are never blocked by a rule that tightened since they last ordered.
Reorder icon floating above hand
07

Enforce rules that do not exist out of the box

Infigo runs standard PitStop profiles rather than a restricted subset, so Action Lists work too. Where a native check does not cover a requirement, an Action List builds the logic instead.

Why it matters: An unusual production requirement does not have to become a manual check.
Pitstop Pro icon floating above laptop
08

From validated file to the right press

Infigo Sync routes the passed file to the correct output device. The preflight result travels with the order into Tharstern, printIQ and CERM through native plugins. Webhooks and the Connect REST API expose the same status for anything custom.

Why it matters: Failed work never reaches the production queue unnoticed.
API icon floating with Tharstern, printIQ, and CERM logos
control

You decide what happens when a file fails

This is the part most people ask about first. Preflight is not a single behaviour. Every check you configure has three possible outcomes, and you choose which applies.

Reject
Fix
Warn
What the customer sees
An error message and a downloadable report. The Continue button is disabled until they upload a corrected file.
The file is corrected automatically and the order proceeds.
A flag explaining the issue. The order still proceeds.
When to use it
Problems that will ruin the job. Wrong trim size, missing critical content.
Issues with one correct answer. RGB to CMYK conversion, adding missing bleed.
Judgement calls. Resolution that is low but workable for the viewing distance.
Order proceeds
—
✓
✓

Preflight stops being a technical gate and becomes a policy you set. Strict where it matters, permissive where it does not.

Trusted by print businesses running real volume

REAL-WORLD USE CASES

What this looks like in practice

Commercial print

A corporate portal means hundreds of people who have never prepared a print file submitting artwork. Preflight catches the problems at source, and a reorder references the file that already passed.

Labels

A brand running dozens of SKUs off one palette drifts apart without something holding them to a standard. Preflight checks each job against its own spot colour names and colour rules.

Packaging

Structural artwork is checked by spot colour name and PDF layer, so a path set to the wrong cut swatch is caught at checkout rather than at the die.

Large format

Resolution that fails on a business card is fine on a banner seen from ten metres, and a banner supplied at 300 DPI just clogs the RIP. Infigo enforces a ceiling as well as a floor.

Impact

What changes when preflight stops being manual

Before Infigo
After Infigo

An operator opens every incoming file and checks it by hand.

Every file is checked automatically at submission.

Problems surface in prepress, after the customer has paid.

Problems surface on screen, before checkout completes.

Skilled prepress time goes on RGB conversions and missing bleed.

Routine fixes are applied automatically, with no operator involved.

A broken file can sit in the queue undiscovered until morning.

Only validated files enter the queue, so lights-out running is safe.

Every product variant needs its own profile to build and update.

One profile resolves per order, and a rule change propagates everywhere.

Job details are re-keyed from files that may still be wrong.

The job ticket is populated from a file that already passed.

Infigo's most purchased module

Connect: PitStop is the most adopted integration across the Infigo platform.

Control Media doubled order volumes year on year

and grew small-run digital orders eightfold, reaching 3,000 order lines in a single month.

Read their story here

In Practice

What changed when TAG stopped fixing files by hand

Talient Action Group is a print and marketing provider in Manchester, New Hampshire, part of a group that also includes a marketing agency and a creative studio. Before Infigo, corporate clients emailed print PDFs and TAG’s team preflighted and corrected every one by hand.

 

It was the biggest bottleneck in the business, and Digital Services Manager Marc Forest is direct about what it cost them.

"We never knew how clean or broken the files would be, and we couldn't control how they were sent to us. That uncertainty killed our efficiency and ate into all the profit." - Marc Forest, Digital Services Manager, Talient Action Group

Today those same clients order through their own branded portal, and every file is validated before it reaches production.

"Every file in our print portal is fully vetted, so we're not dealing with errors or reprints. The whole process is so efficient now, we can actually price our projects in a way that makes sense."
FAQ'S

Frequently Asked Questions

Didn’t find the answer?

No worries! If you have any other questions or need more information, feel free to reach out directly. We’re always happy to help and make sure you feel confident. Let’s chat!

Book a demo
  1. Automated preflight software checks print files against a defined specification without an operator opening them. It validates colour space, resolution, fonts, bleed, trim geometry and PDF structure, then either rejects the file, corrects it automatically, or flags a warning. Infigo runs that check inside the ordering process, before the customer completes checkout.

  2. Infigo’s preflight runs on Enfocus PitStop, the industry standard engine. What Infigo adds is where it runs: inside the ordering process, checking each file against the specification the customer actually ordered. You license the Enfocus software separately and build profiles in PitStop Pro, then upload the .ppp file into Infigo. Existing profiles work unchanged.

  3. Anything the engine can check. Infigo runs standard .ppp profiles rather than a restricted subset, so the full check set is available: page and layout geometry, colour spaces, image resolution, fonts, trim, crop and media boxes, and PDF structure and standards compliance. Where a native check does not cover your requirement, an Action List builds the logic instead.

  4. At submission, before checkout completes. This is front-of-house preflight: the customer uploads or finishes their file, Infigo runs the assigned profile, and the result appears on screen before payment. In MegaEdit, quality warnings surface earlier still, during the design session itself. Back-of-house checking after the order is placed is also possible.

  5. No. Connect: PitStop runs natively inside Infigo and does not require Switch. If you already run Switch, the two work together: the customer-facing check happens in Infigo at the point of order, and heavier prepress automation continues downstream in Switch. Connect: Switch is a separate integration for job, asset and status exchange.

  6. Yes, and there is no fixed list of what can be mapped. Any variable defined in a PitStop profile can pull from Infigo at runtime through a Job Ticket XML file: customer-selected attributes like stock or lamination, specification attributes like page count and orientation, or fixed constants. One profile then enforces trim, bleed, colour space and page count across an entire catalogue.

  7. Not unless you want them to. A storefront reorder references the already-validated file and bypasses the check, so a repeat buyer is never blocked by a rule that tightened since they last ordered. Products categorised as approved reprint items can have preflight suppressed entirely, which keeps known-good static PDFs out of the queue.

  8. Preflight operates on PDFs. Multipart Upload products can additionally accept supporting assets including PSD, AI, EPS, JPEG and PNG. The default upload ceiling is 5 MB, which administrators raise in Infigo settings. For print-ready multi-page PDFs, Infigo recommends setting it to 100 MB or higher. MegaEdit .mex packages have a separate, independently configurable limit.

  9. Multipart Upload products, and MegaEdit in both Editor and Upload configurations. In practice, any product where the customer supplies or builds a print-ready PDF. If you have a product type not listed here, it is worth asking, because the documented list covers the common cases rather than every possible configuration.

  10. Yes. Native plugins for Tharstern, printIQ and CERM carry the order status across. For anything else, webhooks and the Connect REST API expose the validation state, and Connect: Flow maps it into a custom schema. The validated file itself routes to the correct output device through Infigo Sync.

  11. Uploading profiles and assigning them to products is done in the Infigo admin under Configuration > Resources > PDF Profile Setup. Dynamic profile configuration, where product attributes feed the profile at runtime, is covered in a structured technical workshop. Infigo also offers professional services if you would rather have profiles authored for you.

  12. Connect: PitStop is a paid module rather than a core platform feature, priced on request. Most customers add it once their storefront is live and order volume justifies it, though operations already losing prepress time to file errors typically include it from launch. The Enfocus licence is purchased separately.

See it in Action

See preflight running against your own product specifications.

Book a demo and we will show you the check, the correction, and the handoff to production.

Person working on laptop and notebook

Prefer to Explore First?

Watch the Platform Walkthrough