If you have ever distributed a single, EP or album, you have probably encountered two identifiers that look more complicated than they really are: ISRC and UPC.
They often appear in the same release form, which is why independent artists regularly assume they do the same thing.
They do not.
An ISRC identifies an individual recording.
A UPC identifies the release or product that contains that recording.
That distinction sounds small, but it becomes extremely important when you release an album, reuse a previously released single, create a remix, move your catalog to another distributor or begin managing music for several artists.
Once you understand what each identifier belongs to, most of the confusion disappears.
The Simple Difference Between UPC and ISRC
The easiest way to remember the difference is:
ISRC = recording
UPC = release/product
Imagine you release a three-track EP called After Midnight.
The EP itself has one UPC.
Inside that EP are three individual sound recordings.
Each recording has its own ISRC.
The structure therefore looks something like this:
After Midnight EP
UPC: one release identifier
Track 1: After Midnight
ISRC: one recording identifier
Track 2: Empty Streets
ISRC: another recording identifier
Track 3: November
ISRC: another recording identifier
The UPC describes the package.
The ISRCs describe the recordings inside that package.
The International ISRC Registration Authority makes the same distinction: ISRC is assigned to recordings, not to the music product containing them. Music products are generally identified separately using UPC/EAN identifiers. ifpi-isrc
Once you think about the two identifiers this way, catalog management becomes much easier.
What Is an ISRC?
ISRC stands for International Standard Recording Code.
It is the internationally recognized identifier for an individual sound recording or music video recording.
An ISRC remains associated with a particular recording even when that recording moves between distributors, appears on different releases or changes ownership.
For example, imagine you release a single called Runaway.
The original studio master receives an ISRC.
Six months later, you include exactly the same recording on an album.
You do not create a new recording just because it now appears inside an album.
The original ISRC can continue identifying that same master.
That is one of the fundamental purposes of ISRC: allowing the recording to remain identifiable independently of the product in which it appears. ifpi-isrc
We covered this system in much more detail in our What Is an ISRC Code? guide, including remixes, remasters, catalog transfers and ownership changes.
Read the complete DistroVibe ISRC guide
What Is a UPC?
UPC stands for Universal Product Code.
In everyday digital music distribution, artists frequently see "UPC" used as the identifier for a single, EP or album as a complete release.
Technically, the wider product-identification system is based around GTINs, or Global Trade Item Numbers. UPC-A and EAN-13 are widely used barcode formats within that system. GS1 describes GTINs as global identifiers for trade items, while UPC-A and EAN-13 are among the most widely used barcode formats for identifying those items. GS1 GO Customer Service Portal
For an independent artist using a digital distributor, however, you normally do not need to become a barcode expert.
The practical distinction is more useful:
The UPC identifies the release as a product.
So if you distribute:
one single;
one EP;
and one album;
those are three different releases and can each have their own release-level identifier.
Each recording inside those releases then has its own ISRC.
Does a Single Need Both a UPC and an ISRC?
Yes.
This is where the difference becomes easiest to see.
Imagine you release one song called Stay Tonight as a standalone single.
There is only one track.
You still have two different things being identified.
The single release itself needs its release/product identifier.
The sound recording inside the single needs its recording identifier.
So even a one-track single can have:
UPC → identifies the single release
ISRC → identifies the actual recording
Because there is only one track, artists sometimes assume the codes are interchangeable.
They are not.
They simply happen to be attached to a release containing only one recording.
What Happens With an Album?
Albums make the difference much clearer.
Suppose your album contains twelve tracks.
The album itself has one UPC.
Each individual recording has its own ISRC.
That means the project could contain:
1 UPC
and
12 ISRCs
If one of those twelve recordings was previously released as a single and the exact same master is being used on the album, that recording generally keeps its existing ISRC.
The album, however, is a different release product from the original single and therefore has its own release identifier.
This is one of the most important concepts to understand when building a catalog.
The recording and the release are related, but they are not the same asset.
What Happens When a Single Later Appears on an Album?
This happens constantly.
An artist releases a lead single in January.
A second single arrives in February.
The full album is released in April and contains both singles.
If the exact same sound recordings are being used, the singles should normally retain their existing ISRCs when they appear on the album.
The album receives its own release-level identifier because it is a different product.
For example:
January:
Single: Falling
UPC A
ISRC 1
February:
Single: Home
UPC B
ISRC 2
April:
Album: Everything We Left Behind
UPC C
Track 1: Falling → ISRC 1
Track 2: Home → ISRC 2
Track 3: Another recording → ISRC 3
Track 4: Another recording → ISRC 4
The album does not require you to pretend that Falling and Home suddenly became new recordings.
They remain the same masters.
This is why keeping your ISRC records organized becomes increasingly valuable as your catalog grows.
Do You Need a New ISRC for a Remix?
Usually, yes.
A remix is a different recording version.
The International ISRC Registration Authority specifically identifies remixes and edits as examples of modifications that can require a new ISRC. ifpi-isrc
Imagine your original release is:
Midnight
Original recording → ISRC A
You later release:
Midnight (Club Remix)
Remix → ISRC B
The remix should not simply reuse ISRC A because it is no longer the same recording.
If the remix is released as a new standalone single, the new release would also normally have its own release-level UPC.
That means the remix could receive both:
a new ISRC because the recording changed;
and a new UPC because a new release product was created.
What About an Acoustic Version?
A newly recorded acoustic performance is also a separate sound recording.
Even though the songwriting may be identical, you recorded a new performance.
For example:
Broken Again
Original studio version → ISRC A
Broken Again (Acoustic)
New acoustic recording → ISRC B
The underlying composition may be the same.
The masters are not.
This is another reason why thinking of an ISRC as a "song code" can create confusion.
It is much more accurate to think of it as a recording identifier.
What About a Live Version?
The same principle applies.
If you record a live performance at a concert, that recording is not the same master as the studio version.
Studio version → one ISRC
Live version → another ISRC
If you then release a full live album containing ten separately exploited live recordings, the album itself can have one release-level UPC while the individual live recordings receive their appropriate ISRCs.
Again:
UPC follows the product.
ISRC follows the recording.
Does a Remaster Need a New ISRC?
Not automatically.
Remastering is more nuanced than recording a completely new acoustic version or remix.
The International ISRC Registration Authority says that keeping the original ISRC is generally appropriate where a remaster remains fundamentally the same recording. A new ISRC may become appropriate when significant new creative input changes the resulting recording. ifpi-isrc
Simply making a master louder, cleaner or more suitable for modern playback does not necessarily create an entirely new recording.
This is why labels managing older catalogs should avoid automatically generating new ISRCs every time they process an archival master.
Does Changing the Audio Format Require a New ISRC?
No.
Changing a WAV file into another audio format does not create a new recording.
ISRC identifies the recording regardless of normal differences in format or bitrate. ifpi-isrc
For example:
24-bit WAV → ISRC A
16-bit WAV of the same master → still ISRC A
Lossless delivery copy of that same master → still ISRC A
The file format changed.
The recording did not.
What Happens When You Change Music Distributors?
This is probably the most practically important part of the entire subject.
Changing distributor does not automatically mean changing your recording identifiers.
If you are transferring exactly the same recording, the existing ISRC should normally remain with that master.
Suppose you originally released through Distributor A.
Two years later, you decide to move your catalog to Distributor B.
The recording has not changed.
Your distribution partner changed.
Those are completely different things.
You should therefore preserve the existing ISRC for the recording rather than assigning a new identifier just because you moved the catalog. IFPI explicitly states that an existing ISRC should be retained when the same recording continues to be used across different releases, formats, countries or licensing arrangements. ifpi-isrc
Should You Keep the Same UPC When Changing Distributors?
Where your new distributor supports importing the existing release identifier and you are transferring the same release, preserving the existing UPC is generally the cleaner approach.
However, UPC behaves differently from ISRC because it identifies the release/product rather than the underlying recording.
The critical information you should never casually replace during a catalog transfer is the ISRC attached to the unchanged master.
For UPCs, what is appropriate depends on whether you are actually transferring the existing release or creating a new product configuration.
The official ISRC guidance notes that each different music product requires its own UPC/EAN identifier. ifpi-isrc
This is why catalog transfers should be handled deliberately rather than by randomly re-uploading old audio as if every track were a new release.
Can the Same ISRC Appear Under Different UPCs?
Yes.
This is completely normal.
In fact, the single-to-album example demonstrates exactly why.
Suppose an artist releases:
Single: Cold Streets
UPC: 111
ISRC: AAA
Three months later, the exact same master appears on:
Album: No Way Home
UPC: 222
Cold Streets → still ISRC AAA
There is no contradiction.
The release changed.
The recording did not.
The single and album are separate products, so they can have separate UPCs.
The master inside them remains the same recording, so it retains the same ISRC.
This ability to separate the recording from the product containing it is one of the reasons the two identification systems exist.
Can Multiple ISRCs Appear Under One UPC?
Absolutely.
That is what happens with virtually every multi-track EP or album.
Imagine an eight-track album.
UPC:
Album identifier
ISRCs:
Track 1 identifier
Track 2 identifier
Track 3 identifier
Track 4 identifier
Track 5 identifier
Track 6 identifier
Track 7 identifier
Track 8 identifier
One product.
Eight recordings.
This is also why labels should never use a UPC as a substitute for maintaining track-level catalog records.
Knowing the album's UPC does not tell you the individual recording identifier for every master inside it.
Does a Music Video Use the Song’s UPC or ISRC?
Music video identification has another important distinction.
The International ISRC Registration Authority states that a sound recording and a music video recording are separate recordings for ISRC purposes, even when the same audio is used. They should therefore have different ISRCs. ifpi-isrc
So you might have:
Official audio master → ISRC A
Official music video → ISRC B
They belong to the same artist and song campaign, but they are separate recorded assets.
This becomes especially relevant for artists and labels working with professional music video distribution and VEVO.
Can You Reuse an Old ISRC?
No.
Once an ISRC has been assigned to a recording, it should not later be recycled for another recording.
Even if you ultimately decide not to release the original recording, that identifier should not be reassigned to a different master.
IFPI explicitly states that assigned ISRCs must not be reused. ifpi-isrc
This is another area where labels need proper record keeping.
Trying to make your ISRC numbering sequence look neat is not more important than maintaining unique identifiers correctly.
Can You Reuse a UPC?
You should not take an identifier assigned to one release product and arbitrarily attach it to an unrelated release.
Product identifiers are intended to distinguish trade items.
GS1's system is based on unique product identification, with distinct products receiving distinct identifiers. GS1 GO Customer Service Portal
For artists, the practical rule is straightforward:
Do not recycle old release codes just because you want to avoid receiving another one.
Keep the identifier attached to the release for which it was assigned.
Does a UPC Prove Who Owns an Album?
No.
Neither UPC nor ISRC should be treated as copyright certificates.
A UPC identifies a product.
An ISRC identifies a recording.
Neither identifier, by itself, proves that the person presenting it currently owns the relevant copyright.
Rights ownership needs to be established through contracts, licenses and other rights information.
This becomes particularly important when catalogs are sold.
A sound recording can change owner while retaining the same ISRC because the recording itself has not changed. ifpi-isrc
Similarly, being able to provide a UPC for an album does not automatically establish that you hold the rights to commercially distribute everything inside it.
Identifiers and ownership serve different purposes.
Do Spotify and Apple Music Use UPC and ISRC?
Digital music platforms receive structured metadata from labels and distributors, and identifiers such as ISRC and release-level product codes play an important part in identifying catalog assets throughout the supply chain.
For artists, this means the numbers sitting inside your distributor dashboard are not meaningless technical information.
They form part of the metadata associated with your catalog.
That is why you should retain them.
A distributor may make catalog management easier, but the artist or label should still maintain its own release records.
Why Artists Should Keep Their Own UPC and ISRC Records
One of the most common catalog-management mistakes is depending entirely on a distributor's dashboard.
When the release is new, that feels harmless.
Everything is visible in the account.
Then several years pass.
You change distributor.
An old account is closed.
A release needs to be transferred.
You want to reuse an existing single on a compilation.
Suddenly you need catalog information that you assumed would always be one login away.
Maintain your own records.
For every release, it is worth preserving:
release title;
primary artist;
original release date;
UPC or other release identifier;
track titles;
ISRC for every recording;
original audio masters;
artwork;
songwriter and contributor information;
relevant rights documentation.
This becomes even more important for record labels.
Once you manage several artists and hundreds of recordings, your metadata effectively becomes part of your company's infrastructure.
Our Music Distribution for Record Labels guide goes deeper into catalog management, transfers, royalties, metadata and label-level distribution workflows.
Read Music Distribution for Record Labels
UPC vs ISRC for Record Labels
Labels need to understand both systems because they manage assets at two different levels.
ISRC lets the label keep track of recordings.
UPC lets the label keep track of release products.
Suppose a label controls 500 masters distributed across 80 releases.
Those numbers immediately demonstrate why a single identifier type would not be enough.
One recording may appear on several products.
One product may contain many recordings.
An organized label should therefore maintain a catalog database that understands the relationship between:
artist → release → UPC → tracks → ISRCs → master ownership.
This becomes particularly useful when dealing with catalog acquisitions or transfers.
If another label sends you only a spreadsheet of album names and UPCs but no track-level ISRC information, the catalog data is incomplete.
Likewise, receiving a list of ISRCs without understanding which products and releases they belong to makes release-level management harder.
Professional catalog management needs both layers.
A Practical Example: Single, Remix, Album and Deluxe Edition
Consider an artist called Nova Vale.
First release:
Falling Apart — Single
UPC 1
Falling Apart → ISRC A
Two months later:
Falling Apart (Nightdrive Remix) — Single
UPC 2
Falling Apart (Nightdrive Remix) → ISRC B
The remix has both a new UPC and a new ISRC because there is a new release product and a different recording.
Then the artist releases:
Slow Motion — Album
UPC 3
Falling Apart → ISRC A
Track 2 → ISRC C
Track 3 → ISRC D
Track 4 → ISRC E
Track 5 → ISRC F
Track 6 → ISRC G
Track 7 → ISRC H
Track 8 → ISRC I
The original Falling Apart master keeps ISRC A even though it has moved from the standalone single into the album.
Later, the artist releases:
Slow Motion (Deluxe)
If this is being treated as a different release product, it can have another release identifier.
The unchanged masters can retain their existing ISRCs.
Brand-new bonus recordings receive their own ISRCs.
This one example explains most real-world UPC and ISRC situations.
Which Code Does DistroVibe Need?
When creating a release through a digital distributor such as DistroVibe, both recording-level and release-level identification become part of the distribution workflow.
If you are releasing new recordings, the required identifiers can be handled as part of preparing the release.
If you are transferring an existing catalog, preserving your existing recording information becomes much more important.
The goal is not to generate new numbers simply because you changed platforms.
The goal is to accurately represent the catalog that already exists.
For an unchanged master, keep the existing ISRC.
For a genuinely new recording, use a new ISRC.
For a new release product, the release requires its appropriate product identifier.
Once you follow those three rules, the system becomes much easier to understand.
UPC vs ISRC: The Rule Worth Remembering
You do not need to memorize barcode standards to distribute music professionally.
You only need to understand what each identifier belongs to.
ISRC follows the recording.
UPC follows the release.
Your album can change while the recording remains the same.
Your distributor can change while the recording remains the same.
A previously released single can appear on a new album while the recording remains the same.
In those situations, the existing ISRC continues identifying that master.
But if you create a genuinely different recording — a remix, new acoustic performance or new live recording — you are dealing with a new master that needs to be identified separately.
Treat UPCs and ISRCs as part of your catalog records rather than meaningless numbers generated during distribution.
It may not seem important when you have one single.
It becomes extremely important when that one single turns into fifty releases, several distributors, multiple artists and years of catalog history.
Good metadata is easiest to maintain before you desperately need it.
