What Is Export Flow for Music Delivery?

Direct answer: Export Flow is the delivery side of Kora — per-contact delivery profiles, filename templates and folder recipes, required-deliverable and required-metadata checklists, and a preflight that runs before anything leaves your machine. Its audio-processing engine — conversion, loudness analysis, metadata embedding and MP3 rendering — is disabled in shipping builds, so today it organises and validates files rather than processing them.

What actually happens between “render” and “delivered”?

You render the files yourself, from your DAW, in the format the client asked for. Export Flow takes it from there.

The recipient’s delivery profile carries the spec. Four ship built in, you can create your own, and profiles map to a contact — so the client determines the naming convention, folder structure, required deliverables and required metadata rather than you remembering which library wants what. Naming templates and folder recipes render a live preview, so you see the filenames and folder tree before a single file is written.

Preflight then checks the set: are the required deliverables present, are the required metadata fields supplied, do any two files resolve to the same output path, do any filenames contain characters that will break on the receiving end. After that comes sync-readiness scoring, delivery preferences, an email draft, an assisted portal open, and Mark Delivered.

None of this is plan-gated. Export Flow runs on Local, Creator and Pro alike.

Which tokens, checklists and formats does it ship with?


Default filename template	`{album}_{track}_{mixType}_{composer}`
Default folder recipe	`Deliverables/{album}/{date}/{intent}/{mixTypeFolder}`
Deliverable types you can require	Full Mix · Alt Mix · Instrumental · No Drums · TV Mix · Stems · Other
Metadata fields you can require	Album · Composer · Publisher · PRO/Copyright · Artist · Label · Genre · Keywords · Mood · Year · Contact Email · ISRC · UPC · Description
Preflight catches	Duplicate output paths · illegal characters
Accepted inputs	`.wav` · `.aif` / `.aiff` · `.mp3` · `.flac` · `.m4a` — no AAC
Profile output targets	WAV 24/48 · WAV 24/44.1 · WAV 16/44.1 · MP3 320

The template tokens available to filenames and folder recipes are {album} {track} {mixType} {composer} {publisher} {artist} {label} {genre} {mood} {keywords} {year} {isrc} {upc} {contactEmail} {bpm} {key} {version} {date} {intent}, plus {mixTypeFolder} for folder structure. Key Shift Pro uses its own default, {publisher}_{album}_{composer}_{title}_{key}_{version}.

What is switched off, and what does that block?

Shipping builds go out without FFmpeg, so the audio-processing half of Export Flow is disabled. Four capabilities are off:

Format conversion
Loudness analysis
Metadata embedding
MP3 rendering

In the app they sit behind a notice reading “Enhanced Export Flow is coming soon.”

The knock-on effects are not obvious from that notice, so they are worth stating:

The Deliverable Ledger stays empty on a fresh install. The only thing that creates a version record is the disabled export path.
Review links are blocked twice over — they need a version record and MP3 normalisation.
Dropbox and Google Drive uploads are built but unreachable. Both integrations work; both wait on a version record that nothing currently produces.
The metadata read path is disabled too. There is no tag library in the build, and the Audio Library metadata editor writes to a local override map, not into your files.

What Export Flow will not do, engine aside

Some limits are structural rather than temporary:

No batch multi-library delivery. One project, one destination, one spec per run. Delivering the same album to three libraries is three runs.
No version history. A delivered file records its filename, output path, and optionally size, SHA-256 hash and mix type. There is no version number, revision index or per-file date.
The deliveries list shows the 10 most recent, and only in the Advanced workspace.
No BWF or iXML. Broadcast wave and iXML chunks are not implemented.
macOS 13 or later only. There is no web version and no Windows build.

Frequently asked

Does Export Flow require a paid tier?

No. Export Flow is available on Local, Creator and Pro. If you have seen it listed as a higher-tier feature, that was wrong and this page is the correction.

Why is my Deliverable Ledger empty?

Because the only producer of a version record is the export path that is currently disabled. The ledger is not broken and there is nothing to fix on your side — it fills once the processing engine is enabled.

Can Export Flow convert my file to the format a client asked for?

Not yet. Render the required format from your DAW; Export Flow handles naming, folder structure and validation around it, with the profile stating the target spec.

Can I deliver one album to several libraries in a single run?

No. Each run is one project to one destination against one spec. Per-contact profiles mean every run applies the right naming and checklist automatically, but they remain separate runs.

Does Export Flow write ISRC, composer and publisher into the file?

Not yet. It checks that the fields a client requires have been supplied and flags what is missing; writing tags into the audio file is part of the disabled engine.

What Is Export Flow for Music Delivery?