Distribution workflows and delivery monitoring
Monitor delivery from your SpaceMedia platform to stores, and separate your approval from store publication.
Three stages, two owners
| Stage | Owner | Means |
|---|---|---|
| Approved | You | Your team cleared it. Nothing has shipped. |
| Delivered | SpaceMedia | Store has the data and is processing. |
| Live | The store | Published, in that territory. |
Most delivery escalations are one of these mistaken for another. A release at Delivered is not stuck, and no amount of escalation moves a store's queue.
Monitoring
Watch delivery state per release and per destination. Different stores move at different speeds for the same release, so a partial rollout is normal rather than a fault.
Investigate when a destination sits far outside its usual window, when a specific store consistently fails across releases, or when delivery state contradicts what the store publicly shows.
Choosing destinations
The destination list on the release is authoritative for that release. Availability depends on content, territory, configuration, and current delivery support. Do not promise a store to a customer without checking it is offered for their release.
When a customer reports a missing store
Work through this before escalating:
- Was that destination selected on that release?
- Did the release pass your review and reach Delivered?
- Has the release date passed in that store's territory?
- Is the customer searching the right territory and the exact artist name?
- Is the artist mapping correct, so it is not live on a different artist page?
Point five catches more cases than the rest combined.
Escalating
Include the release UPC, track ISRC, destination, territory, delivery state shown, and the date checked. See Troubleshooting and escalation.