Reprtoir provides a professional-grade delivery system that allows you to distribute your music assets to multiple Digital Service Providers (DSPs) with precision, transparency, and full control.

What is a Release?

A Release is a distributable asset derived from an Album. It is the unit of delivery sent to a specific DSP. If you deliver the same album to multiple DSPs, each delivery is considered a distinct Release.

Key Characteristics of a Release:
• A Release is created from an Album. • All metadata from the Album and its Tracks is inherited by the Release. • Delivery-specific metadata (such as release dates, territories, or pricing) is configured at the Release level. • A Release is targeted to one or more DSPs (e.g. Spotify, Apple Music, Deezer). • Each recipient combination (label + DSP) generates an independent Release for tracking and control purposes.

Delivery Workflow

Here’s the standard workflow for delivering your music to DSPs using Reprtoir:

1. Create a Complete Album

Begin by creating an Album in your catalog, making sure that all associated Tracks and metadata are correctly filled out and verified.

2. Create a Release

From your Album, initiate the creation of a Release. You will be prompted to:
• Select the intended recipient (label or distributor, if applicable). • Choose one or more DSPs for delivery. • Define all delivery-specific metadata (e.g. release date, territories, price tiers).

3. Submit the Release for Review

Once the Release is complete, submit it. This triggers our internal validation process.

4. Internal Verification by Reprtoir

Our content operations team will review the metadata to ensure that it meets industry standards and DSP-specific formatting rules.

5. Feedback & Corrections (if needed)

If the verification fails, you’ll receive an email notification outlining the required corrections.

You can:
• Edit and resubmit the Release with the necessary changes. • Or, contact our team via the support channel if you believe the request for changes is unfounded.

6. Delivery to DSPs

Once your Release is approved, it is sent to the selected DSPs. You’ll be notified when the delivery is successful.

Post-Delivery Actions

After a Release has been sent to DSPs, you still retain full control:

Submit Updates

You may submit an update at any time. Only the modified metadata fields will be revalidated by our team before being sent to the DSPs as an update.

Takedown a Release

You can issue a takedown request at any moment. Takedowns do not require team approval and will be processed automatically across the DSPs concerned.

Best Practices

• Always ensure your Album and Track metadata is complete and accurate before creating a Release.
• Double-check territories, dates, pricing, and ownership details at the Release level. • Use the support channel if you need clarification on metadata standards or correction feedback.