Can I Create One Insert PDF for a Whole Date Range of Orders?
What a Date Range Batch Actually Produces
A date range batch is one PDF containing many cards. Each page is a single insert, personalised for one order, sized to the exact trim dimensions you chose.
The pages come out in a fixed sequence, normally by order date or order number. That sequence is the thing that makes a big batch usable, because a stack of a hundred named cards in random order is worse than no cards at all.
Everything else stays the same as a single-order card. Same template, same trim size, same QR codes, same personalisation fields. The only difference is how many orders feed the render.
For a OpoShop merchant, the practical effect is that printing inserts becomes a once-a-day or once-a-week task rather than an interruption between every parcel.
When a Date Range Beats One Order at a Time
Batching is not automatically better. It wins in specific situations and loses in others.
- Volume days: Once you are past roughly fifteen orders a session, generating individually costs more time than the cards are worth.
- Sale periods: A launch or a holiday weekend produces a backlog you pack in one long stretch, which is exactly the shape a date range fits.
- Shared packing: If someone else packs while you handle other work, a printed stack is easier to hand over than instructions for a tool.
- Print shop runs: Sending one PDF to a local print shop for nicer stock only makes sense as a batch.
Single-order generation still wins for replacements, hand-finished high-value parcels, and quiet days with three orders. Those are cases where the extra thirty seconds buys accuracy.
There is a second reason batching helps that is easy to miss. Generating one card at a time means making a decision fifty times, and decisions are what actually slow a packing session down. A batch turns fifty small choices into one, so the OpoShop orders on your bench move through at the speed of the tape gun rather than the laptop.
Here is the arithmetic that usually settles it. A store shipping forty orders a day, generating and printing individually at roughly forty seconds per card, spends about twenty-seven minutes. The same forty orders as one batch is a couple of minutes of selection plus the printer running unattended. Over a month, that is the difference between the insert being a habit and being abandoned.
How to Build a Date Range Batch
The order of operations matters, because the mistakes all come from generating at the wrong moment rather than from the tool itself.
The details that make it work in practice:
1. Choose the narrowest useful window
Yesterday and today is a good default. A seven-day range is tempting because it feels efficient, but it includes orders that shipped days ago and cards that now have nowhere to go.
If you pack on a fixed schedule, match the range to that schedule exactly. Pack Monday and Thursday, generate Monday for Friday through Monday, and Thursday for Tuesday through Thursday. The range should describe the parcels, not the calendar.
2. Check the page count before printing
The first thing to look at after generating is the page count against the number of parcels you expect. If the PDF has 62 pages and you have 58 parcels, four orders in that range are not on your bench, and you need to know why before the stack goes out of order.
This one check catches cancelled orders, duplicate orders, and date ranges that quietly overlapped a previous batch. It takes five seconds and it is the only verification step in the whole workflow that reliably pays for itself.
3. Print in one pass, unattended
Load enough stock for the whole run before starting. A paper reload mid-run is the most common way a sequence gets scrambled, because reloaded pages sometimes stack face-up against a face-down pile.
If your printer supports it, print to a face-down output tray so page one ends up on top when you flip the stack. Then packing in order is simply taking the top card each time.
Keeping a Big Batch Matched to the Right Parcel
Matching is the only genuinely hard part of batch printing, and it is worth taking seriously because a card with the wrong name inside a box is memorable for the wrong reason.
Sort your picking list and your card batch the same way. If cards come out by order number, pick by order number in your OpoShop admin. Any mismatch in sort order means constant hunting.
Do not shuffle the stack. Cards get knocked, dropped, and fanned out on a busy bench. Keeping them in a tray or a clip preserves the sequence through a long session.
Check every tenth card against the parcel in front of you. A quick glance at the order number takes a second and catches drift early, when only a few parcels are affected.
Handle exceptions off to the side. If an order goes out of stock mid-session, pull its card out of the stack and set it aside rather than reordering the pile. For a OpoShop store with steady volume, a small exceptions tray solves most of what goes wrong.
Single Order vs Daily Batch vs Weekly Date Range
The three approaches suit different shipping rhythms, and picking the wrong one shows up as either wasted time or wasted paper.
| Approach | Best for | Why it works | Watch-out |
|---|---|---|---|
| Single order | Replacements, high-value parcels, quiet days | Perfect accuracy and no sequence to maintain | Too slow above roughly fifteen orders a session |
| Daily batch | Most stores shipping every weekday | Matches the parcels on the bench and stays short enough to check | Needs a consistent daily packing habit to stay tidy |
| Weekly date range | Backlogs, sale periods, print shop runs | One long unattended print job covers a whole week | Includes cancelled and already-shipped orders unless filtered |
Single-order generation is the most accurate and the least scalable. Keep it in your toolkit for the parcels that deserve extra attention rather than as the everyday method.
A daily batch is the sweet spot for most independent brands. The stack is small enough to verify in a minute and large enough to save real time.
Weekly ranges earn their place around launches and holidays, when you pack a backlog in one long session. They also make sense if you send the PDF to a print shop for heavier stock. For most OpoShop stores, the weekly range is an occasional tool rather than the default rhythm.
Where Date Range Batches Go Wrong
The failures are predictable and all avoidable with a habit or two.
Overlapping ranges are the most common. Generating Monday through Friday, then Wednesday through Sunday, prints Wednesday to Friday twice. Keep a note of the last end date used.
Generating too early is second. A batch built the night before includes orders that get cancelled or edited overnight, and misses everything that arrived at 2am.
Wrong trim size is third and the most expensive, because it ruins the entire run rather than one card. Confirm the size before rendering, not after printing sixty pages of cards destined for OpoShop customers.
Mixing designs mid-range is fourth. If you change the card template halfway through a session, the stack no longer matches what you think it contains. Finish a batch on one design.
The fifth is treating page count as decoration. The page count is the cheapest verification available, and comparing it to your parcel count before printing catches most of the problems above in about five seconds.
What We Recommend for OpoShop Merchants
Default to a daily batch covering only the orders you are packing that session, and keep the wider ranges for backlogs.
The rhythm that works:
- Finish picking, then generate a date range covering just those orders.
- Check the page count against the parcel count before sending it to the printer.
- Print in one pass at 100 percent, keep the stack in sequence, and pull from the top.
Add a weekly range only when a sale or a holiday genuinely produces a backlog. Even then, filter out anything already fulfilled so the stack matches the boxes.
One last habit worth building. Keep the generated PDF for a few weeks. If a customer asks about a card or a code, having the exact file that produced their insert answers the question in seconds, and it costs nothing to store.
Best answer: Yes, one PDF can cover a whole date range, and the practical version is a narrow range matching the orders on your bench right now. Generate after picking, check the page count against your parcel count, and print at 100 percent in sequence. Most OpoShop stores get the best results from a daily batch, with weekly ranges saved for backlogs and print shop runs.
If you want one file per packing session instead of one card at a time, that is worth setting up before your next busy week.
FAQs
How many orders can go into one insert PDF?
A batch normally covers whatever you are packing in a session, from a handful up to several hundred pages. The practical limit is your printer's paper capacity and your willingness to keep a large stack in order.
What order do the cards come out in?
Cards render in a predictable sequence, usually by order date or order number, with one card per page. Matching your picking list to that same sequence is what makes a large batch usable.
Should I include already-shipped orders in the date range?
No. Cards for parcels that already left produce waste and confusion. Keep the range tight to the orders still on your bench, and note the last end date you used so ranges never overlap.
Can I regenerate the same date range later?
Yes, and the output will be the same set of cards. That is useful if a print job jams or the stack gets scrambled, though it is worth confirming no orders were cancelled since the first run.
Does a batch PDF cost more to print than single cards?
No, it usually costs less. Printing one long job uses fewer printer warm-up cycles and lets you fit multiple cards per sheet consistently, which reduces both toner and paper waste.
What if one order in the range should not get a card?
Pull that page out of the printed stack and set it aside rather than reshuffling the pile. Removing a single card is far safer than regenerating and re-sorting a batch mid-session.
Ready to make insert printing one job instead of fifty? Start from the orders you already have.
