Released 22 Sep 2026

IM: Store price create remembers store group selection across tenants, creating the price for the wrong store group (RTC-62327)

Remembered Store and Store Group Selections

Store and store group selections remembered while creating store prices or viewing Effective Prices are now scoped per tenant. Previously, switching tenants could silently reuse a selection from another tenant, causing a price to be created for the wrong store group without any warning. A store the user is no longer authorized to view can also no longer remain as the remembered selection. As part of this change, all previously remembered selections are cleared.

Numeric fields on item details cannot be cleared — save returns a server-side error (RTC-62711)

Item Details Numeric Fields

Numeric fields on the item details page — such as weight, volume, tare, quantity in supplier package, minimum order quantity, deposit quantity, and shelf life — can be cleared and saved as empty.

[Item Management] Refactor price calculation: import new price elements (RTC-43809)

Price Import Calculation Elements

Item price imports carry every element the chain's price calculation uses — supplier discount, retailer kickback, local discount 1 and 2, calculated breakage, freight, customs, and handling costs — each stated as a percentage or a fixed amount, with the percentage taking precedence if both are sent for the same element. The cost price is calculated from these elements in the order and bases configured for the chain, with signs taken as sent, so an element that reduces the cost price is delivered as a negative value. An element not stated in an import keeps the value from the price currently in effect, and an element the chain's calculation does not include is ignored, so an import only needs to state what changes.

While copying item - wrong spelling in error text (RTC-62994)

Item Copy Error Message

The Norwegian error message shown when copying an item with an invalid validation number is spelled correctly ("Ugyldig valideringstall").

IM: Profiles with bonus not loading for item group (RTC-63163)

Item Group Profiles

Profiles with bonus load correctly in the item group view.

IM: New fields in price calculation UI + json import (RTC-60547)

Price Calculation from Setup Register

The cost price section of a price follows the price calculation configured in the Price calculation setup register. Creating a price shows the cost elements the chain uses — such as retailer kickback, local discounts, calculated breakage, customs, or handling costs — in the configured order, each calculated from the elements it builds on through to the net price and sales price, with values updating as they're entered. Changing the setup affects only prices created afterward; opening an existing price shows the breakdown it was calculated with, including any cost element since removed from the setup. Chains keeping the standard setup see the price calculation exactly as before.

IM: Exclude ordinary price from LP30 calculation (RTC-58950)

Exclude Price from LP30 Calculation

Expired ordinary prices in an item's price history can be marked as excluded from the lowest-price-last-30-days (LP30) calculation, and the marker can be cleared again. Only expired ordinary prices can be marked; active or future prices are not eligible. The exclusion state is clearly visible in the price history and persists across reloads, affecting only the exclusion state, not the price value or validity dates. The ordinary price export carries the exclusion marker so the LP30 calculation can disregard excluded prices.

IM: Restore ingredient weight auto-calculation from base item weight (RTC-60501)

Ingredient Weight Calculation

Net and gross weight for an ingredient created or edited from a base item with a weight set are calculated and shown automatically in the ingredients grid, without manual entry. Weight fields remain blank when the base item has no weight defined.

IM: Better warnings/errors for json import (RTC-57251)

Gateway API Import Field-Level Validation

When an item or price import sent through the Gateway API fails because a field doesn't meet the required format or a business rule, the response identifies which field was rejected and why, rather than a single generic error. If a record has multiple issues — for example, an invalid country of origin together with a negative shelf life — all of them are listed at once, so every fault can be corrected in one pass. This applies to single item import, batch item import, and batch price import.

Item import crashes when a nutrition is sent without a code (RTC-63240)

Item Import

When an item was imported with nutrition or allergen information that had no code, the import used to fail with an unexplained error, giving no clue about what was wrong. This kind of item is now correctly rejected as an invalid submission, with the sender's system informed that the import contains bad data. Nutrition and allergen entries that specify a code that simply isn't recognised are unaffected - they continue to be reported as an unknown nutrition or allergen value, same as before.

IM :Search Indexing: SQL timeout in ItemStoresChangesReader.GetAreaTexts blocks (RTC-62621)

Search Indexing Performance

Item and store search indexing is more reliable under heavier load, preventing timeouts that could previously leave search results stale.

IM: Store group type not resolve correctly in promotion import (RTC-63267)

Promotion Import

Promotions targeting a store group that is set up as a price zone could fail to import into Item Management, so the campaign price or offer never reached the stores in that price zone. This has been fixed — promotions now import correctly whether the targeted store group is set up as a team or a price zone.

Item service: Export price calculation fields (RTC-55720)

Price Calculation Fields Export

The item price export includes the price calculation elements — such as supplier discount, retailer kickback, local discount1, local discount 2, calculated breakage, freight, and totalSupplierDiscountPercentage — alongside the existing price fields.

storeLocalAttributes[].storeIdentifier missing in import payload causes silent NullReferenceException and full item failure (RTC-62716)

Item Import Validation

Item imports return a validation error when storeLocalAttributes entries are missing storeIdentifier or storeNumber, instead of failing without explanation. The Swagger schema marks these fields as required.

ApprovalImport notification handler crashes on single-item import with ValidationFailed status (RTC-63076)

Approval Import Validation Handling

A single-item import that fails validation, such as an item not found or missing required fields, no longer causes the approval import job to crash. Users receive a notification listing the specific validation errors, without disruption to the job.

Batch item import: replace BatchPreloader temp-table lookups/loads with cached-plan TVP queries (incl. Item table scan fix) (RTC-63229)

Item Import

Batch item imports now spend less time on preparation work before processing begins. Small imports, which previously spent most of their time on this preparation step, now finish in a fraction of the time they used to. Larger imports also complete noticeably quicker overall, since the same preparation step no longer takes several seconds regardless of how many items are being imported. Actual gains vary with batch size and system load.

IM: Import local items with configured gtin range (RTC-60753)

Excel Import GTIN Assignment

When importing new items via Excel with GTIN range mode active, leaving the GTIN/EAN field empty automatically assigns a GTIN from the organization's reserved number series, and re-importing the same file updates the existing item instead of creating a duplicate. Users authorized only to manage local items can no longer supply their own GTIN on import, as it is generated automatically; users authorized to manage central items can still supply one as before. Automated system integrations are unaffected.