An ISRC identifies a specific sound recording.

It does not identify the song as an abstract composition, the artist or the whole release. It follows one particular recorded version.

That distinction determines whether you should reuse an existing code or assign a new one.

Reuse the ISRC for the exact same recording

You should generally reuse the original ISRC when moving the unchanged master to another distributor.

Keeping the same code helps streaming services recognise that it is the same recording. This can support continuity across:

  • Stream counts
  • Playlist placements
  • Listener libraries
  • Release history
  • Royalty reporting

The release metadata should also remain as consistent as possible.

A distributor transfer does not create a new recording

Changing distributor does not, by itself, justify a new ISRC.

The recording is still the same recording even though a different company is delivering it.

When transferring a catalogue:

  1. Download the original metadata.
  2. Retain every ISRC and UPC.
  3. Upload the identical audio.
  4. Match the artist and track information.
  5. Wait for the replacement delivery to appear.
  6. Request removal of the old version.

Avoid taking the original release down before the new delivery is available.

When does a recording need a new ISRC?

Assign a new code when the recording has changed substantially.

Examples can include:

  • A new studio recording
  • A live version
  • A remix
  • An acoustic version
  • An instrumental version
  • A different vocal performance
  • A materially altered edit

These are separate recordings even when they represent the same underlying composition.

What about remasters?

A remaster may require a new ISRC when the sonic result is materially different.

A tiny technical adjustment does not necessarily create a new recording identity. A newly marketed remaster with meaningful audio changes normally should be distinguished from the original.

Keep the original code attached to the untouched original master.

What about clean and explicit versions?

Clean and explicit versions normally contain different audio and should have separate ISRCs.

The same applies where words are muted, replaced or removed.

This lets stores and listeners distinguish the versions correctly.

Do not reuse an ISRC for a different song

Never place an existing ISRC on unrelated audio to inherit streams or playlist history.

That creates inaccurate metadata and can lead to:

  • Incorrect royalty allocation
  • Store removals
  • Catalogue conflicts
  • Fraud concerns
  • Problems for future transfers

An ISRC is not a promotional shortcut.

Common transfer mistakes

Artists often run into trouble when they:

  • Generate fresh codes unnecessarily
  • Change several pieces of metadata at once
  • Upload different audio
  • Remove the old version too early
  • Create duplicate artist profiles
  • Forget contributor information

Treat a distributor migration as a careful metadata transfer rather than a brand-new release campaign.

Keep a catalogue master sheet

Store the following information for every recording:

  • ISRC
  • UPC
  • Exact title
  • Version title
  • Primary artists
  • Featured artists
  • Release date
  • Songwriters
  • Master filename
  • Distributor
  • Ownership information

Good records make future transfers, licensing and royalty checks much easier.

RouteNote allows artists to supply existing ISRCs when appropriate, helping catalogue moves retain consistent recording identities.