Delivery is the final step of the proofing workflow. Once your client has approved their selects, you trigger a delivery from the project and Shootbin generates a secure ZIP archive of those photos in the background. When the package is ready, your client receives a notification with a download link. You can optionally require payment before the client can access the files.Documentation Index
Fetch the complete documentation index at: https://docs.shootbin.com/llms.txt
Use this file to discover all available pages before exploring further.
Triggering delivery
Open the Deliver page
From inside your project, click Deliver in the project navigation. This opens the delivery overview where you can see the current status and initiate a new delivery.
Configure delivery options
Review the photos that will be included — by default this is all approved photos in the project. If you have set up a payment requirement, confirm the payment settings before proceeding.
Start the delivery
Click Generate Delivery. Shootbin begins packaging the approved photos into a ZIP archive in the background. You will see a status indicator showing that the package is being prepared.
The delivery package is generated in the background so large projects do not time out. The client’s download page shows a “preparing your files” state until the ZIP is ready, at which point it automatically becomes available.
Client download
Once the package is ready, your client receives an email notification and an in-app alert with a secure link to the delivery page. From there they can download the ZIP archive containing all their approved photos. The download link is protected — clients must be logged in (or have a valid signed URL) to access the files. Photo files are never served from public, guessable URLs.Payment gate
You can require your client to complete payment before they can download the delivery package.Enable the payment requirement
In the project’s Payments settings, turn on the payment requirement for delivery. You can also manually mark a payment as received if payment was collected outside of the platform (bank transfer, cash, etc.).
Client sees the payment gate
When your client visits the delivery page, they see a payment prompt instead of the download button. They must complete payment — or you must manually mark it as received — before the download becomes accessible.
Cancelling a delivery
If you need to pull back a delivery after it has been generated — for example, because additional edits are needed — you can cancel it.Cancel the delivery
Click Cancel Delivery. The existing ZIP package is removed and your client receives a notification that the delivery has been cancelled.
Cancelling a delivery does not remove the client’s approval decisions — only the download package itself is discarded. All approved photos remain approved until you or your client changes their status.
Delivery status reference
| Status | What it means |
|---|---|
| No delivery | No package has been generated yet |
| Generating | The ZIP is being built in the background |
| Ready | The package is available for download |
| Cancelled | The delivery was cancelled; no download is available |
Related pages
- Review workflow — the full proofing loop that leads up to delivery
- Approve, reject, and select photos for delivery — how clients choose their final selects
- Add visual annotations to photos — leaving feedback before the project reaches delivery