Create a new order with a link to the old one
Copying a completed order into a new draft preserves the old job as evidence of what was actually agreed and delivered. Give the new order a new ID and retain a source-order reference so staff can follow the relationship.
Do not reopen the completed order and replace its quantities or due date. That makes the historical approval appear to belong to work it never covered.
YoPrint documents cloning a job order as a reuse workflow. Our recommendation to recheck commitments and obtain a fresh approval is a PrintLatch workflow policy, not a claim about which approval data that product does or does not copy. [1]
Copy references, then recheck commitments
Artwork, garment style and print notes can be useful starting references. They still need a current check, especially when a customer uses “same” to mean the same design but a different quantity or color.
YoPrint’s quote guide includes checking vendor stock and pricing before finalizing an order. This is useful context for rechecking supply and price on a repeat job; a historical order alone does not establish today’s availability. [2]
Keep the old job
Preserve approval, price and delivery history
Create a new draft
Reuse references; recheck quantities and price
Get new approval
New date, version and work ticket
| Useful to copy as a draft | Must be checked again |
|---|---|
| Source order and artwork references | Whether those exact files are still wanted |
| Garment/style description | Current availability, color and supplied-by responsibility |
| Previous size breakdown | This order’s sizes and total quantity |
| Print positions and dimensions | Any requested design or placement change |
| Past quote for comparison | Current unit price, setup charges and discount terms |
| Prior production notes | New promised date and current delivery arrangement |
Do not copy an approval
An approval belongs to the earlier order and revision. The new draft should have no approval or release attached, even if every visible specification initially matches. The new customer request may involve a different buyer, timing or commercial agreement.
Likewise, do not silently reuse a discount or zero setup fee forever. If previous setup can genuinely be reused, let the shop confirm that decision and show the resulting price clearly.
Handle the next change on the new record
Suppose last month’s job was 48 shirts with artwork A. This month starts as a repeat but becomes 54 shirts with artwork B. Keep last month untouched; make the changes on this month’s draft and request approval of its current revision.
Before production starts, compare the current work ticket with the current approved record. If work has already started, record additional work explicitly rather than rewriting what the crew was told to make.
A quick repeat-order handoff checklist
The goal is to reuse helpful information without inheriting old promises.
- The new job has its own order ID and source reference.
- The customer has confirmed the current artwork and size rows.
- Supply, pricing and the new date have been checked.
- Previous approval and release are not carried forward.
- The new approved version is the one on the work ticket.
- The earlier order and its archive remain unchanged.
Use the old job as a checklist, not an instruction to print
Start by asking what “same again” means this time. The customer may want the same artwork but different garments, the same total with a different size mix, or the same products with a new delivery date. Confirm each independently instead of inheriting a complete promise from the old order.
Write a short repeat brief containing the source order, the new quantities, changed products, intended print positions and new timing. Attach a current proof when any visual detail has changed. If nothing visual changes, still identify the exact artwork reference the customer is accepting for this order.
Check the handoff when only some items repeat
Suppose the earlier job contained black tees and ivory hoodies, but the customer now wants only the tees. Remove the hoodie line from the new draft and review any print placements or charges that belonged only to it. Do not leave an attachment with an ambiguous label that could send the operator toward the wrong garment.
Keep the earlier job intact, including its delivery and payment history. The new order needs its own commercial decision and collection record. If the customer later asks why the repeat price differs, you should be able to point to changed quantities, supply assumptions or the pricing rule without editing the historical evidence.
Our proposed acceptance exercise is to let a second staff member make the repeat without guidance from the person who handled the first job. Record every question they must ask. That gives you concrete evidence about the handoff; a successful synthetic example alone does not establish that a real shop will find it faster.
How the current product handles it
PrintLatch’s repeat action opens a new draft, clears the old promised date, base garment price and setup fee, and keeps a source-order link when copying a saved order. Additional garment-line prices must also be reviewed; they are not automatically refreshed from a supplier. Confirm all commercial details before saving.
The software is a handoff aid, not an automatic inventory or supplier check. Start with an authorized repeat job and compare whether your team can complete the whole process without someone manually reconciling files afterward.
References & methodology
These vendor documents support the specific software examples cited above. They are not industry standards, independent product tests or endorsements of PrintLatch. Template fields, version-handling recommendations and synthetic calculations are PrintLatch editorial work; example amounts are not market rates.
- Reuse a Job Order by Cloning ↗YoPrint Knowledge Base · Checked 2026-09-20Back to cited passage ↑
- Create a Quote ↗YoPrint Knowledge Base · Checked 2026-09-20Back to cited passage ↑
Choose the next step for your task
Use the template for the immediate task; evaluate software when repeated team handoffs justify it.
