The Complete Code 39 Barcode Guide (And a Free Bulk Generator)

Code 39 turns 52 this year, and it still outlasts barcodes half its age. It's not on your grocery receipts — but it's on the parts bin at your local auto shop, the ID badge around your neck, and the label on military cargo. If a client, a standard, or a legacy scanner has ever told you "we need Code 39," here is everything that means and how to generate it in bulk without typing each one by hand.

1. What Is a Code 39 Barcode?

Structurally, every Code 39 character is built from 9 elements — 5 bars and 4 spaces — of which exactly 3 are "wide" and 6 are "narrow." That 3-out-of-9 ratio is the actual origin of the "39" in the name, and it's also what makes the symbology self-checking: because only a small, fixed number of wide/narrow patterns are valid characters, a single misprinted or misread bar almost never accidentally produces a different valid character. It just fails to scan.

That self-checking property is the whole reason Code 39 doesn't require a check digit the way EAN-13 or UPC-A do. The character set covers uppercase A–Z, digits 0–9, a space, and seven symbols: - . $ / + % and space. An asterisk (*) marks the start and end of the code and can't appear as data. Lowercase letters aren't supported in standard Code 39 — for that, you need Extended (Full ASCII) Code 39, which pairs up standard characters to represent the extra symbols, and requires a scanner that's specifically configured to decode it.

2. Who Actually Uses Code 39 Today?

Code 39 never made it to retail checkout — that's UPC and EAN-13 territory, and always will be. But in every industry where the barcode never has to leave the building, Code 39's simplicity and near-universal scanner support have kept it in daily use for five decades:

If any of that sounds like your warehouse rather than your retail shelf, it's worth checking our warehouse bin labeling guide too — many facilities run Code 39 for legacy asset tags alongside Code-128 for active SKUs. Two applications worth a closer look on their own: encoding Vehicle Identification Numbers as Code 39 for automotive parts, and the full Code 93 vs. Code 128 comparison if Code 39's low density is a dealbreaker for your label size.

3. Code 39 vs. Code 128: Which Should You Use?

This is the question we get most from sellers and 3PLs setting up a new labeling process. Both encode letters and numbers — the difference is density, and it usually decides the answer for you.

The short version: if you're free to choose and just need the densest, most flexible label for a modern warehouse or Amazon FBA shipment, use Code 128. If a standard, a customer, or a piece of legacy equipment specifically calls for Code 39, use Code 39 — fighting the requirement usually costs more than the extra label space does.

4. The Optional Mod 43 Check Digit, Explained

Because Code 39 is self-checking, most implementations skip the check digit entirely. But some standards — LOGMARS among them — require it for an extra layer of verification. It's called a Modulo 43 (Mod 43) check digit, and unlike EAN-13's check digit, you can calculate it by hand in under a minute.

You'll almost never need to do this by hand in production — any decent generator calculates and appends it automatically when you turn the option on. It's useful to understand mainly for troubleshooting: if a barcode fails LOGMARS validation, a wrong check digit is one of the first things to rule out.

5. Why Won't My Code 39 Barcode Scan? (5 Common Fixes)

Code 39 is forgiving compared to most symbologies, but these five issues cause the vast majority of real-world scan failures we hear about:

1. Missing start/stop asterisks. If the encoded string doesn't include the leading and trailing "*", most software won't generate a valid Code 39 symbol at all — this is usually a data-entry problem, not a printing one.
2. A trailing space in your source data. A stray space at the end of a spreadsheet cell is a valid Code 39 character, so it silently gets encoded — producing a barcode that's technically correct but doesn't match the value you expected.
3. Printed too small. Code 39 needs a wide-to-narrow bar ratio of roughly 2:1 to 3:1 to stay reliably readable. Shrink the label too far and that ratio collapses, and adjacent bars start blurring together.
4. Not enough quiet zone. Scanners need blank white margin on both sides of the barcode — as a rule of thumb, at least 10x the width of the narrowest bar — or they can't reliably find where the code starts and ends.
5. Extended Code 39 on an unconfigured scanner. If you're using lowercase letters or extra symbols (Extended/Full ASCII Code 39), the scanner has to be explicitly set to decode it — otherwise it reads the raw character pairs instead of the intended text.

6. How to Generate Code 39 Barcodes in Bulk

If you're labeling more than a handful of items, typing each Code 39 value into a font-based generator one at a time doesn't scale. Here's the fast path:

Everything runs client-side in your browser — your part numbers and asset lists never touch our servers. If you'd rather see the full workflow first, the Excel-to-barcode guide walks through column setup and common formatting mistakes.

6. 仓库贴标常见问题解答