Purpose
This guide explains how to use an application-level production queue before sending jobs to a printer, RIP, or official driver.
The queue reduces media waste by keeping jobs in hold mode until preflight, operator approval, and test output are complete.
1. When to use the production queue
| Situation | Queue benefit |
|---|---|
| Roll-to-roll jobs | Prevents accidental long runs and roll media waste. |
| E-commerce batches | Groups jobs by SKU, template, media, or printer. |
| CMYK + White jobs | Requires white proof and operator approval before output. |
| Sheet label batches | Lets the operator test one sheet before the full batch. |
| Repeat orders | Use reprint from history instead of rebuilding the job manually. |
2. Recommended queue states
New
Job is created from template, order data, hotfolder, REST API, or manual ticket.
Hold
Job waits for preflight, proof, operator check, media confirmation, or customer approval.
Released
Job can be sent to the printer, driver, RIP, or Label Server route.
Done / Error
Result is recorded with logs, backend job ID, printer name, and reprint option.
3. Operator actions
| Action | Use when | Notes |
|---|---|---|
| Hold | Waiting for approval, proof, stock, or media change. | Default for risky jobs. |
| Release | Job is validated and ready. | Release after short physical test for roll jobs. |
| Retry | Technical error occurred before usable output. | Keep same job parameters. |
| Cancel | Wrong job, wrong printer, wrong media, or customer canceled. | Use before printer starts if possible. |
| Reprint | Need more copies or replacement labels. | Use history to preserve traceability. |
4. Preflight before release
- Template and quantity are correct.
- Printer profile and media are correct.
- Barcode validation passed.
- Color/RIP audit passed.
- White plate or separation proof checked if needed.
- Inventory stock is sufficient.
- Operator is identified.
5. Reprint without losing traceability
Reprint should reuse the original job history: template, data, operator, printer route, quantity, media, and validation status.
Do not rebuild manually unless the artwork or data changed. Rebuilding makes audit and cost tracking unreliable.
6. Waste-reduction workflow
Recommended flow: create job → hold → preflight → print short test → approve → release final quantity → update inventory → keep history for reprint.