Released 29 June 2026
Labels Print API (RTC-58095)
The Labels Print API (POST api/gateway/labels/print) returns the details of created label print orders, including the generated OrderedLabelListId for each store and label type combination. The response also includes a list of item identifiers that could not be printed, such as items without an active price or items not active in the assortment. Duplicate items within the same request are merged automatically, with quantities summed rather than triggering a validation error.
Item Import (RTC-58384)
Previously, importing an article with localised text provided only for a non-default language (for example, Norwegian text when the chain's default language is English) — combined with item planning data — could cause the import to fail with an internal error. This was unpredictable and gave no useful feedback about what went wrong. This has been corrected. The import now returns a clear validation error ('Item name is required') when a language entry is present in the import but no item name is provided for it and the article has no existing saved text for that language. This allows the sending system to identify and correct the data before re-submitting.
Faster item and price imports (RTC-60063)
Updating large volumes of items and prices during import is now faster. This is especially noticeable for big nightly imports, helping them complete more quickly and making it easier to stay within the nightly update window.
Highlighted text: import/export via JSON and Excel (RTC-58337)
The 'Highlighted text' assignment on items and store-group overrides can now be set in bulk through JSON imports and Excel. Assignments are matched by code against the active Highlighted-text register — an unknown or inactive code rejects only that item row with 'Unknown Highlighted text', an explicit null clears the assignment, and an absent value leaves it unchanged. The import never creates, updates or deactivates register entries; localized names in the payload are informational only. Item and store-group exports gain Code and Name columns (under the Category section), with the name shown in the user's content language.
As part of this work, Excel export language now follows the user's content language for all export types. Previously only Item and StorePrice exports honored it; Supplier, Brand, Item Group, Item Hierarchy, Store Routines and Import Item exports fell back to the tenant default. The content language is captured when an export job is scheduled; the tenant default remains only as a fallback when no content language is set.
Local values for nutrition and allergens (RTC-49085)
The StoreGroupLocalAttributes contract and database schema have been extended to support nutrition data, allergen information, and weight declarations at a per-store level using the existing store-group mechanism.
These changes are additive and do not modify or remove any existing properties, enabling parallel development of related features such as UI, import/export, and API enhancements. The schema now supports storing nutrition values with references, allergens with content types, and weight declarations per item and store group.
Item Management — Reliability (RTC-60831)
After a deployment, users could experience an outdated version of the Item Management app being loaded due to the browser serving a cached page. This has been resolved: the app now instructs browsers to always check for the latest version when navigating to Item Management, while still caching the underlying files efficiently.
Price Control — Price Suggestions (RTC-60803)
Fixed a bug where a price suggestion was silently skipped when two prices for the same item were saved in quick succession. In this situation, the earlier price was permanently marked as already processed before the price suggestion job had a chance to handle it, so franchise store managers never saw the expected price suggestion in their Price Control view. Both prices are now correctly processed and their suggestions will appear as expected.
Support multicountry for assortment codes (RTC-54277)
Assortment Code name is displayed based on the available Supported Languages configured in System Parameters. In all places and grids where the Assortment Code name is displayed, the language shown is based on the user's preferred content language.
The Assortment Code names for each language are exported to AssortmentCode and StoreGroupLocalAttributes. These language-specific names also imported to JSON or Excel files. Similarly, Assortment Code names based on the configured languages are exported to Blob storage and Excel files.
Fix for: Item import validation for unidentified suppliers (RTC-60513)
Item imports that include a supplier item number without a corresponding supplier identifier (GLN, External No, or Name) are now validated and rejected with an UnknownSupplier error. The remaining items in the batch continue to be processed normally.