One system between customer artwork and production.
Prepta takes the file the customer actually sent, works out what it is, checks it against the rules of the workflow it is going into, repairs what can be repaired safely, validates the result and escalates the rest. Output is a production file with a record of everything that changed.
Object model
- Job
- One customer order. Holds files, the assigned production profile and the current status.
- File
- A single piece of artwork as supplied, preserved unchanged.
- Preflight
- One run of the profile’s checks against a file version, with results and severities.
- Issue
- A single finding: what, where, the measurement, and the policy that applies to it.
- Repair
- One applied transformation, with its parameters and the rule that authorised it.
- Production profile
- The rules for one workflow: requirements, tolerances, automation policy.
- Version
- An output state of a file. v1 is always what the customer sent.
- Review
- An open decision assigned to an operator, with the recommendation attached.
Accepts what customers actually send
Files arrive as PDFs and as images, from a portal, an inbox or a member of staff. Prepta fingerprints each one, records it as supplied, and classifies the likely source before any judgement is made about quality.
Source classification is reported as a likelihood with a confidence level. It informs the recommendation; it does not override profile rules.
Formats today
PDF, JPEG, PNG, TIFF and SVG natively; AI and PSD with conditions; EPS and HEIC through a recorded conversion. InDesign, CorelDRAW, Office and web images are recognised and turned away.
Fingerprinting
Duplicate and near-duplicate submissions identified across a job.
Source classification
Camera photo, screenshot, web asset, design-tool export, Office export, design application.
Original preservation
The supplied file is stored unchanged as version 1.
Checked against your workflow, not a generic standard
Every check runs against the production profile assigned to the job. The same file can pass for a banner and fail for a sticker, which is the point.
Findings carry a severity (error, warning or information), so the report can be acted on rather than read in full.
Geometry
Page size, trim and bleed boxes, orientation, dimensions against the order.
Colour
Colour spaces, output intent, spot colour definitions, overprint.
Images
Effective DPI at final size, compression, colour depth.
Text
Font embedding and subsetting, minimum sizes.
Output
Transparency, PDF standard compliance, cut contours, vector integrity.
Applies only what the profile authorises
Repairs are policy-driven. Each issue type carries an automation policy in the profile, and Prepta cannot exceed it. Enabling automation is therefore a decision you make per rule, not per file.
Policies: AUTO runs without a click when your workspace turns on Auto-fix safe issues, and otherwise when someone starts it. AUTO + REVIEW runs once a person confirms its warning. REVIEW proposes only. BLOCK stops the job. IGNORE records without acting.
Colour
RGB to CMYK through your production colour profile: automatic for images whose profile is known, approved by a person for PDFs; spot colours stay separations.
Bleed
Mirrored from the page edge to the required amount and labelled reconstructed; in a PDF, live text or lines at the edge go to review.
Transparency
Flattening where the profile requires flattened output.
Cut contours
Generation where none exists: the trim rectangle as a safe fix, a traced outline after you confirm.
Vector
Removal of empty paths and duplicate points that do not change appearance.
Re-checks its own output before releasing it
A repaired file is preflighted again against the same profile settings. A job is only marked ready when nothing is left open, and every check stores the profile settings it ran against.
Nothing is released on the assumption that a repair worked.
Re-preflight
Full check of the output file, not only of the changed properties.
Standard output
A production PDF with trim and bleed boxes set. Prepta does not write PDF/X identification.
Status
Per job: ready only when nothing is open, otherwise review or open findings. Per file: send as is, open this one, or do not send.
Profile settings
Stored with every check, so a later rule change does not rewrite history.
Hands over the decisions with the evidence attached
Escalations arrive as a queue of decisions, each with the measurement behind it, the affected area, and a recommendation. Every automatic change made before the escalation is visible in the same place.
The customer file is never overwritten, so any repair can be compared against the original or discarded.
Review queue
Open decisions per job, with recommendation and measurement.
Audit trail
What changed, the values used, the rule that permitted it, who confirmed it.
Versions
Every output state retained and comparable against v1.
Reporting
Per-job report suitable for sending to the customer.