Choose the right post-purchase moment
Ask about unboxing, setup, first use, product instructions, or support depending on when the customer is likely to see the code. A single package can include a different destination for a setup need than for a broader experience question.
Write the invitation clearly
Tell customers what they will get by scanning and keep the first question focused. Avoid making the code look like a required registration step when it is an optional feedback request.
Make the printed asset dependable
Test the code on the final material, in expected lighting, and at the size customers will encounter. Keep it away from folds or seams and include a short URL or support path when appropriate.
Separate support from feedback
If a customer needs help with a damaged product, safety concern, or account issue, provide a clear support route. Feedback can reveal friction, but it should not delay a request that needs direct assistance.
Learn from themes across products
Use product, batch, or packaging context only when customers understand it and the team needs it. Review comments alongside support conversations to improve instructions, onboarding, and the product experience.