Pre-flight validation for every distributor.
Every distributor has its own rules: allowed genres, file format requirements, metadata field minimums, naming conventions, ISRC handling, lead-time windows. Most are documented across a dozen pages and a partner portal, and most labels learn them by getting a release rejected. Distributor Playbook is that rule set codified into Labelflow.
Submit and wait for the rejection is the current loop.
You upload, the release sits in review for four days, and then an email arrives saying the metadata is invalid. Not which field, not which track. You guess, fix, resubmit, and lose another four days of the lead time you had carefully planned.
Two rounds of that and the release date moves, which moves the promo, which moves the launch party. The original mistake took thirty seconds to make.
The rules, made operational.
Four pieces. The first two are the library and the check; the second two are what makes the check usable.
Every distributor's actual rules: genre allow-lists, metadata field minimums, naming conventions, ISRC handling, lead-time windows. Maintained centrally and updated as distributors change them.
Before a release ships, it is checked against your distributor's rules. Anything that would trigger a rejection is flagged with the specific rule that is failing.
Not that the metadata is invalid, but that track four's genre tag is not on this distributor's allow list, or that track two's ISRC conflicts with an earlier release. You know what to fix.
Where the fix is obvious, Labelflow proposes it. A genre mismatch comes with the closest accepted alternatives; an empty required field comes with what belongs in it.
Some of it is already working.
Live now: distributor-aware deliverable checklists, lead-time-driven due dates, and distributor-specific handling such as ISRC assignment happening at distribution rather than earlier.
In development: the full rule engine, the specific error messages and the auto-fix suggestions. Proton SoundSystem rules ship first, and more distributors follow as the library expands.
The roadmap tracks where it sits in the build order.
For labels who have lost a release date to a rejection.
The playbook starts paying back on the first rejection it prevents, which is measured in days of release-cycle time rather than in money.
Included on both plans. Distributor Playbook is core, at no add-on cost, and nothing is charged for the parts that are not built yet.