Stores and services

Destinations

Choose stores, understand each store requirement, and track each store response after delivery.

Destination tracking should separate pre-delivery requirements from post-delivery store responses, rejections, corrections, redelivery, and takedowns.

Track destinations Store checklist Get help

8

Focused detail

Spotify

Metadata, audio, artwork, explicit status, and country availability are ready.

Status

Ready

Area

record

Show all destinationsOpen Check readinessOpen Get helpOpen

What must be ready

Each destination row opens store-specific requirements and response history.

Required

Store responses and rejections are visible after delivery.

Required

Correction, redelivery, and takedown routes stay attached to the destination state.

Required

Detailed records

Spotify

Metadata, audio, artwork, explicit status, and country availability are ready.

Ready

Apple Music

Artwork quality check must clear before delivery.

Artwork review

YouTube Music

Album and single profile requirements are ready for package review.

Ready

Next actions

Open store response historyOpen Fix destination blockersOpen Prepare packageOpen

When something goes wrong

Store rejects the delivery

Open a correction case tied to the store, reason, release, and affected assets.

Open fix path

Store becomes unavailable

Keep other stores active and show the unavailable destination as paused.

Open fix path