Separate an ISRC from a release barcode

Start with three different objects

A release spreadsheet often puts the song title, ISRC and UPC in neighbouring columns, making the identifiers look interchangeable. They point to different levels: the composition, a particular recording, and the product or edition carrying recordings.

The International ISRC Registration Authority defines ISRC as an identifier for sound recordings and music videos. It explicitly says the code does not identify the composition or the product that contains the recording. The difference is practical: a song can have more than one recording, while one recording can appear on different products or formats. ^[1]

Use the ISRC at track-recording level

Treat an ISRC as the persistent reference for one recording, rather than as a label for an album campaign. IFPI says it remains with the recording across formats, bit rates, releases and licensing arrangements. A change of ownership alone does not call for a new code. That makes the ISRC useful when a track moves through a distributor, appears on a later compilation, or is delivered in another audio format. ^[1]

The code needs dependable reference data beside it. IFPI lists the recording code, main artist, track title, any version title, duration, content type and first-publication date among the minimum data to retain. Store those fields together in a stable table and use the same spelling and version description in delivery files. The code does not repair inconsistent metadata by itself. ^[2]

A remix or edit is not just a new container for the same audio. IFPI identifies remixes and edits among changes that require a new ISRC; its FAQ also says a substantial creative contribution during remastering can justify a new code, while a conventional remaster generally keeps the existing one. The appropriate assignment depends on what changed in the recording, so consult the current handbook or your authorised ISRC manager for borderline cases. ^[1]

Use the product code for the edition

A UPC or EAN barcode represents a Global Trade Item Number, or GTIN. GS1 describes the number as the identity of a product, with a database record carrying details such as brand and product name. The bars are a machine-readable representation of the number; the printed digits let a person read the same reference. Neither the bars nor the number are a substitute for the track-level ISRC. ^{[3] [4]}

Think of an album delivered as a download and as a physical CD. The recordings may retain their track ISRCs, while each product edition has its own product identifier where UPC/EAN or GTIN is used. A multi-track album does not receive one ISRC in place of the track codes: IFPI says product identifiers support supply-chain tracking and distinguish products or formats. ^[1]

Do not infer a GTIN’s meaning from its digits. GS1 says GTINs are non-significant identifiers: product details are looked up in a database, not decoded from the barcode. GS1 says distinct products have their own GTINs. For a changed edition, check current GS1 rules and your sales channel instead of guessing from the artwork. ^[4]

A worked release-sheet example

Imagine a self-released metal EP with four tracks. The band has approved the final stereo master for each track, an instrumental mix of track two, a digital edition, and a short-run CD. The four main recordings each need their own recording row and ISRC. The instrumental is a distinct version, so its row should not be hidden under the vocal master’s identifier; follow ISRC guidance for assigning the right code to the changed recording. The release sheet should make the version name explicit.

Then make separate product rows for the editions you actually distribute. Record each product identifier in its product row, not copied into every track’s ISRC field. Link the rows with clear references: product edition, track position, recording title/version, ISRC, and the relevant product code. This simple relation lets a collaborator ask “which audio asset?” or “which edition?” and get a different, unambiguous answer.

For a reissue that uses the unchanged original recordings, preserve their ISRCs. Evaluate the product identity independently: new packaging or a changed format may create a different trade item, but the exact GTIN decision follows GS1’s rules and the release’s distribution context. Keep the decision and the source of the code in your records so the next delivery does not silently invent another identifier.

Run a handoff check before delivery

Check the recording side first: one row per distinct recording, an accurate artist and title, a useful version label, duration, content type, publication date, and an ISRC that has not already been assigned elsewhere. If a distributor assigns codes for you, record what it assigned and who controls the source data. IFPI recommends that registrants preserve reference metadata for each ISRC and explains that first owners may assign directly or use an ISRC manager. ^[2]

Check the product side next: one row per edition or sellable product, the correct UPC/EAN or GTIN where required, consistent product naming, and a clear link to the track list. Compare the digital delivery form with the physical package proof if both exist. A mismatch between the barcode on a sleeve and the release sheet is a product-level problem; a duplicate or wrongly reused ISRC is a recording-level problem. They need different fixes.

Keep the working sheet and final delivery receipt with the approved masters. Identifiers make assets and editions easier to track, but do not establish ownership, grant permissions, prove publication, or guarantee correct store metadata. They are reference keys inside a larger rights and release record.