In-store launch asset checklist

An in-store launch asset checklist should specify what each asset helps the Shopper do, where it appears and who approves it. Prepare Product information, visual content, interactive logic, physical artwork and operational materials together. Track versions and requirements by Retailer, language and Touchpoint rather than treating the global launch toolkit as a finished retail Experience.

Agree the Experience before exporting assets

Start with the Shopper questions and intended physical placement. A comparison needs structured Product facts; a Story needs useful visual detail; a Finder needs recommendation rules. Confirm the actual screen orientation, viewport, print dimensions and accessibility requirements before the studio prepares final files.

Keep editable masters and usage-rights records. A social edit or global Product film may provide valuable material, but its pacing, text and framing should be adapted to the retail task.

Copy this working asset register

| Asset | Required information | Owner | Version or language | Approval status | | --- | --- | --- | --- | --- | | Product facts | Model identifiers, dimensions, compatibility, included items and limitations | Assign Product owner | Enter version | Record reviewer and date | | Product images | Approved cut-outs and physical detail views | Assign studio owner | Enter files | Record rights and approval | | Story storyboard | Shopper question, card content and optional actions | Assign Experience owner | Enter market | Record factual and creative review | | Video or demonstration | Task, viewport, captions, sound behaviour and playback controls | Assign producer | Enter export | Record tested output | | Product Comparison | Consistent attributes, units, sources and retailer range | Assign category owner | Enter dataset | Record sign-off | | Product Finder | Questions, rules, recommendations and no-match paths | Assign category and UX owners | Enter logic version | Record branch tests | | Destination map | Retailer URLs, Product codes and location scope | Assign account owner | Enter mapping | Record live checks | | QR or NFC artwork | Route, prompt, carrier and batch identifier | Assign production owner | Enter proof | Record physical tests | | Localisation | Approved copy, units, local models and qualifications | Assign market owner | Enter language | Record local review | | Colleague briefing | Main questions, use instructions and support route | Assign field owner | Enter version | Record distribution | | Support and recovery | Device configuration, local behaviour and restoration route | Assign technical owner | Enter configuration | Record failure tests |

Replace the owner and status fields with actual project information. Do not mark an item complete merely because a file exists; approval and testing are separate checks.

Prepare for each Touchpoint

For Interactive Displays, specify the installed orientation and resolution, accessible control layout, reset behaviour and any local playback requirements. Test the actual Device configuration rather than assuming standard browser behaviour.

For QR and NFC, test the final print or assembled carrier with representative phones. Make the physical invitation match the opening module. Record whether location mapping is store-specific or shared so reporting requirements do not arrive after production.

Separate editable text from footage where useful

Clean footage and separate text can make localisation and updates easier when the implementation supports them. Fixed playback exports may need embedded text or captions. Agree which workflow applies, retain editable sources and check that translated copy fits without losing essential qualifications.

Review any clinical, performance, compatibility or comparison claim with the appropriate Product specialist. Do not turn an illustrative line in a brief into an approved Product promise.

Include test and release evidence

Record tested devices, physical materials, languages and key outcomes. Check loading, navigation, access needs, pre-launch states and destinations. Confirm the configured analytics Events separately from the visual review.

After launch, retain the approved asset version and publish changes through a named owner. Remove expired offers and update Product information without losing the history needed to interpret reporting.

Final asset checklist

• Assets map to a defined Shopper task
• Product facts and rights are approved
• Every range and language variant is accounted for
• Physical proofs and target viewports are tested
• Finder rules and destinations have been checked
• Release, recovery and maintenance ownership is recorded

Turn launch assets into a useful Experience

MyPlayer supports interactive Experiences built around Product information and physical context. Scope the content requirements with your creative and delivery teams before final production. Discuss your launch asset requirements.