How it works · Books, diaries and commercial print

See where your print margin goes

Verbal proofs, makeready waste, missing covers and rush overtime cost you every week. Walk through your print floor, tick what you see, and find out what you can save when the floor records its own work.

Takes about four minutes. Nothing is submitted, nothing is sent. The list stays in your browser.

A press does not lose money in one big event. It loses it in makeready sheets, plate remakes, gathering errors, foiling rejects and outsourced binding nobody measured. Each one is small. But there are hundreds of them a year, and none show up in any report.

The other problem is the calendar. Educational titles land together and tender dates do not move. Diaries are worse: eleven quiet months, then every corporate client wants their logo foiled on 4,000 books before the first week of January. With that rush, there is no time to check anything twice. A wrong logo goes to print on Tuesday and is found on Friday.

Below is the process, stage by stage, as it really runs in most presses. Read the left column and tick what is true for you. There is no form, nothing gets submitted, and nothing is sent anywhere.

Tick every line true in your factory.

Be honest. Nobody is watching. Each one you tick lights up the way the same moment runs on Prodman ERP, and adds what that problem is quietly costing you every year.

How book and diary printing runs today
The same moment, on Prodman ERP

Estimate and quotation

You quote from what the same kind of job actually cost.

Every closed job carries real makeready, real paper consumed, real binding hours and real rejects. The next estimate is built on those.

Stop discovering in March that the biggest job of the season was the one you lost money on.
See the module
Every open quotation has an owner, a date and a reminder.

Quotes sit in a pipeline with a status. Anything untouched for a week gets flagged on its own.

Your win rate becomes a number you can read, not a feeling you have.
See the module
One order number holds the whole specification, from enquiry to lorry.

Trim, extent, paper, binding style, foiling, lamination, quantity and every revision sit on one record everyone reads from.

The office and the floor stop working from two different versions of the same job.
See the module

Artwork, proof and approval

No job starts until an approved version is on record.

The client approves the exact file, on the portal, with a name and a timestamp attached. Nobody can mix up version 4 and version 2 again.

No more reprint fights. The approval is in writing, with a version number.
See the module
The floor cannot start a job that is not approved.

The check sits in the system, not in someone's memory under deadline pressure. No shortcut will start that work order.

One prevented reprint of a cover run or a signature pays for a year of software.
See the module
Every approval and every change is on record, with a date and a name.

A change after approval shows up as exactly that, in writing, and the approval check opens again by itself.

Late changes become a cost you can bill, not a gift.
See the module

Planning the load

Every job, every signature, every machine, on one board.

The production board and Gantt show the whole press loaded against real capacity, readable by anyone who should see it.

Planning no longer stops when one man is away.
See the module
You see the load on a chart before you say yes.

The Gantt shows every accepted job against real machine and line capacity. An order that will not fit shows up in September, while you can still act.

You take the orders you can deliver and price the ones you cannot afford to rush.
See the module
The system works out the sheet and signature plan. Your man checks it.

Extent, trim and sheet size set the forme plan. It goes with the work order, not on a loose sheet.

Paper is the biggest cost you have. This is where you save it or lose it.
See the module

On the floor

Two scans and two numbers, and the whole press is up to date.

The operator scans the job, scans the machine, enters produced and rejected. That is all the data entry your floor does.

The floor tells you where each job is. You stop walking all season.
See the module
Makeready and spoilage are entered at the machine, per job.

The operator enters produced and rejected. Spoilage rolls up by machine, by operator and by job, in rupees.

Once makeready is a number, it starts to fall. You cannot cut what you cannot see.
See the module
Every entry carries who ran it, on which machine, on which shift.

Each scan has a name on it. Output and rejects link to a person and a shift, with no register to fill.

You learn which of your seasonal hands to call back next year, and which not to.
See the module
Every stoppage is logged at the machine, with a reason.

Downtime hours add up per machine and per cause, all year.

You can name the machine that costs you most, with the hours to back up replacing it.
See the module

Paper, board and stores

Stock is checked against the job before the job is released.

Requirement from the forme plan, live godown balance, and a low-stock warning early enough to buy one lot instead of two.

One lot, one batch, bought at a normal price instead of a panic price.
See the module
Stock moves when the floor moves it, and buying runs off the plan.

Issues and receipts happen at the point of work, so the register matches the godown. Demand from accepted orders becomes a buying list with dates, approvals and goods receipts on one record.

You negotiate in September at September rates instead of begging in November.
See the module
Leftovers go back into stock against the job, with a value.

Balances and overs are recorded at the end of the run, not pushed under a table.

You stop buying and printing material you already own.
See the module

Binding, finishing and outsourced work

Your vendors confirm dates and quantities on a portal.

Outsourced stages sit on the same job record, with the vendor confirming receipt, quantity and completion in writing.

The delay reaches you the day it happens, not on the day the job was due.
See the module
The check happens at the stage that caused it.

Quality checks at each stage catch the fault at gathering or sewing, on that machine and shift, before the next 3,000 are made the same way.

You rework 40 books instead of 4,000.
See the module
Every reject is entered with a stage and a reason.

Wastage rolls up by stage, machine, operator and job, in rupees, not in vague percentages.

You cannot cut wastage you cannot see. This makes it visible.
See the module

Dispatch and the customer

Delivered against promised is on screen before the lorry leaves.

Produced, bound, packed and dispatched are compared to the ordered quantity at dispatch, not after.

A corporate client never forgives a short delivery in the first week of January.
See the module
The split is on the order record, and the packing list is generated from it.

One order number carries every delivery address and quantity from enquiry through to the packing slip.

No more re-couriering at your own expense in the last week of the year.
See the module
You hear about the problem weeks earlier, while you can still fix it.

Jobs falling behind their promised date raise an alert on their own, without anyone running a report.

A slip caught in week two is a plan. A slip caught in week six is a penalty.
See the module
Your client sees their own job's stage without calling you.

The client portal shows exactly which stage their job is at, updated by the floor, not by an executive typing an update.

You stop being your client's status desk in the busiest eight weeks of your year.
See the module

After the job

Every job closes with what it really cost.

Paper, plates, makeready, press hours, binding, foiling, outsourced work and rejects roll into one job cost you can compare against the estimate.

Next season you quote from real numbers. You know which clients to chase and which to charge more.
See the module
0 of 24 ticked

Tick the lines above to see what they cost you.

See it for yourself

We set up every factory on site, by hand. That is why we take only a few each quarter.

Six months later

What a Monday morning looks like after that.

  • You open one page at 9am and know every job, every signature and every machine, without a floor round.
  • Not one book goes to press on an artwork or proof the client has not approved in writing.
  • Makeready and spoilage are numbers per machine and per operator, and they are falling.
  • Paper and rexine are bought in September against a plan, in one lot, at a rate you negotiated.
  • Your laminator, foiler and binder confirm dates on a portal, so a delay reaches you the day it happens.
  • A gathering or binding fault is caught at that machine, on that shift, not at the packing table.
  • Your ten biggest clients check their own status on the portal, and stop calling you in November.
  • In February you sit down with the season's real numbers instead of a bank balance and a theory.
See how Prodman ERP is set up for printing

Straight answers

What owners ask us at this point.

Every job we print is different. Can a system handle that?

Different specification, same stages. Prepress, plates, printing, folding, gathering, sewing or wiro, binding, foiling, lamination, trimming, packing. The specification changes per job and travels on the order. The stages are configured once, to your press.

Our diary work is only three months. Is an ERP worth it for a seasonal unit?

The short season is exactly why you need it. A press that runs steadily all year can absorb a mistake. A unit doing most of its diary business in eight weeks cannot. The reprint you avoid in November is worth more than the same reprint avoided in April, because in November there is no time to make it again.

We outsource binding, foiling and lamination. Does that break it?

No. Outsourced stages are part of the same job. The vendor confirms receipt, quantity and completion on the supplier portal, so an outside stage is as visible as an inside one. Losing track of material once it leaves the gate is a main reason presses miss dates.

Will my operators and seasonal binders actually enter data?

Scan the job, scan the machine, enter produced and rejected. That is the whole interaction and it takes seconds. We kept it short on purpose. Every system that asked the floor to fill in forms has failed.

Does this replace Tally?

No. Tally keeps your books and stays where it is. Prodman ERP runs the floor and the orders, which Tally was never built for. They work alongside each other.

When should we start, if our season begins in September?

Before June. We set every factory up on site, by hand, and we want a full quiet cycle to configure your stages, load your items and train your team before the first big order lands. Starting in August means learning the system in the same weeks you are trying to ship.

You should not need to spend your life walking the floor to discover the truth.

Bring us one problematic production order, one chronic bottleneck, or one metric nobody trusts. In thirty minutes, we will show you how Prodman restores order and calm, without asking your machine operators to become clerical typists.

Limited on-site implementations each quarter · Configured by hand