OmniHuman 2.0: What to Check Before You Say “Print It”

The QR code scanned on the first try. It opened last year’s menu. The café owner was about to approve a whole batch of takeaway labels.

Did the code take customers to the menu they were supposed to see? That’s the check the owner nearly missed.

Give the Customer Three Things to Check

Send the final proof with a short checklist so the customer knows what to review before replying.

• Read the wording. Check the café name and anything that changed since the last draft.

• Check the fit. Print the PDF at 100% with page scaling off. Hold it against the bag to see whether the label fits and the small text is readable.

• Scan the printout. Open the code on a phone and make sure it leads to the current takeaway menu.

If the printer provides a sample on the actual label stock, stick it on the bag and scan it again. That lets you check how easily the code scans once the label is in place.

Show the Step People Tend to Skip

A short clip can show customers what to look for when they scan. If you already have a shop mascot, pair its image with your own recording in OmniHuman 2.0 to make a brief introduction.

Before you approve the label, scan the code on your proof and check which menu opens.

Then cut to real footage of a phone scanning the proof and opening the correct menu. Send the clip alongside the proof and keep the checklist in the message, where the customer can refer to it as they review the file.

Put the Version in the Approval

A reply that just says “approved” can be hard to match to the right attachment once several versions are in the same email thread. Name the proof and ask the customer to use that name in their reply.

Approved for print — Takeaway Label v3

If the code changes, send a new version and ask the customer to scan that copy before approving it. The print team can then match the approval to the exact file the customer checked.