Generation is only the middle of the audio workflow. A usable BGM service has to receive the generated master, store it reliably, create a web-friendly MP3, normalize loudness enough for comfortable playback, attach metadata, and publish a page. Users judge the whole chain, not only the model.
Volume consistency is especially important in public libraries. If one track is quiet and the next is loud, the player feels unprofessional. Basic normalization does not have to destroy the mix. It simply makes previews easier to compare and playlists easier to hear.
File format strategy also matters. A FLAC master is useful for future premium downloads and archival quality. MP3 preview is useful for fast web playback. The user should not wait for every possible format before hearing something, but the system should keep the master when higher-quality use is needed.
Titles and descriptions are part of post-processing too. A title that repeats the full prompt becomes unreadable. A title that is too generic becomes impossible to browse. The prompt engine should produce short, distinct names and metadata that explain the mood without exposing internal clutter.
When the workflow is clean, the user experiences one simple thing: the track is ready. Behind that simplicity is the operational product: generation, conversion, storage, metadata, license, and playback all working together.