A catalogue reissue does not automatically need a new recording code. If the audio is the same recording, keep its International Standard Recording Code (ISRC), even when the label, distributor, format or territory changes. If the team has made a different recording or a substantive edit, assign a new one. That is the decision rule in IFPI’s ISRC guidance, and it belongs on every reissue checklist.
The distinction matters before delivery. A new code can make an unchanged master look like a separate recording in the metadata that distributors, stores and rights organizations exchange. Conversely, giving a remix the original code hides a real version difference. IFPI says the code identifies the recording, not the song, release or current owner; its ISRC explainer describes how that identifier supports usage reporting and rights management.
Keep the code when the recording is the same
A transfer of ownership is not a new performance. IFPI’s FAQ says an assigned ISRC stays with the recording throughout its life, including after an acquisition. Its handbook says the same for a licensed master, an unchanged compilation appearance, and a version delivered in a different encoding or resolution.
That means a label preparing a 2026 digital edition of an older album should first retrieve the original code for each unchanged track. A new package may need its own release identifier, but a package is not a new recording. The handbook explicitly says to use product identifiers when the business needs to distinguish one release from another; ISRC cannot separate an album track’s exploitation from the same audio on a compilation.
Ordinary remastering also usually keeps the code. IFPI says uniform level changes, equalisation, compression and technical cleanup without changing creative choices across the recording do not call for a new ISRC. Its FAQ reserves a new code for a remaster with significant new creative input. The word “remastered” on artwork is therefore not enough evidence to allocate another identifier.
Give distinct audio its own identity
A different take, live performance, remix, added vocal, extended version or clean edit is a separate recording under the IFPI handbook. The same is true of a music video: it needs a separate ISRC even when its soundtrack uses the released audio master. Keep the audio and video codes related in your catalogue record rather than treating them as interchangeable.
Length needs care. IFPI’s handbook says removing or adding a verse or chorus requires a new code regardless of duration. For a change such as a fade that does not substantively change the creative content, a difference under 10 seconds normally keeps the existing code; a difference of 10 seconds or more calls for a new one. The rule is about the nature of the edit as well as the clock, so a short clean edit cannot borrow the original code.
If an old recording genuinely never received an ISRC, IFPI says one can be assigned before reissue. Search the existing catalogue and ask the former distributor or licensor first: the IFPI FAQ points rights holders to its public database when an earlier code is uncertain. Do not recycle a code assigned to an abandoned track; IFPI says assigned codes cannot be reused.
Make the release decision auditable
For each proposed track, record the original ISRC, source master, version name, duration, rights holder and what changed in the audio. Then mark one of three outcomes: reuse the code, assign a code for a distinct recording, or investigate an uncertain match before delivery. This is a narrower, more useful gate than a blanket “new release, new codes” rule.
Cross-check the result against the release-calendar metadata check and the royalty-blocking metadata failures already covered by this desk. A distributor can carry a clean identifier map to every digital service, but the label has to decide which audio each code names. That is the handoff InterSpace Distribution and label clients using ToneGrid should resolve before a reissue leaves the catalogue team.
