It’s 4pm on a Thursday. Twelve short-run jobs need to go out tomorrow, someone is re-keying specs from the webshop into the MIS, and the press operator is waiting on a file that’s sitting in someone’s inbox. Sound familiar?
Third-generation family business or newcomer, the pressure is the same: more jobs, smaller runs, tighter margins. Automation is how print companies keep up. In this post we’ll look under the bonnet at how automation works on the CoCoCo Platform, and what it changes on your shop floor.
Why automation matters for print
Manual processes are slow and error-prone. Every time someone retypes a job ticket or chases a status update, time disappears and mistakes creep in. Automation takes those repetitive tasks off your team’s plate, so you can handle more jobs and deliver faster.
Here’s what that looks like in practice:
- More output from the same team: jobs move from step to step without waiting for someone to push them along.
- Lower costs: less manual handling, less waste and fewer reprints.
- Consistent quality: automated checks apply the same rules to every job, every time, so your output meets customer expectations and protects your reputation.
Automation starts with connected data
Automation is only as good as the data it runs on. If your MIS, prepress and presses each describe the same job differently, any workflow you build on top will trip over the gaps.
That’s why the CoCoCo Platform starts with the Data Model. Every vendor speaks its own dialect: JDF/JMF (Job Definition Format and Job Messaging Format) in theory, local accents in practice. The Data Model translates those signals into one standardised, versioned schema, so a job, a press or a substrate means the same thing everywhere.
Integrations connect your business software, such as your MIS, webshop and prepress tools. On the shop floor, Edge Apps run on a CoCoCo controller on your local network, right next to your presses. They receive MQTT messages, monitor OPC UA values and poll SNMP or Modbus devices, with small Lua handlers deciding what to do with each reading.
All of it is available through the Pulse API, one GraphQL interface that your operators, machines and webshop all query. Not a GraphQL person? Magic Query lets you ask in short, readable strings such as jobs?status=COMPLETED,limit=10 and get flat JSON back.
How a workflow actually works
On the CoCoCo Platform, automation lives in the workflow engine. A workflow is a flowchart that runs itself: steps, called nodes, joined by connections, called edges. Each node does one job. It might query data, test a condition, run a Lua script, call an external service, wait, or repeat work for every item in a list.
A workflow starts when something happens. You can trigger one:
- on a schedule, such as every night at 10pm;
- when a record changes on the platform, for example a new order;
- when a connected device publishes a message;
- when a webhook is called, say by your webshop;
- when an Edge App reports an event;
- when a file lands in a watched folder.
Steps can run one after another or in parallel, and branches split and rejoin as the job needs. Each node’s result is available to every step after it, so data flows through the run instead of being copied across by hand.
Back to Thursday afternoon
Here’s how that 4pm scramble could look with a workflow in place.
An order arrives from the webshop and calls a webhook. The workflow creates the job on the platform through the Pulse API, complete with parts, quantities and substrate. It then runs a PDF preflight on the artwork against the standard you’ve chosen, PDF/X-4 for example, and saves the report on the job.
A switch node checks the result. Clean files carry on to imposition, where the platform plans the layout and places the pages on the press sheet. Files with problems go to a task for your prepress team, so a person decides what happens next. Either way, a message node tells customer service where the job stands.
Nobody re-keyed anything, and nobody went digging through an inbox for a file. Every run is recorded as an execution you can open later: its inputs, the status and output of every step, and any error. When something goes wrong, you see exactly where, instead of flying blind.
Automation doesn’t mean handing over the keys
Fully hands-off isn’t always what you want. Some decisions need a person: approving a colour proof, signing off a rush job, choosing which press takes the overflow.
Task nodes handle this. The workflow creates a task for a person or a team, pauses, and carries on once the task is resolved. You can also hand routine decisions to an AI agent that picks from the task’s predefined outcomes, with a fallback that creates a task for a person whenever the agent can’t decide. Human-in-the-loop by design.
Control goes further than that. Each workflow runs under its own execution identity, a bot user whose permissions decide what it can read and change, so you give it only the access it needs. You edit a draft, save it as a version and choose when to make it active. Activating a new version never rewrites an old one, so you can always see what ran and when.
Room to grow, and the data to grow with
As volumes rise, the same workflows handle the extra work. Adjust them for different job types and volumes, from a run of 50 business cards to a large catalogue job, without rebuilding from scratch. When a step needs logic of its own, a Lua script node gives developers direct access to live data with zero infrastructure setup.
Better data comes with it. MicroSQL gives you a safe, read-only SQL schema for reporting, and workflows can run reports on a schedule, so the morning production summary lands without anyone building it by hand. Producibility audits check a job against current progress data and flag what’s at risk before the deadline slips. And ml_predict nodes run machine learning models trained on your own production history, because algorithms are only as smart as the information they receive.
That’s the shift from guessing to knowing: real-time data on where the bottlenecks are, and the tools to do something about them.
How CoCoCo helps you automate
No two print businesses are alike, so we don’t hand you a one-size-fits-all package. Our team works with you to build an automation plan around your existing systems and the way you actually work.
Most shops start small. One workflow for order intake, say, or a nightly report. Once that’s running, the next one gets easier, because the data is already connected. And because the CoCoCo Platform is open, you can bring in new presses, finishers and software as they arrive, without starting again.
Support every step of the way
Moving to automation can feel daunting. CoCoCo provides full onboarding and ongoing support, and our experts are on hand to help you overcome challenges and get the most from your investment. We’re print people, and we want to be a partner, not just a software vendor.
Ready when you are
We know adopting automation is a big decision, and now might not be the right time for every business. That’s fine. It’s still worth understanding what automation could do for you, so you’re ready when the time comes.
That 4pm Thursday scramble only happens when your systems aren’t talking to each other. Connect them, and Thursday afternoon gets a lot quieter.
