Loading WKS
Skip to content

For labels and distribution teams

DDEX delivery.
Built for your catalog.

Package a release as a DDEX ERN message and hand it to each DSP on its own terms. Files are staged and hashed before transfer. Delivery status follows the transfer, not a store listing going live.

ERN 4.3.2 is the recent audio addition. ERN 3.8.2 and ERN 4.3 remain supported.

Become a labelContact

01 · Catalog

Release package

  • Title, ISRC, UPC
  • Artwork and audio
  • Territories and deals

02 · DDEX

ERN message

Illustrative ERN excerpt
<DisplayGenre ApplicableTerritoryCode="Worldwide">
  <GenreText>Electronic</GenreText>
</DisplayGenre>
<Role>
  <Value>Artist</Value>
</Role>
<ContainsAI>Partly</ContainsAI>

Fragments from an audio message. Not a complete or validated file.

03 · Handoff

DSP destination

  • FTP or SFTP
  • Hash, then remote size
  • Transport status

Message formats

Three ERN versions. One catalog.

Each DSP is set to the message it receives. ERN 3.8.2 and ERN 4.3 stay available for audio and video. ERN 4.3.2 is the audio addition.

  1. ERN 3.8.2

    Electronic Release Notification 3.8.2

    Audio and video releases. This version remains supported.

  2. ERN 4.3

    Electronic Release Notification 4.3

    Audio and video releases. This version remains supported.

  3. ERN 4.3.2Recently added: New

    Electronic Release Notification 4.3.2

    Audio releases only. Adds DisplayGenre, a Role and Value structure, SoundRecording ContainsAI (None, Partly, All), and AVS 5.

How a delivery moves

Review, package, transfer, monitor.

  1. 01

    Review

    Confirm the release metadata, credits, and which DSPs should receive it.

  2. 02

    Package

    Build the ERN message in that DSP's format, including the artwork, audio, and identifiers the message needs.

  3. 03

    Transfer

    Stage every file, verify its byte count, hash it, send it, and check the size that arrived.

  4. 04

    Monitor

    Watch transport status and errors on the delivery. That status does not mean the DSP has ingested the release or put it live.

Recent

Recently added.

ERN 4.3.2 is the new audio message. AI disclosure and reviewer-approved credit handling belong to that format. Delivery inspection is the new record of a transfer. None of this replaces ERN 3.8.2 or ERN 4.3.

AI disclosure on ERN 4.3.2Recently added: New

When a DSP opts in, each audio sound recording can declare ContainsAI as None, Partly, or All. This records a human declaration. It is not an AI detector. Only ERN 4.3.2 can carry ContainsAI. A required declaration holds back only the DSP that asked for it. WKS does not guarantee that every DSP will accept AI audio.

Reviewer-approved AI credit handlingRecently added: New

For a fully AI audio track, a DSP can omit human contributor rows from the ERN 4.3.2 message. Reviewer approval is required, and the decision is kept as an audit snapshot. Catalog credits are never modified.

Delivery inspectionRecently added: New

The delivery record shows uploaded files, transport status, errors, and a package download. XML inspection is limited to super admins.

In every package

What the handoff already does.

Identifiers, media, territories, and deals

A package can carry the release title, ISRC, UPC, artwork, audio, territories, and deal terms.

Localized titles and credits

Title metadata can be localized, and artist and contributor credits map into the message.

Staged files, hashes, and remote size

Each asset is copied to local staging and checked by byte count before a connection opens. The hash is computed on that file. After upload, the remote size is checked. Transfers use FTP or SFTP.

Updates and takedowns

The same destination can receive an update or a takedown. Destination settings are configured per DSP.

Sender identity

The message sender defaults to the organization profile. A DSP can override the sender name and DPID when the store expects a different party.

Questions

Before you send.

Which ERN versions can WKS send?

Audio and video releases can be sent as ERN 3.8.2 or ERN 4.3. ERN 4.3.2 is for audio releases. Merlin is a separate exchange type, not a DDEX version. Sending an ERN message is not a DDEX certification.

What does ERN 4.3.2 change?

On audio releases it adds DisplayGenre, a Role and Value structure for contributors, SoundRecording ContainsAI values of None, Partly, or All, and AVS 5. It does not add a video message.

Does a successful delivery mean the store is live?

No. Delivery status is the transport status. It is not confirmation that a DSP ingested the release or that the store listing is live. WKS does not promise real-time receipt from every DSP.

Who can inspect the XML?

Super admins can inspect and download the XML for a delivery. The delivery record also shows uploaded files, status, errors, and a package download. The public site does not offer XML downloads.

How are AI tracks disclosed?

Disclosure is opt-in per DSP and only on ERN 4.3.2. A person declares the track human, partly AI, or fully AI. WKS does not detect AI in the audio. If a declaration is required, that requirement applies only to the DSP that asked for it. Not every DSP accepts AI audio.

Can human credits be left out of a fully AI track?

Only for a DSP configured to do so, and only after reviewer approval. The approval is stored as an audit snapshot. Catalog credits are never modified.

Send the catalog in the format the store expects.

Open a label account, or tell us which DSPs should receive the releases.

Become a labelContact