Meat Foodservice Panel Data requirements

Descriptions

Signed contract 27/10/2025

Awarded to Numerator, please see notices:

Notice identifier: 2025/S 000-054824

Procurement identifier (OCID): ocds-h6vhtk-055abb published on the 8th September 2025.

Also Notice identifier: 2025/S 000-038050 Procurement identifier (OCID): ocds-h6vhtk-055aba

Published 8 July 2025, 7:53am

Requirement was for:

AHDB core Foodservice data requirements

1. The basic measures required will consist of the following as a minimum:

• Spend

• Servings/packs

• Price

• Buyer numbers i.e. penetration

• Servings/packs per buyer i.e. frequency and volume per trip

2. Data must be split by method including the following as a minimum:

• Dine out - Eating in or on the go

• Takeaways - Collected or delivered

3. Data must be split by channel (we are open to agencies proposing different channel coding

approaches):

• Quick service retail e.g. coffee shops, fast food, cafes, bakery/sandwiches

• Full service restaurants e.g. restaurants, diners

• Pubs and bars

• Contract catering e.g. workplace canteens, hospitals, schools etc

• Travel & leisure e.g. train, ferries, events etc

• Multiples including forecourts e.g. supermarkets, convenience stores etc

4. Data must be split by product type/meal, with the protein identifiable (beef, lamb, pork,

chicken, fish, vegetarian, vegan) and key cuts (e.g. steaks, burgers, roasting joints,

sausages etc) specified or obvious. A read of meat-free/alternatives is also beneficial.

5. Data must be able to be split by day part and demographics to help analysis

6. It would be beneficial for data to be split by operator for volume estimate purposes