Key takeaways
- ISRC identifies a recording; UPC or EAN identifies the release product that contains it.
- The same recording can appear on more than one release. Check the recording and the package separately.
- Use identifiers to narrow a store match, then verify the artist, version and destination before publishing.
The distinction that matters
Think of the recording and the package separately. A recording may appear on a single and later on an album. The recording identifier and the release product identifier answer different questions.
| Identifier | Identifies | Use when checking a link |
|---|---|---|
| ISRC | An individual recording | Check that the track is the intended recording or version |
| UPC / EAN | A release product | Check that the single, EP or album is the intended package |
The IFPI ISRC guidance explains the distinction: ISRC is for recordings, while music products use identifiers such as UPC or EAN. Changing ownership alone does not require a new ISRC; materially different recordings may need their own.
Why titles alone are not enough
Search for a common song title and you may find remixes, clean versions, radio edits, live performances and unrelated tracks with the same name. Artist spelling can also vary across services.
When creating a fanlink, compare the identifier as well as the title. Then review the artwork, duration and version label. An exact identifier is a stronger signal than a plausible-looking search result, but incorrect source metadata still needs human attention.
Keep a small release record
Create one row per track and retain the release-level code alongside it. Include the final artist credit, version, duration and release date. Add store URLs once you verify them.
- Release: title, UPC or EAN, artwork and date.
- Recording: title, artist, version and ISRC.
- Destinations: checked store URLs and any territory notes.
Keep codes as text in a spreadsheet. That avoids losing leading zeros or having a long number reformatted. Do not guess a missing code from another store listing; confirm it with the distributor or your original release record.
What to do when a match looks wrong
Stop before publishing the destination. Compare the version, duration, explicit status and release context. Ask whether the store result is a track or an album; a correct album page may still be the wrong destination for a single-song campaign.
If the code in your source record differs from the store result, return to the distributor’s metadata. Keep the disputed result separate from verified links so the next person does not assume it was approved.
How this changes your link workflow
Use identifiers to reduce repetitive searching, then review the fan-facing result. Unsleeve’s automatic store matching uses exact UPC or ISRC matches; uncertain search results need approval. A manually chosen link stays under your control.
Explore music smart links, or use the release checklist to collect these details before announcing your next song.
Sources & further reading
Provider documentation and Unsleeve’s own product information serve different purposes. Check current provider requirements before planning a release. Read our editorial approach or report a correction.
