ISRC and UPC Codes: What They Are and Why They Follow Your Track Forever
Two codes get generated the moment you upload a release, and most people never think about them again until something goes wrong. Understanding what each one actually does prevents that.
An ISRC, in plain terms, is a permanent ID number attached to one specific sound recording. Not the song, the specific recording of it. If you record the same song twice, an original version and an acoustic version, that's two different sound recordings and two different ISRCs, even though it's technically the same composition underneath. Think of it as the recording's fingerprint. It's how every downstream system, streaming platforms, PROs, SoundExchange, identifies which exact recording generated a given stream or play.
A UPC is different, and covers a different level entirely. Where the ISRC identifies one recording, the UPC identifies the release, the single, the EP, the album, as a retail product. A five-track EP has one UPC for the whole release and five separate ISRCs, one per track. The UPC is what a retail or streaming system checks to identify which specific product a purchase or stream belongs to. Same underlying idea as a barcode on a physical product, because that's essentially where the standard came from.
Who assigns them, and when? Your distributor generates both automatically as part of the upload process. You don't need to purchase or register them separately. The ISRCs are typically visible in your distributor dashboard within a day or two of submission, well before the actual release date if you've uploaded with reasonable lead time.
Why do you need them for PRO registration and SoundExchange? Because those organizations are matching royalty activity, actual streams, actual plays, back to your registered works using these codes. Your PRO work registration and your SoundExchange recording registration both ask for the ISRC specifically, because that's the identifier that lets the royalty flowing in from a platform get matched to the correct recording in their system. Without the correct ISRC on file in the right places, royalty activity on your track can go uncollected or misattributed, not because the money wasn't generated, but because nothing tied the activity back to your registration.
What happens if you release the same recording twice with different ISRCs? You fragment your own royalty history. Streaming platforms and collection societies track performance by ISRC, so the same recording appearing under two different codes looks, to their systems, like two different, unrelated recordings with separate, smaller streaming histories, rather than one recording with a single combined history. This matters for chart eligibility, for algorithmic momentum on some platforms, and simply for having an accurate picture of how the track has actually performed.
Can you change an ISRC after release? No, not on the existing release. Once a track is uploaded and live, the ISRC is locked to that specific delivery. Changing it requires deleting the release entirely and re-uploading as a new one, which means losing the streaming history, saves, and any playlist placements tied to the original release and starting over from zero. This is exactly why it's worth getting metadata right before the initial upload rather than treating early mistakes as easily fixable later. They generally aren't.
The codes are quiet infrastructure. Nobody thinks about them until royalties don't match up or a re-release fragments a track's history, and by then the fix is a lot more work than getting them right the first time would have been.
Josh, Founder, JG BeatsLab
