A 1D barcode stores data in a single row of lines and spaces, encoding a reference number that points to a database. A 2D barcode stores data in a grid of dots, squares, or modules, encoding enough information to travel with the item—no database lookup required.
For enterprise operations choosing scanning hardware in 2026, the real question is not which format is better in the abstract. It is which format your supply chain partners, regulators, and workflows actually require.
How 1D and 2D barcodes encode data differently
A 1D barcode on a shipping carton is a licence plate. It tells the scanner a number. Everything that number means—origin, contents, destination, expiry—lives in a database somewhere else. A 2D barcode is the manifest itself.
This distinction matters the moment your operation loses connectivity. And it happens more often than anyone admits in facilities with concrete walls and metal racking. When a warehouse worker scans a 1D code and the WMS is unreachable, the scanner returns nothing useful. The worker is stuck. The pick stops. The line backs up.
A 2D code with embedded lot number, serial number, and expiry date still gives that worker actionable information on the device screen—even with no network connection at all.
The data capacity gap is not marginal. A standard UPC-A barcode encodes 12 numeric digits. That is enough for a product identifier and nothing else. A QR Code, by contrast, can encode up to 7,089 numeric characters or 4,296 alphanumeric characters. That is the difference between storing a reference number and storing the product’s entire identity: lot, batch, serial, expiry, origin facility, destination, and a URL pointing to handling instructions.
For pharmaceutical traceability, cold chain logistics, or any workflow where the database might not be available at the moment of scan, that difference is operational.
The physical encoding works differently too. A 1D barcode encodes information in the width of vertical bars and the spaces between them—one dimension, read horizontally. A 2D barcode encodes information in a grid of modules across both axes. This is why 2D codes can pack vastly more data into the same physical footprint.
A GS1 DataMatrix can encode 2,335 alphanumeric characters in a symbol as small as 2.5mm square. That is what makes direct part marking on tiny components feasible—a capability 1D barcodes physically cannot achieve.
There is another practical difference that rarely appears in spec sheets but shows up constantly in the field: error correction. 1D barcodes have none. If a label gets scuffed, wet, or partially torn, the scanner returns nothing. 2D barcodes use Reed-Solomon error correction, which adds redundant data to the code. At the highest correction level, a QR Code can still be read when up to 30% of the symbol is damaged.
In a cold-chain environment—think a -20°C truck cab where condensation forms on labels the moment the door opens—that error correction is not a spec sheet feature. It is the difference between a successful scan and a manual exception that delays the delivery.
1D barcode symbologies still in active use
Most enterprise 1D barcodes fall into five symbologies, each tied to a specific industry or use case. If you are managing scanning operations, you are almost certainly encountering at least two of these daily.
UPC-A and EAN-13—retail product identification
These are the barcodes on consumer products. Your warehouse workers scan them at receiving. They encode a product identifier only—12 digits for UPC-A, 13 for EAN-13. Everything else about that product lives in your inventory database.
Code 128 and GS1-128—shipping and logistics
Code 128 is the workhorse of transportation and logistics. It can encode any ASCII character, making it flexible enough for serial numbers, dates, and alphanumeric identifiers.
GS1-128 extends Code 128 with Application Identifiers—standardised prefixes that tell the scanner what the following data represents. A GS1-128 barcode can encode batch number, serial number, expiry date, and ship-to location within a single 1D symbol. This is the most data-rich 1D symbology in common use.
But even GS1-128 maxes out at roughly 48 characters. When supply chain partners start requiring more—and they will—1D hits a ceiling.
Code 39—government and defence applications
Code 39 is the legacy standard in government and defence procurement. The U.S. Department of Defense mandated it decades ago, and the infrastructure persists across North American government supply chains.
Code 39 supports 43 characters: uppercase letters, digits, and seven special characters. It is not compact. It is not efficient. But it is deeply embedded in procurement systems, and you will encounter it if your operation touches government contracts or defence logistics.
2D barcode symbologies driving enterprise adoption
Three 2D symbologies account for the vast majority of enterprise scanning requirements in Canada. Each shows up in specific operational contexts, and understanding where you will encounter them determines what scanning hardware your fleet actually needs.
GS1 DataMatrix—healthcare, pharma, and manufacturing
This is the symbology Health Canada requires on pharmaceutical packaging. It is the format mandated for unique device identification (UDI) on medical devices. If your operation receives, stores, or administers pharmaceuticals or medical devices in Canada, you are already scanning DataMatrix codes—or you should be.
DataMatrix is also the dominant format for direct part marking in automotive and aerospace manufacturing. Under IATF 16949 traceability requirements, components carry DataMatrix codes etched or printed directly onto metal, plastic, or glass surfaces.
Here is what actually happens when an organisation underestimates this requirement. We have seen hospitals attempt to deploy consumer-grade 1D scanners for medication administration workflows and fail within the first week. The nurse scans the patient wristband—a 1D code. Then scans the medication unit dose—a 2D DataMatrix. The scanner cannot read it. The verification step breaks. The workflow stops. The devices get pulled and replaced mid-deployment, at significant cost and disruption.
QR Code—logistics, marketing, and asset tracking
QR Codes are the most recognised 2D format. Your workers know what they look like. Your customers know what they look like. That recognition has operational value.
In enterprise contexts, QR Codes appear in asset tracking, equipment maintenance workflows, and increasingly in GS1 Digital Link implementations that embed product identifiers within a URL structure. A single QR Code can point to a product database, authenticate an item, and trigger a maintenance checklist—depending on the application scanning it.
QR Codes support four error correction levels (L, M, Q, H), letting you trade data capacity against damage tolerance based on the operational environment. A label in a clean office can use minimal error correction. A label on equipment that gets dragged through a construction site needs the highest level.
PDF417—transport documents and government ID
PDF417 appears on Canadian driver’s licences, provincial ID documents, shipping manifests, and transport documents. It is technically a stacked linear symbology—rows of 1D-style bars arranged vertically—rather than a true matrix code. But it is universally grouped with 2D formats because it requires a 2D area imager to read.
PDF417 can encode up to 1,850 alphanumeric characters or 2,710 numeric characters—over 1.1 kilobytes of data. That capacity is why governments use it for identification documents that need to carry biographic data, licence class information, and machine-readable verification codes.
If your operation includes ID verification—healthcare intake, government services, age-restricted retail, public safety—your scanning hardware must decode PDF417. A 1D scanner cannot.
Side-by-side comparison: 1D vs 2D barcode specifications
The table below covers the dimensions that matter most when you are choosing between 1D and 2D barcode infrastructure for an enterprise deployment.
| Feature | 1D Barcode | 2D Barcode |
|---|---|---|
| Data encoding direction | Horizontal only | Horizontal and vertical (grid/matrix) |
| Typical data capacity | 20–25 alphanumeric characters | Up to 7,089 numeric / 4,296 alphanumeric (QR Code) |
| Data self-sufficiency | Encodes a reference number; requires database lookup | Can encode full data payload; operates without database access |
| Error correction | None; damaged code is unreadable | Built-in Reed-Solomon error correction; readable when partially damaged |
| Line-of-sight requirement | Scanner must align with barcode horizontally | Omnidirectional reading; orientation does not matter |
| Common symbologies | UPC-A, EAN-13, Code 128, Code 39, Interleaved 2 of 5 | QR Code, GS1 DataMatrix, PDF417, Aztec Code |
| Scanner technology required | Laser scanner or linear imager | Area imager (also reads 1D codes) |
| Enterprise use cases | Retail POS, basic inventory lookup, shipping labels | Pharma traceability, direct part marking, proof of delivery, clinical workflows, asset tracking |
One row in this table deserves particular attention: scanner technology required.
A 2D area imager reads both 1D and 2D codes. A 1D laser scanner reads only 1D. This asymmetry has a direct implication for any hardware purchase decision you make this year.
GS1’s Sunrise 2027 initiative is enabling 2D barcodes at point of sale globally. Canadian retailers and their supply chain partners—distributors, manufacturers, 3PLs—will need 2D scanning capability as GS1 Canada aligns with this timeline. The transition has already begun.
For any organisation purchasing scanning hardware today, this means one thing: buy 2D-capable. Even if your current workflows are entirely 1D, purchasing 1D-only scanners in 2026 means purchasing hardware that will be functionally obsolete within two to three years.
The scanner that reads both formats costs marginally more upfront. The scanner that reads only 1D costs a full fleet replacement when your supply chain partners or regulators mandate 2D codes.
Where 2D barcodes are required across Canadian industries
The shift from 1D to 2D is not theoretical for most Canadian enterprise verticals. It is already mandated, underway, or operationally necessary.
Healthcare and pharmaceutical traceability
Health Canada’s Unique Device Identification (UDI) framework requires GS1 DataMatrix on medical devices. Pharmaceutical serialization requirements use the same symbology. If your organisation receives, stores, or administers medical devices or pharmaceuticals, your clinical scanning environments must support 2D codes to comply.
Medication verification at point of care is the most visible workflow. The nurse scans the patient wristband, then the medication package. If the scanner cannot read DataMatrix, the five-rights verification breaks. This is not a future requirement. It is happening now, in Canadian hospitals, every shift.
Transportation, logistics, and proof of delivery
PDF417 on transport documents. GS1-128 on shipping labels. Increasingly, QR codes for proof-of-delivery workflows that capture recipient signatures and geo-stamped confirmation.
Drivers using mobile computers scan both formats at every stop. A single delivery route might require reading 1D codes on cartons, PDF417 on manifests, and QR codes for POD capture. Transportation and logistics scanning operations that standardise on 2D area imagers eliminate the need for multiple device types.
Manufacturing and automotive part marking
DataMatrix for direct part marking on metal, plastic, and glass components. IATF 16949 traceability requirements in automotive. Aerospace MRO workflows that track individual components across decades of service life.
The challenge in manufacturing environments is not just reading 2D codes—it is reading them on curved, reflective, or low-contrast surfaces where the code has been etched or laser-marked rather than printed on a label. This requires specific scan engine capabilities beyond basic 2D decoding.
Retail and warehouse inventory accuracy
GS1 Sunrise 2027 is pushing 2D barcodes to the retail point of sale. But warehouse operations already use 2D for item-level inventory, BOPIS fulfilment, and cycle counting.
Retail scanning operations that have standardised on 2D area imagers are already prepared. Operations still running legacy laser scanners face a hardware refresh that cannot be deferred much longer.
Government and public safety
PDF417 on Canadian driver’s licences and provincial ID documents. QR codes for government asset tracking. Federal procurement specifications that reference specific symbology requirements.
Any workflow that involves scanning Canadian identification documents requires PDF417 decoding capability—which means 2D area imagers are mandatory, not optional.
The barcode format your operation needs to read determines the scanner technology you need to deploy. That connection between symbology and hardware is where procurement decisions either set you up for the next five years or lock you into a refresh cycle you did not plan for.
Enterprise barcode scanner types and when each applies
The barcode format dictates the scanner technology. Choose the wrong scanner category and the code will not read at all—no error message, no partial result, just nothing. This is not a software configuration issue you can fix remotely. It is a fundamental hardware limitation.
Four scanner categories exist in enterprise environments. Three of them are becoming legacy technology faster than most procurement cycles account for.
Laser scanners—1D only, legacy use
Laser scanners project a thin red line across the barcode and measure reflected light. They are fast on linear codes, inexpensive, and still common in light-duty retail environments where the only codes encountered are UPC-A on product packaging.
They cannot read 2D codes. If your operation touches any 2D symbology—DataMatrix on pharmaceutical packaging, PDF417 on transport documents, QR codes on asset tags—laser scanners are not an option. Full stop.
Linear imagers—1D only, light-duty
Linear imagers use CCD sensors instead of moving laser components. They read 1D codes from screens and paper, handle damaged labels somewhat better than lasers, and have no moving parts to fail.
They still cannot read 2D codes. The technology captures a single horizontal line of data. A grid-based symbology is invisible to it.
Area imagers—the enterprise default for 1D and 2D
Area imagers capture a full two-dimensional image of whatever is in front of the sensor and decode any symbology present—1D or 2D, in any orientation. This is the scanner technology inside every current-generation Zebra and Honeywell enterprise handheld.
2D area imagers read 1D barcodes as well, making them backward-compatible with existing 1D infrastructure while supporting any 2D format your supply chain partners or regulators require. If you are selecting scanning hardware for any enterprise environment in 2026, an area imager is the baseline. Anything less is a hardware refresh waiting to happen.
Mobile computers with integrated imagers
The dominant enterprise form factor in 2026 is not a standalone scanner. It is a mobile computer with an integrated area imager—devices like the Zebra TC52, TC73, MC33, or Honeywell CT45, CT60, and CK65 series.
These are Android mobile computers running enterprise applications, connected to your WMS or ERP, managed through MDM platforms like SOTI or 42Gears. The scanner is one component of a device that also handles task management, real-time inventory updates, proof of delivery capture, and communication with dispatch.
Here is what most barcode education content misses entirely: the same physical scanner can perform dramatically differently depending on how its scan engine is profiled.
A Zebra SE4770 scan engine optimized for direct part marking on metal components behaves very differently than one profiled for long-range scanning of paper labels on warehouse racking at three metres. The hardware is identical. The configuration is not.
When we stage a fleet of mobile computers for a warehouse deployment, the scan engine configuration is part of the Gold Image. The wrong profile—say, optimized for near-field DPM when the operation is scanning paper labels across a wide aisle—means every pick takes an extra second. Multiply that by 10,000 picks a day across 12 locations and you have a measurable productivity problem that traces back to a configuration decision made during staging.
This is not documented in spec sheets. It comes from deploying thousands of these devices and watching what happens when the profile does not match the workflow.
Can a 2D scanner read 1D barcodes?
Yes. Every 2D area imager reads 1D barcodes. The reverse is not true.
A 2D area imager captures a full image of whatever is in front of it and decodes any symbology present—1D or 2D, linear or matrix, horizontal or rotated 45 degrees. A 1D laser scanner reads only the single horizontal line it projects. Point it at a QR Code or DataMatrix and it returns nothing.
This asymmetry is why standardising on 2D-capable hardware eliminates future risk. Your current workflows may be 1D-only. Your supply chain partners’ label formats and your regulators’ requirements may not stay that way.
Choosing the right barcode scanner for your operation
For most Canadian enterprise operations in 2026, the decision is not 1D vs 2D. It is which 2D-capable device best fits your environment, your workflows, and your fleet management model.
That question has layers. The physical form factor—handheld gun-style vs. compact touch computer vs. wearable ring scanner—depends on ergonomics and task duration. The scan engine variant depends on whether workers are reading paper labels at arm’s length, DPM codes on metal parts, or codes displayed on screens. The ruggedness rating depends on whether devices live in climate-controlled offices or -20°C freezer environments.
But the harder problem is not choosing a single scanner. It is speccing, procuring, staging, and deploying hundreds or thousands of scanning devices across distributed locations—and then managing scanning devices through their full lifecycle as they break, age, and eventually need replacement.
This is where the difference between buying hardware and operating a fleet becomes clear.
When a scanner breaks on a Monday morning at a distribution centre in Calgary, someone has to ship a replacement. That replacement has to arrive configured identically to the device it replaces—same scan engine profile, same application stack, same MDM enrollment, same user assignment. If it arrives as a factory-fresh unit that needs an hour of IT setup before the worker can use it, you have converted a hardware problem into a productivity problem.
PiiComm is a Zebra Technologies Premier Partner and sources scanning hardware from Zebra, Honeywell, and Samsung. But sourcing scanning hardware for enterprise deployments is only the first step. PiiComm’s staging team configures every device—including scan engine optimisation for the specific use case—in Canadian facilities before deployment. When a device fails in the field, PiiComm’s Spare-in-the-Air programme ships a pre-staged replacement same-day, configured and ready to scan.
The procurement decision and the operational reality are not separate problems. They are the same problem, separated by time.
Talk to a PiiComm mobility specialist about scanner selection and device lifecycle management for your operation.
Frequently asked questions
Can a 2D barcode scanner read 1D barcodes?
Yes. 2D area imagers capture a full image and decode any symbology present, including all 1D formats. A 1D laser scanner cannot read 2D codes. Standardising on 2D-capable hardware ensures backward compatibility with existing 1D labels while supporting any 2D format your operation encounters now or in the future.
Are 1D barcodes being retired?
GS1’s Sunrise 2027 initiative enables 2D barcodes at retail point of sale globally, beginning the transition away from 1D-only infrastructure. 1D barcodes will not disappear overnight, but organisations purchasing scanning hardware today should ensure 2D capability to avoid a premature refresh cycle within two to three years.
What is the difference between a QR Code and a DataMatrix barcode?
Both are 2D symbologies serving different enterprise purposes. QR Codes are optimised for high-volume consumer scanning and can encode URLs for marketing or asset tracking. GS1 DataMatrix is the standard for healthcare, pharmaceutical serialisation, and direct part marking in manufacturing—encoding product identifiers in very small physical spaces where QR Codes would not fit.
What type of barcode scanner do I need for a warehouse?
A 2D area imager—either standalone or integrated into a mobile computer like the Zebra TC-series. Warehouse operations encounter both 1D shipping labels and 2D item-level codes. An area imager handles both formats in any orientation, eliminating the need to maintain two scanner types or retrain workers on different devices.
Why do 2D barcodes work when damaged but 1D barcodes do not?
2D barcodes use Reed-Solomon error correction, which adds redundant data to the code. At the highest correction level, a QR Code can be read even when up to 30% of the symbol is damaged. 1D barcodes have no error correction—any damage to the bars or spaces causes a read failure.
Is a QR Code a 1D or 2D barcode?
A QR Code is a 2D barcode. It encodes data in a square grid of black and white modules, both horizontally and vertically. It requires a 2D area imager to read—a 1D laser scanner cannot decode it. QR Codes support four error correction levels, allowing you to balance data capacity against damage tolerance.
The hardware decision is the easy part
The barcode format comparison is settled. 2D area imagers read everything. 1D scanners read only 1D codes. For any enterprise operation purchasing scanning hardware in 2026, the answer is clear.
The harder question—the one that determines whether your scanning infrastructure actually works at scale—is what happens after you choose the device. How does it get configured for your specific workflow? Who stages it before it ships? What happens when it breaks in the field on a Saturday? Who manages the refresh when your supplier changes their label format or a regulator mandates a new symbology?
Those are operational questions, not procurement questions. And they are the ones that separate organisations running a fleet from organisations chasing problems one device at a time.