Contact: Chip Lister
Managing Director
212.633.1100
info@radius-global.com

::Case in Point: A major pet product manufacturer needed to assess how a new package fared against the existing package and two competing brands. EyeScan™ software, along with diagnostic and evaluative ratings, uncovered the positive overall appeal of the new package, but the product's safety perception was lower than desired. Ultimately, this research identified ways to simplify the package to better connect with consumers and their concern for their pet's safety.


Strategies: EyeScan™

Radius Global Market Research can help you achieve any business objective of a packaging change using EyeScan,™ our proprietary technique that provides invaluable insights into the power of packaging to influence consumer purchase.

Why is EyeScan™ unique?
EyeScan™ software collects "hard-wired" data by tracking eye movement along a shelf set or an in-depth demonstration of your package displayed on a computer screen. EyeScan™ does not require cumbersome headsets or other paraphernalia to track eye movement. One advantage of using this method is that all information collected via EyeScan™ is objective since eye movement is involuntary.

To ensure a complete package evaluation, Radius uses the EyeScan™ technique in conjunction with diagnostic and evaluative measures. Overall impression, purchase intent, uniqueness and open-ends on likes/dislikes are a few examples of additional measures incorporated into a package test with EyeScan™. We believe that while each component is useful on its own, when the measures are used in concert with one another, the package assessment is comprehensive and most actionable.

What questions does EyeScan™ help answer?
Key questions that can be answered from an EyeScan™ package test include:

  • How does your package perform relative to key competitors?
  • How long does it take for consumers to find your package on the shelf?
  • Which elements of your package are holding consumers' attention?
  • Are brand, logos or product messages being noticed?
  • Are any aspects of the package being ignored?
  • Is there a way to increase recognition?