What happens when your ISRC prefix isn’t yours anymore
16 · · 9 min read · Español
Nothing happens to the codes. Every ISRC ever assigned to your recordings is permanent — it survives the distributor you are leaving, the label deal that ended, the catalogue sale you just signed. What ends is quieter: where your next code comes from, and who is holding the register of the old ones. Settle both while the logins still work and this is an afternoon of admin. Leave them, and you will be reconstructing your own catalogue from the outside.
- An ISRC already assigned never changes. A recording sold, licensed, or moved to a new distributor keeps its code, and re-use of an assigned code is not permitted.
- The prefix identifies whoever assigned the code. The ISRC Handbook states that its characters cannot be assumed to identify a current rights owner.
- Assignment is what ends: only the owner, an exclusive licensee, or an authorised ISRC Manager may assign, so new recordings need a prefix you or your new distributor controls.
- Whoever assigned your codes must provide their details to you. For a distributor, the duty is written into the standard’s annex on ISRC Managers.
- A catalogue purchase moves the recordings and their codes. The seller’s prefix stays behind, and the seller must tell the buyer every code.
Whose prefix was it in the first place?
An ISRC prefix identifies whoever assigned the code, and the ISRC Handbook is explicit that its characters cannot be assumed to identify a current rights owner.
The standard even keeps separate verbs for the two halves of the arrangement. A prefix is allocated — handed to a party for future use. A code is assigned — bound to one specific recording, for good. The prefix went to your distributor. The codes went to your recordings. Keep those two facts apart and most of what follows answers itself.
Clause 3.3.1 closes the door on reading anything more into those five characters:
In particular, the characters of the Prefix Code cannot be assumed to identify a current rights owner as the recording may have changed hands since code allocation or the code may have been assigned by a third party.
A prefix is a return address, not a deed. Halley never owned the comet — he did the arithmetic, and the name stuck. Five characters record who did the paperwork on the day it was done, and the standard refuses to let anyone read more into them.
Do the codes on your released tracks still work?
Yes. An ISRC already assigned stays on its recording unchanged, whoever owns the recording now and whoever delivers it next.
Clause 4.6 has the least ambiguous title in the document — “ISRC Does Not Change”. Sell or license a recording on in unchanged form and no new code shall be assigned: the code stays the same, the Registrant must inform the new owner what it is, and the new owner tells business partners so the right party gets credited. Read the traffic in that clause twice. Money moves, names move, the code does not.
The permanence has teeth in the other direction too. Re-use of a code that has already been assigned to another recording is not permitted (4.3), and a code is never edited in place. If a code on a released track is genuinely wrong — a typo, somebody else’s, the wrong version — that is a different problem with its own order of operations, and fixing a wrong ISRC after release walks it.
What do you actually lose?
Access to new codes. Authority to assign under a prefix ends with the relationship that granted it, and future recordings need codes from somewhere else.
The Handbook’s annex A.5 draws the circle tight: an ISRC shall be assigned only by the owner of a recording — or a long-term exclusive licensee — or someone authorised as an ISRC Manager, which is the standard’s name for the role your distributor was playing. Annex D adds the fine print on that role: an ISRC Manager assigns only to recordings its clients own, and only on instruction. You were never a co-owner of that prefix. You were a customer of it.
So when the account closes, nothing happens backwards and everything happens forwards. The released catalogue keeps its codes. The next single needs one, and it cannot come from a prefix whose owner no longer works for you. Where it comes from instead — your new distributor’s prefix, or one allocated to you — is a decision made before the next delivery, not during it, and how to get an ISRC without a distributor prices every route.
What do you collect before you leave?
The assigned details of every code: ISRC, main artist, track title, version title, duration, content type, and date of first publication.
That list is not ours. The seven fields are Annex E’s reference metadata — the dataset the standard requires a Registrant to keep bound to every code it assigns. And on who must hand it to you, Annex D does not blink:
Once assigned, the details of assigned ISRCs shall be provided by the ISRC Manager to the owner of the recording who shall use the assigned ISRC to identify the recording in all circumstances thereafter.
Shall. Not on request, not at support’s discretion, not export-available-on-the-annual-plan. The details travel to the owner because the recordings are the owner’s — supplying them is a condition of the role, not a favour from it. Ask while “export” is still a button for you, rather than a message into a mailbox that no longer has to care.
And if you are already late — the account has gone cold, nobody answers — the codes that reached the stores can be read back from outside. Where to find the ISRC of a track already on streaming is that errand, with the one caveat that matters here: a lookup returns what a service was handed, and only the register says what was assigned.
What are the two mistakes that turn this into damage?
Assigning new codes under the old prefix, and assigning fresh codes to recordings that already have them.
The first is simply not yours to do. A.5’s circle — owner, exclusive licensee, authorised manager — has no seat for “former client who still remembers the prefix”, and the Handbook’s error annex (A.13.4) files an incorrect prefix among the mistakes that reach past your own catalogue into other Registrants’ territory — the kind registration agencies end up coordinating across borders to clean up. You would be minting codes in somebody else’s name.
The second is the popular one, because software offers it politely. A new distributor’s upload flow will offer fresh codes for everything you deliver — that is what a distributor’s prefix is for — and on a back catalogue that offer is a trap wearing a favour’s clothes. Accept it and every re-delivered recording carries two live codes, and the standard’s remedy (A.13.2) is bookkeeping rather than recovery — two ISRCs on one recording is that week, itemised. Enter the existing codes instead. Every field, every track, the fucking lot.
What if you’re the buyer?
A catalogue purchase moves the recordings and their assigned codes. The seller’s prefix is not part of the deal, and does not need to be.
The Handbook talks to buyers directly, and it assumes exactly as much diligence as deals actually have:
Further, a party acquiring the rights in a recording shall not assign an ISRC unless it is sure that the previous owner did not assign an ISRC.
So the question at closing is not what to rename — the answer to that is nothing — it is whether you have been told every code. Clause 4.6 puts the duty on the seller: the Registrant must inform the new owner of the recording’s ISRC. Make the register a deliverable, in the same folder as the masters and the paperwork. Recordings you make after the purchase are new recordings; they take codes from a prefix of your own, and that is the same route decision every self-releasing artist makes before a first delivery.
None of which requires you to feel anything about the old prefix. It was a return address. The asset is the recordings; the codes are theirs for life, wherever they travel; the register is what proves it — and a register that only exists inside somebody else’s dashboard is exactly the finding the catalogue audit checklist exists to surface while it is still cheap. Check it once a year. Switch distributors out of choice, not fear.
FAQ
Do your ISRCs change when you switch distributors?
No. An ISRC already assigned stays with its recording, and the new distributor delivers the same recordings under the same codes. Only a recording that never had a code needs one assigned.
Can you keep using your old distributor’s prefix?
No. A distributor assigns codes as an ISRC Manager, only for its clients and on their instruction. Once the relationship ends, new recordings take codes from the new distributor’s prefix or from one allocated to you.
Does buying a catalogue include the seller’s ISRC prefix?
No. The recordings keep the codes they were assigned, and the seller must tell the buyer what those codes are. The prefix remains allocated to the seller, and the buyer’s new recordings need a prefix of their own.
What if your old distributor won’t hand over your codes?
The ISRC Handbook obliges an ISRC Manager to provide the details of assigned codes to the recording’s owner. The codes that reached streaming services can also be read back from those services and checked against your own records.
Sources
- IFPI, ISRC Handbook, 4th Edition (2021) — the prefix read against ownership and the allocation/assignment distinction (3.3.1); who may assign (4.2 and A.5); no re-use of an assigned code (4.3); the code’s survival of a sale and the seller’s duty to inform the buyer (4.6); the reference metadata kept for every code (4.7, Annex E); the duplicate remedy (A.13.2); incorrect-prefix errors and their cross-border cleanup (A.13.4); and the ISRC Manager’s obligations, including supplying assigned details to the owner (Annex D). Clause codes in the text link to their page in the PDF.
One source, cited by clause, because every claim on this page is a claim about what the standard says. The Handbook quoted is the 4th Edition, 2021, read on the date at the top of this piece; the International ISRC Registration Authority updates its guidance between editions on its own site. None of this is legal advice.
Keeping the register
A register that lives with the catalogue cannot be held hostage by a switch. CatalogTracker keeps the ISRC on the track itself, beside the version and the recording type; search reads the identifiers directly — paste a code, get the recording — and every change to the register is kept with who made it and what it said before. In development for iPhone.