DISTROBOLT ARTIST GUIDES
Why the same ISRC cannot identify two different tracks
When two entries share an ISRC, first establish whether they contain the same recording or different recordings. Reuse across products can be correct; assigning one code to genuinely different recordings creates an identification problem.
Compare the recordings, not only the titles
Collect the source masters, durations, version descriptions, existing delivery records and assigned codes. Listen to the actual files. A renamed copy of an unchanged master is not automatically a new recording, while two takes of the same song can be different recordings even when their titles match.
Classify the apparent duplicate
IFPI requires an assigned ISRC not to be reassigned to a different recording. An unchanged single recording appearing on an album is a different situation from accidentally giving the single and a new live performance one code. Write which case you have and keep evidence of the original assignment.
Request a controlled correction
Before delivery, pause the affected draft and ask DistroBolt to confirm the correct identifier treatment. After delivery, provide the exact affected products and recordings through support. Do not simply change a spreadsheet and assume public store records are corrected. Avoid another competing upload while the case is unresolved.
Preserve the audit trail
Keep the old and corrected values, reason, approval and delivery outcome. Do not delete historical statements or adjust accepted collaborator percentages to disguise an identifier conflict. Review whether a correction affects other products using the recording. Identification helps trace the music; it does not by itself guarantee preserved playlists or automatically reconcile royalties.
Sources and review
Reviewed 4 November 2026. Platform requirements and plan terms can change. Examples are planning aids, not a promise of account access, release acceptance or earnings.
Continue your release planning
Ask the DistroBolt team about your release. Send a concise question and release reference; never send account passwords or verification codes.