This release makes it straightforward to keep every alternate code tied to a product — supplier codes, previous references, import aliases — organised in one place inside the product editor, rather than scattered across spreadsheets or side notes. Product and inventory teams can add, reorder, and remove these codes directly on the product record, choose which ones print on labels, and rely on automatic validation to catch duplicate entries, codes that clash with the product's own main code, or codes already used elsewhere. The result is cleaner product data, fewer picking and ordering mistakes, and a smoother handover when supplier codes change or products get re-coded during imports.
Additional product codes, organised on the product record
Inventory and product data teams often need to track more than one code per product: the code a supplier uses, the code the product had before a re-code, or an alias created during a data import. A new section in the product editor brings all of this together. You can add as many additional codes as needed, specify the code type — supplier code, previous code, or import alias — link a code to a particular supplier, and mark whether it should be printed on product labels. Codes can be reordered and removed at any time, keeping the list accurate as supplier relationships or product references change.
- Add, sort, and remove additional codes (supplier code, previous code, import alias) directly on the product record
- Assign a supplier to a code and choose whether it prints on product labels
- Automatic validation flags duplicate codes, codes that match the product's own main code, and codes already assigned to another product
- Clear on-screen messages point out exactly which entry needs correcting before you can save
01
What changes for you
Anyone maintaining product data no longer needs a separate spreadsheet for supplier codes or old references — everything now lives on the product record itself. Adding a new supplier code, retrieving a previous code after a re-code, or logging an alias used during an import is a direct action, with typing mistakes and duplicates caught before you save.
Being able to choose which codes print on labels means you can tailor product labels to warehouse or shop-floor needs without maintaining parallel versions of your product data.
02
Why it matters
Duplicate or conflicting codes are a common source of picking errors, wrong orders, and failed imports. Catching them at the point of entry, rather than discovering them downstream, saves checking time and reduces the risk of stock or orders being linked to the wrong product.
For teams working with multiple suppliers or handling regular product re-coding, having supplier codes and previous codes always visible on the product record makes it faster to cross-check price lists, process returns, and keep a clear history of how each item has been coded over time.