Released 01 Sep 2026

IM: Saving changes skips setting price end dates (RTC-62596)

Price Management

When a new price was saved for an article, the price it replaced was not always closed with an end date, so both could remain valid at the same time. The same saves could also fail to make the article available in the stores the price applied to, and price changes intended to reach the point of sale immediately were not always passed on. This affected prices saved a few at a time, for example when working on a single article in Item Management, while prices arriving through a large import were handled correctly. Saving a price now closes the price it supersedes, links the article to its stores, and passes on immediate price changes as expected.

IM: Fixed price flag is not carried over when creating a new price suggested from the active price (RTC-62318)

Price Management

When creating a new price for an item on the "New price" screen, the "Fixed price" checkbox is now correctly suggested from the item's current active price for the selected store group and valid-from date. Previously the checkbox always started unticked, so if left untouched, a new price created for an item that had an active fixed price would silently lose that fixed-price setting from its valid-from date onward.

Now, if the active price being suggested from has "Fixed price" set, the checkbox is shown ticked to match, and it is re-evaluated automatically whenever you change the store group selection or the valid-from date. If there is no active price to suggest from, the checkbox falls back to the item's own fixed price setting. You can still tick or untick the checkbox yourself before saving, and whatever you leave it as is what gets saved on the new price.

Unable to activate article for a single store in Item Management – activates in all stores instead (RTC-62408)

Store Assortment

Activating an article for one specific store now works as intended. In "Manage active assortment" user can choose between all stores and a single store. Previously the single-store choice was ignored and the article was activated in every store, which could add articles to assortments where they were never meant to be sold. The article is now activated only in the store the user selected. Choosing all stores works as before.

IM: Cleanup old labels (RTC-26100)

Electronic Shelf Labels & Label Printing

ItemService now automatically cleans up old, superseded label records in the background, instead of keeping every label ever generated for an item/store forever. Only labels that are no longer relevant are removed: for each item, store and label type, the system always keeps the current label and, where relevant, the most recently printed label, so nothing that could still be printed or exported is ever touched.

The one visible change: a small number of stale, never-printed label entries that had already been permanently superseded by a newer printed label will disappear from the label-printing list in the item management module. These entries could never have been printed anyway, since printing them would have produced a label with an out-of-date price. Everything else you see and print is unaffected — no relabeling, re-exports, or unexpected reprints will occur as a result of this change.

IM: Item cannot be saved when a text field contains a leading/trailing space, and no error is shown (RTC-62077)

Item Save Validation

Items save successfully even when stored data contains leading or trailing spaces in fields such as supplier model numbers or item numbers. Extra spaces in hidden fields no longer prevent saving, and when a validation error is present on the form, the screen scrolls automatically to the first field that needs correction.

IM: Fix saving import data in transaction (RTC-62123)

Import Consistency for Price Validity

Imports save as a single unit: if any part fails, nothing from that batch is saved, and the import is marked as failed so it can be run again once the cause is resolved. This prevents cases where items and prices were saved but end dates on affected price validity periods were left unchanged, allowing an older price to remain open-ended alongside a new one.

Batch import error results should include the item identifier, not just the index (RTC-62412)

Item & Price Import

When a batch of items or prices is submitted through the import API, the response reports one result per entry. Results for entries that failed now identify the item itself, not only its position in the file. They carry the same item identifier — GTIN, SKU, external item number, or product ID — that successful and rejected results already carry. Where the item already exists in Item Service, the identifier is the stored one; where the item is new, it is the identifier as supplied in the request. Identifying a failed entry therefore no longer requires keeping the original file and counting through it. Successful and rejected results, and the position number on every result, are unchanged.