DDEX comes up every time a release is rejected, a royalty statement looks wrong, or a distributor asks for a field nobody at the label has heard of. It sounds like a technical standard for engineers. In practice it is a shared vocabulary for the whole music industry, and a label that organizes its data around that vocabulary stops fighting with its distributor.
What DDEX actually is
DDEX (Digital Data Exchange) is a standards body, and the name is used loosely for the message formats it publishes. The idea is simple: instead of every label, distributor and streaming platform inventing its own spreadsheet layout, everyone exchanges data in agreed structures with agreed meanings. A ‘release’, a ‘resource’ (a sound recording or video), a ‘party’ (a person or company) and a ‘deal’ (who may sell what, where, when) mean the same thing to every participant.
You will most often hear about ERN, the Electronic Release Notification that carries a release and its metadata to a platform, and DSR, the Digital Sales Reporting format that carries usage and revenue back. There are others, such as RIN for studio and recording information, but ERN and DSR are the ones that touch a label's day-to-day work.
The identifiers that hold everything together
DDEX messages are built on identifiers, and identifiers are where labels most often fall short. Every recording needs an ISRC. Every release needs a UPC or EAN. People and companies should carry ISNI or IPI numbers where they exist, and every sender in the chain has a DDEX Party ID. When identifiers are missing or reused, systems cannot match your data to the rest of the world's, and the result is rejected deliveries or misattributed royalties.
- ISRC: one per recording, never reused for a different mix or edit.
- UPC/EAN: one per release, including each single and each format.
- IPI: identifies songwriters and publishers to collecting societies.
- ISNI: identifies people and organizations across the industry.
- DPID: the DDEX Party ID of the sender, usually your distributor or label.
Why distributors reject deliveries
Rejections rarely come from the audio. They come from the data around it: a featured artist listed as a primary artist on one track and a contributor on another, a writer with no role, a territory list that contradicts the deal, a release date in the past, or an explicit flag missing on a track with explicit lyrics. Each of these is trivial to fix and expensive to discover after delivery, because the release goes back into a queue.
The common thread is inconsistency. Data that was entered by different people, in different tools, at different times, does not agree with itself. DDEX simply makes that disagreement visible.
Map your internal data to DDEX concepts
The practical move is to structure your own catalog the way DDEX thinks. Keep one record per release with its identifiers and dates. Keep one record per recording with its ISRC, duration and contributors. Keep one profile per party, whether artist, writer, producer or publisher, with their identifiers and default roles. Attach deal information (territories, start dates, formats) to the release rather than to a note in an email.
When internal data already respects these shapes, delivery becomes an export. When it does not, every delivery is a manual mapping exercise that someone repeats, slightly differently, for every release.
A practical checklist
Before any release moves toward delivery, run through the fields that cause the most trouble.
- Every track has a unique ISRC and the release has a UPC.
- Primary artists, featured artists and contributors are labelled consistently on every track.
- Every writer has a role, a split and, where possible, an IPI and publisher.
- Explicit flags, language and genre are set per track, not assumed.
- Territories, release date and pre-order date match the signed deal.
- ℗ and © lines carry the right year and owner.
Common mistakes worth avoiding
Reusing an ISRC for a remaster or radio edit, treating a group as one party instead of a group with members, storing splits only in a PDF contract, and keeping territory rules in a spreadsheet nobody updates after renegotiation. Each of these creates a mismatch between what you deliver and what you are entitled to, and mismatches cost money for years.