Barcode placement
Where Should a Barcode Be Placed on Product Packaging?
A technically correct barcode can still scan badly when packaging puts it on a fold, seam, tight curve, reflective area or a place the cashier cannot reach easily. Placement is part of barcode quality, not a cosmetic afterthought.
Updated 18 October 2026
For many retail packages, GS1 guidance prefers the lower-right quadrant of the back of the trade item, while keeping the barcode and its Quiet Zones away from edges and scanning obstacles. Package shape can change the exact answer, so choose a flat, visible area and avoid folds, seams, perforations, ridges, overlaps, tight curves and other features that can distort or cover the symbol.
Start with the back of the package when the format allows it
GS1 General Specifications describe the back of the trade item as the preferred placement area for many retail packages and identify the lower-right quadrant of the back as the preferred general position. This is a starting rule, not permission to ignore package-specific exceptions.
The goal is to make the symbol easy to present to the scanner without twisting the package or covering the code with a hand. If the product shape or package construction makes the preferred area unsuitable, use the relevant GS1 package-specific guidance rather than forcing the symbol into a bad surface.
Keep the complete symbol away from folds, seams and tight curves
GS1 explicitly warns against placing barcodes and their Quiet Zones on perforations, die-cuts, seams, ridges, edges, tight curves, folds, flaps, overlaps and rough textures. These features can change bar widths, hide modules or break the clear area a scanner needs.
Transparent film, glossy finishes and highly curved containers can add reflections or geometric distortion. Test the final package, not only a flat proof from the design file.
Do not crowd the package edge
GS1 applies an edge rule because codes placed too close to an edge are easier to cover, wrinkle or damage during handling. The exact distance can depend on the trade-item and scanning environment, so use the current applicable specification instead of copying one number across every package type.
Also keep nearby text, borders and graphics out of the required Quiet Zones. White space inside a design is not automatically a valid Quiet Zone if another element intrudes into it after trimming or printing.
Approve placement on the real package before the production run
- Print or mock up the package at final size.
- Confirm the barcode is flat enough and fully visible in normal handling.
- Check that trimming, folds, glue areas and seams do not enter the symbol or Quiet Zones.
- Scan from realistic angles with the hardware that will actually read the item.
- For expensive or compliance-sensitive packaging, use formal barcode verification where required.
Review cosmetics on the filled container, not a flat dieline
A small jar, tube or bottle can turn a flat printable panel into a tight curve after filling and closure. Hold a paper mock-up on the actual container and check whether the scanner can see the complete pattern without the edges disappearing around the side. Keep the code away from cap seams, label overlaps and areas a hand naturally covers. A compliant-looking rectangle in the artwork does not establish readability once the label bends, wrinkles or encounters a reflective finish.
Test food packaging under its actual surface conditions
A flexible pouch can crease differently when filled, while a chilled pack may develop condensation or a film that reflects light. Place an actual production-style sample at the normal checkout or receiving position and test before approving the artwork. Keep required product and safety information available; the barcode does not replace ingredient, traceability or other applicable labeling obligations. This article addresses barcode placement, not a complete food or cosmetic regulatory review. Obtain the responsible business’s approval of the whole package separately.
Avoid duplicate scan targets during overlabeling
If a secondary sticker is applied over an existing package, decide which identifier the receiving workflow should use and ensure obsolete scan targets cannot cause ambiguity. Do not casually cover information that must remain visible. Compare the visible product description with the approved identifier before applying a replacement sticker. A hypothetical 50×30 mm sticker is a layout example, not a guarantee that every EAN or long internal reference fits. Check clear areas, readable digits and the actual container geometry before repeating it.
Keep a packaging-specific acceptance sample
Record the approved material, filled pack, artwork revision and scan position. If a label supplier changes adhesive or finish, revisit the sample even when the number stays the same. Test representative curved, folded or reflective cases with the intended reader. A phone read is helpful but does not substitute for any partner-required verification. Link the barcode artwork to the correct product variant and packaging level so a copy-and-paste mistake cannot move one product’s valid code onto a similar-looking cosmetic or food pack.
Common questions
Frequently asked questions
Can a working flat proof guarantee a jar label will scan?
No. Curvature, reflection and label application can change the optical result. Approve a filled-container sample at the intended position and with representative equipment.
Does a barcode satisfy all cosmetic or food label rules?
No. Barcode placement is one part of packaging. The business must separately check applicable mandatory information and approval requirements for the complete label and product.
May I leave two product barcodes visible?
Determine the receiving process and avoid unintended competing targets. Preserve required information and obtain an approved overlabeling decision rather than casually adding another code.
What should trigger a new placement test?
Changes to container shape, fill, label stock, finish, adhesive or scan position can matter even when the identifier is unchanged. Compare a real production-style sample before expanding the run.
Sources & standards
Technical claims in this guide are checked against primary or official documentation where available.