Releases
What is a Release?
A Release represents the delivery-ready version of an Album. It includes all parameters required to deliver that Album to a specific Recipient (Reprtoir Distribution, DSP, or Distributor).
A Release is the operational unit used for:
- delivering an Album to a recipient,
- updating metadata already sent,
- taking down content from DSPs.
Releases follow a strict one-to-one logic: one Release equals one delivery instance.
This architecture ensures clean tracking, independent updates, and safe takedown control.
How Releases are built?
A Release is created from an existing Album and automatically inherits:
- all Album-level metadata,
- all Track-level metadata,
- all Track audio files,
- and the Album’s artwork.
On top of this inherited data, the Release adds its own delivery parameters:
- the Recipient (Reprtoir Distribution, DSP, Distributor),
- included or excluded territories,
- pre-order and release dates.
This allows an Album to become a delivery-ready object that can be processed, validated, and transmitted through the Asset Delivery System..
When should I create a Release?
You must create a Release every time you intend to:
- deliver an Album to a DSP or Distributor,
- deliver the same Album to multiple DSPs (one Release per DSP),
- export a delivery package for a third-party distributor,
- issue an update for a previously delivered Release,
- perform a takedown.
Releases are required for all Delivery Channels:
- Reprtoir Distribution,
- Direct-to-DSP Delivery,
- Direct-to-Distributor Delivery.
Release List
Where can find the Releases List?To display the Releases list, go to the navigation menu located on the left of the Workspace, click on the “Catalog Management” icon, browse to the “Assets” section, and click on the “Releases” list.
The Releases List displays several columns by default, including:
| Column Name | Description |
|---|---|
| Artwork | Artwork inherited from the Album |
| Display Title | Album title (inherited) |
| Release Status | Current lifecycle status (Draft, Validated, Delivered, etc.) |
| Recipient | DSP or Distributor targeted by this Release |
| Delivery Status | Progress of the delivery instance |
| Validation Errors | Number of issues detected by automatic validation |
| Delivery Type | Delivery Channel selected for this Release |
| Release Date | Official public release date |
| Creation Date | Date of Release creation |
You can add or remove additional columns using the optional Custom Columns feature.
Release Status
There are several Release statuses:
| Status | Instructions |
|---|---|
| Draft | Status by default |
| Submitted | The release has been sent to the Recipient |
| Released | The release is available to the public |
| Taken Down | The release is no longer available to the public |
In the case of a manual feed, the Release Status is managed manually, except for the "Released" status, which is automatically updated by the Reprtoir system on the day of the digital Release date. Please note that in the case of a manual feed, modifying a status in Reprtoir does not affect statuses on the Recipient’s end.
In the case of an automatic feed, the Release Status is fully managed by Reprtoir. Please note that changing the status in the automatic flow directly impacts the status of your Release with your Recipient and its availability on DSPs.
Updated 1 day ago