Use case
Get a mock-up signed off
A PDF or an image sent under a code, previewed by the client in the page, approved in one click or sent back with a comment.
$ colis statut K7QP2M4X
à corriger
envoyé 2026-09-22 10:00
ouvert 2026-09-22 11:30
à corriger 2026-09-22 12:45
comment Le logo en SVG, et le fond plus clair.
$ colis statut K7QP2M4X --json # the whole receipt, for a scriptThe situation
What is actually going on.
The problem
You email a mock-up, and the client answers three days later in another thread, with “fine by me” or an annotated screenshot. You do not know whether they opened it, nor which version they approved.
What colis does about it
Drop the mock-up on your delivery page, or colis envoyer it from a terminal: you get a code and a link. The client opens the link, sees the preview (image, PDF, video, audio, text) and answers: approve the delivery, or ask for changes and say what should change. The answer is final and timestamped. You see it on your sending page, with colis statut, or in a webhook.
Worth watching
The things that are easy to get wrong.
One answer per parcel
A verdict is never overwritten. For a new version, send a new parcel: each version gets its own code and its own receipt.
Opened means opened by the client
Your own visit to the pickup page is recognised by a sender token and does not count as an opening.
Clean the bucket
The expiry stops a parcel being handed over; only a lifecycle rule deletes the object. colis verifier tells you when one is missing.
Related
Other ways to deliver.
Send it. They sign off. You know.
Your storage, a delivery page under your name, a webhook at every step. Nothing hosted by someone else.