Qpro+ is a Quando Solutions product — supply chain & manufacturing IT
For contract manufacturers, co-packers, and operations
Every customer has their own artwork. Every retailer has their own routing guide. Multiply those and you are maintaining hundreds of label and document variants, each with a different owner and a different approval chain — and one wrong version becomes a chargeback billed to you. Qpro+ holds every variant centrally and resolves it at print time, so a customer's change is an edit, not a production project.
What it costs today
Retailers deduct billions from supplier payments every year, and label and barcode errors sit among the leading causes. The penalties are published, per-incident, and taken straight off the remittance.
| Failure | Typical published penalty | Where it comes from |
|---|---|---|
| Labeling violation | $25 – $200 per incident | Wrong template version, stale data, missing field |
| Unscannable or misplaced GS1-128 | ~$10 per box | Symbology, quality, or placement drift between sites |
| Defective carton barcode | under $1 each, at scale | Encoding errors multiplied across a full pallet run |
| ASN doesn't match the pallet | 3% – 5% of cost of goods | Label printed before the shipment was final |
| Non-compliant packaging | ~2% deducted from payment | Retailer-specific routing guide not reflected in the template |
Figures are drawn from publicly published retailer compliance and routing guides and vary by retailer, program, and year. Check your own routing guides for the numbers that apply to you.
Almost none of these are printing failures. They're data and version failures — the right label, printed from the wrong template, or the right template filled with values that were already stale.
Time to production
A new brand almost never arrives with a genuinely new label. It arrives with a spec that is mostly something you have already built, printed, and had signed off — a different logo, a different declaration block, the same routing guide underneath. Clone the closest approved template, change only what differs, and send that for approval.
Duplicate a label or document design with its layout, fields, symbologies, and placement intact, then edit only what the new customer changes.
Copies arrive unapproved and inactive. Nothing a clone inherits reaches a printer until someone promotes it deliberately.
Build one compliant base per retailer, then clone it per brand. The routing guide gets solved once instead of forty times.
Clone a live template to test a new field, symbology, or placement against real data without touching what the line is printing right now.
Pallet placards, packing lists, and certificates of analysis live in the same library and duplicate under the same rules.
Adding a customer is canvas work. The API call that prints their labels is the one your systems already make.
This is the number to put a stopwatch on. Not print speed — the days between a brand handing you artwork and the first compliant pallet leaving the dock. That interval is where cloning pays, and it's the one your customers actually notice.
Real-time data
Lot number, pallet and box identifiers, piece quantities, expiry, customer codes — your systems know all of it at the instant the pallet closes. Pre-printing means guessing at those values hours early, then absorbing the difference.
| Situation | Pre-printed batch | Rendered at print time |
|---|---|---|
| Run finishes short | Surplus labels discarded | Nothing printed that wasn't needed |
| Run finishes long | Goods wait, unlabelled and unaccounted | Print continues without interruption |
| Lot changes mid-run | Reprint the batch, or relabel by hand | Next label carries the new lot |
| Customer changes artwork | New stock, new setup, new batch | New template version, live on the next print |
| Wrong version reaches the line | Pull the run and relabel by hand | Roll back to the last good version and keep printing |
| Night shift, no one available | Product stranded until morning | Prints on demand, unattended |
| Audit asks what shipped | Reconstruct from paperwork | Print history by date, reprint from the list |
The 2D transition
GS1 Sunrise 2027 calls for retail point-of-sale systems to be able to read 2D barcodes — GS1 DataMatrix, or QR carrying a GS1 Digital Link — by the end of 2027. It's a capability milestone rather than a mandate, and 1D isn't going away. But individual retailers are setting their own supplier timelines, and the transition means dual-marking: carrying both codes on the same artwork.
That's a re-issue of every template you own. If your layouts live inside application code or a per-site desktop tool, it's a development project multiplied by every system and every site. If they live in Qpro+, it's an edit.
Add a GS1 DataMatrix or Digital Link QR alongside the existing UPC or GS1-128 without rebuilding the layout.
Full 1D and 2D types, including GS1-128, DataMatrix, QR, and SSCC serialization for case and pallet hierarchy.
Brands and retailers will transition at different speeds. Clone the template, add the 2D code, and promote it when that customer is ready — no single cutover date.
Encode RFID-enabled stock as part of the template, configured alongside the printed artwork rather than in a separate tool.
Approval and accountability
When a retailer rejects a pallet or a lot gets pulled, the question is rarely what the label said. It's who changed it, when, and who signed off — and in contract manufacturing, that answer decides who absorbs the cost.
Work on a customer's template without affecting what the line is printing right now. Promote it deliberately.
Route a change to the person who owns that customer's artwork for a green check or a red X before it reaches the floor.
Every revision is retained — what changed, who changed it, and when. The trail exists before anyone asks to see it.
Restore an earlier version and the next request prints it. No rebuild, no re-import, no waiting for whoever made the change.
A record of what was produced and when, with reprint from the list view when a label is lost or damaged.
Every site resolves against the same templates, so "which version was that line running" has a single answer instead of a search.
How rollback behaves, plainly: a rollback restores a version that was already approved, so it goes straight to Active rather than back into the approval queue. That's deliberate — rollback exists for the moment the line is running the wrong artwork and every minute is another pallet. The revert is itself recorded, so the trail shows the rollback as clearly as it shows the change that caused it.
On the label
Contract work means somebody else owns the artwork, and it rarely arrives simplified. Colour, logos, compliance marks, and creative treatments have to survive alongside the barcode.
Logos, marks, and compliance artwork per brand. Upload once and reuse across every template for that customer.
Not limited to monochrome thermal. Full type, colour, transparency, and layering when the artwork calls for it.
Smart guides, edge and centre snapping, equal-spacing hints, and X/Y nudging — because routing guides specify placement, not just content.
Label dimensions in inches, millimetres, or pixels, with 45° rotation increments for awkward applicator positions.
Pallet placards, packing lists, certificates of analysis, and form-fill PDFs render from the same template library, as PDF rather than ZPL.
Nothing to install at each site and nothing to maintain. Print through the browser dialog, or hand output to PrintNode.
Getting there
Start by rebuilding your worst customer's label set and printing from the browser. When you're ready to connect your MRP, ERP, WMS, or a custom application, the same templates are already there — you're adding a trigger, not rebuilding a library.
The signal to watch: count your live label and document variants and how often they change. High variant count with frequent revisions is where centralizing pays for itself well before the print volume does.
Put a single brand's full variant set on the canvas. Print on real stock, on your own printers, and check it against their routing guide.
Once one customer is right, the next ones start from it rather than from a blank canvas. Clone, change what differs, approve.
Name the values your systems supply. Qpro+ generates the request snippet to hand to whoever owns the calling system.
The line, the scanner, or the scheduler calls the API. The same templates now print themselves, across every customer you serve.
The free account doesn't expire and doesn't cap prints, and ZPL output is never watermarked. Take the customer template that causes the most rework and see how long it takes — then clone it for the next customer and see how much less.
Qpro+ is a Quando Solutions product — supply chain & manufacturing IT