DDEX is the standardised set of file formats and message specs that lets one music release move cleanly from a distributor to every digital service provider in the world.
If you have ever wondered why your release went live on Spotify but not on Boomplay, or why the producer credit you swore you typed in never showed up on Apple Music, the answer is almost always DDEX. It is the pipe. When the pipe is built wrong, the water comes out somewhere else.
This guide is for artists, label owners, and distribution ops people anywhere in the world who keep running into “delivery failed” errors and want to understand what they are actually fighting. We will include an African-market section because the gaps there are sharper than the generic guides admit, but the standard itself is global and the rules are the same on every continent.
What is DDEX?
DDEX means Digital Data Exchange. It is a not-for-profit standards body, founded in 2006, made up of record labels, music publishers, distributors, DSPs, and collective management organisations. They write the technical standards for how music metadata moves between companies.
The standards themselves are XML schemas with names like ERN (Electronic Release Notification), DSR (Digital Sales Reporting), MWN (Musical Work Notification), and RDR (Recording Data and Rights). When someone says “we deliver via DDEX,” they almost always mean ERN — that is the message that says “here is a new release, here is the audio, here are the credits, here is when it goes live.”
The current general-availability version is ERN 4.3. ERN 4.2 is still widely deployed across the distributor ecosystem and both versions remain in production at most DSPs. The difference matters and we will get to it.
Why does DDEX exist?
Before DDEX, every DSP had its own ingestion spec. A distributor delivering to ten DSPs maintained ten different file formats, ten different metadata templates, and ten different ways of saying “this song is explicit.” If you were a label trying to get on iTunes, Spotify, Deezer, and a regional service in 2008, you needed a person whose entire job was reformatting CSVs.
DDEX collapsed that into one spec. Now a distributor builds against ERN once, and any DSP that supports ERN can accept the delivery. That is the whole game. It is plumbing, but it is the plumbing that makes the modern distribution industry economically possible.
How does DDEX work in practice?
A DDEX delivery is a folder. Inside that folder there is one XML file (the ERN message) and a set of audio and image assets. The XML carries everything the DSP needs to know:
- Release identifiers — a UPC for the release, an ISRC for each track.
- Metadata — title, artist, contributors, language, genre, explicit flag, original release date, label name.
- Rights — territory by territory, who has the right to stream, sell, or include in a playlist.
- Files — pointers to the audio (WAV preferred) and the cover art (3000×3000 JPG, sRGB, no rounded corners).
- Commercial models — is this stream-only, download-allowed, available on which tier, ad-supported or premium only.
The distributor ships the folder to the DSP via SFTP or a private API. The DSP ingests, validates, and either accepts or rejects with an error code. If accepted, your track is queued for the release date you specified.
When royalties flow back, they come on a DDEX message too — DSR (Digital Sales Report) files, usually monthly, that say “this ISRC played this many times in this country at this price.” Your distributor parses those, applies splits, and pays out.
What DDEX means in practice for indie artists and labels
This is where the generic guides stop and the real conversation starts.
1. Your distributor’s DDEX support determines your DSP coverage. If your distributor only delivers ERN 4.1 (still common at the bottom end of the market), you are silently locked out of newer DSP features. Some regional DSPs have started rejecting deliveries below 4.2 entirely. Ask your distributor in writing which ERN version they ship.
2. The producer credit problem is a DDEX problem everywhere. Releases across genres routinely under-credit producers because the distributor’s intake form does not map producer names into the right DDEX Contributor role. The credit shows up on the release page but never makes it into the underlying ERN. When sync agencies later try to clear the track, the producer’s name is not in the database. They lose the fee. This bites Afrobeats and Amapiano harder than most because producer-as-writer is the norm in those scenes.
3. Regional DSPs accept DDEX, but with quirks. Boomplay’s ingestion is stricter on territory rights for African countries than Spotify is — list every African territory explicitly or you will get a partial release. Audiomack is looser on rights but stricter on explicit-flag accuracy. Anghami requires Arabic-language transliteration on certain fields. JioSaavn cares about regional-language tags. The base spec is the same; the per-DSP edge cases are not.
4. DSR reports are the source of truth for your payout dispute. If you think a DSP underpaid you in Q4, the DSR file from that DSP is the document. Ask your distributor for the raw DSR for the period. If they cannot produce it, that is a red flag.
Common DDEX mistakes and gotchas
- Wrong ERN version sent to a DSP that requires a newer one. Silent reject, no email, release just never appears. Always confirm acceptance, not just submission.
- ISRC reused across two distributors. DDEX assumes one ISRC equals one master recording. If you switch distributors and the new one re-issues an ISRC, both deliveries collide at the DSP and one gets quarantined.
- Cover art with embedded ICC profile other than sRGB. Apple Music rejects on this and the error message is cryptic (“asset validation failed”). Convert to sRGB before upload.
- Featured artists in the title field instead of the contributor field. “Asake (feat. Olamide)” stuffed into the title means Olamide never gets the algorithmic credit on Spotify for Artists.
- Territory excluded by default. Some distributors default to “world excluding {list}.” If South Africa is silently on the exclusion list, you will not appear on Spotify ZA no matter how many times you check.
- Date confusion. DDEX uses ISO 8601 with timezone. A 2026-05-13 release with no timezone defaults to UTC, which means it goes live in Lagos at 1 a.m., not midnight.
How InterSpace Distribution handles this
InterSpace Distribution is a global distributor in the same category as DistroKid, TuneCore, ONErpm, Symphonic, EMPIRE, and Believe. We ship DDEX ERN 4.3 natively to 150+ DSPs, including the regional platforms that majors-focused distributors deprioritise — Boomplay, Audiomack, Anghami, Mdundo, JioSaavn, KKBOX, Zing, NetEase. Every delivery is validated against the DSP’s spec before transmission, contributor roles map cleanly from the upload form into the ERN, and DSR files are available to artists on request. Get started at cms.interspacemusic.com/signup.