Two codes can sit around the same release and still be doing completely different jobs.
That is the easiest way to understand ISRC vs. UPC.
An ISRC identifies a specific sound recording or music video recording. A UPC/EAN identifies a product or release package — the thing that may contain one recording or several.
IFPI, which runs the International ISRC system, states the distinction directly: an ISRC identifies the recording, not the album, single package, CD or digital product that carries it. Music products generally use UPC/EAN identifiers instead.
If you distribute music independently, knowing that difference saves you from treating every code in your dashboard like interchangeable metadata.
ISRC follows the recording
Think about one master recording of a song.
That recording can appear as a standalone single. Later it can appear on an EP. Later still it can be included on an album or compilation.
The product around the song can change while the underlying recording stays the same.
That is what the ISRC is designed to identify.
IFPI says ISRC is assigned to recordings and remains associated with that recording regardless of supply chain, price or format. If the exact same master is reused on another release, the existing ISRC generally continues to identify that recording.
A genuinely different recording can require a different ISRC. Examples can include a newly recorded performance or another version that is materially a separate recording. The exact assignment rules matter, so do not create new codes just because a distributor screen makes it easy.
UPC/EAN follows the release product
Now move one level up.
The single package you send to stores is a product. The album package is another product. A physical edition can be another product again.
IFPI explains that music products are generally identified by UPC/EAN barcodes. Those identifiers help distinguish the product being supplied and sold rather than the individual recording inside it.
That means an album with 12 songs can have one product identifier for the album while each of the 12 recordings has its own ISRC.
If one of those recordings was previously released as a single, that single release may have its own UPC while the recording retains the same ISRC when the same master appears on the album.
That is the relationship artists usually need to visualize:
Recording → ISRC
Release/product → UPC or EAN
Your distributor may generate both
Independent artists often first encounter these codes inside a distributor.
Many distributors can assign ISRCs and product codes during the upload process. That convenience does not change what the codes mean.
Before submitting, check whether you already have an ISRC for a recording that has been released before. If you are reusing the same master, blindly generating a new identifier can fragment the recording’s metadata history across systems.
The opposite mistake is assuming an old album UPC somehow identifies every song inside the project. It does not. The product code and recording codes operate at different levels.
Distributor workflows vary, so follow the platform’s instructions while preserving the identity of recordings that already have valid codes.
Keep a release-code sheet
You do not need complicated software for this.
For every release, keep a simple record with:
- song title;
- version name;
- final master filename;
- ISRC for that recording;
- release title;
- UPC/EAN for that release product;
- distributor;
- original release date;
- songwriter/composer information;
- ownership and split records;
- links to the live release after distribution.
If a song moves from single to album, you can immediately see which identifier belongs to the recording and which belongs to each release package.
This becomes especially useful when you change distributors, correct metadata, deliver a deluxe edition or license an existing recording somewhere else.
Do not make a new code just to make the dashboard look clean
Metadata should describe what actually exists.
If the same master already has a valid ISRC, the goal is not to erase its history because a new upload screen is asking for a code. Find the existing identifier and determine whether it should travel with that recording.
If you created a newly recorded version, then you may be dealing with a genuinely new recording that needs its own identifier.
Likewise, a new release package can need its own product identifier even when it contains recordings that already have ISRCs.
The code should follow the thing it identifies.
The move
Before you upload your next release, make one distinction:
Am I identifying the recording, or the release that carries it?
If you are talking about the individual master recording, think ISRC.
If you are talking about the single, EP, album or other product being delivered to stores, think UPC/EAN.
Once that becomes automatic, the rest of your release metadata gets much easier to organize.