DDEX feeds, in and out, to the standard

Send and receive releases as DDEX messages instead of spreadsheets and shared folders. Aevora builds ERN feeds for delivery, ingests the ones you already produce, and validates every message before it moves.

Messages
ERN for releases, DSR for sales reports
Transport
SFTP or cloud storage batches
Validation
Schema and store rules before delivery

A release, as the stores read it

Every delivery is an ERN message: who is sending it, the sound recordings, the release, and the deal terms for each territory. Aevora generates it from your catalog, so the metadata you edit is the metadata that ships.

  • New releases, updates and takedowns all travel as messages
  • Each message is validated before it leaves
  • Store acknowledgements are matched back to the release

Night Drive: messaggio di uscita

Dati di esempio

NewReleaseMessageern/43

ReleaseList

2 nomi diversi da 3.8.2

ReleaseId/ICPN
198004417319
Non ancora controllato
ReleaseReference
R0
Non ancora controllato
ReleaseType
Single
Non ancora controllato
DisplayTitleText
Night Drive
Non ancora controllato
ResourceGroup
A1, A2
Non ancora controllato
PLine/PLineText
2026 Northfield Audio
Non ancora controllato
CLine/CLineText
non impostato
Non ancora controllato

Convalida rispetto a ERN 4.3

What the feed handles

Inbound ingestion
Already producing ERN? Point your feed at Aevora and releases appear in your catalog, ready to deliver onward.
Updates and takedowns
Metadata changes and removals travel as messages too, so stores stay in step with your catalog.
Acknowledgements
A store response is tied to the message that caused it, so a rejection lands on the right release.
Batching
Deliveries are grouped into batches per store, with manifest files where a store asks for them.
Sales reports
Sales and usage reports that arrive as DSR files are parsed straight into royalty accounting.
Validation
Messages are checked against the schema and against each store’s own rules before they are sent.

The feed at a glance

Stores differ in the message version and transport they accept. Aevora produces what each destination asks for.

Release messages
ERN: new release, update and takedown
Sales reporting
DSR flat-file reports
Identifiers
ISRC, UPC or EAN, and your own catalog numbers
Transport
SFTP and cloud storage
Audio resources
WAV and FLAC, referenced from the message

Questions about DDEX

A set of standard message formats the music industry uses to exchange release metadata, sales reports and rights information between labels, distributors and stores.

No. You edit releases in the catalog and Aevora writes the messages. The feed is there for teams that already work with DDEX.

Yes. Inbound feeds are ingested into your catalog and can then be delivered to any connected store.

Replace the spreadsheet with a feed