In this lesson you will learn: Reading delivery and store status (pending, live, issue). Territories, takedowns, and re-delivery without panic. What “propagation time” means in the real world.
**Distribution** is the pipe; **stores** are the endpoints. In **LUCY**, use **release and delivery status** in the app to see whether your package is accepted, processing, or live—and where to look first when a platform lags. Public integration docs describe the same product as **450+** storefront destinations on the marketing site; your screen is the source of truth for **your** territories and go-live.
Distinguish **ingestion** (distributor → DSP) from **storefront display**—some DSPs surface new releases hours after ingestion.. Note **territory** and **explicit/clean** flags before you announce; fixes often require **re-delivery** from the app.. Keep a **change log** when you re-cut audio or art—your future self thanks you during audits and support tickets.
Store propagation varies by DSP and region; industry comms teams avoid **street-date promises** until key markets show green.. Takedowns and policy strikes follow **contract + platform rules**—your app status is the first screen, not the last word with legal.