— Aperçu de CONTENU (rythme & densité). Le design final = blocks shadcnblocks. Catégorie naissante : angle onboarding/no-lock-in, cas FUGA. — ← toutes les pages
Moving to Reprtoir shouldn't mean re-uploading years of releases by hand. Where a partner can deliver your catalog to us over the same standards we use everywhere else, you start with your catalog already in place — and keep the distribution deals you already have.
FUGA delivers the catalog of your shared clients into Reprtoir over DDEX. Instead of exporting and re-importing release by release, your catalog is delivered to us the way releases are delivered anywhere — automatically, in a format we already speak. You move your operations to Reprtoir without giving up the distribution relationship you have with FUGA. It's the first partner we ingest from this way; the standard is what lets more follow.
The catalog is what keeps teams stuck on a tool they've outgrown — nobody wants to re-enter it. Catalog import is how you say yes to Reprtoir without that cost.
Start inside Reprtoir with your releases, metadata and identifiers already there — ready to work, not waiting to be typed in.
Coming in doesn't force you to drop your distributor. You keep the commercial relationships you built; only your operations move.
Because it rides DDEX, importing a catalog isn't a custom project every time — it's the same language delivery already runs on.
Where your catalog can be delivered to us — starting with FUGA over DDEX — onboarding means arriving with your work already in place, and keeping the deals you already have.