How to get feedback on a packaging design
To get feedback on a packaging design, export a flat PNG or PDF of the mockup and share it as a review link — not an email attachment. Clients who describe feedback in words ('the logo bit at the back') are rarely looking at the same face you are. A link where they click the exact panel and pin a note removes that ambiguity before revision 1 even starts.
Export a flat review file, not the source
Export a flat PNG or PDF of the dieline — not the Illustrator or Figma source. For multi-face packaging, lay all panels side by side in one file (front, back, left, right, top, bottom) so every piece of feedback can name a face. Version the filename: 'tea-box-v2-review.pdf', not 'final.pdf'. The version number alone prevents the most common packaging approval error: two people reviewing different revisions and neither realising it.
Share a link rather than an email attachment
Emailing a PDF produces the most common packaging approval breakdown: your client opens it on their phone, highlights a vague area, and sends back a screenshot — or worse, a voice note. On a six-panel dieline, 'the thing on the right side' could mean three different faces. Share the export as a review link instead. The client opens it in their browser, clicks the exact panel they mean, and leaves a text note anchored to that spot. No download, no app. Every note lands in one thread, tied to the exact element — 'back label, third line: change net weight to 250g', not 'fix the writing at the back'.
Ask specific questions, not 'what do you think'
Open-ended requests invite vague answers. Give your client a short checklist alongside the review link: Is the product name readable at a glance? Does the flavour or variant read correctly on the front panel? Is all the required legal copy present on the back? Any barcode, QR code, or batch-code placement concerns? Clients who struggle to articulate design instincts ('it doesn't feel premium') often respond well to direct functional questions — they can answer yes/no even when they can't name what's wrong. Anchored notes on specific panels are the output you want; the checklist is the prompt that gets them there.
Collect sign-off in writing before going to print
Before sending files to print, get written sign-off that names three things: the version number, who approved, and that every open note is resolved. A 'looks good!' over WhatsApp with no version reference is not a sign-off — it's a liability gap. If brand, legal, and regulatory all have to review, route them through the same link. Reconciling four separately annotated PDFs from four different inboxes is how print errors slip through.
If your client is the one reviewing — not you — skip the email attachment. Drop the exported mockup (PNG or PDF dieline) into Drafty and share the link. They click the exact panel — front face, back label, side copy — and pin a text note right to that element. No account, no download. Every note lands anchored to the spot, in one thread you can reply to and resolve. Once everything is addressed, the resolved thread is the written sign-off. For a multi-face packaging job where 'the right side' could mean two different panels, anchored comments are the only feedback that goes to the printer without a follow-up call.
Open a live demoQuestions
- How do I ask a client for feedback on a packaging design?
- Share a flat export of the mockup (PNG or PDF) as a review link with a short checklist: product name legible, variant correct on the front panel, legal copy complete on the back. Specific prompts produce specific feedback. 'What do you think?' produces 'looks great!' or 'make it pop' — neither of which can go on a print order.
- What should I send to a client to review a packaging design?
- A flat PNG or PDF export of the dieline with all panels visible — front, back, left, right, top, bottom in one file — versioned by number. Not the editable source file. Include a note on what you need them to confirm: copy, hierarchy, colours, any regulatory text. A review link they can open without software is better than an email attachment.
- How many revisions are normal for a packaging design?
- Two to three rounds is typical for a freelance packaging project, but revision count usually tracks to how specific the brief was at the start and how structured the feedback loop is. Vague feedback ('more premium') costs an extra round. Anchored, panel-specific notes ('front face: typeface on the product name needs to be heavier') cut revision rounds because the designer knows exactly what to change.
- How do I get packaging design feedback from multiple stakeholders?
- Route everyone through the same review link on the same version. When each stakeholder marks up their own copy and emails it back, you spend a day reconciling four PDFs that may conflict — and you lose the thread of who approved what. A shared link keeps all notes on one artifact: brand, legal, and regulatory can each pin their notes to the exact element, you reply, resolve, and there is one approval record.
- How do I get client sign-off on packaging before going to print?
- Before sending files to the printer, confirm in writing: the version number, who is signing off, and that all open comments are resolved. A resolved comment thread on the review version is cleaner than a 'yes looks good' message with no file reference — especially if a print error surfaces later. Never go to print on a 'final_FINAL_v3_approved_USE-THIS-ONE.pdf' with no written sign-off trail.
- Can I get packaging design feedback without the client installing anything?
- Yes. Share the flat export as a review link that opens in their browser. They click the panel, pin a note, and you see it instantly — no app, no account, no emailed screenshot of a screenshot.
Keep exploring
Stop emailing files back and forth.
Share one link. They comment on the exact spot — no account, always the current version.