In this guide 6 sections
When your jobs follow the standard path of estimate, artwork, press, finishing and dispatch, buy a ready product, because that path is already built and proven. Build custom where coating adds steps. Test the fit by running five real job tickets through a demo, including your messiest coated or laminated job, before you sign anything.
What a ready product already does well
Commercial print management products cover the common path of press, bindery and van, holding customers, price lists, quotes, job tickets, purchase orders for stock and delivery notes. Most also link to the accounts package. Useful.
If your work is labels, cartons or books on standard stocks, that path is probably enough, and a ready product is cheaper to start and proven by other users. It keeps improving without extra bills.
- Quote to job ticket to invoice in one record
- Stock and paper reel tracking
- Delivery notes and proof approvals
- Standard reports on job margin
Where industrial printing breaks the standard path
Industrial work adds processes outside the usual press and bindery, such as a flexible packaging line that prints, laminates, cures for a set number of hours, slits and rewinds. Each step has its own waste. Each has its own queue.
A coating line runs on recipes. Ink viscosity, nip pressure, oven temperature and dwell time belong to the job, and a ready product can store them as a note but cannot enforce the recipe. Nothing warns you when a batch runs outside its viscosity or oven limits, so the deviation surfaces later as a customer complaint.
- Lamination adhesive batches and cure time before slitting
- Anilox roller and cylinder tracking per job
- Roll traceability from raw film to finished reel
- Food contact or pharma batch records
- Customer specific test certificates
Questions that decide build or buy
Ask what the software must do that a spreadsheet cannot, and sort each answer into standard work or something only your plant does. A standard quote and job ticket? Buy. A batch record, a recipe check or a costing rule that nobody else uses is the part worth building, because no vendor will ever prioritise it for you.
Ask who changes the rules. If your costing logic changes monthly and only your estimator understands it, a rigid product becomes a workaround factory that nobody wants to maintain once the estimator retires. Ask what happens when a vendor withdraws a feature you rely on, whether a costing report or a barcode label layout, and note how long the answer takes. Silence is an answer.
A middle path: buy the core, build the edge
Most industrial printers do best with both. Use a ready product for quotes, orders, stock and invoicing, and build a small module for the one unique step, such as lamination batch tracking. Link them by API.
The build stays small. It also keeps your most unusual process under your control, and you should write the interface down as a document so either side can be replaced later.
Run a five ticket test before you sign
Pick five tickets from last quarter. Include your messiest one, the job with coating, lamination and a customer test certificate, then have the vendor key each ticket into a demo, cost it and schedule it. Mark every spot where a person must work around the screen, whether a manual cure time entry, a pasted batch number or a note scribbled on the ticket.
Count the workarounds. A few are fine, such as a manual entry for the certificate number, but a dozen on your best-paying work means the product does not fit. Hand the list to a developer as the first draft of a specification, with each workaround described in the words your operators use.
Build or buy scorecard
Twelve process steps run down the left side of this one-page scorecard, from quote through coating, lamination, cure and slitting to dispatch. Columns show whether a ready product handles each, needs a workaround or needs custom work, with a notes column and a final tally.
Open a blank worksheet to printQuestions owners ask
Is custom software only for large printers?
No. Size matters less than process. A small converter with a unique laminating step may gain more from a custom module than a larger plant on standard work.
Can a ready product be modified?
Some allow custom fields, scripts or an API, but ask exactly what is supported and who repairs your changes after a version upgrade breaks them.
What data should a custom module hold?
Start with the job number, recipe or batch, machine, operator, start and end times, waste and approval, then link the record to the main job so nothing is retyped. Keep it small.
How do I avoid being locked in?
Own the data, get exports in open formats such as CSV, and keep the interface documented in plain language, so either system can be replaced without losing job history.