UPC Codes Explained

A UPC is a product-level identifier used to distinguish one music release from another. In music distribution, it generally identifies the release as a whole—such as an album, EP, single, or other packaged product—while an ISRC identifies an individual sound recording. A multi-track album can therefore have one release identifier and separate recording identifiers for each track.

Whether you need to obtain a UPC yourself depends on the distributor you choose. There is no single universal rule established by the evidence that every artist must independently purchase or supply a UPC before delivering music to Spotify, Apple Music, YouTube Music, or every other digital service provider. Some distributors require a UPC but assign one for you; others may accept an existing UPC/EAN or generate one during their workflow. Check the selected distributor’s current submission rules before you begin.

What does UPC mean?

UPC means Universal Product Code. In GS1 terminology, GTIN-12 is the 12-digit identification key commonly represented by a UPC. GS1 describes that key as being made up of a U.P.C. Company Prefix, an item reference, and a check digit. The check digit helps validate the number when it is used in the identification system. For the current technical definition and structure, see the GS1 General Specifications Standard, Release 24.0.

People often use “UPC” to refer both to the number and to the barcode image printed on a product. They are related, but they are not exactly the same thing. GTIN-12 is the numeric identification key. UPC-A is the corresponding retail barcode symbology: the scannable visual format that encodes the GTIN-12 and includes its check digit. In other words, the number identifies the product, while the barcode is a machine-readable representation of that number. GS1’s specifications distinguish the identification key from the barcode construction; keeping that distinction clear helps avoid confusion when a distributor asks for a code, a barcode, or release metadata.

For digital music, the practical question is usually not whether you need to print a retail barcode on a physical package. It is whether the release has a release-level product identifier that can be included in the metadata delivered to distribution partners. Depending on the system and territory, related identifiers may be described as UPC, EAN, or JAN. DDEX, the standards organization for digital entertainment metadata, lists UPC/EAN/JAN and GRid among common identifier types for a release’s ReleaseId field in its Release Notification Implementation Starter Guide.

What does a UPC identify in a music release?

A UPC/EAN identifies the release or product, not one particular track. That distinction is central to organizing music metadata. The International ISRC Registration Authority and IFPI explain in their International Standard Recording Code FAQ that ISRC identifies sound recordings rather than products or releases, while music products generally use UPC/EAN barcodes. The FAQ also notes that each different product requires its own UPC/EAN code.

Consider a six-track EP. The EP as a packaged release can have one UPC/EAN. Each of the six recordings can have its own ISRC. If one of those tracks is later included on a different album, the new album is a different product and can have a different release-level identifier, even though the underlying recording may retain its ISRC when the recording itself has not changed and the distributor’s workflow permits that treatment.

The simplest way to remember the relationship is:

• UPC/EAN: identifies the release or product.
• ISRC: identifies an individual sound recording or music video.
• DDEX ReleaseId: a release-level metadata field that can contain an identifier such as UPC/EAN/JAN or GRid.

The Why Use ISRC resource from the International ISRC Registration Authority and IFPI describes ISRC as a unique identifier for individual recordings used by distributors, licensing organizations, broadcasters, and webcasters for identification and reporting. That is why a release is not normally represented by one code alone. The release needs a product-level identity, and its recordings need track-level identities.

A UPC is therefore not a replacement for ISRC. Supplying a UPC does not mean that every track on the release has been assigned the same identifier. Conversely, having ISRCs for the tracks does not eliminate the need to follow a distributor’s release-level metadata requirements. The identifiers describe different layers of the same package.

How identifiers move through digital distribution

When a distributor sends release metadata to music services and retail partners, the release identifier is part of the information used to describe the product. DDEX’s Release Notification Implementation Starter Guide explains that ReleaseId contains unique identifiers for a release and commonly uses UPC, EAN, JAN, or GRid as identifier types.

This makes the release identifier operationally important. DDEX warns that changing the ReleaseId can cause a retail partner’s systems to treat an update as a new album. That does not guarantee that every digital service will behave identically, but it explains why release-level identifiers should be handled carefully. A change that looks minor in a distributor dashboard can have consequences for how a partner matches the submission to an existing product.

The same principle applies when you submit a corrected or updated release. Before changing a UPC/EAN, confirm what the distributor considers a new product, a replacement delivery, or an update to an existing release. Do not invent a number, reuse a code from another product, or casually replace an established release identifier. Use the distributor’s documented process and retain a record of the identifier associated with each release.

TuneCore gives a provider-specific example in its What changes cannot be made after distribution? help article. TuneCore states that a UPC cannot be changed after a release has been sent to stores. According to that page, changing release-level product information requires a takedown and resubmission as a new product, while unchanged tracks may retain their ISRCs. This is TuneCore’s stated workflow, not a universal rule for every distributor, so treat it as a warning to check the policy for the service you use.

Do you need a UPC to release music?

The answer is distributor-specific.

CD Baby currently states in Understanding UPC barcodes that releases distributed through its services require a UPC. Its documented workflow allows CD Baby to automatically assign a UPC after approval if the artist does not already have a valid one. CD Baby also says it accepts valid existing UPCs and prohibits reusing or inventing them. The company describes the code as supporting release reporting and platform indexing.

TuneCore documents a different operational path in TuneCore UPCs and ISRCs. TuneCore states that an artist may enter an existing UPC/EAN before distribution under the stated plan conditions. If no existing code is supplied, TuneCore generates a UPC after the release passes its content-review approval process. The cited page is localized for TuneCore’s India help center, and account, plan, service, or regional terms may matter, so verify the current instructions that apply to your account.

These examples show why “Do streaming platforms require UPCs?” is too broad a question. The evidence establishes distributor requirements and assignment practices, not one universal rule imposed independently by every DSP. A distributor may require a release identifier as part of its delivery process while taking responsibility for assigning one. Another may allow you to provide an existing code. The chosen provider’s current instructions control.

You should also avoid assuming that a UPC must always be purchased separately, that it is always free, or that possessing one creates a legal or financial entitlement. The supplied evidence supports describing UPC-related value as release identification, metadata delivery, indexing, and reporting support. It does not establish that a UPC creates copyright ownership, guarantees royalty payment, creates royalty entitlement, or independently creates sync-licensing rights. Identifiers help systems match and report information; they do not by themselves establish the underlying rights in the music.

A practical release workflow

Use this sequence when preparing a release:

1. Choose the distributor and read its current UPC/EAN and ISRC instructions. Look for rules about existing codes, automatic assignment, plan restrictions, territories, and post-delivery changes.

2. Decide whether you already have a valid release identifier. If you do, confirm that it belongs to this exact product and that the distributor accepts it. Do not reuse a code from another release or make one up.

3. If you do not have one, check whether the distributor assigns a UPC after approval or generates one during submission. CD Baby and TuneCore document automatic-assignment workflows, but their processes differ.

4. Keep the release-level identifier separate from the track-level ISRCs. An album, EP, or single can have its own UPC/EAN, while every individual recording may have its own ISRC.

5. Review the final metadata before delivery. Confirm the release title, track list, versions, artist information, and identifiers match the product you intend to distribute.

6. Save the approved identifier and submission record. This is especially important if you later need to correct metadata, replace audio, or communicate with distributor support.

7. Before requesting a change after delivery, ask whether the change will update the existing product or require a takedown and resubmission. DDEX guidance and TuneCore’s policy both illustrate why release identifiers should not be changed casually.

Worked example: one EP, several identifiers

Suppose an artist is releasing a four-track EP. The distributor’s workflow assigns or accepts one UPC/EAN for the EP. The four individual recordings each have an ISRC. The distributor then places the release-level identifier in the relevant release metadata and supplies the track-level identifiers with the recordings.

Later, the artist wants to include two of those same recordings on a new compilation. The compilation is a different product, so it may have its own release-level UPC/EAN. The recordings remain conceptually separate from the compilation: each recording has an ISRC, while the compilation has its own release identity. If the distributor requires a new product submission, follow its instructions rather than changing the original EP’s identifier.

This example also explains why a UPC is not simply “the album’s ISRC.” The EP and its tracks exist at different metadata levels. Confusing the two can lead to incorrect submissions, duplicate product identities, or avoidable support issues.

Common mistakes to avoid

Do not describe the barcode picture and the numeric identifier as interchangeable technical terms. The GTIN-12 is the 12-digit key; UPC-A is the barcode symbology that encodes it. For background, consult the GS1 General Specifications Standard, Release 24.0.

Do not assign one UPC to every track on an album. The UPC/EAN is release-level. Tracks use ISRCs, as explained by the International Standard Recording Code FAQ.

Do not assume every distributor follows CD Baby’s or TuneCore’s process. Their help-center pages are useful examples of current provider policies, but they are not universal DSP rules. Recheck the selected distributor’s instructions because requirements can vary by account, plan, service, territory, and date.

Do not change a release identifier simply because you are making a metadata correction. DDEX guidance says that changing ReleaseId may cause a partner to treat an update as a new album, and TuneCore states that its UPC cannot be changed after delivery. Ask the distributor what will happen before taking action.

Finally, do not treat a UPC as proof of ownership or a guarantee of royalties. It is an identifier that supports the organization and exchange of release information. Copyright, contracts, licensing, and payment questions require separate documentation and professional advice where appropriate.

Bottom line

A UPC/EAN identifies a music release or product. An ISRC identifies an individual sound recording or music video. A multi-track release can use both: one release-level identifier and separate track-level identifiers. In digital distribution, the distributor’s workflow determines whether you supply an existing UPC/EAN, receive one automatically, or follow another process. Because policies change and differ among providers, check the chosen distributor’s current rules before submission—and protect the release identifier once the product has been delivered.

Open Music Business provides educational information, not individualized legal, financial, tax, contract, or royalty advice.