Why both identifiers can appear in one delivery
A distributor's upload form may ask for a code for the recording and another for the release. Those fields can look interchangeable when an artist is preparing one song, but they describe different things. The International ISRC Registration Authority's FAQ says an ISRC identifies a sound recording or music video recording, while music products are generally identified by UPC or EAN codes.
The short version is simple: an ISRC identifies the recording; a UPC or EAN identifies a product. Keeping the two levels separate makes it easier to read delivery metadata and to spot a code pasted into the wrong field.
ISRC: the recording-level identifier
ISRC means International Standard Recording Code. The IFPI FAQ says it identifies a particular sound recording or music video recording. It does not identify the composition, performer, release product, or ownership of the rights. A composition and a recording are related, but they are not the same object.
An ISRC is meant to remain associated with the same recording over its lifespan, including when ownership changes. The FAQ says codes must not be reused. A music video recording and the corresponding audio recording are also treated as different recordings, even when the audio is the same, so each has its own identifier.
For an artist, that means the code should follow the specific recording rather than the name of an album or the date it was uploaded. A changed title or new package does not automatically create a different recording, while a remix or a materially different edit may require a new code under the applicable assignment guidance. Confirm edge cases with the rights holder or distributor rather than guessing.
UPC or EAN: the release-product identifier
A UPC or EAN belongs to the product level. In GS1's system, the broader Global Trade Item Number identifies a trade item that may be priced, ordered, or invoiced. UPC-A and EAN formats are among the ways GS1 identifiers can be carried. The GS1 guidance on GTINs and barcodes describes the trade-item scope; IFPI notes that music products are generally identified by UPC/EAN codes.
For a release, the product can be a single, EP, album, or another package distributed to stores and services. The exact identifier requirement can depend on the distributor, release configuration, territory, and product version. A deluxe edition, a separately issued physical format, or a changed product listing should be handled according to the distributor's and GS1's allocation rules, not by copying a code from an unrelated release.
How the two work together
Imagine an album containing ten tracks. The album is a release product and may have a product identifier. Each track is a recording and has its own ISRC. If one of those same recordings also appears on a single, its recording-level ISRC can remain associated with that recording, while the single and album are separate products whose product identifiers are handled at the release level.
That example is a model for keeping fields straight, not a universal rule for every distributor form. Some platforms assign or populate identifiers during delivery, and some artists do not need to purchase or enter a UPC themselves. Follow the instructions from the distributor or label that is delivering the release.
A short metadata check before delivery
- Confirm that each ISRC is attached to the intended recording, not to the composition or release title.
- Confirm that any UPC or EAN is attached to the release product field requested by the distributor.
- Keep the distributor's final metadata export or confirmation with the release records.
- Do not create, reuse, or alter codes by hand when the code's assignment authority or product configuration is unclear.
- If the recording is being reissued, remixed, edited, or transferred, ask the rights holder or distributor which identifier should carry forward.
An ISRC reference can help with the recording-level term. The identifiers themselves do not establish ownership, a license, or a royalty split. Those questions belong to the relevant agreements and rights records, not to a code field.
Frequently asked questions
Is an ISRC a UPC?
No. An ISRC identifies a recording. A UPC or EAN identifies a product or release at the trade-item level.
Does an ISRC prove that I own the master?
No. It identifies a recording. It is not an ownership document, transfer, or license.
Can one ISRC be used for an album and a single?
If it is the same recording, the ISRC is intended to remain with that recording. The album and single are different release products, so their product-level identifiers are separate questions.
Subscribe to the Sunday Stem
A short, honest dispatch on American music, three mornings a week, with the Sunday Stem on craft, catalog, and the writers keeping the long tradition alive.
More from the Indie Label / Artist Dev desk →Frequently asked
Is an ISRC the same as a UPC?
No. An ISRC identifies a particular sound recording or music video recording. A UPC or EAN is a product identifier used for a release or other trade item.
Does an ISRC identify who owns a recording?
No. An ISRC is an identifier, not a statement of ownership or permission.
Can the same recording have an ISRC on both a single and an album?
The ISRC is intended to stay with the same recording over its lifespan. Release-product identifiers are separate and follow product-level allocation rules.
Further reading on From The Stem
· What Is an ISRC Code?
· What Is a Music Metadata Sheet?
· ISRC
· UPC/EAN