Direct-to-Distributor Delivery
This delivery channel does not require any specific contract or technical activation with Reprtoir. You simply need to already be affiliated with the Distributor you want to deliver to. Reprtoir can help initiate contact when necessary, but acceptance and onboarding remain entirely at the Distributor’s discretion.
What is Direct-to-Distributor Delivery?
Direct-to-Distributor Delivery allows you to use Reprtoir as your central metadata, asset, and release preparation system while delivering your content through an external Distributor such as Believe or The Orchard.
This channel is ideal when you already rely on a distribution partner and want to prepare Releases inside Reprtoir to streamline delivery operations.
Reprtoir does not act as a distributor in this configuration. You remain responsible for the contractual relationship with each Distributor and DSP, including rights, licensing, and revenue reporting.
Depending on the Distributor’s technical capabilities, two delivery mechanisms are supported:
- Manual Packages — Reprtoir generates a fully formatted ZIP archive containing metadata spreadsheets, audio files, artwork, and the required folder structure.
- Automated Delivery Feeds — When a Distributor supports DDEX, API, or custom ingestion endpoints, Reprtoir can submit the Release through those feeds.
Reprtoir does not perform manual quality checks for this delivery channel. Validation relies solely on Reprtoir Smart Control and the Distributor’s internal ingestion workflow.
Combining Delivery ChannelsIf you hold direct DSP licenses for some platforms but not others, you may use Direct-to-DSP Delivery, Reprtoir Distribution, and Direct-to-Distributor Delivery simultaneously without conflict.
How does it work?
A Release is created from an Album in your Workspace. It automatically inherits all metadata, audio files, and artwork from that Album.
The Release defines:
- the Recipient (the Distributor),
- the authorized DSPs (if supported by the Distributor),
- authorized territories (if supported by the Distributor),
- pre-order date (if supported by the Distributor),
- release date.
Each Release represents one delivery instance to one Distributor. The Distributor then handles downstream delivery to DSPs.
Before submission, Reprtoir Smart Control validates metadata and media. All issues must be corrected before exporting or submitting the Release.
Once validated:
- For Manual Packages, you export and upload the package to the Distributor.
- For Automated Feeds, you submit directly from Reprtoir.
Initial Delivery Workflow
Follow these steps to create, validate, and deliver Releases through Direct-to-Distributor Delivery.
◼ 1. Adding a Release
For more information about the Releases list, visit the dedicated page: https://docs.reprtoir.com/releases
To add a Release:
- Open the navigation menu on the left.
- Click “Catalog Management”.
- In the “Assets” section, open the “Releases” list.
- Click “New Release” (orange button) located at the top right of the list.
A creation form appears with the required fields.
Details Tab
| Fields | Instructions |
|---|---|
| Album | Select the Album to use as the source |
| Recipients | Select your Distributor |
| Authorized DSPs | If supported, select the DSPs the Distributor should deliver to |
| Distributed Territories | Choose territories (if required) |
| Included Stores | Optional: available only if the Distributor supports i |
| Excluded Stores | Optional |
| Release Date | Enter the Release Date |
| Pre-Order Date | Enter the pre-order date (optional) |
| Notes | Add optional notes |
Tags Tab
| Fields | Instructions |
|---|---|
| Custom Tags | Apply custom tags if required |
Click “Save” to create the Release or “Cancel” to close the form.
Bulk Release CreationFrom the “Albums” list, select several Albums, right-click, and click “Create New Releases”.
◼ 2. Checking that the Release is compliant
Check the “Validation Errors” column.
- If the status is Valid, proceed to step 3.
- If errors are listed (e.g. “6 errors”), metadata or media is missing or inconsistent.
Click the error count to open the “Error Assistant” sidebar, which guides you through each issue and helps you correct the metadata efficiently.
It displays issues detected at:
- Album level,
- Track level.
Click “Make Corrections” to go directly to the problematic fields.
Updating metadata at the Album or Track level automatically updates all Releases linked to that Album.
If the error count does not refresh, click “Re-Validate this Release”.
Once no issues remain, the Release is ready for export or submission.
◼ 3. Submitting the Release
Your submission workflow depends on the Distributor’s technical capabilities.
Manual Packages
From the “Releases” list:
- select one or several Releases,
- right-click and click “Export Files (ZIP)”.
A ZIP archive is generated containing:
- a metadata spreadsheet formatted for the Distributor,
- audio files renamed and structured according to their spec,
- compliant artwork files,
- a folder structure matching the Distributor’s ingestion format.
Download the ZIP from the notification center and upload it manually to the Distributor’s interface.
Automated Delivery Feeds
When a Distributor supports automated ingestion:
From the “Releases”. list, select one or several Releases, right-click, hover over “Automatic Feed Actions”, and click “Submit”.
The Distributor receives your Release directly.
Reprtoir performs no manual verification — metadata is transmitted exactly as provided.
Post-Delivery Actions
Update and takedown capabilities depend entirely on each Distributor’s ingestion system. Many Distributors do not support automated updates or takedowns from external tools.
Updates Workflow
Updates are not universally supported by Distributors.
- For Manual Packages, updates must generally be applied manually in the Distributor’s dashboard.
- For Automated Feeds, support depends on the Distributor’s ingestion capabilities.
If updates are supported:
From the “Releases”. list, select one or several Releases, right-click, hover over “Automatic Feed Actions”, and click “Update”.
If updates are not supported, all changes must be made manually in the Distributor’s dashboard.
Takedown Workflow
Takedowns are not universally supported by Distributors.
If takedowns are supported:
From the “Releases”. list, select one or several Releases, right-click, hover over “Automatic Feed Actions”, and click “Takedown”.
If takedowns are not supported, they must be executed manually inside the Distributor’s dashboard.
Delivery History
To view delivery logs for a Release, open its panel and consult the “Delivery History” tab.
Updated 10 days ago
