What Actually Happens When You Upload a Track to DistroKid, TuneCore, or CD Baby

You drag a WAV into a browser window and click Submit. Three weeks later your track appears on streaming platforms and you tell yourself "distribution just works now." It does not "just work." Between that click and a playlist load, a pipeline of automated checks, metadata registration, and delivery queuing runs on your behalf. Here is what actually happens.

The Ingestion Phase

Your file lands on the distributor's server and immediately runs through a validation pipeline. Sample rate, bit depth, loudness, clipping detection, file integrity. The check is shallow — most distributors flag true-peak overs and nothing else. They want your content, not perfection. A track that passes validation gets transcoded to the delivery formats each platform expects: AAC for Apple, Ogg Vorbis for Spotify, FLAC for Tidal, MP3 for stores that still need it. The original WAV stays on the distributor's side.

The Metadata Layer

This is where the pipeline splits from what users think it does. Your track title, artist name, featured performers, ISRC code, and UPC are not just display fields. They are registry entries that connect your release to royalty collection databases.

The ISRC (International Standard Recording Code) is the unique identifier that tells every PRO, collection society, and streaming platform which recording is playing. If you did not provide one, the distributor generates it. If you re-upload a corrected version later, the ISRC must stay the same or the new version starts with zero play history.

The UPC (barcode) identifies the release as a product. TuneCore assigns one. DistroKid does not — your release gets a DistroKid-specific identifier instead, which saves you money but limits your ability to track physical or broadcast sales outside their ecosystem.

Both codes get registered with RightsFlow (now part of Free Haven) or similar metadata aggregators that feed the royalty system. A missing or incorrect ISRC means your micro-pennies go to a holding account or, worse, to someone else's ISRC match.

Store Delivery and Timing

Once validated, the release enters a delivery queue. Distributors do not push to stores in real time. They batch deliveries on a schedule — typically every 24-48 hours for major platforms.

Spotify: 2-5 business days to appear, up to 2 more for metadata indexing (artist page updates, genre tags). Apple Music: similar timeline but requires a separate audio delivery pipeline for Spatial Audio if you submitted an Atmos mix. Amazon Music and YouTube Music: faster, often 24 hours. TikTok/SoundCloud: variable and inconsistent.

The "three weeks early" rule exists because of this staggered window. Submit on Monday, the track lands on Spotify on Wednesday, Apple on Thursday, Amazon on Friday. Your release date is not when you hit Submit. It is when the slowest platform catches up.

Royalty Collection and Reporting

After delivery, the distributor tracks streams and purchases through platform reporting APIs. Each platform reports on a different cadence. Spotify reports weekly. Apple reports monthly. Tidal reports quarterly. The distributor aggregates these into a single dashboard that shows you a blended number. The latency between a stream happening and you seeing it in your dashboard ranges from 3 days (Spotify) to 60+ days (some smaller platforms).

The distributor takes its cut before passing the remainder to you. DistroKid charges an annual flat fee. TuneCore charges per-release and per-platform and takes no percentage. CD Baby takes a 15-20% royalty cut plus a setup fee. Each model shifts the incentive: flat-fee distributors want volume, per-release distributors want quality, percentage-based distributors want longevity.

Bottom Line

Uploading a track is not the end of a creation process. It is the start of a metadata-administration process that determines whether you get paid, how fast, and for what. The file is the easy part. The identifiers are the actual product.

One Thing to Try This Week

Pull the ISRC off one of your released tracks from your distributor's dashboard. Paste it into a search on the ISRC search engine (isrc.soundexchange.com or similar). If it shows up correctly attributed, your metadata pipeline is clean. If it does not, you just found a leak.