Record-Label Distribution: Choose and Control a Provider
Choose record-label distribution by matching catalogue volume, territories, stores, formats, metadata support, delivery control, reporting, royalty accounting, advances, fees, revenue share, term, exclusivity, reserves, support, fraud response, takedowns, and exit to the label's operating capacity. Verify catalogue authority, owners, payees, tax data, UPCs, ISRCs, artist IDs, and approvals before onboarding. An ISRC identifies a recording; it does not prove ownership.
Lead visual
Start a record label map
Context
Business · Label
What this guide is helping you understand.
Decision
Record-label distribution
The practical choice or setup step to get right.
Next
Action
What to check before you move the release forward.
Business · Label
Failure path map
signal
Read the exact rejection before changing artwork that may already be sound.
What to measure
Validator text, exported file properties, visible claims, third-party material, and the distributor's current rule.
A broad redesign can preserve the real failure while creating new file, credit, or rights problems.
The point of Record-label distribution is not more activity. It is a clearer loop from signal to next action.
Key takeaways
- Choose a provider from catalogue jobs, reporting needs, economics, support, control, and exit.
- Verify label entity, authority, owners, payees, tax, bank, and account recovery before intake.
- Preserve UPC, ISRC, artist ID, delivery ID, acknowledgement, rejection, correction, and store evidence.
- Treat metadata validation and rights approval as label controls, not distributor cleanup.
- Export the complete catalogue and statement history before notice, takedown, or migration.
Which distribution route fits the label's operating model?
Label distribution decision
Seven choices before provider onboarding
Catalogue job
Use when
Artists, releases, cadence, territories, stores, formats, physical needs, neighbouring rights, sync, and service gaps are quantified.
Avoid when
The label is shopping for prestige without a workload model.
Authority
Use when
Every recording, territory, term, owner, licence, composition, sample, contributor, payee, and release approval is traceable.
Avoid when
The label expects provider acceptance to validate rights.
Delivery
Use when
Audio, artwork, metadata, identifiers, artist IDs, pricing, dates, territories, credits, and correction paths meet documented specs.
Avoid when
Files and fields are assembled in the upload form.
Economics
Use when
Fee, share, advance, recoupment, minimum, reserve, currency, tax, statement, payment, audit, and post-term collection are modeled.
Avoid when
A headline percentage is compared without the revenue base or services.
Operations
Use when
Onboarding, roles, support, rejections, fraud, claims, takedowns, urgent changes, security, recovery, and service levels have owners.
Avoid when
One founder's personal login is the complete supply chain.
Data
Use when
Transaction detail, territories, services, recordings, currencies, adjustments, exports, APIs, identifiers, and historical retention fit accounting.
Avoid when
A dashboard total is assumed sufficient for artist statements.
Exit
Use when
Notice, exclusivity, overlap, redelivery, identifiers, takedown, reserves, statements, assets, data export, support, and final handoff are workable.
Avoid when
The catalogue cannot leave without losing essential records or control.
Which distribution record proves each supply-chain state?
| Required record | Failure prevented | |
|---|---|---|
| Authority | Artist agreement, master schedule, licence or ownership, territory, term, approvals, samples, and contributors | Delivery exceeds the label's rights or release duty |
| Identifier | UPC and ISRC assignment source, recording/version, audio checksum, year, owner, provider, and prior code | Duplicate codes, changed recordings, or ownership inferred from identifiers |
| Package | Approved audio, artwork, metadata, credits, P and C lines, artist IDs, pricing, dates, territories, and explicit flags | Store display diverges from contract and approved assets |
| Delivery | Provider release ID, submission timestamp, recipients, acknowledgement, validation, rejection, correction, and accepted version | No trace between label package and DSP state |
| Live | Store release and artist IDs, URLs, territories, pricing, credits, availability, profile mapping, and verification date | A delivery acknowledgement is mistaken for a correct public release |
| Statement | Provider file, period, service, territory, recording, units, gross, fee, tax, currency, adjustment, net, and import batch | Money cannot be joined to artist contract accounting |
| Exit | Notice, export, open issues, reserves, post-term receipts, redelivery, overlap, takedown, final statements, and account closure | Catalogue and evidence disappear with provider access |
Do not create a new ISRC for an unchanged recording
A provider or label change does not make a new recording. Preserve the original identifier and identical audio when the same recording is redelivered, and document any true remix, edit, remaster, or replacement as a separate version decision.
compare provider economics against the label's actual catalogue
Which sources govern record-label distribution and identifiers?
Frequently asked questions
How does an independent record label distribute music?+
Most independent labels use a distributor or label-services provider that sends release and availability data to DSPs, receives reports and money, and supports corrections. The label supplies authority, audio, artwork, metadata, contributors, identifiers, dates, territories, pricing, and deal instructions. DDEX ERN describes this release-delivery relationship. The label must still validate inputs, preserve acknowledgements and store IDs, reconcile statements, and plan provider exit.
Should a small label use an aggregator or label distributor?+
Choose from actual needs, not the prestige of a selective provider. Compare catalogue size and cadence, territories, stores, physical and neighbouring-rights support, metadata, artist-ID mapping, reporting detail, currencies, payment, support, fraud handling, advances, fees, revenue share, term, exclusivity, minimums, reserves, audit, takedowns, and export. A simple aggregator can fit a disciplined small catalogue better than services the label cannot use or measure.
Who assigns ISRCs for a record label?+
The International ISRC authority says the legal producer of the recording normally assigns the ISRC, either through its registrant code or an authorized manager such as a distributor. Document who assigned each code, the recording and version, year, owner, audio checksum, and provider. ISRC does not identify the copyright owner, and an unchanged recording should not receive a new code merely because the label or distributor changes.
What metadata does a label need before distribution?+
Control release and track titles, versions, primary and featured artists, roles, contributors, writers, publishers, splits, copyright owners, P and C lines, label display, UPC, ISRCs, languages, genres, explicit flags, territories, dates, pricing, lyrics where applicable, artwork, audio, credits, samples, rights, and artist IDs. Validate against contracts and assets, then preserve the submitted package, acknowledgements, corrections, and live store results.
How should a label switch distributors?+
Export agreements, catalogue, assets, metadata, UPCs, ISRCs, artist and release IDs, statements, analytics, payment records, open support issues, store statuses, and takedown restrictions before notice. Map term, exclusivity, post-term collection, reserves, migration help, identifiers, redelivery, overlap, takedown, and final accounting. Keep identical recordings and original ISRCs where applicable, but never promise track linking, playlist continuity, or identical store outcomes.
Get better release strategy in your inbox
Release planning checklists, royalty explainers, and artist strategy notes from Velveteen. No daily noise.
Was this useful? Send a signal or flag a correction.
Keep reading
Pillar guide
Start an independent record label
A nine-link label operating chain joining thesis, ownership, capital, rights, assets, supply, campaigns, transaction-level accounting, and catalogue operations.
Related guide
Record-label release calendar
An eight-gate multi-artist release workflow and seven-lane capacity board across rights, assets, supply, campaigns, people, cash, launch support, and post-release duties.
Pillar guide
Label Services vs DIY Distribution
A distribution deal delivers your music to streaming services for a flat fee, and you keep 100% of your masters and 86 to 100% of royalties.
See which distributor model actually fits you
Enter your release volume and expected streams to compare flat-fee, commission, and label-services models against your own numbers, not a pricing page.