Prepare and publish a final delivery

Before you start

You need a project connected to a client, at least one active project contact, and the files you want to deliver. A Pro or Studio plan with project management access is required to add files or publish a package. Viewers can inspect a delivery, but they cannot edit, publish, or unpublish it.

Approval belongs to a specific version. Check the approval and version number in Review & Delivery before you start. If the project has no client, the delivery editor shows Connect this project to a client before preparing final delivery.

1. Open the delivery editor

1. From Projects, open the project.
2. Open Review & Delivery.
3. Select the track you want to deliver.
4. For an approved track, select Prepare delivery.

The right panel opens with the title Prepare delivery and a Draft badge. A track that is already in a published package uses the action Update Final Delivery. Its panel title is Update delivery and its badge is Published.

2. Check the files and versions

For a new package, the Package section starts with approved versions selected by default. An existing delivery reopens its saved selection. Review every row, because the package can contain more than the track you used to open the editor.

• Open a row to see its version, stems, and spatial files.
• Use the row menu and choose Remove from package when a selected file should not ship.
• If the package has no files, add one or select an approved version in Version choices. The editor shows No files in this delivery until you do.

Open Version choices to review the source for each project file. Its description reads Approved versions are selected by default. A row without a current approval is marked Approval required.

Include a different version deliberately

If you need a version other than the approved one, open Version choices and select Include unapproved versions. The button changes to Use approved versions. Select the candidate, then choose a version from Version for [file]. The approved option is labeled (Approved).

Mixhaus records when a selected version differs from the approved source. The editor does not ask you to type a reason. If a project file has an approved version, you can save a deliberate version override. A project file with no approved source can be saved in a draft, but publishing is blocked until it has a current client approval.

3. Set the package name and order

Open Advanced to show package-only files and package structure controls.

1. Under Package structure, edit Downloaded package name if the default does not fit the project.
2. In Package contents, select New folder to add a folder. Rename folders, choose a parent folder, and add subfolders as needed.
3. Use each file's folder selector, filename field, drag handle, or move controls to set its location and order.
4. Keep the package root for files that should sit at the top level. Custom folder and filename choices are carried into the downloaded ZIP.

When no custom package manifest is present, Mixhaus uses an automatic layout for attached stems and other entries. In the current editor, new entries appear under Package root until you assign a folder, so check Package contents before publishing. Custom folder settings take precedence over the fallback layout. See Add stems and extra files to a delivery for upload and stem-specific steps.

4. Choose client access

The Client access card controls the final delivery, not the earlier review link.

• Playback with the description Listen before downloading. lets the client play supported audio in the portal.
• Downloads with the description Individual files and ZIP. controls download access. The final delivery portal currently presents one Download package action for the ZIP.
• Delivery note adds a message below the final delivery in the portal.

Check the audience line at the bottom of the card. It should read For [contact name]. If it reads Add an active project contact before publishing., add an active contact to the project and reload the editor.

5. Publish the package

1. Wait for any package-only files to reach Ready. The primary action remains Checking files… while an additional file is being checked.
2. Recheck the package rows, version numbers, folder name, and client access switches.
3. Select Publish delivery.

Mixhaus saves the delivery, marks it available to the active project contacts, and queues the package build. The client sees the delivery in the project's Deliveries page when the package is ready.

For a published delivery, select Update delivery after changing its contents. Mixhaus queues a new package revision for the current delivery. It does not send the first-publish notification again, so tell the client separately when an update needs their attention.

To remove the package from the portal, select Unpublish delivery. To make that same delivery available again, open the editor and select Publish delivery. The current interface uses Publish delivery, not Republish.

Expected result

The panel shows a Published badge and the client can open Deliveries in the project portal. The delivery page shows Final delivery with a Ready badge. If downloads are enabled, the client can select Download package. Mixhaus records the publication and later package activity.

What happens next

Keep the project open while the client checks the package. Read Check what the client downloaded to review download completion and receipt confirmation. If you still need to add stems, artwork, documents, or a ZIP, see Add stems and extra files to a delivery.

Common problems

The delivery editor says to connect the project to a client

The project has no client association, so there is no portal audience. Connect the project to a client, then return to Review & Delivery and select Prepare delivery again.

Publish delivery is disabled

Check the package for at least one selected file, check that an active contact appears after For, and wait for every additional file to show Ready. Mixhaus also blocks publishing when a project file has no current approval.

The package asks for approval

Open Version choices. Select the approved version, or use Include unapproved versions only when you deliberately need a different version from a file that already has an approved source. A file with no approved source must go through client approval before it can publish.

The client cannot see the delivery

Check that the delivery is still Published and that the client is an active project contact. An unpublished or revoked delivery is removed from the portal. Ask the client to verify the portal link with the contact email you invited.

I changed a published package but the client still sees the earlier files

Package builds run after you save. Refresh the delivery editor after the update finishes, then ask the client to refresh the Deliveries page. If the client needs to know that the package changed, send a separate message because an update does not repeat the original publish notification.