Define what the sample must prove
Start with the target buyer, sales channel, product format and the specific decisions still open. A sample for visual direction is different from a sample intended to approve application behavior, packaging fit or a complete kit.
- Target market and buyer
- Product family and intended use
- Reference attributes to match
- Attributes to avoid
- Packaging or kit scope
Translate references into visible attributes
Explain what matters in each reference instead of asking for a generic copy. For lashes, identify the density, mapping, curl, length progression, root or band and visible finish. For kits, list every liquid, tool, tray and instruction component that must work together.
- Fiber and style direction
- Root, stem or band construction
- Pickup and application route
- Tray and component fit
- Retail presentation
Review the physical product under one checklist
Compare samples in the intended use condition and record the result. Photography helps document appearance, but approval should also cover pickup, placement, release, component fit and labeling where they apply.
- Appearance against the brief
- Handling and application behavior
- Consistency across the sample
- Product-to-tray fit
- Label and component accuracy
Separate product approval from artwork approval
Confirm the physical product and component architecture before final artwork. A box design should not be treated as product approval, and a good lash sample does not confirm that the tray, insert, instructions and outer pack are ready.
- Approved product reference
- Approved component list
- Approved tray and box structure
- Approved artwork version
- Open items and owners
Create the handoff for production
Record the approved sample, specification notes, packaging files, component count and agreed QC checkpoints. Commercial quantities, timing, documents and destination requirements are then confirmed for the exact project rather than assumed from a generic product page.
