Pharma QR code won't scan? Don't reach for a new cartridge yet

Quality just forwarded a customer complaint: the QR code on their packaging will not scan, while your own quality check on a fresh sample looked perfectly fine. The troubleshooting drags on for days — cartridges get swapped, printheads get cleaned — and the real cause turns out to be resolution the whole time, not ink. A 300 DPI setting can look completely readable to the eye and still fail a scanner on a dense code. If that story sounds familiar, read this before you order another box of cartridges.

Here is the short answer first: a QR code that will not scan is often not a cartridge problem at all. It is a resolution problem. 300 DPI struggles with high-density codes, while 600 DPI is built for exactly that job, at the cost of speed and setup time. Below is how the relationship actually works on a production line, plus a real troubleshooting case from a pharma packaging plant.

A Failed Scan Usually Means Dot Density, Not Ink

Every module in a QR code needs enough dots to hold a clean edge. The smaller and denser the modules, the higher the resolution requirement. 300 DPI is not incapable of printing a QR code — it is incapable of printing a very dense one cleanly.

Think of a QR code as a mosaic. Each tiny tile needs a sharp edge for the overall pattern to be recognized. 300 DPI is like building that mosaic with larger tiles: fine for a simple pattern, but a detailed pattern turns into a blur at the edges, and a scanner cannot find the module boundaries. 600 DPI is like using smaller tiles — it renders a finer pattern, at the cost of placing four times as many dots for the same physical size.

Industrial TIJ printheads are typically 600 DPI vertical by design, set by nozzle spacing, while horizontal DPI is tied to line speed — run the line faster and the real horizontal density drops. This is exactly why some plants say "we bought a 600 DPI machine and the QR still will not scan." The hardware supports it, but the speed was set too high to actually reach 600 horizontally. The equipment is not the problem; the speed setting is.

Content density matters just as much as the printed size:

• A simple serial number: modules are relatively large, and 300 DPI usually scans fine.
• GS1 traceability data or a multi-field Data Matrix: modules shrink, density rises, and 300 DPI tends to blur at the edges, causing repeated failed scans.
• A code printed in a small physical area, like the corner of a pharma carton: modules compress further, making 600 DPI close to mandatory.

So when a line reports "the QR won't scan," the first question is not "should we swap the cartridge or clean the head." It is "does the code's density and printed size actually match 300 DPI or 600 DPI in the first place?" If the resolution is fundamentally insufficient, adjusting ink density or cleaning nozzles will not fix it.

600 DPI Is Not a Settings Toggle — Re-verify Speed and Read Rate

Moving from 300 to 600 DPI is not a simple settings switch. Line speed and the read-rate window both need re-validation, or the code gets sharper on paper while output quietly drops on the floor.

The camera analogy fits. Shooting in a high-resolution mode produces a finer photo, but storage and processing time both grow, and burst speed drops. A coding printer behaves the same way: the same printhead now has to place twice the dots over the same distance, and the firing frequency cannot keep up with the old line speed, so speed must come down — otherwise the dots smear and the QR code actually gets blurrier, not sharper.

A common mistake is the blanket upgrade. A packaging line originally runs a simple lot number at 300 DPI, then a customer asks for a GS1 traceability code added to the message. If the whole message switches to 600 DPI at the original speed, the lot number now prints slower than it ever needed to (it never required high resolution), while the QR segment still blurs because the speed was not actually reduced enough to hit true 600 DPI density. That approach loses on both fronts.

The better method is to split the message: keep the lot number at 300 DPI at the original speed, and set only the QR segment to 600 DPI, slowing the line or adjusting the trigger timing specifically for that portion so the dot density holds. The overall speed loss for the whole line ends up far smaller than a blanket 600 DPI switch.

One more cost is easy to overlook. At 600 DPI, the controller processes four times the data of 300 DPI. Older or entry-level controllers can drop characters or break codes at higher speeds, even with correct ink and resolution settings — the real bottleneck becomes controller processing power, not print quality. Before upgrading resolution, confirm the controller and firmware version can actually sustain stable high-density output.

The executable troubleshooting order is:

1. Verify line speed matches the target resolution. Faster line means lower real horizontal density.
2. Verify the controller outputs stably at that speed. Check firmware and processing headroom.
3. Only then check cartridge and printhead condition. Ink and nozzles matter only once resolution is confirmed adequate.

Reverse that order and you waste time swapping ink and cleaning heads on a problem resolution never fixed.

Scan Rate Is Measured by a Scanner, Not Your Eyes

Whether a QR code is "clear enough" cannot be judged by eye. It must be measured with the actual scanner the line uses, at the actual line speed, not on a slowed-down sample print.

This is like checking color accuracy on a print job. To the naked eye, two colors might look close enough; an instrument can reveal a gap large enough to fail a brand standard. QR codes work the same way — something that "looks fine" to the eye can still fail repeatedly on a scanner because of tiny jagged edges at the module boundary. Resolution acceptance has to be measured by equipment, not by feeling.

A verification checklist you can run on the floor:

• Use the real production substrate, not the vendor's sample sheet.
• Print at the actual production line speed — do not slow down just for the test.
• Use the scanner already installed on the line, scan every unit in a batch, and log the read rate — do not judge from a handful of spot checks.
• Test 300 DPI and 600 DPI at the same speed and compare the actual gap in read rate.
• If 600 DPI still fails to hit target read rate at normal speed, the bottleneck may be controller processing power or printhead condition, not just the resolution setting.
• Keep the test log and lot number on file for future retests and traceability.

When does a near-100% scan rate become mandatory? Pharma, medical device, and other regulated traceability scenarios, plus any order where the customer contract specifies a minimum scan rate. These cannot ship on "it scans most of the time" — they need a formal read-rate verification report. On the other end, internal lot codes and warehouse tracking codes can tolerate a looser standard, where 300 DPI plus a normal verification routine is enough.

Case Study: A Pharma Carton Line That Blamed the Cartridge

A pharmaceutical packaging plant added a GS1 Data Matrix traceability requirement to a small printed area on the side of a carton, at a customer's request. The line had run stable at 300 DPI for years printing date and lot numbers, so the team simply added the new code at the same resolution, assuming "the equipment hasn't changed, so it should be fine."

During the first production trial, quality control sampled the scan rate and found it hovering around 70%, and the customer reported occasional failed scans on their end too. The floor's first instinct was a cartridge problem. They swapped in fresh cartridges and cleaned the printhead. The read rate barely moved. After nearly a week of troubleshooting, some on the team started suspecting a hardware fault and considered contacting the manufacturer about a possible return.

A technician eventually re-examined the problem from the resolution angle and found the root cause: the Data Matrix code was printed in a small physical area with high information density, and 300 DPI simply could not hold clean module edges at that density — the cartridge and printhead had nothing to do with it. They set that single segment to 600 DPI, confirmed the controller firmware supported stable high-density output, and slightly reduced line speed for that segment before re-testing.

After the adjustment, they scanned an entire shift's output with the line's own scanner and held a read rate above 99%. The date and lot segment stayed at 300 DPI and the original speed, so overall throughput dropped only slightly — far better than switching the whole message to 600 DPI would have cost. The customer's follow-up audit confirmed the fix, and the issue closed for good.

The lesson worth repeating is not "every QR code needs 600 DPI." It is to separate the real cause first: is this a cartridge or printhead issue, or is the resolution fundamentally unable to hold the code's density? Skip that separation and you burn time swapping consumables that were never the problem.

Bottom Line

Most plants do not need a pricier cartridge. They need to separate "won't scan" into a consumable problem or a resolution problem first. When a China-based TIJ maker such as a FIRSTCOLOR CODING printer team talks with a factory, the question that comes up most is not "will a new cartridge fix it," but "can 300 DPI even hold this code's density in the first place?"

When a QR code fails to scan, check resolution and density match first, then controller processing power, and only then cartridges and printheads. Get the order right and troubleshooting time drops by more than half.

Related Reading

• Can You Actually Tell the Difference Between 300DPI and 600DPI Coding With Your Eyes? — why DPI matters more than it looks on a quick visual check.
• QR Codes and Beyond: Smart Labeling Solutions — how codes fit into a broader traceability and labeling plan.
• Can Compatible Cartridges Replace Genuine HP45? Factory Test Data Gives the Answer — the consumable-quality question, settled with an 8-hour line test.
• Water-Based vs Solvent-Based Ink: The Complete TIJ Cartridge Guide — match ink chemistry to the substrate before you negotiate price.
• How to Print an Invisible QR Code on a Bottle Cap with UV Ink — adding a hidden anti-counterfeit layer on top of the visible code.