Skip to main content

How to Update the ISRC for an Existing Product

  • Updated

Introduction

This article explains how to correctly update the International Standard Recording Code (ISRC) for an audio asset by duplicating a product and redelivering it to Digital Service Providers (DSPs). Updating the ISRC field directly on a delivered product will not be recognized by DSPs and may cause metadata conflicts or distribution issues.

 

Overview

When a product has already been delivered to DSPs, ISRC values can not be edited directly. Instead, users must duplicate the product and re-upload the correct audio asset with the updated ISRC. This ensures DSPs treat the new asset as a separate, valid submission. Once the new product is live, the original product containing the incorrect ISRC should be taken down.

Step-by-step Instructions

  1. Duplicate the Product
    From the Product Overview page, select the product that requires the ISRC change. Use the Duplicate function to create a copy of the existing product.
  2. Remove the Incorrect Asset
    In the duplicated version, locate the track with the ISRC you wish to replace. Remove this asset.
    Note: The duplicate initially uses the same asset and metadata, including the ISRC. Editing the ISRC directly will also change it in the original product, which can disrupt takedown operations.
  3. Upload the Correct Asset
    Click Upload new and re-add the audio file you want to deliver with the corrected ISRC.
  4. Enter Correct Metadata
    Fill in all required metadata fields for the new asset. Be sure to enter the correct ISRC during this step.
  5. Review and Deliver
    Review the product in full to confirm all fields are populated correctly. The system will automatically add "(Copy)" to the duplicate's title so that you are able to differentiate between the original & the duplicate. Once confirmed, deliver the product to DSPs.
  6. Takedown the Original Product
    After confirming that the new product is live on DSPs, initiate a takedown for the original product containing the incorrect ISRC.


Troubleshooting

  • Why can’t I edit the ISRC directly?
    Because DSPs do not recognize updated ISRCs for assets that have already been delivered. Changing the ISRC in-place may cause rejection, duplication issues, or failure to properly process takedowns.
  • What if the ISRC is linked to multiple SubClients?
    Review whether the same asset is reused across other deliveries. If so, coordinate all changes to avoid unintended takedowns.
  • The original product is still live after takedown. What now?
    Allow up to 5 business days for DSPs to process takedowns. If the product remains live, contact your FUGA representative or reach out via our support channel.

 

 

 

Related articles