DDEX is the international standards body that defines how music data moves between distributors, streaming platforms, and rights organisations. Most independent artists have never heard of it — but the quality of their royalty reporting and the accuracy of their metadata on streaming platforms depends entirely on it.
What is DDEX?
DDEX — pronounced 'dee-dex' — stands for Digital Data Exchange. It is an international standards-setting organisation, founded in 2006, whose members include major record labels, streaming platforms, distributors, and collecting societies. DDEX does not distribute music or collect royalties. Instead, it defines the technical formats and protocols that these organisations use to communicate with each other — specifying how a release should be packaged when delivered to a streaming platform, how that platform should report usage back to a distributor, and how rights information should be communicated between parties in the music supply chain. Without DDEX, every distributor would communicate with every streaming platform in a different format, making large-scale automation of music distribution and royalty reporting impossible.
The main DDEX standards
DDEX publishes several distinct standards, each covering a different type of communication in the music supply chain:
- ERN (Electronic Release Notification) — the format used to deliver a release from a distributor to a streaming platform or digital store. An ERN package contains the audio file, the artwork, and all the metadata for the release in a standardised XML structure. Spotify, Apple Music, Amazon Music, and other major DSPs require ERN-compliant deliveries. If your distributor is not ERN-compliant, your releases may be rejected or delivered with incomplete metadata.
- RDR (Royalty Data Reporting) — the format used by streaming platforms and stores to report usage and sales data back to distributors. An RDR report tells the distributor which tracks were streamed, how many times, in which territory, at what rate, and what payment is due. Standardised RDR reports are the foundation of automated royalty statement generation.
- MWN (Music Works Notification) — used to communicate information about the underlying compositions — the works, their rights holders, and their ISWCs — between rights organisations and other parties in the chain.
- DSR (Digital Sales Reporting) — an older standard for reporting digital sales, largely superseded by RDR for streaming contexts but still in use for some digital download and physical sales reporting.
Why DDEX matters for independent artists
Independent artists do not interact with DDEX directly — but the quality of their distribution experience is determined by whether the parties in their supply chain are DDEX-compliant. A distributor that sends ERN-compliant deliveries to streaming platforms ensures that all metadata fields are correctly structured, that ISRCs are properly embedded, that artwork specifications are met, and that the delivery is accepted first time. A distributor using a non-standard or partially compliant delivery format may find that certain metadata fields are dropped, that ISRCs are incorrectly formatted in the platform's system, or that releases are rejected and require manual redelivery. These errors cascade downstream: a missing ISRC in the Spotify metadata means that streaming log data cannot be reliably matched to the recording for royalty purposes.
How DDEX affects your distributor choice
When evaluating a distribution service, DDEX compliance is a meaningful technical indicator of quality. Most major distributors — DistroKid, TuneCore, CD Baby, Amuse, and the major label distribution arms — are DDEX-certified members and use ERN-compliant delivery pipelines. Some smaller or regional distributors operate partially compliant or bespoke delivery systems. The difference matters most when something goes wrong: a DDEX-compliant distributor can receive a standardised rejection notice from a platform and understand exactly which field caused the failure, whereas a non-compliant distributor may receive a generic error that requires manual investigation. For artists releasing at scale or managing a large catalog, working with a DDEX-compliant distributor is the baseline expectation, not a premium feature.
What happens when DDEX metadata is wrong?
DDEX standards define what fields must be present and how they must be formatted — but they cannot guarantee that the content of those fields is correct. An ERN delivery that includes an incorrectly formatted ISRC, a misspelled artist name, or an omitted songwriter credit is technically compliant with the standard but commercially incorrect. The downstream effects are the same as any metadata error: the streaming platform stores the incorrect information, royalty matching fails, and payment either goes to the wrong party or does not distribute at all. DDEX compliance is a necessary but not sufficient condition for correct distribution. The metadata itself must also be accurate, complete, and consistent with what has been registered at the PRO.
Code Group Music works with DDEX-compliant distribution pipelines as standard and audits release metadata for accuracy before delivery — not just format compliance. If you have existing releases whose metadata may have been delivered with errors, a Catalog Assessment will identify where corrections are needed. Start at codegroupmusic.co.uk/#catalog-assessment.
Published