
Printer rejected the shops file — 5 mistakes that get small orders kicked back
Small orders get kicked” when files have wrong format, missing bleed, RGB, fonts, or unclear size. 5 common mistakes and how to avoid them before you send.
A shop owner sends a file to the printer with the mindset “just print a small run for us.” The plant opens the file, sighs, and replies something like: “This file isn’t print-ready yet — please revise.”
On large jobs, printers still try to help. On small jobs — a few hundred takeaway boxes, one seasonal cup-label run, bags for an opening — many plants will reject or deprioritize, because rebuilding the file costs more than the order is worth.
Below are 5 mistakes that make shop files easy to “kick back,” how to avoid them before you send, and when to self-standardize a file vs ask someone technical.
1. Wrong format / only sending a pretty web image
A logo pulled from Facebook or Zalo, or a low-resolution PNG scaled up on a large box → jagged, soft print. Printers need vector or enough DPI for the real size (PDF/AI/SVG per plant requirements), not a “pretty phone photo.”
Bitmap images: at least about 300 DPI at actual print size.
Logos: prefer SVG/AI/PDF vector; avoid JPGs that have been recompressed many times.
A phone screenshot of a menu is almost never enough to print a large box.
2. Missing bleed and not understanding the die-cut
Packaging has a die-cut path. Missing a few millimeters of bleed means white edges after cutting. Canva/export files that sit “flush to the frame” often die at this step — even when they look clean on screen.
Ask the plant how much bleed (often 2–3mm, depending on product).
Keep important type/logos inside the safe zone, not against the cut line.
Don’t send a file at “exact product size” with no overrun for die-cutting.
3. RGB on screen, dull / off-brand in print
Screens use RGB; commercial offset/digital presses work in CMYK (or the plant profile). Neon colors on a phone usually don’t hold on paper. Shop owners think the printer “made it ugly,” when actually the file wasn’t print-color ready.
Accept that print color is somewhat muted vs screen.
For important brand colors: ask Pantone / hard-proof before bulk.
Don’t compare a bright screen to a print under shop lights with a different color temperature.
4. Plant machine doesn’t have the font, type jumps layout
Sending a file without outlined/converted curves → opened on another machine with a substitute font → whole slogan lines shift. Small jobs get kicked back more easily because the plant doesn’t want to “guess” the font.
Outline text before sending, or embed fonts correctly per plant requirements.
Avoid licensed fonts the shop isn’t allowed to share — prepare substitutes ahead of time.
Check kerning / line breaks after outlining (sometimes characters glue oddly).
5. Sending “final_v7_latest” with unclear size / SKU
One shared file for size S and size L boxes, or no print-area dimensions noted → the printer isn’t sure which product they’re making. Clear naming and size notes (for example cake box 18×12×5, cup body label 90×50) help small jobs get accepted faster.
Filename includes: product type + size + color (CMYK) + dated version.
Attach a short brief: quantity, substrate, matte/gloss finish, needed-by date.
One SKU per file (or one clearly labeled page) — don’t cram 5 sizes into one unlabeled file.
Why small jobs often get the cold shoulder
Plants live on presses running steadily. Fixing fiddly files for a 200–500-piece order eats the printer’s internal designer time. If the shop sends a plant-ready file (correct frame, bleed, color, fonts), a small job still gets far more priority than a file that is “pretty but not printable.”
In other words: printers don’t “hate small jobs” — they hate small jobs paired with a long technical-fix ticket. Clean file = small jobs still go on press easily.
5-minute checklist before you hit send
Size matches the real product + bleed?
Images/logos sharp enough at print size?
Color print-oriented (CMYK/profile), not expecting neon RGB?
Fonts outlined / embedded?
Filename + SKU/quantity/substrate notes clear?
Tick these 5 before sending to the plant on Zalo — you’ll cut a lot of “please revise” replies.
When to DIY the file, when to ask a technical person
DIY / template: change text, price, accent color on a frame that already has bleed and a die-line.
Ask a designer / the plant: new box structure, flattened old files, tight Pantone matching, many SKUs launching together.
Don’t: send a web image and ask the plant to “just make it pretty” on a small job — easy to get rejected or billed a high rebuild fee.
A cleaner workflow for shops
Measure the real product size (box, bag, label…) before designing.
Work toward print color, not only screen color.
Export to plant requirements or use a tool with templates + print-ready export.
Hard-proof a small quantity before bulk.
Keep the master on the shop side so next time you don’t start from a Zalo image.
FAQ — what to do when the printer “kicks” the file?
The plant says “file isn’t printable” but doesn’t name the error? Ask back on exactly 4 points: missing bleed? wrong color mode? fonts? missing size/SKU? Log the answer into next time’s checklist.
Should you just ask the plant to rebuild from an image? On large jobs it can be fine (with a fee). On small jobs, it’s often more expensive than standardizing on a template yourself — and you still don’t hold the master.
Is PDF enough? Many plants accept PDF if size, bleed, outlined fonts, and CMYK are correct. Ask requirements (PDF/AI/SVG) first so you don’t send back and forth.
How Printaz reduces the “file kicked back” loop
On Printaz, shops can pick packaging/label templates, edit in 2D, preview, and export files ready for the printer — cutting the file ping-pong that matches the pain above. The goal is not to replace the printer, but so small jobs can also send a clean file the first time.
Need advice on size or files before ordering print: [email protected] · try it on printaz.vn.
Share this article