Release Notes February 2026: New features, attributes, validations and system fixes to Erudus
At Erudus we’re always looking to improve - to make life easier for our customers and progress further in our mission to make accurate food data more easily and quickly accessible to everyone who needs to see it. So we frequently introduce new features to the platform, and perform upgrades and fixes that keep things running smoothly and come as a direct response to any issues that our users are having. With that in mind, here’s what our team have been working on lately…
New Features
Manufacturer users
Traffic light labelling on "per serving"
There is now an option for Manufacturers to display traffic light nutritional labelling on their specifications - per serving.
API Users
Erudus API Terms of Use
A notice has been added to the Erudus API documentation (developer.erudus.com) to advise that by using the API, users agree to be bound by the Erudus API Terms of Use.
All users of Erudus API Version 2 are required to familiarise themselves with these terms before using the API.
Fixes
All users
Error regarding >20ppm gluten changes on product update emails
There was an issue with daily product update emails whereby products that had a change of gluten concentration from <20ppm to >20ppm weren’t being flagged as an allergen change. This has been rectified and now, if a product's gluten content is changed from <20ppm to >20ppm for any cereal, it will be tagged as an allergen change in the daily update email.
Validations
Traffic light nutritional labelling per serving required attributes
If Manufacturers choose to display traffic light nutritional labelling per serving, they will be required to enter all of the per serving attributes that are displayed on traffic light labelling:
- Energy (kcal) per serving
- Energy (kJ) per serving
- Fat per serving
- Saturated fat per serving
- Sugar per serving
- Salt per serving
You may also be interested in…
You may also be interested in…
