DDEX Feed Generation Explained: ERN Delivery for Labels (2026)

DDEX feed generation is the process of turning a music release and its metadata into a standardized XML message that streaming platforms can ingest automatically. The format is DDEX’s ERN (Electronic Release Notification), and it carries everything a DSP needs to publish a release: titles, artists, ISRCs, artwork references, audio resources, territories, and deal terms. Generating that feed correctly is what gets your music delivered without manual re-entry.

DDEX (Digital Data Exchange) is the standards body that defines the XML messaging used across the digital music supply chain, between labels, distributors, DSPs, publishers, and collection societies (DDEX ERN documentation). You don’t have to be a DDEX member to implement the standard. The work, and the part most labels would rather not own, is generating valid ERN feeds and keeping them current as each DSP’s requirements drift.

This guide explains what an ERN message contains, how feed generation works step by step, the difference between ERN 3.8.2 and 4.3, and how to evaluate a provider that handles it for you, including where LabelGrid fits.

What is a DDEX ERN feed?

An ERN feed is an XML document that describes one release and how it should be made available. The core message is the NewReleaseMessage, and it bundles three things a DSP needs together: the assets, the release, and the terms.

• ResourceList holds the sound recordings, video, and images, each with identifiers (ISRC for tracks) and technical details.
• ReleaseList is the release itself: title, display artist, label name, UPC, genre, release date.
• DealList sets the commercial terms, including which territories and platforms get it, release timing, and any pre-order or pre-save windows.

Record companies and distributors send these messages to DSPs; the DSP parses the feed and publishes the release according to the deal terms (DDEX ERN documentation). A takedown, a metadata correction, or a new territory each becomes its own message in the same format. Get one required field wrong and the DSP rejects the whole feed, which is why validation matters as much as generation.

How does DDEX feed generation work?

Feed generation takes your release data and produces a DSP-ready ERN package. A typical pipeline runs like this:

1. Collect the metadata. Release and track fields, contributors, identifiers (ISRC, UPC), territories, and explicit advisories.
2. Reference the assets. Audio files transcoded to each DSP’s spec and artwork meeting size requirements (typically 3000x3000px minimum) are attached as resources.
3. Validate. The feed is checked against DDEX schema and the target DSP’s own profile before anything is sent. Missing copyright lines, malformed ISRCs, or undersized art are caught here.
4. Generate the ERN XML. The NewReleaseMessage is built with the right version (3.8.2 or 4.3) for the destination.
5. Deliver. The package is pushed to each DSP and an acknowledgment is returned.
6. Handle updates. Corrections, takedowns, and new-territory adds are sent as follow-up messages keyed to the same release.

The reason this is non-trivial: roughly 99,000 new tracks were delivered to streaming services every day in 2024 (Luminate 2024 Year-End Report). Nobody hand-codes XML at that volume. LabelGrid handles DDEX feed generation end to end, generating and validating ERN against each DSP’s current profile and delivering to all major platforms, so labels and distributors send releases rather than build and maintain a feed engine.

ERN 3.8.2 vs ERN 4.3: which version do DSPs use?

Two ERN generations are in live use today. ERN 3.8.2 is still the most widely deployed; ERN 4.3.x is what DDEX recommends for new implementations. They are not interchangeable. A feed engine has to speak whichever version each DSP expects.

The practical takeaway: many mid-size distributors stay on ERN 3.8.2 because DSPs still accept it and ERN 3-to-4 migration means restructuring the entire territorial data model. But newer capabilities, including native Dolby Atmos metadata and PartyList deduplication, only exist in ERN 4.x. A provider worth using supports both and picks the right one per destination. LabelGrid supports DDEX ERN 3.8.2, 4.3.0, 4.3.1, and 4.3.2 for delivery and import.

The stakes for getting delivery right keep climbing. Streaming reached 69.6% of global recorded music revenue in 2025, with 837 million paid subscribers (IFPI Global Music Report 2026). A rejected or malformed feed is lost visibility on the channel where most of the money now is.

What should you look for in a DDEX feed generation service?

If you’re choosing a provider to generate feeds rather than building your own, this is the checklist that matters.

How to deliver music via DDEX: a step-by-step path

1. Decide build vs buy. Maintaining an ERN engine and tracking every DSP profile change is real ongoing engineering. For most labels and distributors, using a provider is the rational call.
2. Confirm version coverage. Make sure the provider generates both ERN 3.8.2 and 4.3.x and routes the right version to each DSP.
3. Prepare clean metadata. Accurate ISRCs and UPCs, correct copyright lines, and artwork at spec. Clean input is what passes validation.
4. Validate before delivery. Run the feed through schema and per-DSP checks. Fix what’s flagged before anything ships.
5. Deliver and confirm. Push to each DSP and watch for acknowledgments. Track which platforms have accepted the release.
6. Maintain the catalog. Send corrections, new territories, and takedowns as follow-up messages, and keep an eye on feeds when DSP specs change.

LabelGrid fits this path with full DDEX feed generation across ERN 3.8.2, 4.3.0, 4.3.1, and 4.3.2, pre-delivery validation, audio transcoding, and delivery to all major DSPs. For teams that want to run it programmatically, the same pipeline is available through LabelGrid’s REST API with a sandbox and public docs. As a Spotify Preferred Provider and Merlin Network member, LabelGrid keeps feeds current as platform requirements evolve.

DDEX feed generation: the bottom line

DDEX feed generation converts a release into a standardized ERN message, the NewReleaseMessage carrying resources, release data, and deal terms, that DSPs ingest automatically. The two live versions are ERN 3.8.2 (most deployed) and 4.3.x (recommended, smaller, spatial-audio-ready), and a good provider speaks both, validates before delivery, and tracks DSP spec changes. Building your own engine is a continuous maintenance burden; for almost everyone, a provider that handles generation, validation, and delivery is the better choice. LabelGrid handles DDEX delivery for labels and distributors across all four supported ERN versions, with API access and SOBO for direct-deal catalogs.