🚧
Setup Required
Direct-to-DSP Delivery requires configuration of your DSP credentials in Reprtoir. Contact our team so we can validate your contracts and activate the necessary delivery endpoints.

What is Direct-to-DSP Delivery?

Direct-to-DSP Delivery is designed for Organizations that hold their own licensing agreements with Digital Service Providers. This channel allows you to deliver content directly from your Reprtoir Workspace to DSPs through compliant integrations such as DDEX feeds, APIs, or other authorized delivery protocols.

Reprtoir does not act as a distributor in this configuration. You remain responsible for the contractual relationship with each DSP, including rights, licensing, and revenue reporting. Reprtoir provides the technical delivery infrastructure and metadata orchestration required for compliant, automated ingestion.

Reprtoir does not perform manual quality checks for this delivery channel. Validation depends on Reprtoir Smart Control (automated validation) and the DSPs internal workflows

👍
Combining Delivery Channels
If 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 (a specific DSP you hold a license with),
authorized territories,
pre-order date,
release date.

Each Release represents a single delivery to a single DSP.

Before submission, Reprtoir Smart Control validates mandatory metadata and media. All issues must be corrected before delivery.

Once validated, the Release can be submitted. Because Direct-to-DSP Delivery sends content directly to the DSP ingestion pipeline, no manual review is performed by Reprtoir. The DSP receives the data exactly as you submit it.

The DSP then processes the Release through its own automated and manual validation systems.

You retain full control over updates and takedowns at all times.

📘
Best Practices
DSPs apply their own automated checks (metadata, artwork, audio, rights) and may apply manual editorial review. For details on common DSP validation behaviors, please refer to the Best Practices and Delivery Compliance dedicated page.

Initial Delivery Workflow

Follow these steps to create, validate, and deliver Releases through Direct-to-DSP 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 the DSPs you hold a direct agreement with
Distributed Territories	Choose territories to include or exclude
Included Stores	Add DSPs to include (leave empty to include all)
Excluded Stores	Add DSPs to exclude
Release Date	Enter the Release Date
Pre-Order Date	Enter the pre-order date
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 Creation
From 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 sidebar will indicate that the Release is valid and ready to be submitted.

◼ 3. Submitting the Release

From the “Releases” list, select one or several Releases, right-click, hover over “Automatic Free Actions”, and click “Submit”.

The Release is sent directly to the DSP through your configured delivery feed. Reprtoir does not review or modify the content.

If a field is incorrectly formatted, missing, or non-compliant, the DSP may return an ingestion error or silently reject the Release according to its internal policies.

◼ 6. DSP Ingestion & Validation

Once received, the DSP processes the Release through its own validation systems, which may include:

automated metadata checks,
artwork and audio compliance validation,
rights, copyright, or fingerprinting analysis,
manual editorial review for specific cases.

Because these checks occur after delivery, preparing clean metadata and compliant assets upstream is essential.

Updates Workflow

◼ 1. Understanding Out-of-Sync Alerts

Any modification to Album, Track, or Release metadata — including artwork or audio — automatically sets the Release to Out of Sync.

The Out of Sync status appears in the “Status” column.

Before submitting an Update, always check the “Metadata History” tab to confirm the reason for the change.

If the change is intentional → submit an Update.
If the change is not intended to trigger a new delivery → leave the Release Out of Sync.

❗️
Changing UPC or ISRC values after delivery is not supported by DSPs. Never modify these identifiers once a Release has been delivered. If you need to change them contact us.

◼ 2. Submitting Updates

From the Releases list, select one or several Releases, right-click, hover over “Automatic Free Actions”, and click “Update”.

Updates are sent instantly to the DSP.

🚧
DSP processing times vary and cannot be accelerated by Reprtoir.

Takedown Workflow

You may request a takedown at any time.

From the Releases list, select one or several Releases, right-click, hover over “Automatic Free Actions”, and click “Takedown”.

Takedowns are sent instantly to the DSP.

🚧
You are fully responsible for issuing a takedown by mistake. Always double-check your selection before confirming.

Delivery History

To view delivery logs for a Release, open its panel and consult the “Delivery History” tab.