As part of our quality policy, OpenHealth allows customers who wish to break down very finely the method of calculating sales volume and product value on a sample of products of their market.
Our clients wishing to replace their current panelist with OpenHealth sometimes ask us for such studies in order to provide a documented understanding of possible data discrepancies with their former panelist.
What are the criteria that determine the quality of the data of a panelist like Openhealth and to be taken into account in such a study?
The criteria are obviously numerous, and here is a non-exhaustive list of points of attention at OpenHealth:
We distinguish the date of interception of the first sale and the date of registration in the database. Indeed, the sales of a product must be calculated in relation to the date of observation of the first sale and not on the date of registration in the database.
Price calculation is also a key variable. Indeed, our prices are applied to the transaction (= price actually displayed on the receipt), to reflect the market prices in euro, and not from reference prices
The rate of pharmacy cover . OpenHealth communicates transparently to its customers or prospects
Input data, to be given by the customer:
List of GTINs
Output data, provided by OpenHealth:
Date of first intercepted sale
Date of registration in the database
List of GTINs with their Technical Codes
A product sometimes has several GTINs and Openhealth thus uses a technical code called "Grouping code" in order to make the link between the different codes. This, in the following cases:
If a product is made in France in 2 different factories, there may be 2 separate GTINs for traceability aspects, even though it is the same product.
If a product experiences a "minor" modification to its product sheet (example: the cap changes color), this will generate the creation of a new GTIN even though it is the same product.
Conversely, it is necessary to have another code serving as a "separator", in order to distinguish the 2 products and follow the evolution of sales over time, in in this case, the Technical Code is an "explosion code"
For example in the case of reuse of the same GTIN over time by a firm for a new product when the old one is no longer marketed.
ANNEX 2: method of calculating sales volume and value