Version Control for Erudus Specifications
This guide will help explain Version Control in Erudus, how it works, and provide further details around the types of changes and what implications those changes have to the version of a product.
How does Version Control work in Erudus?
Every time a manufacturer updates a product specification (e.g., changes an ingredient, nutritional value, allergen status, or packaging details), Erudus saves that new version while retaining the old one. Each version is timestamped, and it's clear who made the change. As the previous versions of products are still available, this allows Erudus users (Wholesalers & Caterers) the ability to access historic versions of the product.
Version Control Overview
Erudus product version steps are governed by which attributes are being changed on the specification and are categorised as Major and Minor changes.
Major Changes
A Major change to a specification creates a full 1.0 version step of a specification and represents a significant change to the product. Some attributes that would cause a Major change version step include:
- A GTIN change
- Product weight
- Product pack size
Minor Changes
A Minor change to a specification creates a 0.1 version step of a specification and is not considered to represent a significant change to the product. Some attributes that would cause a Minor change version step include:
- Product description
- Waste packaging updates
- Accreditation changes
What changes will cause a Major or Minor change?
In Erudus, we are often evolving and adding or refining attributes with the aim of improving the Erudus data model; as such, the list of what attributes contribute to each Major or Minor change is subject to change.
You can access a live Erudus schema that highlights what attributes result in a Major or Minor change here - Erudus Generic Schema
If you have any further questions, please feel free to reach out to the Erudus support team on 0333 121 8999 or via email at support@erudus.com