— Aperçu de CONTENU (rythme & densité). Le design final = blocks shadcnblocks. Guide éditorial (pas une garantie de conformité). — ← toutes les pages
Inside Reprtoir your metadata stays flexible. Delivery to DSPs doesn't. This is how Reprtoir structures your data into the fields DSPs expect — so releases pass validation instead of bouncing, and go live faster.
Most rejected releases fail on the basics: a featuring artist buried in the title, a version in the wrong place, a producer credited as a main artist. Reprtoir gives every one of these its own dedicated field — main artists, featured artists, remixer, composers, authors, producer, and the classical roles — so the data maps straight onto each DSP's schema.
Where featuring, versions and subtitles belong — and what never goes in a title.
Main vs featured, remixer, producer and the credits DSPs read — each in its own field.
Title case, sentence case and non-Latin scripts — the right convention for 15+ languages.
Work and movement hierarchy, conductor, orchestra and soloist roles — done properly.
What triggers a rejection — promo words, emojis, non-compliant artwork — and how to avoid it.
Correct and incorrect side by side, so the whole team formats the same way.
Every rejected feed is a delay between finishing a release and earning from it. By preparing your data in structured, standards-aligned formats, Reprtoir cuts the back-and-forth with DSPs — fewer bounces, faster go-live, and a catalog that stays searchable and payable downstream. See Metadata Enrichment →
Structured to the industry's standards, ready for every DSP — so your releases clear the first time.