Managing Changes to Your Release on Nodable

Written By nodable

When your release has already been delivered to digital streaming platforms (DSPs), the type of changes you can make depends on the nature of the update. This applies whether your release is already live or still pending, once delivered, these rules always apply within the Nodable ecosystem.

1. Changes You Can Make Independently

Certain updates can be handled directly from your Nodable dashboard without needing support assistance and without taking down your release.

What you can update:

  • Release cover image and title (must remain consistent with each other)

  • Language localization (artist names, submissions, public domain tracks)

  • Additional artist names and roles

  • Record label name

    • ⚠️ If using a parent-child account structure, you must switch into the child account before editing the label (except when editing from the Inspection page)

  • Track titles and additional contributors

  • Genre

  • P & C lines

  • Publishing information

  • Preview clip start time

  • Explicit content flag

  • Distribution territories

  • Pricing tier

  • Sale start date

  • Minor audio corrections
    (e.g. silence, static, or corrupted sections — keeping the same ISRC)

Important note on audio updates:

You can replace the audio file only if it remains substantially the same track (same ISRC and similar duration).
The greater the difference in length or structure, the higher the chance DSPs may reject the update.

Procedure:

Simply edit your release in Nodable and resend it to DSPs.

2. Changes That Require Nodable Support (No Takedown Needed)

Some updates require manual intervention from the Nodable team but do not require removing your release.

What requires support:

  • Original release date (historical date, not the go-live date)

Procedure:

Contact Nodable support and provide:

  • Release ID or UPC

  • Correct release date

Our team will handle the update for you.

3. Changes That Require a Takedown and Redelivery

Certain elements are locked once your release has been delivered. To modify them, DSPs require a full takedown and redelivery with a new UPC.

Changes that require takedown:

  • Track order

  • Number of tracks

  • UPCs / ISRCs

  • Major audio changes (non-corrective or significantly different duration)

  • Apple-specific metadata:

    • Release catalog ID

    • Track catalog ID

Exceptions:

These restrictions may not apply if:

  • Your release is part of a Merlin Apple agreement within Nodable

  • Your release was first distributed through Nodable after November 2024

Procedure:

  • Take down the existing release

  • Create and deliver a new version with a new UPC

Key Takeaway

Nodable gives you flexibility to manage most updates independently, but certain structural or identity-related changes are controlled by DSP requirements. Understanding these distinctions ensures your releases remain compliant while minimizing disruptions to your catalog.

If you're unsure which category your change falls into, it's always best to check with Nodable support before proceeding.