Developer Help Center

Updating Distributed Releases

In many cases, it is possible to update a release without a full takedown. Stores do not require a full takedown as long as the following are all true:

  • Primary artists are the same on the release and tracks (including contributors with the role Primary Artist).

  • Track count, order and ISRCs are the same.

  • No audio changes other than those that correct an error (such as blank space, static, or corruption) and do not significantly change track length.

  • Same UPC.

Note

  • If any of the above need to change, you must issue a takedown, edit the release, and redistribute it with a new UPC.

  • Restrictions on updating releases apply as soon as the DSP processes the release, even if the release has never been live.

Updating a release without issuing a takedown can often be accomplished without unlocking the release. Editing the following fields do require that you unlock the release:

  • previouslyReleased

  • releaseDate

  • releaseTypeId

  • hasRecordLabel

Updating a release without unlocking
  1. Edit the release. See Adding/Editing Releases.

  2. Resend the release to the store(s). See Adding Releases to the Distribution Queue.

Updating a release with unlocking
  1. Unlock the release. See Unlocking Releases.

  2. Edit the release. See Adding/Editing Releases.

  3. Lock the release. See Locking Releases.

  4. Resend the release to the store(s). See Adding Releases to the Distribution Queue.