Release Notes April 2026: New features, attributes, validations and system fixes to Erudus

New Features

Manufacturer users

Auto-saving on draft specifications

When creating new specifications in the Product Editor, changes made to draft specifications will now be saved periodically to avoid accidental loss of progress (due to not clicking the “Save” button before leaving the editor). However, Manufacturer users creating new specifications are still advised to actively save their draft specifications using the “Save” button as this feature is a failsafe to prevent accidental data loss.

Wholesaler Users

API allowance and additional charges

The Wholesaler pricing page (erudus.com/wholesalers#pricing) on erudus.com has been updated to reflect the API allowances included in Wholesaler subscriptions, and charges for additional API calls outside of the subscription. Wholesalers have 4,000 daily API calls included in their subscription and can purchase blocks of additional 1,000 daily calls for £300 per year.

Fixes

Manufacturer users

Negligible sodium content on specifications

When declaring sodium content as negligible for a product, the specification had been declaring the negligible amount at <0.01mg and not <5mg as it states in the Product Editor. This has been fixed and now when declaring sodium present in a product at negligible levels, the specification will state the negligible amount at <5mg.

E number errors in the validation engine

The validation engine was not correctly validating certain E numbers against dietary suitability attributes. This has been resolved and the validation engine now recognises all E numbers correctly for diet suitability validations.

Validation errors for allergen presence on non-food specifications

Validation errors for allergen presence in the ingredients declaration were occurring for non-food specifications when there are no allergen attributes to complete. This has been amended and now when completing a non-food specification, users will not have their ingredient declarations validated for allergen presence.

Wholesaler Users

Automatic version stepping issue

Some users were experiencing an issue with automatic version stepping for Wholesaler accounts: If a product received a major update that was not acknowledged in a Wholesaler’s product catalogue and then the product received a minor update at a later date, the system would incorrectly "skip" the major change and automatically step the product to the latest version with the minor change made. We have now resolved this, and if a major change is pending, any subsequent minor changes will be blocked until the major change is manually reviewed and accepted or dismissed.