If you’re releasing music digitally, you’ll come across two key identifiers: UPC and ISRC codes.
They are not creative tools, but they are essential to how your music is tracked, distributed, and paid.
Understanding them properly helps avoid problems later.
What Is an ISRC Code?
An ISRC (International Standard Recording Code) is a unique identifier for a specific recording.
Think of it as a fingerprint for an individual track.
Each version of a track needs its own ISRC:
- Original recording → one ISRC
- Radio edit → new ISRC
- Remix → new ISRC
- Remaster → new ISRC
It stays with that recording for life, across all platforms.
What ISRC Codes Do
- Track streams on platforms like Spotify and Apple Music
- Ensure royalties are correctly attributed
- Help collecting societies identify recordings
- Allow your music to be tracked globally
If two distributors upload the same track with different ISRCs, they are treated as completely separate recordings.
That can split plays and royalties.
What Is a UPC Code?
A UPC (Universal Product Code) identifies a release as a whole.
It applies to:
- Singles
- EPs
- Albums
So while ISRC = track, UPC = release package
What UPC Codes Do
- Identify your release in stores and databases
- Group tracks together under one product
- Help platforms organise your catalogue
- Used in reporting and sales tracking
If you re-release the same album later (for example, a deluxe edition), it usually gets a new UPC.
ISRC vs UPC (Simple Breakdown)
| Code | Applies To | Purpose |
|---|---|---|
| ISRC | Individual track | Tracks plays and royalties |
| UPC | Whole release | Identifies the product |
Where Do You Get These Codes?
Most distributors handle this automatically.
For example:
- DistroKid
- AWAL
They will:
- Generate ISRCs for each track
- Assign a UPC for the release
You usually don’t need to think about it unless you want full control.
When Should You Care About ISRCs?
This is where it becomes important.
1. Re-releasing Music
If you upload a track again:
- Using the same ISRC = keeps your stream count
- Using a new ISRC = starts from zero
If you’re moving from one distributor to another, keeping your ISRCs avoids losing momentum.
2. Building a Long-Term Catalogue
If you plan to:
- Release regularly
- Repackage music (EP → album)
- Distribute across multiple platforms
Then consistent ISRC use keeps everything connected.
3. Royalties and Tracking
Streaming platforms rely on ISRCs to:
- Count plays
- Match recordings
- Pay royalties
Incorrect or duplicated codes can cause:
- Missing royalties
- Split data
- Confusion in reporting
Do You Need to Buy Your Own Codes?
In most cases, no.
Distributor-generated codes are fine for:
- Independent artists
- First releases
- Simple workflows
You might consider your own ISRCs if:
- You run a label
- You want full control across multiple distributors
- You manage a larger catalogue
Common Mistakes to Avoid
- Uploading the same track with a new ISRC unintentionally
- Losing ISRC data when switching distributors
- Assuming UPC and ISRC are interchangeable
- Not backing up your release metadata
A simple spreadsheet with:
- Track name
- ISRC
- Release (UPC)
…goes a long way.
Why This Matters More Than You Think
These codes sit behind everything:
- Streams
- Playlist placements
- Royalties
- Catalogue management
They are invisible, but they define how your music exists in the industry.
If you get them right early, you avoid problems later.
Summary
- ISRC = track identifier
- UPC = release identifier
- Distributors usually assign both
- Keeping ISRCs consistent protects your streams and royalties
This article is part of the Music Production Reference Library, organised into volumes covering sound, theory, production, and release.
