Skip to content

From master to store, and the money back.

Every release takes the same checked path: specs, metadata and copyright before review, DDEX delivery to each store, and sales reports matched back to the recording.

Apply now

Capabilities

What happens on the way.

Checked before it leaves

Audio specs, artwork and metadata checked on submit.

DDEX to every store

ERN 4.3 messages, direct or via Merlin, store by store.

Status back from stores

Each store's response on the release, live or not.

How it works

One path for every release.

  1. 1

    Ingest

    Builder, XLSX or API

    You

  2. 2

    Check

    Specs and copyright

    Automated

  3. 3

    Review

    Approve or fix

    HILLS team

  4. 4

    Deliver

    DDEX ERN

    Automated

  5. 5

    Report

    DSR matched

    HILLS finance

FAQ

Common questions.

Which standards do you use?

DDEX ERN 4.3 for releases and DDEX DSR for sales reports, with ISRC and UPC/EAN identifiers, and ISWC and CWR for compositions.

How do you deliver to stores?

Under HILLS's direct store deals, or through Merlin deals where you have them, over each store's own delivery channel.

What happens if a store rejects a release?

The store's response comes back to the release, our team fixes or asks you, and the release is redelivered.

Can we send releases from our own systems?

Yes, through the HILLS API in early access, or in bulk with an XLSX upload.

Apply to distribute with HILLS.

Submit an application — we get back to you within 1–3 business days to discuss terms.

Apply now Explore services