Distributor Says Delivered but Music Is Not Live: What to Check
If your distributor marks a release as delivered but you cannot find it in a store, treat that status as a handoff checkpoint, not proof that every store page is live. Confirm the release details, search each destination directly, check the correct artist profile, and contact the distributor with the missing store and evidence you recorded.
Lead visual
Release work is a sequence
Plan
date, assets, budget
Deliver
audio, artwork, metadata
Pitch
DSPs, press, creators
Follow
signals after release
Distribution · Switch
Release sequence map
Orient
Put the work in the right order before the public date locks you in.
Check
Upload windows, pitch deadlines, asset readiness, pre-save timing, launch week, and follow-up signals.
Move
A release plan with fewer last-minute fixes and clearer momentum after launch.
Read this as a working sequence for Delivered but not live, then use the article below to make the tradeoffs concrete.
The word delivered is useful, but it is not the finish line I use for a release. I treat it as the point where the distributor has handed the release into its delivery workflow. The next job is yours: prove that the right version is visible on each destination you selected.
This is a store-status guide. The existing release timeline covers planning and date changes. The catalog transfer guide covers the migration itself. Here, the question is what to check after a dashboard says delivered and before you change anything else.
What does a delivered status prove?
My working rule is simple: delivered is a checkpoint, not a store audit. It tells you where to start looking. It does not give you a verified page for every DSP, a correct artist profile, or a clean match between the package you submitted and the catalog page you expected.
Spotify's own artist support documentation says independent artists need an approved distributor or record label to get music onto Spotify.
That first-party detail matters because the distributor is part of the handoff. It is not the same thing as Spotify or another DSP confirming the final page. You can read the source directly in Spotify for Artists' Getting music on Spotify support page.
Run the four-check store audit
Do this before changing a release date, starting a second delivery, or taking down an older version. Keep the record beside your release metadata so you can compare the same package across destinations.
- Save the distributor status, intended release date, UPC, and the ISRC for each affected recording.
- Open the destination store directly. Search the exact artist name, release title, and version title instead of relying only on the distributor dashboard.
- Check the artist profile, artwork, track order, explicit flag, and release date. A result under the wrong artist is not a clean delivery for your catalog.
- Save the exact page URL or write “not found” beside that destination. Do not turn an empty search into a guess about what happened.
The point is a small evidence table. One row per destination. One clear status per row. That gives you something concrete to send to support and a way to tell a missing page from a metadata or profile problem.
Use identifiers to prove which release you mean
Titles and artist names are easy to mistype. An ISRC is the identifier for a specific sound recording, and the code stays with that recording when its ownership or distribution changes. That is why the original code belongs in your delivery record and your support ticket.
The CONNECT Music Licensing ISRC guidance is the first-party reference for the Canadian side, while the IFPI ISRC Handbook explains the international standard. For a broader metadata check, use the existing release metadata guide.
Constructed example: one missing store
Your distributor says a single is delivered. Spotify shows the expected artist page, but another destination returns no result. Record the UPC, the track ISRC, the destination name, the intended date, the URL you searched, and a screenshot. Leave the old delivery alone if this is a transfer. That is enough context for a focused support request.
If you are replacing an existing delivery
A missing store is a reason to verify, not a reason to pull the old version immediately. The E3 transfer process says to remove the old release only after confirming the new delivery is live on the platforms you use. The practical source set for that sequence includes Ari's Take's distributor-switching guide.
Keep the difference between these two questions clear: “Has the new package been delivered?” and “Can listeners reach the correct catalog page?” The existing transfer-risk guide owns ISRC reuse, Content ID conflicts, and payment lag. This page owns the check that comes before you take action on a missing destination.
Send support an evidence packet
Contact the distributor once your record is complete. Include the release title, artist name exactly as submitted, UPC, affected ISRC, destination store, intended date, artist profile URL, delivery status, and the exact error or missing result. Ask whether that delivery is accepted by the destination, still processing, or rejected, and what action is required from you.
Keep the ticket and the response with the release record. If the answer changes the metadata, date, or delivery, update the same evidence table and check the destination again. You want a traceable release operation, not a chain of guesses made during release week.
Frequently asked questions
Does delivered mean the release is already live on Spotify?+
Not for your own release check. Use the dashboard status as a checkpoint, then confirm the track on the correct Spotify artist profile. Spotify for Artists explains that an approved distributor or record label is needed to get music onto Spotify, but the dashboard status is not a substitute for checking the destination page.
Should I change the release date while one store is missing?+
Do not move the date just because a search is empty. First record whether the release is absent, attached to the wrong artist profile, or showing different metadata. Then ask the distributor whether that destination has accepted, is still processing, or rejected the delivery. The release-timeline guide covers date planning and changes; this page owns the status check.
Should I take down the old release while the new one is missing?+
No, not if this is a distributor transfer. Keep the old delivery live until you have confirmed that the new delivery is live on the platforms you use. The transfer guide covers the full sequence, and the older account may still need to report royalties from streams that happened before removal.
Which identifiers belong in a distributor support ticket?+
Include the UPC, the ISRC for the affected recording, the exact store, the intended release date, the artist profile URL, the distributor delivery status, and a screenshot or error message. One clean evidence packet gives support a specific delivery to investigate instead of a general report that the release is missing.
What if the release appears under the wrong artist profile?+
Save the incorrect URL and the artist profile where the release should appear. Contact the distributor with both links and do not create a second delivery while the first one is being diagnosed. A duplicate can make the catalog harder to reconcile, especially during a distributor transfer.
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
Choose & switch distributor
To switch distributors without losing streams, reuse your original ISRC and UPC codes, upload the identical audio, keep the old release live for a couple of days so Spotify can link the versions, de-register YouTube Content ID before re-registering, and leave the old account open until royalties clear.
Related guide
Transfer your full catalog
Export every ISRC and UPC, de-register Content ID with your old distributor, upload to the new one using the original codes, then keep both deliveries live for 48 to 72 hours so DSPs consolidate.
Related guide
Release timeline
A delivery-state timeline for planning ahead, diagnosing stuck releases, escalating store ingestion, and changing dates without blind redelivery.
Pillar guide
Release metadata guide
A field-level metadata audit and correction-versus-takedown decision for live releases, products, recordings, credits, dates, UPCs, and ISRCs.
Switch distributors without losing streams
Get a sequenced migration checklist that preserves your ISRCs, royalty records, and release availability so nothing breaks when you move your catalog.