This article explains how to correctly update the International Standard Recording Code (ISRC) for an audio asset by duplicating a product in the FUGA Interface and redelivering it to Digital Service Providers (DSPs). It covers the exact step-by-step process of duplication, metadata updates, and taking down the original product to prevent distribution conflicts.
When a product has already been delivered to DSPs, its ISRC values cannot be edited directly. Instead, users must duplicate the product within the FUGA Interface 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 must be taken down to avoid metadata conflicts.
Step-by-Step Instructions
- Duplicate the product: Navigate to Catalog > Products and select the product that requires the ISRC change. On the product-level overview, click the three dots button on the upper right, and select Duplicate from the drop-down menu that appears.
- Remove the incorrect asset: In the duplicated version of the product, locate the track containing the incorrect ISRC you wish to replace and remove this audio asset.
- Note: The duplicated product initially copies the original asset and metadata, including the incorrect ISRC. Editing the ISRC directly without removing the asset will modify it in the original product as well, which can disrupt subsequent takedown operations.
- Upload the correct asset: Click Upload new on the track and re-upload the audio file you want to deliver with the corrected ISRC.
- Enter correct metadata: Fill in all required metadata fields for the newly uploaded asset, ensuring you input the correct ISRC during this step.
- Review and deliver: Review the product details thoroughly to confirm all fields are populated correctly. The system automatically appends "(Copy)" to the duplicate's title to help you differentiate it from the original product. Once confirmed, deliver the product to your selected DSPs.
- Take down the original product: Once you have confirmed that the new duplicated product is live on DSPs, initiate a takedown for the original product containing the incorrect ISRC.
Key Considerations
- Direct ISRC edits: DSPs do not recognize updated ISRCs for assets that have already been delivered. Attempting to change the ISRC in-place can result in delivery rejections, track duplication issues, or failures to process takedowns properly.
- Asset reuse across Subaccounts: Before initiating a duplication, verify if the asset is used across other active deliveries. Coordinate changes across all affected Subaccounts to prevent unintended takedowns.
- Takedown processing timelines: Takedown requests can take up to 5 business days for DSPs to fully process.
If the original product remains live after this timeframe, contact your FUGA representative or reach out via our support channel.