The customer calls: the tickets have arrived, but the scanner at the gate cannot read every fifth code. The numbering matches, the colors look nice, the paper is fine - yet there is still a complaint. The file is almost always to blame, not the machine. A barcode is not decoration - it is a small visual program that must meet specific geometric parameters, or the scanner simply will not read it. There is no room here for “looks decent enough.”
What offset numbering actually is and how it works
Numbering in offset printing is most often a separate numbering module mounted in the printing press, or an additional pass on a dedicated numbering machine, which applies an increasing or random number to each individual copy. In practice it is used for tickets, coupons, invoices, certificates, vouchers, and forms - wherever every single print needs to be unique and identifiable.
This is a completely different mechanism than standard CMYK printing. The numbering unit works mechanically or digitally in a separate pass, so the project file must clearly mark where the number should appear - the color, font size, number of digits, and whether the numbering should run vertically or horizontally. The actual number is usually not part of the graphic file itself, but a separate specification passed to the production department, since it increases from copy to copy.
What belongs in the file, and what belongs in a separate specification
In the design file itself, it is enough to mark the place for the numbering - ideally as a rectangle in a spot color, with a note in a descriptive layer stating the font and character height. Everything else - the numbering range (from which number to which), the number of digits with leading zeros (e.g. 000001 instead of 1), and any repetitions across two copies (e.g. ticket + stub) - is set in the order, not in the graphic file. Mixing these two things is a simple way to cause an error, because the designer only sees the layout, while the numbering unit reads actual data.
Leading zeros in the wrong place: If the numbering needs a fixed number of digits (e.g. six), state this explicitly in the order. The number 47 instead of 000047 might look like a trivial detail at first glance, but in access control systems or lotteries it can be grounds for the entire ticket to be rejected by the scanning system.
How a barcode works and why geometry matters more than graphics
A barcode is an arrangement of bars and spaces with strictly defined proportions, which a scanner reads as a sequence of digits or characters - not as an image that just has to “look nice.” Every type of code, whether EAN-13 used in retail, Code 128 used in logistics, or QR used in marketing applications, has its own mathematics: the minimum width of the narrowest bar, the required margin (the so-called quiet zone), and the error tolerance.
The problem is that a barcode in a vector file looks identical whether it is printed at 100% scale or scaled by 10%. The human eye will not notice the difference. A scanner will - because scaling changes the proportions of the bars relative to one another, and it is precisely those proportions that carry the information.
Resolution and scale - where things most often go wrong
A barcode should go into the file as a vector object generated directly at the target size, ideally from dedicated barcode-generating software or from the customer's ERP system, not as a bitmap grabbed from a website and dropped into Corel on the fly. If the code must be a raster image, the same rules apply as for images used in offset printing: full target resolution at 1:1 scale, with no last-minute resizing.
Do not scale a barcode “by eye”: Dragging the corner of a barcode in InDesign or Illustrator to “fit it into the page layout” is one of the most common reasons a code fails to read after printing. If the code needs to be a different size, regenerate it at the target scale from scratch - do not rescale the finished file.
Contrast and colors - this is where a barcode forgives the least
A classic barcode reads best as black bars on a white background, because a laser scanner relies on the difference in light reflection, not on color perception the way a human eye does. A red code on a green background might look striking on a screen and be completely unreadable to a scanner, because for the sensor both colors reflect light in a similar way.
In CMYK, the safest approach is to build the code's bars from pure black K=100, without any CMY addition, because offset registration (micro-shifts in color alignment between cylinders) can blur a multi-channel black and thicken the bars beyond tolerance. Keep the background white or very light, with no screen tint or pattern in the background - even a subtle one - because it also affects the contrast read by the scanner.
- Code bars: black K=100, with no CMY overprint
- Background: paper white or a very light, solid color with no screen tint
- Avoid glossy foiling directly over the code - glare confuses handheld scanners
- Do not apply spot varnish directly on the code itself, unless it is a matte, anti-glare varnish
Quiet zone - the margin of silence around the code
The quiet zone is an empty margin on both sides of the barcode, with no graphics, text, or lines, because the scanner needs that empty space to recognize the beginning and end of the bar sequence. For EAN-13, the standard is about 3.6 mm on the left and right side of the code - and this is not the place for a brand logo just because “it happens to fit there.”
We have seen designs where a designer literally placed an advertising slogan right next to the code because there was some free space left on the packaging. The result? The till at the store cannot read the code, the cashier types it in manually, and the customer still assumes it is the printer's fault. The rule is simple: the quiet zone is non-negotiable, even if it visually looks like unnecessary empty space.
The quiet zone around a barcode is not an aesthetic choice - it is a reading requirement. Without it, the scanner loses track of where the sequence begins and ends, no matter how carefully the rest of the design was made.
The most common mistakes in files with numbering and codes
The first and most common mistake is a code taken from a screenshot or an image search - low resolution, blurry, sometimes even with visible JPG compression artifacts. Such a code looks acceptable on a screen because the eye fills in the contours. A scanner fills in nothing.
The second mistake is skipping a test on the actual target material. A code that reads perfectly on white offset paper may be unreadable on metallized foil, because a glossy surface scatters the scanner's light differently than matte paper. The third, very common case, is rotating the code by 90 degrees without recalculating tolerances - some handheld scanners handle this without issue, others struggle with it, especially at lower print quality.
The fourth mistake concerns numbering: no clear information on whether the number should include a letter prefix, whether the numbering should run continuously across the whole print run, or reset after a certain batch. This is not something that can be figured out mid-production - once a numbering unit is running, it will not go back to fix the start of a series.
Make a test print from the real file: Before you commit the entire print run with barcodes, ask for a test print and scan it with an ordinary store scanner or a phone app. Five minutes of testing can sometimes save an entire print run from needing a reprint.
How to prepare the file step by step
Start with the source of the code - generate it in dedicated barcode software or pull it directly from the system where the EAN or SKU database was created, not from a random website. Next, embed the code as a vector object at the target size, with no scaling whatsoever in the DTP program. If the design requires rotating the code, do it at the generation stage, not by rotating the finished graphic in Illustrator.
- Generate the barcode at the target size, ideally as a vector
- Set the bars to pure black K=100, and the background to white with no screen tint
- Leave the full quiet zone on both sides of the code, in line with the standard for that code type
- Mark the numbering placement in the file with a separate spot color and a note in a descriptive layer
- Submit the file as a PDF/X-1a or a properly prepared composite PDF
- Order a test print and scan it before approving the entire run
As for the file format itself: a print-ready PDF is preferred, ideally a sealed PDF/X-1a, or a well-prepared composite PDF; for certain applications, such as a single graphic containing a code with no vector text, TIFF or JPG may also be acceptable, but a vector will always be the safer choice for barcodes, since it does not lose edge sharpness regardless of scale.
Resolution of images around the code
If the same design includes product photos or a graphic background next to the numbering or the code, stick to the 300 dpi standard at 1:1 scale for both offset and digital printing. This does not apply to the code itself, which is best left as a vector, but it does apply to the rest of the graphic material on the packaging or label, where low resolution will be just as noticeable as a poor barcode - only in a different form: blurry photos.
Labels and packaging - details that are easy to overlook
On self-adhesive labels and packaging, the barcode often ends up close to a cut line or a fold, which is risky in itself. The standard safety margin from the cut line is a minimum of 3 mm, and for more complex jobs such as packaging, 5 mm or more is recommended - and the barcode should fit comfortably within that logic, not sit right on the edge.
The most common mistake in label files is an incorrect cut outline, a lack of safety zones, and poorly considered contrast in fine typography - and barcodes fall exactly into that category of problems, since they are also a form of small, precise graphics sensitive to cutting inaccuracies. For packaging, the most common issue is a lack of a properly prepared die-cutting template, failure to account for creases and gluing zones, and incorrect layers for varnish or embossing - and a barcode placed on a box's fold line is a guaranteed read failure, because it creases exactly where the bars need to stay straight.
Do not place a code on a crease line: Folding a carton at the point where a barcode runs distorts the bars enough that some scanners stop reading it. Keep the code on a flat surface, away from creases and cut edges.
When offset, when digital printing for numbering and codes
Variable numbering and barcodes that differ on every copy are a natural fit for digital printing, since data personalization is built into the process there. Offset works well where the code or number is fixed, or applied in a separate pass by a numbering unit on an already-printed sheet - that is, rather for large, stable print runs with a uniform specification than for jobs where every copy carries different variable data.
There is no single number at which offset becomes more cost-effective than digital printing - it depends on the format, volume, paper type, number of versions, and whether personalization is involved. The advantage of offset grows with larger print runs and a stable production specification. If a project calls for fixed serial numbering on a large run of tickets or vouchers, it is worth asking for the technology to be matched to the specific requirements, rather than assuming in advance which option will be cheaper.
What else is worth checking before sending the file
The file format is one thing, but it is equally important to clearly state what you expect from the numbering and codes in the order specification, not just in the graphic design itself. The prepress department cannot guess whether the numbering should start at 000001 or at any other value if nobody has written it down explicitly.
- Barcode as a vector at the target scale, with no manual rescaling
- Code bars in pure black K=100, background with no screen tint
- Full quiet zone preserved around the code
- Code and numbering kept away from cut lines and crease lines
- File as PDF/X-1a or a properly prepared composite PDF
- Numbering specification (range, number of digits, prefix) described separately from the graphic file
- Test print scanned before approving the entire run
Numbering and barcodes are seemingly the least glamorous element of a design, since nobody makes them the main feature of a cover. And yet they are exactly the element that has to work technically, because it determines whether a ticket gets through the gate and a product gets through the checkout. Good graphic design will not save it if the code's geometry is broken.
If you are working on a project with numbering, barcodes, or both, send us the file for review before launching the entire print run - we respond to quote requests within 24 hours at most, so there is no need to wait weeks for an answer.
barcodes print numbering EAN prepress PDF/X-1a labels packaging
Full specification, lead times and a quote: artwork file requirements at drukarniapro.pl.