Carton coding & labelling: the top 5 issues in 2026 – and how to improve GTIN conformance

Apr 13, 2026 by Mark Dingley

Practical coding & labelling insights from real production environments

DOWNLOAD THE FOOD & BEVERAGE WHITEPAPER

Carton coding and labelling has quietly become one of the most critical control points on the production line.

As retailers continue to invest in automated distribution centres, expectations have changed. Cartons need to scan first time, every time. The data behind them needs to be accurate, aligned and trusted.

When it is not, the impact is immediate. Delays at goods-in. Manual handling. Rejected deliveries.

Recent supplier-non-conformance data shows a clear pattern. A small number of issues are responsible for the majority of carton and GTIN-related errors.

Here are the five that matter most, and where to focus if you want to improve.

Image credit: Porcorex

1. Incorrect GTIN on carton

This is the one that causes the most disruption.

The GTIN associated with the carton does not match the product inside or what the retailer is expecting. It often comes down to manual processes or disconnected systems where the wrong code can be selected without anyone realising.

When this happens, cartons cannot move cleanly through the supply chain. They get stopped, checked, and often reworked.

The fix is not complicated, but it does require discipline.

Bring GTIN control back to a single source. Remove manual selection at the line. Make sure only approved data can be used in production.

2. GTIN not recognised by retailer systems

In this case, the code is correct internally but not set up properly with the retailer.From the line’s point of view, everything looks fine. At the distribution centre, it fails.

This usually points to a gap between product setup, GS1 registration and retailer onboarding processes.The best way forward is to validate before anything is printed or applied.

If the GTIN has not been approved or aligned with your trading partner, it should not be available on the line. Simple checks upstream prevent bigger issues downstream.

Image credit: MahirAtes

3. Barcodes that do not scan reliably

A barcode can look fine to the eye and still fail in an automated environment.

Poor print quality, incorrect label application, or inconsistent placement all contribute. On a busy line, these problems are easy to miss until they start causing delays further down the chain.

This is where many operations rely too heavily on visual checks.

A stronger approach is to treat barcode quality as something you measure, not something you assume.

Consistent print-and-apply standards, regular maintenance, and verification where it matters all play a role in keeping cartons moving.

4. Incorrect GTIN hierarchy

This is a quieter issue, but it creates real problems.

Using an inner pack GTIN on an outer carton, or mixing up packaging levels, breaks the logic that supply chains depend on. Inventory becomes harder to manage. Orders do not align. Traceability suffers.

It usually comes back to complexity. Multiple packaging levels, unclear rules, and too much reliance on operator knowledge.

Clarity solves most of it.

Define your GTIN hierarchy properly. Make it visible. Then build it into your process so the right code is applied without relying on memory or workarounds.

Image credit: Sankai

5. Missing barcode or GTIN

This is the simplest issue on paper, and one of the most frustrating in practice: a carton leaves the line without a scannable code or label.

No scan. No compliance.

It often happens when there is no immediate feedback that something has gone wrong. A printer stops. A label is missed. The line keeps running.

Closing that gap comes down to visibility.If a code is not applied, the system should know straight away. Operators should know straight away. The line should not continue as if nothing happened.

What sits behind these issues

None of these problems are new. What is changing is the environment around them. Higher volumes. Faster lines. More automation. Less tolerance for error.

The common thread across all five issues is not the device, it is the level of control around data, setup and verification.When those elements are disconnected, errors slip through.

When they are connected, performance becomes far more predictable.The operations getting this right are not working harder, they have simply built better control into the way their lines run.

Best practice checklist. How do you stack up?

Use this as a quick sense check of your current setup.

  • Are all coding and labelling devices connected to a single, centralised platform?
  • Are your GTIN and product data sourced directly from your ERP or master-data system?
  • Do you have validation in place to prevent unapproved or incorrect GTINs being used?
  • Are barcode-verification scanners installed and actively used on the line?
  • Do you verify both the barcode quality and the data within the code?
  • Are you checking that the correct packaging or label is being applied to the right product?
  • Do you have controls in place for packaging hierarchy, including inner and outer GTIN relationships?
  • Are print failures or missed labels detected in real time?
  • Do operators receive immediate alerts when something goes wrong?
  • Is there a clear audit trail of what was printed or applied, and when?
  • Can you trace issues back to root cause quickly without manual investigation?

If you answered no to more than a couple of these, there is likely an opportunity to improve both compliance and line performance.

Image credit: Narvo Vexar

Need support or have questions?

If any of these challenges are showing up in your operation, it is worth addressing them early.

Fill in the form below if you have questions, or if you would like to organise an on-site training or troubleshooting session with one of our GS1-trained technical specialists.

Sometimes a small change in setup, process or understanding can remove issues that have been sitting in the background for years. Getting that right makes a real difference, not just to compliance, but to how smoothly your operation runs day to day.