Nº 02 · QUALITY TECHNOLOGY
Catch it before the press does.
A file that looks perfect on screen can still fail on press — short bleed, RGB color, type too small to print cleanly. PackOS inspects against the spec like a prepress veteran, instantly, every time. By the time the press sees your file, the expensive mistakes have already been found — here, where they cost nothing.
Nº 01 How it works
Three layers of "are you sure?"
The file, checked against print rules
Bleed, separations, spot naming, overprint on technical inks, ink counts — the failures a converter would bounce, caught up front. Deterministic fixes are proposed with a before/after; raster fix lanes are in preview.
The proof, checked against the paperwork
A vision pass checks the rendered proof against the stated spec — dimensions today, colorways and coverage next — so the picture and the record can't quietly disagree.
The vendor, checked against the approval
Three-way match: what you approved × what was sent × what the plant proofs back. If any corner drifts — a swapped substrate, a nudged panel — it surfaces before production.
Nº 02 The instrument
Find the five.
This label has five press-killing defects planted in it. Click or tap where you think they are — then let the engine show you what it found, in one pass.
- YOU FOUND
- 0/5
- PACKOS FOUND
- –
- ENGINE SWEEP
- –
- AUTO-FIXABLE
- –
Nº 03 The spec sheet
What the quality engine does.
Preflight & auto-fix
AvailableChecks and corrects bleed, dieline separation and spot naming, overprint on technical inks, and ink counts against real print rules — the failures a converter would bounce, caught up front. Deterministic fixes apply on your say-so; raster lanes (resolution, image repair) are in preview.
REPLACES · the 48-hour "your file was rejected" email loopVision referee
In PreviewMeasures the rendered proof against the stated spec and flags where they disagree — dimensions, colorways, coverage — so the picture and the paperwork can't drift apart.
REPLACES · trusting that the pretty render matches the recordThree-way proof match
AvailableReconciles the vendor's proof against the dieline and the record, so nothing quietly changes between what you approved and what the plant makes.
REPLACES · eyeballing two PDFs side by side at 11pmPrint-ready output
AvailableExports PDF/X-4 with a press intent (GRACoL and friends), a measured color gamut, and out-of-gamut recommendations — flagged before plates are cut, not after.
REPLACES · discovering the brand orange doesn't print at the press checkStandards-clean handoff
AvailableLayer naming to a published standard and ISO 19593-1 processing-step metadata a converter's prepress can consume directly — a handoff that reads the same on both ends.
REPLACES · "which layer is the die?" phone callsRolling this out across a brand portfolio? Request an Enterprise Preview →
None of this is theoretical. Every check in this engine earns its place the same way: it is a failure Calyx has actually eaten — a bounced file, a press stop, a reprint — encoded so it never happens twice.
Nº 04 The impact
What one caught error is worth.
Run the math on a press error that ships: the reprint, plus the weeks.
- SHIPPED · REPRINT
- –
- SHIPPED · SLIP
- 3–5 WKS
- CAUGHT UP FRONT
- $0
THE STACK One record flows through all four engines
RECORD · ONE SPEC — EVERY ENGINE READS THE SAME FIELDS
Nº 05 Questions
What quality teams ask.
Does auto-fix change my artwork without asking?
No. Fixes are proposed with a before/after and applied only on your say-so. Some classes (extending bleed from existing art) are safe and one-click; judgment calls stay yours. Every applied fix lands on an append-only, content-hashed change ledger — reversible and auditable.
I'm uploading unreleased artwork. Where does it go?
Analysis runs in your browser session; storage is a private vault; we never train on your artwork and delete on request. The full controls are written down in the security policy.
My converter already preflights. Why duplicate it?
Their preflight protects their press, days after you've committed. This one protects your timeline, before you send anything — and the three-way match keeps watching after they proof it back.
What if it flags something my printer would accept?
Findings are advisory, not gates. Each one shows the measured value against the rule it tripped — bleed in millimeters, effective resolution, ink count — so you can judge it in seconds, and nothing blocks your quote. The finding rides the quote record, so if you overrule it and it bites later, nobody is reconstructing what was known when.
What happens when the engine can't verify something?
It says so. Findings the file can't support are reported as unverifiable — with the reason — instead of guessed. Barcode grading, which needs a hardware verifier on a printed sample, is explicitly excluded from the press-ready call.
Your file has opinions. Hear them before the press does.
Upload artwork and get the findings — what passes, what fails, what can be auto-fixed — in about a minute.
No signup · files stay private · how we handle them