Put previously released singles on an album: files, identifiers and history

Decide which exact recording belongs on the album

Compare the approved single master with the proposed album file. A matching title is not enough. Note differences in performance, mix, edit, duration or creative processing. Keep the earlier release link and identifier as evidence. If you are actually replacing the performance, use the rerecording guide rather than describing it only as an album repackaging.

Keep the recording and package records separate

IFPI says that changing the product carrying an unchanged recording does not itself require a new ISRC. Keep the track’s established code while preparing the album’s own release record and package identifier. An album can therefore contain earlier recordings and new recordings with their respective identifiers. Check the identifier guide for a changed mix, edit or uncertain remaster.

Decide what changed before entering the album

• Same approved recording: keep the existing ISRC and link the album row to the earlier single record.
• New performance, mix or edit: describe the change and review the recording identity before entering an existing code.
• Only the package changes: keep the track record separate from the album title, running order, artwork and package identifier.

For example, using the same single master on an album is a packaging decision; replacing its vocal performance is a recording decision. If a remaster is involved, describe the processing rather than deciding from the filename alone.

Build a track-by-track album sheet

• Final running order and exact titles and version information.
• Approved audio filename and duration for every track.
• Existing ISRC and earlier release reference where applicable.
• Which recordings are unchanged, changed or entirely new.
• Correct main and featured artists, writer and production credits.
• Original release history and the proposed album date, clearly distinguished.
• Artwork, content labels, rights scope and any unresolved task.

An original album example

An artist prepares a seven-track album containing two earlier singles and five new recordings. The first single uses the exact approved master. The second has a newly performed vocal, so its recording identity needs review rather than automatic reuse. The team records those decisions on separate rows before entering the album. This is a hypothetical planning example, not a promise about any store’s display or stream-count matching.

Prepare the actual DistroBolt release

Use the verified New Release → Audio Release entry route in your approved account. Prepare the requested album information and accurate track records. Confirm how the current form represents existing codes, original release history and artist links if those fields are unclear. If a field does not match your existing release records, ask DistroBolt which information to enter before submitting. Keep the established artist identity and correct profile links. Follow the full release plan for review and delivery checks.

Keep existing deliveries until a coordinated decision

Putting a single on an album does not automatically mean the single should be removed. Consider the current agreement, existing links, intended catalogue structure and the actual new delivery before requesting changes. If you also change distributors, coordinate through the transfer guide. Neither a matching code nor an album upload guarantees combined streams, retained playlists or uninterrupted availability.

Check the public album after delivery

Listen to the earlier tracks as they appear on the album and verify the version, credits, artist identity and order. Keep package-level and track-level report records separate when reviewing royalty statements. If the wrong master is live, send the exact album link, track reference and intended correction rather than uploading another duplicate album. Plan coverage and optional assistance follow the current terms; no extra service is included by implication.