How to Start a Music Distribution Company in 2026: White-Label Infrastructure vs Building From Scratch

A music distribution company is a delivery and accounting stack with a brand on it. The domain, the logo, and the company registration matter. They are not the product. The product is a pipe that can put a release on Spotify, Apple Music, Amazon Music, YouTube Music, Deezer, TIDAL and the other major stores, and a royalty engine that turns those stores’ usage reports into statements your labels and artists can actually be paid from.

In 2026 that pipe is a buy-or-build decision. You can still negotiate store deals, implement DDEX, parse sales reports, and write sub-label accounting yourself. Or you license white-label infrastructure and put your brand, your pricing, and your clients on top of a pipe that already exists. It is the decision that determines whether you have a company.

The rest of the setup (entity, bank, contracts, support) still sits with you on either path. What changes is how much of the supply chain you own, and how you charge the people who use your service.

What infrastructure do I need to resell distribution under my own brand?

Four layers. Delivery to the stores: DDEX feeds, plus a platform-specific package where a store requires one. Catalog and metadata, keyed on ISRCs and UPCs. Royalty processing that turns store reports into splits and statements. And the branded front end your clients actually use: signup, release upload, statements and billing. A white-label provider supplies the first three. The front end is where LabelGrid’s two products differ. On Engine, the public REST API that is available now, you build it yourself. Imprint, the LabelGrid white-label portal, is a ready-made front end on your own domain; it is not generally available.

The commercial side has fixed requirements too. Reselling on LabelGrid needs an API plan (minimum Starter API, $1,668 per year, billed yearly in advance on a two-year commitment), full onboarding screening, KYC/KYB for third-party distribution, and the Advanced Services Addendum. Your labels and artists appear on the stores under their own names and credits.

What a music distribution company actually does

A distributor sits between a rightsholder and the stores. Outbound, it sends each release as a DDEX Electronic Release Notification: an XML NewReleaseMessage that describes the release, the recordings inside it, and the commercial terms under which a store may offer it. Inbound, it ingests each store’s sales and usage reports (DDEX Digital Sales Reporting where the store uses it, the store’s own format where it does not) so royalties can be matched and paid onward. DDEX, formed in 2006, publishes those message standards. You do not have to be a DDEX member to implement them. LabelGrid is not a member. It generates ERN 3.8.2, 4.3.0, 4.3.1 and 4.3.2.

The identifiers in that message are not optional decoration. An ISRC names the sound recording. A UPC (a GS1 GTIN) names the commercial release. Using a recording’s ISRC as the release identifier is the wrong layer. Get those two codes right at ingest, because they are what the stores match, and what later sales reports have to join back to.

Everything else a new distributor sells (pitching, marketing, “we will make you famous”) is optional. Delivery and accounting are not. If you cannot move a release to the stores and move money back to the right people, you do not have a distribution company. You have a website.

Three ways to get music to the stores

Pick one of these. A self-serve artist plan is not one of them: standard artist and label plans are not a licence to resell.

Route	What you build	What you buy	When it is live
Build from scratch	DSP deals, ERN/DSR, QC, royalty matching, artist statements, the UI, billing, support	Nothing from a white-label vendor. You are the vendor.	Whenever each store accepts you
Engine (LabelGrid API)	Your UI, authentication, KYC, billing, end-user support	Delivery, catalog, DDEX, royalty calculation, sandbox. Starter API is $1,668 per year, billed yearly.	Now
Imprint, the LabelGrid white-label portal	Configuration. No UI to write.	An Imprint tier on top of an active API (Engine) plan. A branded portal on your domain, plans you price, billing into your own Stripe account, payouts on schedules you set (with the payments and payouts add-on)	Not generally available

Engine is the public REST API at api.labelgrid.com/docs/api. Releases, tracks, splits, distribution status, analytics, statements, webhooks, a sandbox on every plan. Auth is a bearer token. LabelGrid drives onboarding: screening first, then the Advanced Services Addendum, then the plan is charged and API features switch on. The 7-day free trial on standard plans does not include API or sandbox access. There is no API trial.

Published Engine prices, yearly, two-year commitment, no per-release fee:

• Starter API, $1,668: up to 3,000 active tracks, 5 labels, $35,000 per month in royalties processed
• Growth API, $4,668: 10,000 tracks, 25 labels, $115,000 per month
• Scale API, $10,548: 25,000 tracks, 100 labels, $350,000 per month, dedicated account manager
• Custom API: bespoke track and royalty caps, unlimited labels

Exceeding the track cap on Starter, Growth, or Scale is a tier-upgrade conversation, not a metered overage. Support SLA on these plans is first response within 2 business days. See the API plans on the pricing page for the live figures.

Imprint is a separate product that runs on top of an active API (Engine) plan: you pay for the API plan plus an Imprint tier. Ready-made portal, your domain, your logo, your plans. The reseller’s customers pay the reseller, through the reseller’s own Stripe account connected via Stripe Connect. It is not a public self-serve checkout. If you need a dated launch, Engine is the path that exists today. Details live on the white-label portal page.

Reselling is a B2B right of Engine and Imprint customers. Minimum plan is Starter API. Full onboarding screening, mandatory KYC/KYB for third-party distribution, two-year addendum. LabelGrid’s standard artist and label plans are not a licence to resell.

Sub-label royalty accounting, and who moves the money

This is the part a new distributor underestimates, and the part a white-label vendor either gives you or leaves in your lap.

Your clients are labels (and the artists under those labels). Each needs a split on the recording, a statement, and a way to get paid. On Engine, LabelGrid calculates and records that: statements, a ledger, payment requests. The payout itself is yours. You send the money from your own accounts. Artist Payouts on API plans is the recording layer (balances, expenses, “mark this statement paid”), not a processor that moves cash to the artist. If you need LabelGrid to move the money, that is Imprint, which runs payouts on schedules you set, with statements, through the portal. Payouts are an Imprint console add-on, priced separately from the tier.

Royalty accounting is the product name for splits, statements, and the ledger. Set splits when the release is ingested. Waiting until the first statement lands is how you discover a 50/50 that should have been 70/30, after the money has already been allocated.

Can I run a branded distribution service with my own pricing?

Yes. On both LabelGrid white-label paths you decide what your labels and artists pay you. What differs is who builds the billing.

On Imprint, the people who sign up on your domain subscribe to plans you price. Their subscriptions are created on your connected Stripe account, so the money lands with you. On Engine you build that billing yourself: whatever you charge your labels is your software and your Stripe (or otherwise), not a LabelGrid checkout. Either way, the price your client pays you is not the price you pay LabelGrid. Confusing those two numbers is how reseller math goes wrong in month one.

What you keep from the stores is also not a single percentage. On API plans, when you deliver under LabelGrid’s DSP deals you retain 95% of gross on standard stores (a 5% distribution fee) and 80% on UGC and Content ID platforms (a 20% fee that replaces the 5%, it does not stack). When you bring your own store deals, SOBO delivery is available on any API plan: the store pays you directly under your agreement, and LabelGrid takes nothing from that revenue. 100% retention is that path, not LabelGrid’s own deals.

What building from scratch actually means

Licensing is not mandatory. Building is a real option if you want to own every feed. It is also a different job from “start a company.”

Each store is its own deal with its own ingest rules, and more than one ERN version is in use across the industry. DDEX’s latest published ERN is 4.3.2. A production encoder still has to speak more than one version. Apple’s main intake path is its own package format, not an ERN message. Where a store requires a platform-specific package, you build that package too, then ingest the sales reports, DSR (a flat-file format with multiple reporting profiles) from stores that use it and a custom import for those that do not, and join those rows back to ISRCs and UPCs that were correct six months ago, or were not.

You also need a sender identity in that network (a DDEX Party Identifier) and, if you aggregate many small labels, DDEX’s own guidance is that you may need a DPID per client. None of that is secret. DDEX has issued more than 4,000 implementation licences, and a DPID is normally allocated with the licence. The hard part is the store deals: each one is a separate negotiation, and each store decides whether it accepts you as a supplier.

White-label infrastructure is that layer already connected. LabelGrid is a Spotify Preferred Provider in the delivery-platform category. Catalog you send through Engine still goes out as your label name and your copyright credits, not as “distributed by LabelGrid.”

What you still run yourself

Licensing the stack does not license you out of being a company. The list below stays with you on either path.

• A legal entity and a business bank account in the jurisdiction you operate in. Local counsel, not a blog post, on the filing.
• Contracts with the labels and artists you onboard: term, territory, exclusivity, takedown, what happens to ISRCs and UPCs if they leave.
• KYC on your own users, which is mandatory on LabelGrid’s reseller path because you are doing third-party distribution: you screen your users and LabelGrid screens you.
• Support sits with you, because you own the client relationship, and a ticket about a missing ISRC is yours to answer.
• Liability. A DSP takedown, account strike, or enforcement action on content you delivered sits with you, on Engine and on Imprint alike. There is no model where that moves to LabelGrid because the UI is hosted.

You do not have to print LabelGrid on your agreements, signup, release flow, or statements. The surfaces you control stay yours. One exception, and it is a store you will be asked about: YouTube Music videos display a third-party name, because LabelGrid does not deliver to YouTube directly. Every other major store in this post is a direct LabelGrid delivery.

Frequently Asked Questions

Getting started

If the company you want to run is a distributor, start on an API plan, not a self-serve artist plan. Read the public API docs (no login). The distributor page is the product view; white-label setup and the API overview are the operational ones. LabelGrid runs screening, KYC/KYB, and the addendum before tokens exist. Build against the sandbox first.