How to Prepare Your GS1 QR Codes for Targeted Product Recalls

Encoding a batch/lot number on your packaging is one thing. Being able to identify, locate, and recall that batch without stopping safe stock is another.

GS1 identifies targeted recalls as one of the business cases supported by adding data beyond the GTIN to 2D barcodes. But the systems involved must also capture, store, and use that data.

This guide helps you test whether your setup can actually execute a batch-level recall.

New to GS1 Digital Link and Application Identifiers? Start with what GS1 Digital Link is and how it works. 

Planning a wider 2D barcode rollout? See the GS1 Sunrise 2027 migration guide.

Recall precision is a systems question, not a barcode question

Take a moisturizer produced in three runs (batches): L2407, L2408, and L2409.

All three share the same GTIN because they are the same product. A quality investigation later finds a problem only in L2408.

What you can recall precisely depends on what your systems retained:

Identifier retained downstream	What you can isolate
GTIN only	The product across all three runs
GTIN + batch/lot	One production run
GTIN + serial number	Individual units

The barcode may carry L2408 correctly, but imagine that the warehouse receiving system records only the GTIN and quantity.

The batch identity existed on the package, but the system discarded it.

Everything after that point may now have only GTIN-level information. Instead of isolating L2408, the organization may have to treat all three production runs as affected until it can establish otherwise.

That can mean more safe stock being held or removed, wider disruption, and more customer uncertainty than a precise batch-level process would require.

The goal is not to encode every possible piece of information. It is to preserve the level of product identity your recall process actually needs.

The five operational jobs in a targeted recall

A targeted recall involves five basic jobs. Each one is a point where useful product identity can either survive or disappear.

1. Define the affected products

Start with one clear rule:

This GTIN, where batch/lot equals L2408.

If your quality and supply-chain teams cannot clearly define the affected product and batch, downstream systems cannot act precisely.

2. Locate the affected stock

Your warehouse and inventory systems need to answer:

Where is L2408 right now?

And they need to answer without also returning L2407 and L2409.

If the package carries the batch number but your warehouse system does not retain it, this is a recall-readiness gap.

3. Contain it

Once L2408 is found, the manufacturer needs to hold affected stock, distributors need to stop relevant shipments, and retailers may need to remove affected inventory from stores or distribution centers.

Each organization needs both the required product information and a clear owner for the action.

4. Stop the sale

If a retailer’s scanners, checkout system, and backend systems capture and process the batch number, they may be able to compare a scanned product against a recall rule and stop selling an affected item.

GS1 describes POS actions as one use case for additional data carried in retail 2D barcodes.

But this depends on the retailer’s actual setup. GS1 also notes that not every Application Identifier is enabled across every retailer.

So test this capability with trading partners, not assume it.

5. Inform the customer

A GS1 Digital Link QR Code can also connect a customer’s smartphone to online product information.

During a recall, that page should quickly answer the questions that matter:

Is my product affected? Which batch is involved? Should I stop using it? What should I do next? How do returns, refunds, replacements, or support work?

During an active safety issue, that information should take priority over ordinary promotional content.

Can you notify people who already bought the expired product?

There are two different situations.

With scan-driven communication, a customer scans the product and sees current recall information.

With proactive communication, a retailer or brand already knows that a specific customer bought L2408 and contacts that person directly.

The second model requires data outside the QR Code. The batch or serial information must have been captured during the transaction and connected, where appropriate, to a customer or loyalty record.

A scannable product is therefore not automatically linked to the person who purchased it.

If your recall plan depends on direct customer outreach, test that data path separately.

The mock recall: 7 steps

Specifications tell you what your barcode can contain.

They do not tell you whether your organization can execute a targeted recall.

The better test is simple: attempt one before you need one.

Pick a live product and a real batch. Assume L2408 was recalled this morning. Run the scenario through your actual systems, partners, and teams.

Score every step as Pass, Partial, or Fail.

	Test	Question to answer	Pass / Partial / Fail	Owner	Where it broke
1	Define	Can the team clearly state the GTIN and affected batch/lot, plus any required serial or date information?
2	Locate	Can inventory systems return L2408 without also returning L2407 and L2409?
3	Trace downstream	Can distributors, 3PLs, and retailers confirm whether they received L2408?
4	Contain	Can you quarantine L2408 and stop it from moving while keeping safe stock separate?
5	Block at POS	Can the retail system identify L2408 and apply the intended stop-sale rule?
6	Inform	Does scanning L2408 clearly show the recall while L2407 shows the normal experience?
7	Release safe stock	Can L2407 and L2409 continue normally while L2408 remains contained?

Anything short of a clear pass is a gap worth investigating.

Step 1: Define the affected batch

Can your team clearly identify the GTIN and affected batch/lot?

If your recall rule includes serial numbers or date-based identifiers, make sure they are available too. Depending on the scenario, expiration date (AI 17), best-before date, or production date may also help narrow the affected stock.

Your recall cannot be more precise than the affected population you can define.

Step 2: Locate the affected batch

Ask your inventory and warehouse systems:

Where is L2408 right now?

If they cannot answer without also returning L2407 and L2409, trace the product data backwards.

Find the exact system and field where the batch/lot stopped being recorded.

Do not stop at “our warehouse system can’t do it.” Find where the information disappeared.

Step 3: Trace the affected batch downstream

Now test the same question with distributors, logistics providers, warehouses, and retailers.

Can they tell whether they received L2408?

Can they distinguish it from L2407 and L2409?

Your own systems may preserve batch-level identity perfectly while another system in the chain does not.

Recall precision is therefore limited by the least precise system the affected product passes through.

Step 4: Contain the batch

Attempt real operational actions.

Can the affected batch be quarantined? Can fulfillment be stopped? Can further distribution be prevented? Can L2408 remain separated from confirmed-safe stock?

Also identify who owns each action.

Good product data doesn’t help if responsibility for acting on it is unclear.

Step 5: Test the checkout path

If your recall process includes blocking affected products at checkout, test the real retail environment.

Does the scanner capture the relevant batch information? Does the checkout system keep it? Can the backend match L2408 against the recall rule? Does the expected action occur?

Do not use a successful smartphone scan as proof.

A phone opening a webpage and a retail checkout processing batch data are different workflows involving different systems.

For broader 2D barcode testing across scanners and POS systems, see the GS1 Sunrise 2027 migration guide.

Step 6: Test the customer experience

Scan an L2408 package with a normal smartphone.

The customer should immediately understand whether the product is affected and what they need to do.

Then scan L2407 or L2409.

Does the safe batch continue to show the appropriate normal experience?

If your intended setup requires different online information for different batches, this test is also where you confirm that the routing actually works as designed.

Step 7: Prove that safe stock can keep moving

This is one of the strongest tests of recall precision.

If L2408 is affected, can L2407 and L2409 continue through the appropriate business processes?

If everything has to stop together, find where batch-level identity or the ability to act on it was lost.

The completed scorecard becomes your recall-readiness backlog. Give every Partial or Fail result an owner and a next action.

Three failures the test can expose

The mock recall can reveal problems that are easy to miss during normal operations. These failures often occur when product data is lost between systems or when teams assume that a successful QR Code scan proves the entire recall process works.

Batch/lot information disappears in a backend system

The packaging may be correct while an ERP, WMS, retailer, or another system retains only the GTIN.

An ERP manages business processes such as purchasing, production, and inventory. A WMS, or warehouse management system, manages warehouse stock and movement.

If either drops the batch information, downstream recall precision can be lost.

Trading partners have less detailed data than you do

You may be able to isolate L2408 internally while a distributor, logistics provider, or retailer cannot.

That matters because the recall depends on every relevant part of the chain being able to recognize and act on the affected products.

Scan analytics are mistaken for product tracking

QR scan counts describe digital interactions.

They do not tell you where every unit is stored, how many affected products remain in inventory, which customer purchased a unit, or whether a retailer completed a sale.

Scan analytics and supply-chain records answer different questions.

What recall readiness asks of your QR platform

Most GS1 platform requirements are broader than recalls alone. But three questions deserve special attention when recall communication is part of your use case.

First, can the platform preserve the identifiers your process needs? If your recall operates at batch level, the relevant batch data needs to remain part of the product identity.

Second, can you generate variable product data at scale? Different products and production runs may require different identifiers, so bulk creation from structured data can become important.

Third, how will online recall information work? If your planned customer experience depends on showing different information for different batches, verify exactly how destination routing and updates work in your chosen implementation. Do not assume that putting a batch number in a GS1 QR Code automatically creates batch-specific web content.

Also check how generated product information moves into ERP, WMS, printing, traceability, and retail systems. The handoff between systems is often just as important as generating the barcode correctly.

Where QRCodeChimp fits

QRCodeChimp supports the product-identification and consumer-information layer of a GS1 QR Code workflow. For teams preparing product packaging for batch-level identification and recall communication, its GS1 QR Code generator provides these capabilities:

• Add GS1 product identifiers: Build GS1 Digital Links using a GTIN plus supported identifiers such as batch/lot number (AI 10), serial number (AI 21), expiration date (AI 17), packaging date, country of origin, and other supported Application Identifiers.
• Generate GS1 QR Codes in bulk: Upload CSV, XLS, or XLSX files to create codes across multiple products, SKUs, batches, or production records instead of creating them one at a time.
• Connect each code to useful digital content: Send scans to a URL, product page, dynamic PDF, or PDF Gallery, depending on what customers need to access.
• Update linked content after printing: With dynamic output, teams can change the information customers see without reprinting the QR Code. The saved GS1 input identifiers themselves remain fixed, helping preserve the product identity encoded in the code.
• Track consumer scans: View scan activity by factors such as time, device, and location to understand how people interact with the QR Code. These analytics complement, but do not replace, inventory or traceability systems.
• Customize codes for product packaging: Add brand colors, a logo, and QR Code design elements while keeping the GS1 Digital Link structure intact.
• Use branded domains where required: Custom domain support lets organizations keep the digital experience under their own brand rather than sending customers through an unrelated domain.

QRCodeChimp does not replace the ERP, WMS, traceability, retail, or POS systems responsible for locating and containing recalled stock. Its role is to help teams create, manage, scale, and connect GS1 product identifiers to the digital experience around the product.

Healthcare products follow different GS1 and regulatory requirements. GS1 DataMatrix is widely used for regulated healthcare product identification and UDI. See FDA compliance and UDI for medical devices for that use case.

Run the test before you need it

Pick one product.

Pick one batch.

Pretend it was recalled this morning.

Then follow its identity from packaging through inventory, distribution, retail, and the customer experience.

Every place where you cannot answer “Where is the affected batch and what happens to it now?” is a gap to fix while the stakes are still hypothetical.

Frequently asked questions