Release Notes October 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 in our mission to make accurate food data more accessible. So we frequently introduce new features to our 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
Wholesaler users
Weekly range match alerts
After the automated weekly range match runs each Friday evening, every admin on your wholesaler account now receives an alert, in app and by email, listing the products from your range list that have newly matched to Erudus specifications. Each row shows your own code and product name alongside a link to the matched specification, and a button takes you to your range list filtered to the latest matches so you can review the specifications and apply your codes. No alert is sent when nothing has matched.
Fixes
All users
Password resets now clear an expired password
If you had both forgotten your password and let it expire, resetting it through “Forgot your password?” would immediately tell you it had expired and needed changing again. Any password change now restarts the expiry period, so your new password works first time. The “Forgot your password?” link has also moved to directly beneath the password field on the login page, where it’s easier to spot, and a failed login now points you to it.
API users
Clearer date filter examples in the API documentation
The date filter examples in the API v2 documentation used 2024-10-12, which made it unclear whether dates are given as year-month-day or year-day-month. The examples now use dates such as 2024-10-25 that can only be read one way, making it clear the format is YYYY-MM-DD. The filters themselves are unchanged.
Manufacturer users
Cleared gluten answers no longer leave stale validation errors
In the Product Editor, when an allergen answer changed so that a gluten <20ppm answer no longer applied (for example, Wheat set from Yes back to No), the <20ppm field was emptied and hidden but its validation error stayed behind, keeping the Allergens section marked red until you validated again. The error now clears as soon as the field is emptied.
Wholesaler users
Product list imports by Erudus ID now find products
Importing products into a product list by Erudus ID or Outer GTIN reported that none of the products could be found, even though importing the same products by wholesaler product code worked. Imports now match on wholesaler product code, Erudus ID and Outer GTIN within your own range, so all three identifiers return the same products.
Validations
Emojis are no longer accepted in text fields
Every text field in the Product Editor now rejects emojis, showing the message “contains emojis or symbols that aren’t supported. Please remove them.” beneath the field. Emojis could not be stored reliably and broke downstream specification sheets and data feeds. Common symbols such as ©, ® and ™ are still allowed. Any existing product containing emojis will show the error the next time it is edited or published, and products submitted through the API are rejected in the same way.
Energy check now allows for rounded kcal values
The check that compares kcal against kJ in the nutrition section now allows for kcal being rounded to a whole number on pack. Previously, very low-energy products such as diet soft drinks could not be saved as printed: a label reading 1 kcal / 2.1 kJ per 100g/ml was rejected, and a 0 kcal label could not carry any kJ value at all. These labels are now accepted, while genuine mix-ups between the two values are still caught. The prepared energy fields follow the same rule.
