feat & Co
Help Center

Codes & metadataDistributorISRC agencyAny streaming serviceYouTube

My ISRC is wrong, missing or used twice

Quick answer

An ISRC cannot simply be edited on a live release, and a code must never be reused for a different recording. If an ISRC is missing, assign one before the next delivery. If one recording has two ISRCs, pick the original and use it from now on. If two different recordings share one ISRC, ask your distributor to redeliver one of them with a new code. Then tell your collecting society and YouTube Content ID partner so royalties match the right recording.

Who can fix it
You, Your distributor, ISRC agency
Typical time
Varies by distributor; most fixes need a redelivery

Why this happens

  • Same recording, two ISRCs: the track was released again through a new distributor, or on an album, and a new code was generated instead of reusing the original.
  • Two recordings, one ISRC: a remix, radio edit, clean edit, live or sped-up version was uploaded with the original's code.
  • Typing errors: a code was copied by hand from a spreadsheet, or two codes were swapped between tracks.
  • Someone else's code: a code that belongs to another label's recording was entered by mistake, so the distributor or store rejects it as already in use.
  • Missing ISRC: an older or self-released recording never got one.

IFPI's rules are clear: a new or materially changed recording needs its own ISRC, the same recording keeps the same ISRC across releases and formats, and once assigned, an ISRC must never be reused.

How to fix it

  1. Make a list of every version. For each recording write the title, version, duration, release, UPC and the ISRC as it appears in your distributor dashboard and royalty statements. This shows exactly which case you have.
  2. Missing ISRC. Assign one (or let your distributor generate one) before the next delivery. If the track is already live without one, ask your distributor whether they can add it by metadata update or need to redeliver. See how to get an ISRC.
  3. Same recording with two ISRCs. Choose the code that was used first, because it usually carries the most streams and playlist placements. Use that code for every future release of the recording. If the duplicate release is live and creates a second copy of the song, ask the distributor that delivered it about taking that version down. See My song appears twice.
  4. Two different recordings sharing one ISRC. The original keeps the code. Give the other version (remix, edit, live) a new ISRC and ask your distributor to redeliver it. Most distributors cannot change an ISRC on a track that is already live; the usual route is to take the wrong version down and deliver it again, which resets its stream count and playlist adds.
  5. Typing error on a live release. Ask your distributor first. Some can correct metadata on a live track, but many treat an ISRC change as a new track. Ask what will happen to streams, playlists and saves before you agree.
  6. Tell everyone who uses the code. Update your neighbouring rights society or PPL-type organisation, your YouTube Content ID provider (usually your distributor), and any sync or licensing partner. A wrong ISRC is a common cause of Content ID conflicts and missing performer royalties.

If that doesn't work

  • If your distributor says the code is already in use by another company, check the international ISRC database (provided by SoundExchange and linked from the IFPI ISRC site) to see who registered it. Then contact that label or your distributor.
  • If you own the prefix and can't resolve a conflict, your national ISRC agency acts as controller and arbitrator for ISRC questions in its country. Where there is no national agency (including North Africa and most of the Gulf), contact the International ISRC Agency at isrc@ifpi.org.
  • If royalties for months went to the wrong recording, ask your distributor and society for an adjustment, sending your list from step 1 as evidence.

How to prevent it

Keep one master list of ISRCs per recording, give it to every new distributor, and never let a form "auto-generate" a code for a track that already has one. When you switch distributor, follow this checklist and reuse every ISRC exactly.

Official help for this problem

Direct links to the platform or society pages that handle this case.

Not able to do it?

Send us a ticket and we'll help you work it out.

Have these ready:

  • Artist name and links to the affected tracks
  • Each affected ISRC and the recording or version it should belong to
  • Release UPCs
  • Your distributor's name and any messages they sent
  • Screenshots of any 'ISRC already in use' error
Send us a ticket →

Questions people also ask

Can I reuse an ISRC from a deleted track?

No. IFPI says that once assigned, an ISRC must not be reused under any circumstances, even if the original track was taken down.

Will I lose my streams if the ISRC changes?

Often, yes. Stores treat a track with a new ISRC as a new recording, so its play count and playlist placements usually start again. Ask your distributor before any change.

Do clean and explicit versions need different ISRCs?

Yes. They are different edits of the recording, so each version needs its own ISRC.

Who can see who owns an ISRC?

The international ISRC database, provided by SoundExchange for IFPI, lets you search registered recordings. Not every recording is listed, because it depends on what labels have submitted.

Was this guide helpful?

Last checked against official sources on 28 October 2026. General information, not legal or financial advice. Platforms change their tools often: if a step looks different, tell us.

Related guides