Released 25 Aug 2026
Store prices corrupted: UpdateWholesalePricesV2 re-processes prices touched by UpdateStorePricesEndDates (SkipProcessing filter removed in PR 654) (RTC-62314)
Store prices no longer overwritten with outdated values
Applies to chains using Price Control.
When a chain- or profile-level price was replaced by a newer one, the price update job could pick up the replaced price and apply it to the stores again. This showed up in two ways: purchase price details (wholesale price, net price, supplier discount, freight and margin) on an existing store price were reverted to older values, or a brand new store price appeared with an old retail price, taking over from the price the store had deliberately set.
Prices are now only passed down from prices that are actually in effect, and a price that has already been replaced can no longer create a new store price. Store prices set locally are kept.
Async API swagger doc shows ~38 stray Internal API controller tags (RTC-62207)
API Documentation
The Swagger documentation page no longer shows the Async API Documentation section alongside unrelated internal API sections.
Coop - 440714 - Configure reserved (central) PLU ranges (blocklist) (RTC-60741)
Reserved Central PLU Ranges
Chains that split PLU numbering between head office and stores can define which numbers belong to head office. On the System Parameters page, under Item identifiers, a Reserved (central) PLU ranges section allows adding one or more ranges by specifying a From and To number. Ranges can be added, changed, or removed as needed, and are saved for the chain.
IM: JSON import — main and alternative suppliers (RTC-58743)
JSON Import for Main and Alternative Suppliers
JSON import preserves the supplier configuration across all organizational levels. At the Common level, a main supplier and one or more alternative suppliers, along with sub-suppliers and alternative sub-suppliers, can be specified in the import payload. Store group overrides — Profile, Price Zone, and Store — accept their own main and alternative supplier definitions. Importing an item without any supplier fields leaves the existing supplier configuration unchanged. A full round trip is supported: exporting an item and importing it back produces the same supplier configuration at all levels.
IM: Always confirm "unselect all" in store assortment, even when filters are active (RTC-58893)
Store Assortment Selection Confirmation
Unselect all and Select all in the per-store item assortment editor always show a confirmation dialog before proceeding, regardless of active grid filters. The dialog states the consequence — items removed can no longer be sold at that store, and selected items become available at the register. This applies only to store assortments; item lists are unchanged.
Excel export produces corrupt file (Name column disappears) when tenant has one language and user's UI language differs (RTC-60891)
Excel Export Language Selection
When a user's preferred language differs from the tenant's configured languages, the Excel export dialog shows the language selection instead of hiding it, along with an info message explaining that the preferred content language is unavailable. The Export button is disabled until at least one language is selected, preventing the corrupted file that could previously result from exporting without a valid language. Users can select the desired language and export items successfully.
IM: Make opening item details faster (RTC-62282)
Item Details Loading Performance
Opening item details is up to 20% faster, depending on item data and user permissions.
IM: Multi-supplier per level with IsMain flag (RTC-58509)
Multiple Suppliers per Level
Items support multiple suppliers and sub-suppliers at each organizational level — Common, Profile, Price Zone, and Store — with exactly one supplier marked as main per level, used as the default for that level. Multiple suppliers can be added at the same level without conflict, and the supplier list shows all suppliers per level with a clear indicator on the main supplier. Users with the required permission can set any supplier as main directly from the list, which updates the main designation accordingly. A main supplier at a level cannot be deleted while other suppliers exist at that level; another supplier must be set as main first. Item JSON exports include the main supplier flag per supplier across all levels.