Chapter 51: The Retail POS Blockade | Before we embark on our journey through the landscape of retail barcodes, let us establish a clear vantage point. The retail point-of-sale environment is governed by a simple yet absolute rule: the Universal Product Code (UPC-A) in North America and the European Article Number (EAN-13) internationally reign supreme. These symbologies, designed exclusively for numeric data with compact, high-density patterns, are the undisputed standard for checkout systems worldwide. Code 39, despite its versatility and reliability in other sectors, was never a contender for this domain. Its alphanumeric capacity, variable length, and significantly lower data density make it fundamentally unsuitable for the high-speed, space-constrained world of retail checkout. This chapter explores the technical chasm that separates Code 39 from the retail realm, examining how the specific characteristics of Code 39---its self-checking nature, its alphanumeric flexibility, and its moderate density---have relegated it to industrial, military, and logistical applications while erecting an insurmountable blockade at the retail POS. | 
| The Unassailable Standard: How Retail Conquered the Checkout | The modern retail experience is built upon a foundation of speed, accuracy, and simplicity. When a cashier scans a product at the checkout counter, an intricate chain of events is set in motion: the barcode is read, the product is identified, the price is retrieved from a database, the inventory is updated, and the transaction is completed---all in a fraction of a second. This seamless process is made possible by a global standard that dictates exactly which barcode symbology is used on consumer goods. That standard is the UPC-A and its international counterpart, the EAN-13 . | The UPC-A (Universal Product Code) was first scanned in a supermarket in 1974, marking the beginning of a revolution in retail. It is a 12-digit numeric-only barcode that has become the backbone of retail in the United States and Canada. Its counterpart, the EAN-13 (European Article Number), is a 13-digit version used in the rest of the world. Both are based on the same underlying encoding principles and are designed to be universally readable by point-of-sale systems across the globe. | Why did these specific symbologies triumph in retailThe answer lies in their technical design. Both UPC-A and EAN-13 are numeric-only symbologies. They encode only the digits 0 through 9, which is perfectly adequate for a product identification system where every item is assigned a unique numeric identifier issued by GS1, the global standards organization that oversees retail barcodes. By limiting the character set to ten digits, these symbologies achieve a remarkable level of data density. Each character in a UPC-A barcode is represented by a pattern of seven modules (bars and spaces), allowing a significant amount of information to be packed into a relatively small space . This density is critical for retail products, which often have limited label space and must accommodate other information like branding, ingredients, and nutritional facts. The compact nature of UPC-A and EAN-13 means that even small items like lipsticks, batteries, or chewing gum can carry a scannable barcode without covering the entire package. | Furthermore, UPC-A and EAN-13 are designed with a mandatory check digit---a single digit calculated from the other digits in the code that serves as a built-in error detection mechanism. This check digit is integrated into the barcode's structure and is automatically verified by every scanner, ensuring that a misread will almost certainly be caught before it can cause a transaction error. The combination of high density, a dedicated global infrastructure, and robust error checking makes these retail codes not just a choice, but the only practical option for the high-volume, high-speed demands of retail point-of-sale systems . | 
| Code 39: A Portrait of an Industrial Workhorse | In the shadow of the retail behemoths, Code 39 emerged as a different kind of tool---a rugged, flexible, and reliable workhorse built for the industrial world. Conceived in 1974 by Dr. David Allais and Ray Stevens of Intermec, Code 39, also known as Code 3 of 9, was the first barcode symbology capable of encoding alphanumeric characters . Its name derives from its most fundamental structural characteristic: each character in Code 39 is made up of nine elements---five bars and four spaces---with exactly three of those elements being wide and the remaining six being narrow . This 'three wide out of nine' pattern is the defining feature of the symbology and the source of its name. | Unlike UPC-A and EAN-13, which are numeric-only, Code 39 can encode the full uppercase alphabet (A-Z), the digits 0-9, and seven special characters: space, minus (-), plus (+), period (.), dollar sign ($), slash (/), and percent (%) . This alphanumeric capacity was revolutionary at the time of Code 39's introduction. It meant that for the first time, barcodes could be used to encode letters as well as numbers, opening up a vast new range of applications beyond simple product identification. However, this flexibility came at a cost: Code 39 is a low-density symbology. Because each character is encoded using nine elements, and because it uses an inter-character gap (a space between characters that is not part of the data), a Code 39 barcode is significantly longer than a UPC-A or EAN-13 barcode containing the same amount of information. A 10-character Code 39 barcode is roughly 40% wider than an equivalent Code 128 barcode, and considerably wider than a retail code of comparable data length . | Despite its low density, Code 39 possesses a feature that has cemented its longevity and reliability: it is self-checking. This is a crucial technical property that arises from the specific encoding scheme. In a self-checking symbology, the pattern of wide and narrow elements within each character is unique, and a single error in the width of a bar or space cannot be misinterpreted as a different valid character . If a printing defect or scanning error alters the width of a single element, the pattern no longer matches any legitimate character in the Code 39 set, and the decoder will reject it. This self-checking ability means that a mandatory check digit is optional in Code 39, although a Modulo 43 check digit is often added in critical applications for an extra layer of error detection . This inherent robustness has made Code 39 the preferred choice in industries where reliability is paramount, such as the United States Department of Defense (MIL-STD-1189 and later MIL-STD-130), the automotive sector (AIAG B-1), and the healthcare industry (HIBC) . | 
| The Anatomy of a Mismatch: Why Code 39 Cannot Cross the Retail Threshold | The two worlds---retail and industrial---have different requirements, and Code 39's characteristics, while strengths in one domain, become liabilities in the other. Let us examine the specific ways in which Code 39's technical attributes clash with the demands of the retail point-of-sale environment. | 1. Alphanumeric Capacity: The Unnecessary Burden | The most obvious difference between Code 39 and retail codes is the character set. Code 39's ability to encode letters is its greatest asset in applications like asset tracking (where a barcode might represent a serial number like 'A-123-B'), automotive part labeling, or military logistics, where alphanumeric identifiers are standard. The U.S. Department of Defense's LOGMARS program and the automotive industry's AIAG standards rely on Code 39 for exactly this reason . | However, in retail, alphanumeric capacity is not only unnecessary---it is a liability. The GS1 system assigns a unique 12- or 13-digit number to every retail product. This numeric identifier is the product's global passport, recognized by every retailer, distributor, and point-of-sale system in the world. There is no provision for letters in a UPC-A or EAN-13 barcode. A Code 39 barcode on a retail product would be an anomaly, carrying a data format that retail scanners and backend systems are not configured to process. While many modern POS systems can technically read Code 39 if configured to do so, they are not equipped to interpret its data in the context of a retail transaction . They expect a 12- or 13-digit numeric code that maps directly to a product record in the store's database; a Code 39 barcode containing letters or an unexpected data length would be rejected or cause an error. This is not merely a technical limitation but a fundamental incompatibility with the entire retail ecosystem, which is built around the GS1 standard. | 
| 2. Data Density: The Space Problem | Perhaps the most insurmountable obstacle for Code 39 in retail is its low data density. As discussed earlier, Code 39 uses nine elements to encode each character, and it includes an inter-character gap. This means that a Code 39 barcode is physically much longer and wider than a UPC-A or EAN-13 barcode encoding the same amount of information. In the retail environment, where packaging space is at a premium and every square millimeter is valuable real estate, this is a significant disadvantage. | Consider a typical consumer product: a small box of candy, a lipstick tube, a package of batteries, or a paperback book. The available space for a barcode on such packaging is often extremely limited. UPC-A and EAN-13, with their high density and numeric-only encoding, can fit comfortably into these small areas. A Code 39 barcode, however, would be far too large to be printed legibly on such packaging. Even if the product packaging was large enough, the label would have to be disproportionately wide to accommodate the Code 39 symbol, which would be unsightly and impractical. The low density of Code 39 would also require a larger 'quiet zone'---the blank margin on either side of the barcode that is essential for proper scanning. The minimum quiet zone for Code 39 is 10 times the width of the narrow bar, which further increases the space requirements . | 
| 3. The Check Digit: Optional vs. Mandatory | Another key distinction between Code 39 and retail codes lies in the use of check digits. In UPC-A and EAN-13, the check digit is mandatory. It is an integral part of the code and is calculated according to a strict mathematical formula. This check digit is automatically verified by the scanner, providing a powerful safeguard against errors. If a scanner misreads a digit or a label is damaged, the check digit calculation will fail, and the scanner will reject the code, prompting the cashier to try again. | Code 39, in contrast, does not require a check digit. Its self-checking nature provides a degree of error detection at the character level, but it does not offer the same level of data integrity as a mandatory check digit . While a Modulo 43 check digit can be added to Code 39 (and is often required by military and automotive standards), it is optional. In a retail environment, where speed and accuracy are paramount, relying on an optional check digit is not acceptable. The retail infrastructure demands a guarantee of data integrity that can only be provided by a mandatory check digit that is an inviolable part of the barcode standard. | 
| 4. The Legacy Infrastructure and Reader Configuration | The retail point-of-sale system is a complex and deeply entrenched infrastructure. The scanners, the cash registers, the inventory management software, and the supply chain systems are all designed around the UPC-A and EAN-13 standards. Changing this infrastructure to accommodate a different symbology, even one as venerable as Code 39, would be a monumental and expensive undertaking. Retailers have no incentive to do this because their existing systems work perfectly and efficiently. The scanners at retail checkout lanes are optimized to read UPC-A and EAN-13 quickly and reliably. While some may be capable of reading Code 39, they are typically configured to prioritize the retail codes and may not even attempt to decode Code 39 by default . Configuring scanners to read Code 39 would require manual intervention and could introduce the potential for misinterpretation or errors, especially if a scanner encountered a Code 39 barcode on a product that was not intended to be read in that context. The risk of confusion and accidental data entry errors makes the idea of introducing Code 39 into the retail POS environment inadvisable. | 
| Code 39 in the Wild: Where the Workhorse Thrives | While Code 39 is excluded from the retail sector, its unique combination of features---alphanumeric capacity, self-checking reliability, and straightforward implementation---makes it the ideal choice for a wide range of non-retail applications. Let us explore the diverse industries where Code 39 is not just used, but often mandated. | Automotive Industry: The AIAG Standard | The automotive industry relies on a complex and global supply chain, where parts and components are manufactured in one country and assembled in another. Traceability is crucial for quality control, safety recalls, and inventory management. The Automotive Industry Action Group (AIAG) established a standard for barcode labeling in the automotive industry, and Code 39 is at the heart of it. The AIAG B-1 standard specifies Code 39 for identifying parts and materials throughout the supply chain . An automotive part might carry a Code 39 barcode containing a part number, a supplier code, a date of manufacture, and a serial number. The alphanumeric capacity of Code 39 is essential here, as these identifiers often include letters and hyphens (e.g., 'A-12345-B'). The self-checking nature of Code 39 ensures that these critical barcodes can be read reliably even if the labels are exposed to oil, grease, or other harsh conditions. The automotive industry values reliability and consistency, and Code 39, with its decades-long track record, provides both. | 
| U.S. Military and Defense: LOGMARS and MIL-STD-130 | The U.S. Department of Defense is one of the largest and most demanding users of barcode technology. It has a vast inventory of assets, from individual weapons and spare parts to entire aircraft carriers, and it needs a reliable and standardized way to track every single item. Code 39 was adopted as the standard barcode symbology for the Department of Defense's LOGMARS (Logistics Applications of Automated Marking and Reading Symbols) program . It is also specified in MIL-STD-130, which defines the requirements for identification marking of U.S. military property. This means that virtually every item purchased by the U.S. military, from a box of pens to a tank engine, must be marked with a Code 39 barcode. The military values Code 39 for its robustness, its alphanumeric capacity, and its reliability in harsh and unpredictable environments. It is a symbology that can be printed on a wide variety of materials, from paper labels to metal plates, and can be read reliably even when partially damaged or dirty. The military's adoption of Code 39 has been a major factor in the symbology's longevity and widespread acceptance. | 
| Healthcare: The Health Industry Bar Code (HIBC) | The healthcare industry is another sector where Code 39 plays a critical role. The Health Industry Bar Code (HIBC) standard, developed by the Health Industry Business Communications Council (HIBCC), is used to label medical devices, pharmaceuticals, and other healthcare products . The HIBC standard mandates the use of Code 39 for its primary labeling, building upon the symbology's alphanumeric capability to encode information such as the manufacturer's identifier, the product catalog number, and a lot number or expiration date. This information is essential for patient safety, inventory management, and supply chain logistics in healthcare settings. Hospitals use Code 39 barcodes to track surgical instruments, manage medical supplies, and verify that patients are receiving the correct medication. The self-checking property of Code 39 is particularly valuable in healthcare, where a scanning error could have serious consequences. The HIBC standard adds a Modulo 43 check digit to Code 39 to enhance error detection further, ensuring a high level of accuracy in these critical applications. | 
| Industrial Manufacturing and Logistics | Beyond the specific standards of automotive, military, and healthcare, Code 39 is widely used in general industrial manufacturing and logistics. In a factory, Code 39 barcodes might be printed on work-in-progress materials to track their progress through the assembly line. In a warehouse, Code 39 labels on pallets and bins help workers identify and locate items quickly and accurately. The ability to encode alphanumeric data is essential for these applications, as item numbers and location codes often contain a mix of letters and numbers. The reliability and simplicity of Code 39 make it a workhorse in these demanding environments, where barcodes must withstand rough handling, dust, and fluctuating temperatures. Many warehouse management systems and enterprise resource planning (ERP) systems have built-in support for Code 39, further cementing its place in the industrial landscape. Code 39 is also frequently used for internal asset tracking, where organizations use it to identify computers, furniture, and other valuable equipment . | 
| Government and Beyond | The U.S. government's use of Code 39 extends beyond the Department of Defense. Many other federal agencies use Code 39 for internal asset tracking and identification. The Library of Congress, for example, has used Code 39 for decades to track books and other materials. Its simplicity and the fact that it is an open standard make it attractive for government applications, where the ability to avoid proprietary systems is often a requirement. Even the U.S. Postal Service has used Code 39 for internal mail sorting and tracking, although it has moved to other standards like Code 128 and Intelligent Mail for many applications. Code 39 has also found a niche in point-of-sale systems that are not part of the mainstream retail ecosystem. Some smaller retailers or specialized businesses, such as rental car agencies or equipment rental outlets, use Code 39 to track their inventory because they need to encode alphanumeric data that is not compatible with the numeric-only UPC-A standard . | 
| The Divergence Point: A Tale of Two Symbologies | The journey of Code 39, from its invention in the early 1970s to its role in modern commerce, is a story of specialization. It was never intended to compete with UPC-A or EAN-13 in the retail arena. Rather, it was designed to fulfill a different need: the need for a simple, reliable, and flexible barcode that could encode alphanumeric data in environments where space was not the primary constraint. The retail industry, with its vast scale, its demand for speed, and its need for compact symbologies, chose a different path. UPC-A and EAN-13 were specifically designed for the retail environment, and they have been optimized to meet its unique demands. | The two symbologies represent different branches on the barcode family tree, each adapted to its own niche. Code 39 is the rugged off-road vehicle, capable of handling rough terrain and carrying a variety of cargo. UPC-A and EAN-13 are the high-speed racing cars, built for speed and efficiency on a smooth, well-maintained track. Trying to use Code 39 in a retail store would be like trying to drive an off-road vehicle in a Formula 1 race: it is simply the wrong tool for the job. The retail point-of-sale blockade is not a rejection of Code 39's quality or capability; it is simply a recognition that the retail environment has its own specialized requirements, and Code 39 does not meet them. The symbology was never a contender for that domain, and it never needed to be. | 
| Beyond the Retail Barrier: The Enduring Legacy of Code 39 | Despite its exclusion from the retail point-of-sale, Code 39 has secured a lasting place in the history and current practice of automatic identification and data capture. Its enduring legacy is a testament to its thoughtful design and its ability to meet the needs of sectors that require more than just a numeric code. As we have seen, its alphanumeric capacity, its self-checking nature, and its simplicity have made it the standard in military, automotive, and healthcare applications. In these industries, the ability to encode a serial number like 'A-12345-B' or a part number like 'MK-7A' is indispensable, and Code 39 provides a reliable and universally recognized way to do so. | The adoption of Code 39 by the U.S. Department of Defense and the automotive industry gave it a critical mass of acceptance, leading to widespread use in other industrial and government sectors. This legacy effect is powerful: once a symbology is entrenched in a large and influential organization, it becomes a de facto standard for its suppliers and partners, creating a self-reinforcing cycle of adoption. Today, Code 39 remains one of the most commonly encountered barcode symbologies in the world, even if it is rarely seen by the average consumer. It is the quiet, unseen workhorse of the industrial economy, ensuring that everything from hospital medications to military equipment is tracked accurately and reliably. | Moreover, the simplicity of Code 39 has made it a favorite for hobbyists and small businesses. Because it can be printed with a standard printer using barcode fonts, and because it does not require a check digit to be generated, it is accessible to anyone who needs to create a simple barcode labeling system. This accessibility, combined with its robust design, ensures that Code 39 will continue to be used for decades to come, even as newer, more advanced symbologies like Code 128 and Data Matrix gain ground. Code 39 is more than just a barcode; it is a symbol of a pivotal era in the history of automation, a time when the power of alphanumeric identification was first unleashed on the world. | 
| Detailed Summary: The Retail Blockade and the Industrial Domain | The retail point-of-sale blockade against Code 39 is not a matter of preference but a consequence of fundamental technical incompatibilities. We have traversed the key differences that define this divide: | 1. Character Set: Retail's UPC-A and EAN-13 are numeric-only, optimized for the GS1 system of product identification. Code 39's alphanumeric capacity, while a strength in industrial settings, is an unnecessary and problematic burden in retail, where letters are not part of the product identifier standard. | 2. Data Density: The retail standard prioritizes compactness to fit on packaging. UPC-A and EAN-13 achieve high density through their numeric encoding. Code 39's 'three of nine' structure and inter-character gaps make it significantly less dense, requiring approximately 40% more space than an equivalent Code 128 barcode, rendering it impractical for small retail items. | 3. Check Digits: A mandatory check digit is an inviolable part of the retail standard, providing a powerful layer of error detection. In Code 39, a check digit is optional, and its self-checking property, while robust, does not provide the same level of data integrity verification that retail demands for high-speed transactions. | 4. Infrastructure and Standards: The entire global retail ecosystem---from scanners and POS systems to inventory databases and supply chains---is built around the GS1 standards of UPC-A and EAN-13. Introducing Code 39 into this mature and efficient infrastructure would require costly and disruptive changes, with no corresponding benefit. Modern scanners may technically read Code 39, but they are not configured to process it in a retail context, and manual reconfiguration is impractical at scale. | 5. Application Domains: These technical differences have created a clear division of labor. Code 39 is not a failed retail symbology; it is a successful industrial symbology. It thrives in the automotive industry (AIAG), the U.S. military (LOGMARS/MIL-STD-130), and healthcare (HIBC), where its alphanumeric capacity, self-checking nature, and rugged simplicity are invaluable assets for tracking parts, supplies, and equipment. It is also widely used in general manufacturing, logistics, and government asset tracking. | 
| In conclusion, Code 39's failure to penetrate the retail point-of-sale market is not a failure of the symbology itself, but a testament to the power of specialization and standardization. The retail world chose a tool that was specifically designed for its unique needs, while the industrial world chose a different tool that was better suited to its own. Code 39 may be barred from the checkout counter, but it remains an indispensable and enduring pillar of the barcode ecosystem, proving that sometimes, the most effective technology is the one that knows its place and does its job with unwavering reliability. |
|
cs@easiersoft.com