M3 StudiosSpring, TX5 min readJuly 6, 2026An ISRC identifies each individual recording, and a UPC identifies the whole release. Every track you send to Spotify, Apple Music, or Amazon Music needs a valid ISRC, and every single, EP, or album needs a UPC, or the delivery gets rejected and the plays go uncounted. The detail that costs independent artists the most is invisible until it is too late: switch distributors without carrying your existing codes, and your stream counts, playlist placements, and save data can be wiped clean, because the platforms will read your catalog as a brand-new release.
These two codes are the quiet infrastructure under every release, and most artists never think about them because a distributor fills them in automatically. Understanding what they do, and the handful of mistakes that break them, is the difference between a catalog that pays you correctly for years and one that leaks royalties and loses its history the first time you move it. For a Houston artist building a body of work, the codes are the metadata that keeps that work yours.
An ISRC is an International Standard Recording Code. It identifies one specific sound recording, and it is governed by the IFPI under the international standard ISO 3901. Every ISRC is a permanent 12-character code in the format CC-XXX-YY-NNNNN: a two-letter country code, a registrant code for the rights holder, a two-digit year, and a five-digit number for the individual recording. For a United States rights holder, the country code is typically US, QM, or QZ. Once an ISRC is assigned to a recording, it stays with that recording forever, even if the rights are later transferred.
A UPC is a Universal Product Code, the same kind of barcode found on any product for sale. In music it identifies a release as a whole, a single, an EP, or an album. The relationship is simple: a release with ten tracks has one UPC and ten ISRCs, one for each recording inside it. Think of the UPC as the barcode on the packaging and the ISRC as the fingerprint on each song in the box.
There is a third code worth knowing, because people confuse it with the other two. An ISWC, an International Standard Musical Work Code, identifies the underlying composition, the songwriting itself, separate from any particular recording of it. The ISRC is the recording. The ISWC is the song. A single composition can have many recordings, each with its own ISRC and all pointing back to the same ISWC.
Every time your track is streamed, played on radio, or used in a film or television placement, the ISRC is what connects that play back to you as the rights holder. Without a valid, correct ISRC, there is no reliable way for a platform, a distributor, or a collection society to route that payment to the right person. When your music is played internationally, collection societies across different countries match recordings by ISRC to pay neighbouring rights, and a missing or wrong code means that money does not vanish so much as sit unclaimed in a pool that eventually gets redistributed to other artists.
The platforms enforce this at the door. Spotify, Apple Music, Amazon Music, and every other streaming service require a valid ISRC for every track delivered to them, and deliveries with missing, malformed, or duplicate codes get rejected outright. Beyond accepting the upload, the platforms use ISRCs to deduplicate their catalogs, power the credits and "appears on" sections, and aggregate the streaming numbers that decide chart eligibility. Billboard and other chart bodies rely on ISRCs to count plays, so a missing or wrong code can cost a placement you actually earned.
This is the most painful and most avoidable mistake an independent artist makes. When you move your catalog from one distributor to another, the new service asks you to upload your releases. If you do not enter your existing ISRCs and UPCs, the new distributor generates fresh ones. Because streaming platforms identify tracks by those codes, your music then arrives as a completely new release. The stream counts, the playlist placements, and the saves attached to the old codes can all be lost.
The prevention takes minutes. Before you switch, export or screenshot the ISRCs and UPCs for every release from your current distributor's dashboard. When you re-upload, enter those exact codes, and match the rest of the metadata precisely, the same track titles and the same audio files. When the codes match, the platforms recognize the release as the same one, and the history survives the move.
Your ISRCs are the memory of your catalog. Move your music without them, and the platforms forget everything your songs earned.
The codes also carry your name. Platforms pull the credits and "appears on" listings from the metadata tied to a recording, so a clean ISRC keeps a producer, a featured artist, or an engineer attached to the work that made them. When a sync opportunity comes and a music supervisor searches for a track, the ISRC is how they find the exact recording and reach the right rights holder. A catalog with correct codes is searchable, creditable, and reachable. A catalog with broken codes is a pile of songs nobody can route money or a placement to.
The rule is about the audio, not the song. A new recording needs a new ISRC. That includes a remix, an acoustic version, a live recording of a song you already released in the studio, a remaster with audible changes, a version in a different language, and a radio or extended edit that is materially different from the original. Reusing one ISRC across two different recordings confuses the platforms, merges the plays, and tangles the royalty splits in a way that is painful to unwind.
You do not need a new ISRC when the same recording is simply released on a different platform, added to a compilation, or moved to a different distributor, as long as the audio file is identical. The line is clean: if the audio changed, it is a new recording and needs a new code. If the audio is the same, keep the same code.
There are two routes, and for most independent artists the first is all they need. When you upload a release through a digital distributor, it generates the ISRCs and the UPC automatically, at no cost, built into the delivery. You can find the assigned codes in your distributor's dashboard after upload. Save them somewhere permanent, a simple spreadsheet works, because you will need them to switch distributors, register with collection societies, and submit music for sync.
The second route is for artists and labels who want to own and manage their own codes. You can apply for your own registrant code through your country's national ISRC agency, which in the United States is the RIAA-administered US ISRC Manager. That gives you the registrant portion of the code so you can issue your own ISRCs across your catalog. It is more control than a solo artist releasing singles usually needs, but it matters for a growing catalog. One warning holds either way: legitimate codes are free through your distributor or your national agency, so any third-party website charging a fee per ISRC is selling you something you can get at no cost, and their codes are no better.
Codes are one piece of a larger truth: the money follows the metadata. A release with clean, correct codes tracks its own royalties, protects its stream history, and stays eligible for charts and sync. The place to get this right is before release day, which starts with a finished, release-ready master and the full metadata package locked in before the file ever reaches a platform. A record built with intention in the production stage and finished in a Houston recording session deserves the paperwork that keeps it paying.
The codes connect to the wider collection machinery every independent artist should understand, from the streaming royalties a distributor pays to the neighbouring and performance income that flows through separate registrations. Getting the identifiers right is step one, and the rest of the map lives in the Houston music publishing and royalty guide. Your catalog is an asset. The metadata is what keeps the asset yours.
An ISRC identifies one individual recording, one track. A UPC identifies a release as a whole, a single, EP, or album. A ten-track album has one UPC and ten ISRCs. A third code, the ISWC, identifies the underlying composition, the songwriting, separate from any recording.
No. Distributors generate ISRCs and a UPC for free when you upload a release, and you can apply for your own registrant code through your national ISRC agency, which in the US is the RIAA-administered US ISRC Manager. Any third-party site charging a per-code fee is selling something you can get at no cost.
Only if you fail to carry your existing codes. Before switching, export your ISRCs and UPCs from your current distributor and enter those exact codes when you re-upload, matching the titles and audio files. When the codes match, the platforms recognize the same release and your stream history survives. Enter new codes, and your catalog reads as a new release and the old data can be lost.
Yes. A new ISRC is required any time a new recording is created, including a remix, an acoustic version, a live take, a remaster with audible changes, a different-language version, or a materially different edit. The same recording released on a different platform keeps its original ISRC.
Check your distributor's dashboard, where ISRCs are listed alongside each track. If you registered your recordings with a national agency, the codes are in your account there. Keep a running record of every code so you have them ready for distributor switches, collection society registration, and sync submissions.
Follow M3 Studios for the business behind the work: Instagram @metamusicmedia.x, TikTok @metamusicmedia, YouTube @metamusicmedia. Questions: info@metamusicmedia.com. The metadata and royalty mechanics behind a release run through the M3 Studios creator education library.
↑ Back to top