Blog

Invoice numbers explained: an invoice number is a unique ID assigned to every invoice you issue. It tracks payments, reconciles records, and keeps you audit-ready. Never reuse, skip, or delete one. The US sets no federally mandated format — but IRS recordkeeping rules still apply.

What Is an Invoice Number? (And What It Is Not)

An invoice number is the unique identifier assigned to one specific invoice you issue. It exists so that you, your customer, your bookkeeper, and a tax authority can locate the same transaction without relying on names, dates, or amounts that repeat constantly across a set of books.

In practice, the invoice number is the primary key of your accounts receivable ledger. When a customer’s payment lands with a memo line, the characters in that memo are the only thing that reliably ties the cash to the invoice it settles. Statrys describes the number as the reference that lets you locate and verify any specific transaction.

Every invoice number comes down to three components: a prefix, a sequential number, and optionally a date segment, plus zero-padding to keep the digits consistent. The format itself is yours to choose. Uniqueness is not. As Lev Tretyakov, CEO of Fortador USA, puts it: “We always include an invoice number for all sales we make. The invoice number makes it easy to pull up the transaction and provide accurate assistance to our clients.”

It also helps to know what an invoice number is not. It is not a purchase order number, a quote number, a receipt number, or a credit note number. Each of those is issued by a different party, at a different point in the transaction, for a different purpose.

The short version: numbering is an internal control, not an aesthetic decision.

The Three Parts of Every Invoice Number

A prefix identifies the document type or issuing entity, such as INV for a sales invoice or a branch code in a multi-location business. A date segment places the invoice in the right tax period, which speeds up retrieval during a review. The sequential number is the part that carries the control — it must increase logically and never repeat. Statrys recommends starting at 0001 rather than 1 so the sequence accommodates growth without a mid-year format change.

Where the Concept Came From: From Clay Tablets to Internal Controls

Numbered commercial records are not a modern invention. Around 5,000 years ago, merchants in ancient Mesopotamia used cuneiform script on clay tablets to document trade transactions, including quantities, prices, and the parties involved — and roughly 85% of the cuneiform tablets uncovered at Uruk (3000 BCE) represent economic records, according to Wikipedia’s overview of invoicing. Standardized printed invoice forms emerged with the printing press in the 15th century, and printed invoices with company names and logos were widespread by the 19th century. Digital and automated numbering systems followed in the 20th and 21st centuries.

The One Rule of Invoice Numbering: Never Reuse, Skip, or Delete

If you remember one rule from this guide, make it this one: one number maps to one invoice, once and only once. Every serious source on the topic converges on the same principle, and almost every numbering problem traces back to violating it.

A gap in the sequence is not automatically wrong, but an unexplained gap is a problem. During an audit or an internal review, a missing number raises a specific question — was there an invoice here, and if so, where did it go? Alaan notes that gaps are acceptable only when voided invoices are clearly documented; otherwise the sequence looks incomplete.

Reusing a number creates a different failure. If two transactions carry the same identifier, a payment that arrives against that number cannot be matched to a specific invoice, and the ambiguity persists in the ledger indefinitely.

This is why numbering matters beyond bookkeeping mechanics. A continuous, explainable, traceable sequence is itself evidence that your reported revenue is complete. Statrys points out that gaps or duplicate numbers raise questions about whether all income was reported, which matters more if your books are ever reviewed.

The operational rule that follows is simple: when an invoice is wrong, void it rather than delete it. Keep the number, mark the document void, and note the reason. The number stays in the sequence permanently, even though it will never produce a payment.

There is a second baseline rule that keeps your numbering aligned with reality. Lilach Bullock uses a fixed rule of invoicing within 24 hours of work being completed or a milestone being hit, with no exceptions and a calendar reminder attached. That discipline keeps the sequence order identical to the order in which business actually happened.

Why a Missing Invoice Number Triggers Questions

A missing number forces anyone reviewing your records to search by customer name, amount, or date instead of by a key. That search is slower and less precise, and it can end in a dead stop. Statrys frames the practical cost this way: when a client references a past transaction, the invoice number is what matches it to a record, and without one you rely on memory or manual searching. Multiply that across several clients and the gap becomes genuinely difficult to resolve.

Does the IRS Require Invoice Numbers? What US Rules Actually Say

Here is the answer most US readers are looking for: there is no federal requirement governing invoice number format, prefix, starting value, or continuity. Statrys states plainly that there is no legal requirement in the US to use a specific invoice number format, and no single federal requirement that invoice numbers be strictly sequential — though sequential numbering is standard practice and the default in most accounting software.

But “no mandated format” is not the same as “no recordkeeping requirement.” IRS Publication 334 (Tax Guide for Small Business) sets out the general record-keeping standards that apply to small business income documentation. An invoice number is what lets those records tie to each other — it is the thread that connects a payment to a sale to a reported figure.

Retention is the next layer. Ramp notes that the IRS and most tax authorities require keeping invoices for at least three to seven years depending on jurisdiction and business type, and recommends erring longer since digital storage is inexpensive. The practical implication for numbering is that your sequence needs to remain readable and searchable across that entire window, which is an argument against formats you will not be able to reconstruct in five years.

Why does this matter in a review? A complete sequence requires almost no explanation. Statrys describes the alternative: gaps or duplicate numbers raise questions about whether all income was reported, and this matters more if you are subject to an IRS audit or need to produce invoices on request.

For a US small business that wants a defensible default with no deliberation required, use INV-YYYY-NNNN, start at 0001, and decide explicitly whether the sequence resets annually or runs continuously. The European Commission’s work on the Late Payment Directive has estimated that non-payment and late payment of invoices cause 25% of corporate bankruptcies — a non-US figure included here only to illustrate why collection discipline carries real economic weight, not to draw conclusions about US requirements.

One caveat before moving on: this is general information, not tax advice. Confirm your specific recordkeeping and retention obligations with a tax professional.

Federal vs. State: Where Invoice Number Rules Actually Live

The federal layer governs income recordkeeping. The state layer is where invoice content requirements are more likely to appear, particularly around sales tax. Because sales tax is administered state by state, the required fields on a sales invoice can differ depending on where you operate and where your customer is. If you sell into multiple states, check the requirements for each jurisdiction you have nexus in rather than assuming one template covers everything — and confirm the specifics with your accountant.

How Other Jurisdictions Differ (UAE, UK, India, Philippines)

Other countries make numbering far more prescriptive than the US does, which is useful context for anyone comparing systems or reading international guides. In the UAE, VAT law requires a unique, sequential invoice number on every tax invoice, Alaan explains, and missing or duplicate numbers can trigger audit queries or rejected claims; UAE VAT records must generally be retained for at least five years. In the UK, GOV.UK sets out what an invoice must include for VAT purposes. India’s GST e-invoicing system uses a jurisdiction-specific Invoice Reference Number (IRN), a registration identifier generated for an e-invoice rather than the generic “reference” field on an ordinary bill. In the Philippines, invoicing and tax requirements are administered by the BIR. If you operate across borders, treat numbering as a per-jurisdiction compliance question.

Invoice Number vs. PO Number vs. Reference Number: A Numbering Identity Table

The fastest way to eliminate numbering confusion is to separate each identifier by what it points to, who issues it, and when it comes into existence. The table below maps the identifiers that most often get conflated on a single invoice.

The core distinctions are worth stating plainly. A PO number identifies the buyer’s purchase order, and the buyer — not you — supplies it. An invoice reference number connects the invoice to something else useful, such as a customer account, project, job, contract, or order, and does not necessarily identify the invoice itself. A receipt number confirms collection of payment, not the sale. InvoiceAtlas summarizes the relationship well: an invoice can contain both an invoice number and a PO number because each one connects the transaction to a different document, and they are not duplicates.

If your customer requires a PO number, quote the one they gave you — never substitute an internal reference for it. InvoiceAtlas lists “creating a PO number instead of using the one supplied by the customer” among the most common reference mistakes. If the required PO number is missing, ask the customer’s contact before you send the invoice.

The Same Document, Two Perspectives: AR and AP

One party’s invoice is the other party’s bill. From your side of the transaction, the invoice number identifies a receivable you are owed. From your customer’s side, the same number identifies a payable they must clear. Invoice Data Extraction emphasizes that the supplier-issued invoice number is the durable link back to the source document, and that AP teams should record the full value as printed — including prefixes, suffixes, separators, and leading zeros. Changing INV-00417 to 417 makes duplicate detection and supplier queries less reliable because the recorded value no longer matches the source.

Why Separate Number Series Prevent Downstream Matching Errors

Credit notes, pro forma invoices, and any other adjustment documents should run in their own series with their own prefixes, such as CN- or PF-. Alaan recommends distinct prefixes for invoices and credit notes to prevent sequence contamination and protect audit clarity. Statrys makes the same case for pro forma invoices: because they are not final billing documents, they should not run in the same sequence as your official invoices. Mixing them creates documents that look like duplicates of legitimate invoices, which is a self-inflicted reconciliation problem.

Invoice Numbering Formats Explained: Sequential, Date-Based, Client-Coded, Project-Based

Take a typical format apart once and the rest are variations on the same theme. INV-2026-000127 carries a prefix (INV) that identifies the document type, a year segment (2026) that makes retrieval by tax period straightforward, and a four-digit zero-padded sequence (0127) that supports more than ten thousand invoices per year without changing the number of digits.

Four approaches cover the overwhelming majority of US small businesses. Sequential numbering increments by one and is the default in most accounting software. Date-based numbering embeds the period in the number. Client-coded numbering attaches a customer or account prefix. Project-based numbering attaches an engagement code. None of these is more compliant than another in the US — the choice depends on how you actually search your records.

A comparison from Tofu lays out the trade-offs fairly: sequential numbering produces no gaps and audits easily but carries the risk of overlap during system updates; chronological numbering organizes by date but can produce long numbers; alphanumeric formats encode useful detail but require strict format documentation; and fully custom formats adapt to unusual needs at the cost of complexity.

Sequential Numbering: The Default That Audits Easiest

Sequential numbering is the lowest-friction option and the one most software defaults to. Start at 0001 and increment by one for each invoice. Tofu describes it as well suited to small businesses issuing regular invoices without complex categorization needs, and Statrys recommends starting at 0001 rather than 1 to accommodate growth and present more professionally on client-facing documents. The one weakness to plan around is overlap during system changes or migrations, which is why a documented freeze point matters more than the format itself.

Date-Based Numbering and the Annual Reset Question

Date-based numbering embeds the period directly into the identifier, using formats such as 2026-04-001 or YYYYMMDD-XXX. Tofu notes that if you issue multiple invoices on the same day, a numerical suffix distinguishes them. This approach naturalizes annual resets because the year segment already separates one period from another — but it does not remove the need for a written policy. Statrys cautions that switching reset behavior mid-year without documentation creates confusion, and that either a continuous or an annual-reset sequence is acceptable as long as you pick one and stay with it.

Client-Coded and Project-Based Numbering for Agencies and Multi-Entity Businesses

Client-coded formats attach a customer prefix, so CLIENT01-001 sorts invoices by account without opening individual files. Project-based formats attach an engagement code so all invoices tied to one piece of work can be pulled together. Tofu illustrates the pattern with formats like CL-001 for a client code or PROJ-A-001 for a project identifier. The governance cost is real: prefix lists need controls so two branches or teams cannot claim the same code, and codes must stay short enough to survive portal, spreadsheet, and API field limits. Set the code list centrally before anyone starts issuing.

How to Choose and Set Up Your Invoice Numbering System: A 6-Step Framework

This is a decision path, not a format menu. Answer three questions first: is your business a single entity, multi-branch, multi-client, or project-based? Do you need to retrieve invoices by tax year or accounting period? Who actually assigns numbers, and in what system? Only then pick a format.

Step 1 — Choose your prefix. Use prefixes to distinguish document types: INV for sales invoices, CN for credit notes, PF for pro forma documents. Alaan recommends separate prefixes for invoices and credit notes specifically to avoid sequence contamination. If you operate multiple entities or branches, add a controlled entity code and make sure no two entities share it.

Step 2 — Set the sequence length and zero-padding. Work backward from your maximum expected invoice volume over the next three to five years, then pad to that width. Four digits (0001) covers up to 9,999 invoices per year; five digits covers 99,999. Choosing the width up front avoids the renumbering problem that appears when you outgrow a three-digit sequence in month eight.

Step 3 — Write down your reset policy. Decide whether the sequence resets at the start of the year or runs continuously forever. If it resets, decide how the reset avoids collisions with historical numbers — the common solution is to embed the year in the identifier rather than returning the running number to 0001. Record the policy in an accounting policy document rather than leaving it as tribal knowledge.

Step 4 — Document who assigns numbers and when. The assignment rule that matters most is timing: numbers should be generated when the invoice is issued, not when a draft is created. Alaan explains that assigning numbers at the draft stage leaves gaps behind when drafts are abandoned or edited. Lilach Bullock applies the same principle at the workflow level with her rule of invoicing within 24 hours of completion or milestone, which keeps the sequence order consistent with the order work was actually delivered.

Step 5 — Fix the template. Place the invoice number at the top of the document, next to the issue date and the customer’s details, and keep that position identical across every template version. Statrys notes that most invoicing software and standard templates already place it there by default, which makes it easy for a client to find when paying or asking a question.

Step 6 — Set a check point. Run a monthly reconciliation of your numbering sequence against your issued invoices. Look for duplicates and unexplained gaps while the month is still open. Alaan recommends periodic sequence reviews to confirm there are no unexplained gaps or duplicates, because early detection avoids painful corrections during an audit.

Where the Invoice Number Should Appear on the Document

The invoice number belongs near the top of the invoice, in the header block, close to the issue date and customer information. That placement lets a customer retype it accurately into a payment memo and lets an accounts team find it without scanning the whole document. Whatever template you use, the field label and position should stay consistent — InvoiceAtlas recommends keeping important identifiers together near the main invoice details, with the invoice number shown first, followed by the PO number or other reference, then the invoice date and due date.

How to Write an Annual Reset Policy (and When Not To Reset)

A workable reset policy answers four questions in writing: does the sequence reset, on what date, how does the new series avoid colliding with historical numbers, and where is the policy recorded? Alaan confirms that invoice numbers can restart at the beginning of a new financial year provided the reset is clearly documented and the sequence stays continuous within that year. The safer pattern for most US businesses is to embed the year in the identifier — INV-2026-0001 followed by INV-2027-0001 — rather than returning a bare running number to 0001, which risks two open invoices sharing a short reference. If you have open receivables spanning a year end, resetting is usually more trouble than it is worth; run a continuous sequence instead.

Changing Formats Mid-Year: Freeze Points and Migration Rules

Changing formats mid-year is one of the most reliable ways to break continuity. Alaan warns that format changes mid-period complicate reconciliation and reporting, and Tofu lists inconsistent formats as a direct cause of sorting errors when invoices stop following the established system.

If you need to change, set a freeze point — typically the start of a fiscal year or a new quarter — reconcile the old sequence completely before the switch, and never return to the old format. Historical invoices are not renumbered. HashMicro’s numbering guidance describes the migration sequence in practical terms: freeze the cutover point, reconcile open receivables, communicate the new format, and obtain approval for any exceptions before the first invoice leaves the new system.

Why Invoice Number Discipline Is a Cash Flow Lever, Not Just a Compliance Task

Numbering and invoice timing are two halves of the same cash flow mechanism. The invoice date starts the clock on your payment terms. The number is what lets the incoming payment be matched to the right invoice once it arrives. Together they determine how long your cash sits outside your account.

That second half is where the friction shows up. Payment memos are frequently incomplete or mistyped, and a unique, continuous invoice number is the one key that can still reconcile an imperfect payment. Statrys describes the consequence of not having one: tracking outstanding invoices and reconciling payments relies on memory or manual searching, and managing multiple invoices across several clients makes any gap in the sequence significantly harder to resolve.

The scale of the problem is well documented on the receivables side. According to the 2025 Intuit QuickBooks Small Business Late Payments Report, 56% of small businesses have late payments owed to them. On the more severe end, the European Commission’s Late Payment Directive work has estimated that non-payment and late payment of invoices cause 25% of corporate bankruptcies — a figure from a non-US regulatory context, included here as background on why collection timing has outsized consequences.

There is a first-person illustration of how much timing alone can cost. Lilach Bullock describes sending invoices a week or more after delivering work while on standard 30-day terms, which stretched what looked like a 30-day cycle to roughly 45 days from delivery to payment. Across five or six clients on rolling retainers, that produced a persistent cash gap of a few thousand pounds every month. The fix was a single rule — invoice within 24 hours of completion or milestone, no exceptions — which pulled almost two weeks back into the cash cycle without changing a single client’s payment terms.

The same discipline shows up on the service side. As Lev Tretyakov of Fortador USA notes, the invoice number “makes it easy to pull up the transaction and provide accurate assistance to our clients.” Both benefits come from the same underlying habit: a numbering system that stays in step with real business events.

Common Invoice Numbering Mistakes and How to Repair a Broken Sequence

Most numbering failures fall into a short list: duplicate numbers, skipped numbers, deleted or edited numbers, voided invoices with no explanation, format changes mid-year, and multiple systems each generating their own numbers. Each has a documented repair path.

For context on how common invoicing errors are in general, a second-hand compilation cited by Tofu states that 39% of invoices contain errors. That figure is republished without a marked statistical year and should be treated as indicative only — it is useful for illustrating that invoicing errors are not rare, not for drawing conclusions about numbering accuracy.

I Found a Duplicate Invoice Number — Now What?

Do not delete either document. First confirm which of the two is the original issued invoice. Keep the original number as it stands. Void the duplicate and reissue the correct invoice under a new number. Note the original number and the reason for the void directly on the record, and retain the correction in your files. Statrys describes the equivalent workflow for a numbering mistake: mark the incorrect invoice as void and note the reason, then issue a corrected invoice with a new number, which keeps records complete and prevents gaps that could raise questions during an accounting review. Never reassign the duplicated number to a new document.

How to Document a Skipped Number Without Reusing It

A skipped number needs a written explanation, not a backfill. Do not issue a new invoice into the empty slot, and do not reuse the number for anything else. Instead, record the exception in a log with five fields: the number, the date, the reason (voided, never issued, or system error), the action taken, and the reviewer. HashMicro’s control framework treats missing exception logs as a distinct failure mode, because without one, finance cannot distinguish a legitimate exception from an error. Alaan makes the same point about voided invoices: leave voided numbers in the sequence with a documented reason so reviewers can see the run is complete.

Migrating from Excel to Invoicing Software Without Breaking the Sequence

Migration is where duplicate numbers most often appear, because a legacy spreadsheet and a new system can both be generating numbers for a short window. Fix it in order. Freeze the cutover point and stop issuing from the old system. Reconcile the old sequence completely, including any open receivables. Configure the new system’s starting number and format. Preserve legacy references in a separate field rather than overwriting them. Then test duplicate prevention before going live. HashMicro notes that legacy references should be preserved in a separate field when the new system key differs, because legacy and new sequences can collide after cutover.

Two related traps deserve specific mention. Credit notes and pro forma invoices must run in their own series; if they share the invoice sequence, they will look like duplicates of legitimate invoices. And when multiple systems generate numbers, designate one system of record for number generation and let the others sync rather than create.

Invoice Automation: How Software Removes Human Numbering Errors

Automation addresses numbering at the level where the errors actually originate. A system that generates the number at issuance enforces uniqueness by construction, blocks a duplicate before it posts, and holds the sequence intact when several people issue invoices concurrently. Alaan describes automated systems as ensuring numbers are assigned once and only once, sequences remain intact across users and departments, and the same number flows into accounting tools and reports.

Three error classes largely disappear with automation: manual duplicates, format drift between team members, and skipped or never-issued numbers caused by draft-stage assignment. What remains is a different set of exceptions — data migration leftovers, multiple entities sharing a sequence they should not share, and manual overrides of system-generated numbers. Those are governance problems, not software problems, and they need policy rather than a feature.

Buyer-side cost is worth understanding too, because it explains why large customers care how you number. HashMicro cites Ardent Partners’ 2025 global benchmark, which reported a 22% average invoice exception rate — a figure that shows how often invoices fail to process cleanly on the receiving end. Inconsistent or ambiguous references contribute to that failure rate, which is why enterprise AP teams often require a valid PO number and a clear invoice number on every document they receive.

What to Look For in Invoicing Software

Evaluate numbering capability with specific questions rather than a feature tour. Does the system support custom prefixes and zero-padded sequences without manual formatting? Can it share a sequence across entities, or isolate one per entity where that is required? Does it detect duplicates at entry rather than at month-end? Does it keep an audit history showing who issued, voided, or changed a number, and does it prevent edits to issued references? HashMicro recommends restricting manual edits, deletion, backdating, and sequence changes through role-based access, and testing the full workflow — including a duplicate attempt the system must reject and a cancelled document whose reference never returns — before committing to a vendor.

Invoice Numbers in E-Invoicing Standards

If you ever exchange invoices in structured electronic formats, the invoice number becomes a data field with defined transmission rules rather than a visible label. Wikipedia’s overview of invoicing notes that the United Nations EDIFACT “INVOIC” standard includes standard codes for transmitting header information common to the entire invoice as well as line-item detail, and can also carry credit and debit memos. XML-based standards include the UN/CEFACT cross industry invoice and OASIS Universal Business Language (UBL), which is used in public-sector implementations including Denmark, with further implementations in Italy, Spain, and the Netherlands, and the PEPPOL framework for European public procurement. ISDOC was developed in the Czech Republic as a universal electronic invoice format.

There is also a process model that bypasses invoices altogether for some transactions. Evaluated Receipt Settlement (ERS) pays from the packing slip rather than a separate invoice: the supplier ships against an advance shipping notice, and the purchaser confirms the corresponding purchase order or contract, verifies the goods, and pays. If your customers use ERS, your internal numbering still governs your own records even though no invoice number travels with the payment. Because public documentation on e-invoicing standards ages quickly, verify current requirements against the standards body or your customer’s specification rather than a secondary summary.

Conclusion

Invoice numbering is an internal control, not a formatting preference. A unique, continuous, explainable sequence makes payment matching faster and audit questions rarer — and in the US, the real constraint is not the format but whether your records can be traced and reconciled. Three actions to take today: write down your format and reset policy, including prefixes and zero-padding; pin the invoice number to the top of every template and commit to invoicing within 24 hours of completion or milestone; then run one continuity reconciliation and log every existing duplicate and gap in an exception file.

FAQ

Does the IRS require invoice numbers on invoices?

No. There is no federal requirement for invoice number format or continuity. However, IRS Publication 334 requires businesses to keep records supporting income and expenses, and invoice numbers are what let those records cross-reference each other. Some state sales tax rules impose additional invoice field requirements, so check the rules for states where you operate.

Can I reset my invoice numbers at the start of a new tax year?

Yes, but there is no single mandatory US rule — what matters is writing the policy down and applying it consistently. Alaan notes that a reset is acceptable when clearly documented and the sequence stays continuous within the year. A safer pattern for most businesses is embedding the year in the identifier, such as INV-2026-0001, rather than returning the running number to 0001 and risking collisions with open historical invoices.

What should I do if I skip or duplicate an invoice number?

For a duplicate, confirm the original, void the duplicate, and reissue under a new number while recording the original number and reason. For a skip, do not backfill or reuse the number — document it in an exception log with the date, reason, and reviewer. Both cases need a written trail so the sequence stays explainable during any review.

Is an invoice number the same as a receipt number?

No. An invoice number identifies a request for payment; a receipt number identifies confirmation that payment was received. Statrys describes them as different document types serving different purposes that both belong in your recordkeeping system. Many systems generate the receipt number separately, so store them in distinct fields.

Can two different suppliers use the same invoice number?

Yes. Uniqueness is only required within a single issuing entity — Alaan confirms invoice numbers only need to be unique per supplier, not across different businesses. That is why buyer systems typically identify an invoice using the combination of supplier plus invoice number, and why enterprise customers require your business identifier and invoice number to appear together.

Where should the invoice number appear on an invoice?

Place it in the header, near the invoice date and the customer’s details. Statrys notes that most invoicing software and standard templates position it there by default, which makes it easy for a client to locate when paying. Keep the field label and position identical across every template version you use.

UPC vs EAN-13 really comes down to one digit. UPC-A is the 12-digit retail barcode for the US and Canada; EAN-13 is the 13-digit code used almost everywhere else. Both encode GS1 GTINs from the same system — a UPC-A is an EAN-13 with a leading zero. For US retail, license a GTIN from GS1 US and print UPC-A. Sunrise 2027 does not ban it.

UPC vs EAN-13: The 3 Differences That Actually Matter

For a US seller, this is a short answer. If your product gets scanned at a US or Canadian checkout, you print a UPC-A. UPC-A carries 12 digits and serves the US and Canada. EAN-13 carries 13 digits and serves almost everywhere else, as BoxHero describes the split.

Neither format is technically better than the other. Both are GTINs drawn from the same global numbering system administered by GS1 — two regional lengths of one identifier family, not competing standards. That single fact removes most of the anxiety around this decision.

It also helps to separate the number from the picture of the number. The bars are only a carrier. The licensed number is the product’s identity, and the symbol is simply how a scanner reads it. Vxceed puts it plainly: the GTIN, UPC, and EAN are the same idea at different lengths, all licensed from one standards body, while the barcode isn’t a number at all — it’s a picture of one.

Why there are 12-digit and 13-digit versions of the same number

The US grocery industry built the 12-digit UPC first, and the rest of the world standardized on a 13-digit version shortly after. Retail Scan & Stock describes the UPC-A as introduced in North American supermarkets in 1974, with the European Article Number developed shortly after to include a country code prefix. Because the 13-digit form needed room for that prefix, US numbers effectively became the same numbers with a zero in front.

UPC vs EAN-13 at a glance (comparison table)

Barcode vs GTIN vs SKU: three different things

A GTIN is the global identity of a product configuration. A barcode is the machine-readable symbol that carries it. A SKU is a private, merchant-defined code that sits alongside the GTIN inside your own systems — it never replaces it. SKUs are internal and unregulated; GTINs are globally unique and licensed.

Which Barcode Should You Print? A Decision Tree for US Sellers

Here’s the one-line rule: if you’re selling physical consumer goods in the US, print UPC-A from a GS1 US-licensed GTIN. Most readers won’t need an exception to that.

The table below maps five real situations to a format.

A single GS1 GTIN covers both markets. The same number prints as UPC-A domestically and as an EAN-13 with a leading zero abroad, so nobody needs to buy two numbers for one product.

Internal-only labels never need a GS1 license, because they never leave your four walls. BoxHero states the rule directly: a GS1 barcode is required only when the product is sold through a retailer or marketplace that scans it at checkout or verifies it in a catalog.

Three questions settle almost every case: where the item will be scanned, who verifies the number, and whether the code must resolve in a global registry.

US retail shelf vs US marketplace: same barcode, different validation

The symbol is identical in both channels — a UPC-A at unit level. What differs is who checks it. A retail shelf buyer may accept your packaging spec after a vendor onboarding review, while a marketplace validates your GTIN programmatically against the GS1 database before your listing goes live.

Selling internationally from the US: do you need an EAN-13 too?

No. You need a 13-digit number the moment you print for a market that expects EAN-13, but you don’t need a second identifier. Add the leading zero to the same GTIN and render it as EAN-13. That’s a formatting step, not a licensing step.

If your product is a book: ISBN / Bookland EAN instead of a UPC

Books are the one common exception. According to ISBN Services, the 13-digit ISBN is converted into an EAN-13 barcode commonly printed on the back cover, often called the Bookland EAN barcode. The ISBN itself comes from the national agency — Bowker in the United States — so you don’t license a GS1 GTIN for the book edition. For the printing side, our guide to generating an ISBN barcode walks through the Bookland EAN requirements step by step. Non-book items bundled with a book, such as a tote, toy, or media accessory, still need their own GS1 GTIN.

UPC vs EAN-13 Digit by Digit: Prefix, Item Reference and Check Digit

Once you know what each position controls, you know which digits are yours and which ones you must not touch.

What each digit position means in a UPC-A and an EAN-13

Wikipedia’s UPC entry describes the UPC-A structure as SLLLLLLMRRRRRRE, where S, M, and E are guard patterns and the L and R sections carry the 12 digits. The first digit is a number system digit, and the last is an error-detecting check digit. In practice, the first section holds a GS1 company prefix assigned by the local GS1 organization, the middle holds the product reference, and the final digit validates the whole thing.

EAN-13 follows the same logic with one extra position at the front. Vxceed summarizes every GTIN as three parts: a GS1 company prefix, an item reference assigned by the manufacturer, and a mathematical check digit at the end that verifies scanning integrity.

One caution about the EAN-13 prefix: it’s an issuing-region indicator, not a country of manufacture. It identifies which GS1 member organization issued the number. A product manufactured in China and sold by a US brand still carries a US prefix, because the US brand’s GS1 member organization issued that GTIN.

How does the check digit work in a 12- vs 13-digit number?

The check digit is the final modulo-10 computed digit used for error detection. For a UPC-A, you sum the digits in odd positions, multiply by 3, add the digits in even positions, take the remainder modulo 10, and subtract from 10. Wikipedia walks through the example 03600029145x, where the odd-position sum is 14, multiplied by 3 gives 42, plus the even-position digits gives 58, and 58 mod 10 = 8, so the check digit is 10 − 8 = 2.

For an EAN-13, the developer walkthrough on DEV Community uses the same weighted logic with a different weight order: take the first 12 digits of 400638133393, multiply odd positions by 1 and even positions by 3, sum to 89, and reach the next multiple of ten — 90 — so the check digit is 1, giving the complete number 4006381333931.

The error-detection math is worth knowing, because it explains why the check digit isn’t a formality. Wikipedia reports that UPC-A detects 100% of single-digit errors and roughly 89% of transposition errors — a transposition escapes detection only when the difference between two adjacent digits is 5, which works out to about 11.111% of transpositions being undetectable.

GTIN-8, -12, -13 and -14: unit, inner pack, case and store-issued codes

The GTIN family covers more than the two retail lengths. Retail Scan & Stock lays out the hierarchy: GTIN-8 for very small retail packages such as gum or cosmetics, GTIN-12 encoded in UPC-A for US and Canadian units, GTIN-13 encoded in EAN-13 globally, and GTIN-14 encoded in ITF-14 or GS1-128 symbols on outer shipping cartons and master cases.

Two further categories sit outside that hierarchy. Variable-measure and restricted-circulation codes are store-assigned numbers for items weighed or priced at the point of sale — Wikipedia notes that number system 2 is reserved for local use for items sold by variable weight, where the store assigns an item number and the remaining digits carry weight or price. These aren’t GTINs at all, and they’re scoped to the store that issued them. Separately, JAN is Japan’s implementation of the EAN system — a regional name for the same 13-digit structure, not a different standard.

Is a UPC-A Just an EAN-13 With a Leading Zero?

Yes — mathematically. A 12-digit UPC-A is identical to the 13-digit EAN-13 formed by prefixing a zero. Retail Scan & Stock gives the worked example: UPC 012345678905 is represented in global 13-digit databases as 0012345678905. The same equivalence is corroborated by BoxHero and Vxceed, both of which describe the leading-zero relationship in the same terms.

The practical consequences are simple. You don’t buy a new number to sell the same item internationally, and you don’t need to convert anything on the package artwork beyond choosing which length to render.

Conversion is a formatting operation, not an identity change. A genuinely new product, size, flavor, or multi-pack still needs its own GTIN — reusing one number across variants is a separate mistake that has nothing to do with the UPC-versus-EAN-13 question.

Do US checkout scanners actually read EAN-13 barcodes?

Yes. Modern US point-of-sale systems are built to read 13-digit EAN-13, since a US UPC-A is the leading-zero form of the same number. Retail Scan & Stock notes that since the 2005 GS1 Sunrise initiative, virtually all modern retail scanners and smartphone camera decoders read both UPC-A and EAN-13 formats. A US product should still print UPC-A, because that’s what US packaging standards, retailers, and marketplace listings expect.

UPC-E and EAN-8: the compressed formats people confuse with UPC-A and EAN-13

These are separate small-package symbologies, not shortened versions you generate by trimming digits. BoxHero describes UPC-E and EAN-8 as compressed forms for items like a stick of gum or a small cosmetic tube. If you’re weighing the small-package forms, this EAN-13 vs EAN-8 comparison covers the shorter format in detail. Wikipedia adds that UPC-E suppresses the number system digit, trailing zeros in the manufacturer code, and leading zeros in the product code, and can only correspond to UPC-A number systems 0 or 1.

How to Get a UPC or EAN-13 in the US: GS1 Licensing and Costs

GS1 US is the authoritative issuer in the United States. You license numbers — you don’t buy a barcode image from a generator.

There are two routes. A single GS1 US GTIN covers one product. A GS1 Company Prefix covers a catalog, and the prefix is what lets you assign numbers yourself per item and per packaging level.

On reported pricing, BoxHero states that a single GS1 US GTIN costs a one-time $30 with no annual renewal fee, and that a GS1 Company Prefix carries an initial fee based on how many numbers you need plus an annual renewal fee, with published first-year figures starting at a few hundred dollars. Retail Scan & Stock reports the same $30 individual GTIN figure and notes that other GS1 member organizations apply regional fee structures. Treat these as published figures to verify at source — check gs1us.org before you budget.

Assign a distinct GTIN to every sellable variant and to each packaging level: each, inner pack, and case. Reusing one number across variants is the most common expensive mistake, because it corrupts stock records, orders, and sales history at the same time — and the damage tends to surface late.

Single GTIN vs a GS1 Company Prefix: how to choose

Choose a single GTIN if you’re listing a handful of products and don’t expect to change packaging levels soon. Choose a company prefix the moment you have a catalog, multiple sizes, or case-level labeling to manage, because the prefix is what lets you assign the next number yourself instead of starting a new purchase each time. BoxHero notes that once you license the number, the GS1 US Data Hub generates the barcode image as a PNG or EPS file at one fixed size.

Are third-party reseller barcodes safe to use?

Cheap reseller codes are real numbers, but they carry a hidden mismatch. According to BoxHero, these codes come from GS1 company prefixes bought before 2002 that remain legally transferable under a court settlement, and for some purposes they scan fine. The problem is ownership: a code registered to the reseller’s original company name can fail a marketplace check even though the bars scan correctly at a register.

Free barcode generators and validators render symbols and check digits accurately — Yotpo’s generator, for example, handles the specific digit rules and check digit calculation for UPC-A and EAN-13 — but none of them grant you a licensed number. Marketplaces check the registry, not the image.

US Barcode Launch Checklist: From GS1 License to Printed Symbol

This sequence runs from licensing to a scanned proof. Each step names the failure point it prevents.

1. License the GTIN from GS1 US. Failure point: buying a reseller code whose registry owner does not match your brand.
2. Assign a number per variant and per packaging level. Failure point: two flavors or two sizes sharing one code, which corrupts stock records and listings.
3. Create artwork with the correct symbology for the number. Failure point: applying an EAN-13 symbol to a 12-digit payload, or the reverse.
4. Meet size and quiet-zone rules. Failure point: a barcode placed outside the quiet zone, which produces a symbol that will not scan.
5. Scan-test a printed proof with a real scanner. Failure point: discovering a rendering problem after the full print run.
6. Store the number as text. Failure point: database or spreadsheet handling that silently alters the identifier.
7. Verify the number against marketplace metadata. Failure point: a catalog mismatch that reads as an invalid GTIN during listing review.
8. Keep the human-readable digits complete. Failure point: truncated digits printed under the bars, which breaks manual key entry when a scanner fails.

The print specifications your printer needs

Treat these as the spec you hand your printer, not trivia. Wikipedia gives the nominal x-dimension for UPC-A as 0.33 mm (0.013 in) and the nominal symbol height as 25.9 mm (1.02 in), with guard pattern bars extended downward by five times the x-dimension. A complete UPC-A is 95 modules wide: 84 modules for the 12 digits plus 11 modules for the start, middle, and end guard patterns. A quiet zone at least 9 times the x-dimension wide must be present on each side. UPC-A can be reduced or magnified anywhere from 80% to 200%.

For developers and ops: storing, normalising and validating barcode data

Spreadsheet and database handling is where clean identifiers go wrong. Retail Scan & Stock identifies three specific failure modes: leading zeros dropped because a spreadsheet reads 012345678905 as the number 12345678905; long digit strings displayed in scientific notation; and a 15-digit numeric precision limit that converts digits past the 15th position to zeroes. Microsoft Support documentation confirms the 15-significant-digit limit, and the recommended fix is to format the column as Text before entering or importing identifiers.

The DEV Community validator walkthrough makes the same point from the engineering side: keep barcode values as strings, never pass them through Number(), and validate the check digit before rendering anything. That author also draws a boundary worth keeping: a passing check digit means the number satisfies the mathematical rule — it does not mean the number was licensed correctly, that the product exists, or that a marketplace will accept it.

Why Amazon, Walmart and Target Reject Some Seller Barcodes

Marketplaces verify the GTIN against the GS1 registry and expect the brand and company on record to match the listing. A real but mismatched number fails that check and is treated as an invalid GTIN.

The rejection mechanism is catalog mismatch — not a broken barcode, and not a UPC versus EAN-13 format problem. This distinction matters, because sellers often respond to a rejection by reprinting the symbol, which fixes nothing.

How marketplace GTIN validation actually works

BoxHero describes the process: Amazon checks the barcode you enter against the GS1 database and expects the brand and company on record to match your listing, and Amazon’s barcode policy states that it verifies UPCs through the GS1 database and treats codes that do not match GS1’s information as invalid. A reseller code registered to the reseller’s original company name can fail that check, so even when the code scans, a listing may be rejected for an invalid GTIN. The practical safeguard is to license codes directly from GS1 US for anything going to Amazon, Walmart, or Target, and to keep the GS1 certificate on hand — these marketplaces can ask you to prove the code is registered to your company.

ASIN is not a GTIN (and a case code is not a unit code)

Two further mismatches cause avoidable rejections. An ASIN is Amazon’s own catalog identifier and does not replace a GTIN anywhere else, as Vxceed notes in its list of external identifiers a SKU maps to online. And a GTIN-14 case code will not scan as a retail unit — Retail Scan & Stock warns against scanning a master carton symbol as an individual piece count on the sales floor.

Sunrise 2027 and 2D Barcodes: What Changes for Your UPC-A

Sunrise 2027 is a GS1 target for retail point-of-sale systems to read 2D codes — QR, GS1 DataMatrix, GS1 Digital Link — alongside the 1D barcodes they read today. It is a target, not a government mandate.

Sunrise 2027 in one paragraph: target, not mandate

In BoxHero’s rendering, GS1 states that “by the end of 2027, retail point-of-sale systems should be able to read and process 2D barcodes in addition to the 1D barcodes they read today.” Three things keep this in proportion: the UPC is not being banned, there is no fine for skipping it, and the pressure comes from large retailers rather than regulators. A 1D barcode holds one piece of information — the GTIN — while a 2D code holds several thousand characters, including batch number, expiration date, serial number, and a web link tied to the product. Adoption is already underway: GS1 reports the transition is being tested in 48 countries representing 88% of the world’s GDP, per a 2024 GS1 statement cited by BoxHero.

The practical action now is small. Keep printing the UPC-A, leave label real estate for a future 2D carrier, and make sure your GTIN data is clean enough to power one. GS1 suggests printing both the 1D and 2D barcode on the same package during the switch.

From the first 1974 scan to 2D in 2027

The 1D retail barcode has been in continuous use since the first UPC scan. Wikipedia records that the first UPC-marked item scanned at retail checkout was a 10-pack of Wrigley’s Juicy Fruit chewing gum, purchased at the Marsh supermarket in Troy, Ohio, at 8:01 a.m. on 26 June 1974, ringing up 67 cents on an NCR cash register.

That longevity was deliberate. Murray Eden, a consultant on the team that created the UPC barcode and chairman of a committee of scientists at MIT, helped, in his 1970s-era phrasing, “select a symbol that would endure the inevitable rush of technology that lay ahead.” He also chose the font and introduced the human-readable digits below the bars as a fail-safe in case a reader malfunctioned. GS1 now frames Sunrise 2027 as coexistence rather than replacement — which is exactly consistent with a symbol chosen for endurance more than fifty years ago. The history of QR codes tells the same story from the other direction: a 2D carrier invented for Toyota factory floors that now shares labels with the 1D symbol it was never meant to replace.

Conclusion

UPC vs EAN-13 is not a choice between competing standards — it is one GS1 number printed in two regional lengths, and US sellers print the 12-digit UPC-A. License a GTIN from GS1 US (verify current pricing at gs1us.org before budgeting), assign a separate number to every variant and packaging level, generate the symbol to spec, scan-test a physical proof, and store the number as text. Reserve label space for a 2D carrier, but do not reprint anything for Sunrise 2027 — it is a target, not a mandate.

FAQ

Can I convert a 12-digit UPC to an EAN-13, or do I need to buy a new number?

No purchase is required. Add a leading zero to the 12 digits and the result is the valid EAN-13 for the same item — for example, 012345678905 becomes 0012345678905. The conversion changes formatting only, never identity. You still need a new GTIN for a genuinely new product, size, flavor, or multi-pack.

Do US checkout scanners actually read EAN-13 barcodes?

Yes. Modern US point-of-sale systems are built to read 13-digit EAN-13, since a US UPC-A is the leading-zero form of the same number — Retail Scan & Stock notes that virtually all modern retail scanners read both formats. A US product should still print UPC-A, because that is what US retailers and marketplace listings expect.

Can I just make up my own barcode number for my product?

No. The number must come from a GS1-issued prefix so it resolves uniquely in the global registry. A self-invented number may render and even scan locally, but marketplaces and retailers that validate against GS1 will reject it. Internal-only labels for your own warehouse can use your own codes, because they never need to resolve globally.

Is a UPC the same thing as a GTIN?

A GTIN is the umbrella identifier family, and UPC-A (GTIN-12) and EAN-13 (GTIN-13) are two of its lengths. GTIN-8 covers small packages and GTIN-14 covers cases and pallets, so “GTIN” is the safe general term. Most US retail listings that ask for a “UPC” will accept any valid GTIN.

Why does my barcode turn into scientific notation in Excel?

Spreadsheets treat long digit strings as numbers, strip the leading zero, and switch to scientific notation past 15 digits. Retail Scan & Stock notes that Excel numeric precision is limited to 15 significant digits, so digits past the 15th position can become zeroes. Store barcode values as text and validate the check digit before exporting to artwork — and always keep the leading zero on a 13- or 14-digit GTIN.

Will my UPC stop working in 2027 because of Sunrise 2027?

No. Sunrise 2027 is a GS1 target for retail POS to read 2D barcodes alongside 1D, not a ban or a deadline for brands. There is no fine for non-compliance and UPC-A and EAN-13 remain scannable. The practical move is to keep printing your UPC and reserve label space for a future 2D carrier.

Do books need a UPC, or is the ISBN barcode enough?

Books carry a 13-digit ISBN encoded as an EAN-13 Bookland barcode, not a UPC-A, according to ISBN Services. ISBNs come from Bowker in the US, so you do not license a GS1 GTIN for the book itself. Non-book items bundled with a book — a tote, a toy, a media accessory — still need their own GS1 GTIN.

Do I need a separate UPC for each size, color, or multi-pack?

Yes. Every sellable variation that a retailer scans or stocks separately needs its own distinct GTIN. Different packaging levels also differ: each unit, inner pack, and case carry their own GTIN, with GTIN-14 and ITF-14 on cases. Reusing one number across variants is a leading cause of listing rejections and inventory errors.