Planned changes
The features below are available on TEST environment.
Batch sync API (POST items/batch, prices/batch) returns numeric or wrong error/warning codes because gateway enums have drifted from internal enums (RTC-64744)
Item and Price Batch Import
Validation errors and warnings returned when sending items and prices in batches through the integration interface are now always reported with a readable name. Previously, a few of them (for example insufficient area access, an overlapping price period, a price end date earlier than its start date, and an unknown sub-supplier) came back as a bare number, and some warnings (for example that a price is not imported because its end date has passed, or that some barcodes or values are not updated because of insufficient permissions) did the same.
In addition, two age-group errors were reported incorrectly: an unknown sub-supplier was shown as an invalid age group value, and an invalid age group value was shown as "age group requires active substance". Each error is now reported under its correct name. If your integration reacts to these two errors, it will now receive the correct error for each situation.
Measure accepting negative value when values are imported (RTC-63873)
Import Validation for Negative Measures
Imports reject a negative width, depth, height, weight, volume, or tare with a clear error message, and nothing is saved for that item; other items in the file still import normally. This matches the existing restriction on the item page. Zero remains allowed.
StoreRoutines: Create store price always applies to the selected item only (remove variants choice) (RTC-64629)
Store Routines — Create Store Price
Creating a store price in Store Routines saves the price only for the selected item. The variants popup, which could fail or not cancel correctly, no longer appears. To price several variants at once, use item details.
Store routines: Right-pinned, adaptive application windows (RTC-63861)
Store Routines — Window Layout
Windows in Store Routines open pinned to the right side of the screen, sharing the available space when more than one is open and adapting their content to the width available, so a single open window can show more information. Closing a window lets the remaining windows re-flow to fill the gap. A window can be dragged anywhere, with a Snap option to return it to the pinned area.
StoreGroup tab in Local Values shows Store rows (RTC-64060)
Local Values StoreGroup Tab
The StoreGroup tab under Local Values shows only Profile and Price zone values. This resolves a case where store values could also appear there when no filter was set, and could be edited or deleted from the wrong tab. Store values appear only on the Store tab.
Store routines: Support up/down-arrow stepping between items in the grid (RTC-64051)
Store Routines — Grid Keyboard Navigation
Up and Down arrow keys move between items in the Store Routines grid, as in Item Management: clicking a row and pressing an arrow key selects the item above or below it, and any open windows, such as Active price, switch to the newly selected item.
Item management - Store Routines “Campaign price” column price field cannot be displayed for user (RTC-64784)
Campaign Price Column Picker
The two “Campaign price” columns — the checkbox and the amount — can be shown and hidden independently in the column picker, resolving a case where only the checkbox column could be toggled, preventing some users from displaying the amount.
IM: Add assortment code to promotion label big (RTC-64610)
Promotion Label (Big)
The big promotion label prints the item's assortment code in the bottom-left corner, next to the barcode. Nothing is printed if the item has no assortment code, and the rest of the label stays exactly where it was. The digits under the barcode are also larger and no longer bold, making them easier to read.
Labels that have already been printed are not marked as changed by this update. From now on, if an item's assortment code changes, its big promotion label is flagged as changed so it can be reprinted.
Application window not possible to move/administrate (RTC-64047)
Store Routines — Window Docking
Double-clicking the title bar or clicking the maximize button reliably docks the window to the right side of the view, resolving a case where windows could become stuck and unmanageable, such as after double-clicking near the title bar or maximize button.
Unable to save an Edited Ingredient when the error message is shown and removed in Net quantity field. (RTC-63830)
Ingredient Quantity Validation
An ingredient can be saved after correcting a Net or Gross quantity error, resolving a case where correcting a Net quantity previously higher than the Gross quantity caused Save to do nothing and the window to remain open.
IM: Store routines - stock and order point columns (RTC-64603)
Store Routines
The Store Routines grid includes four new columns — In stock, Ordered quantity, Order point min, and Order point max — allowing replenishment decisions without switching screens. Values are shown for the selected store and reload on store switch; if the store has no store-specific active order point, the active order point for all stores is shown instead, with a store-specific order point always taking precedence and future-dated or expired order points ignored. Items without a stock record or an active order point show an empty cell rather than 0, and quantities display without trailing zeros, up to four decimals.
The columns are hidden by default, available from the column menu, and support sorting, filtering, and inclusion in the Excel export. Order point min and max require permission to view store-specific item attributes for the selected store; without it, the columns are not offered. The stock columns require no additional permission.
IM: Remove UsePlanningCodes parameter, unused registers and related logic (RTC-63963)
Item Planning Cleanup
The unused planning code, delivery date and marketing code functionality has been removed. These registers were switched off for all customers and could never be used on items, so day-to-day work in Item Management is unchanged. The related screens, filters and options are gone from item creation, segmentations, the import items grid and Excel export, and saved segmentations give the same results as before. Planning values on items (such as season, collection and sales dates) work exactly as before.
If an import file or Excel file contains delivery dates or marketing codes, those values are now ignored without any error message. The separate screens and interfaces for maintaining planning codes, delivery dates and marketing codes have been removed. This is the complete list of changes; no other fields or values have changed.
Store Routines: Assortment code shows store group values from groups the selected store doesn't belong to (RTC-63940)
Assortment Code Column
The Assortment code column in Store Routines shows the correct code for the selected store, resolving a case where it could show a code from a price zone or profile the store does not belong to. The Excel export from Store Routines reflects the same fix.
Multi-Supplier Support — Excel Import/Export (Main & Alternative) (RTC-58832)
Multi-Supplier Excel Export & Import
The item Excel export includes an “Include multiple suppliers” option. When selected, each supplier and sub-supplier of an item — main and alternates — appears on its own row across all levels (Common, profile, price zone, or store), allowing bulk maintenance of multi-sourcing relationships via re-import. The level of detail follows the existing Values per Store, Values per StoreGroup, and Include common values controls. Selecting this option and price export are mutually exclusive. When the option is off, the export works exactly as before.
On import, a multi-supplier file adds new suppliers, updates known ones, changes the main supplier, and removes records marked for deletion, without affecting suppliers not present in the file. The main supplier at the Common level cannot be deleted; a record attempting this is reported as an error for that item. Default-format files import as before, leaving alternate suppliers untouched.
IM: Highlighted text in label data (RTC-64864)
Labels – Changes on price zones and profiles
Changing a local value on a price zone or a profile (for example assortment code, sales purpose or main supplier) now generates new labels for every store in that price zone or profile. Previously, only changes to an individual store's own values generated labels, even though price zone and profile values were already printed on labels. After editing these values on a price zone or profile, expect more labels than before.
PromotionDatesGuardJob extends price only to the end of the first of consecutive promotions (RTC-64689)
Price Management
Fixed an issue where a store price that ended during a promotion was extended only to the end of the first promotion when the item was on two or more consecutive promotions. The later promotions then ran without a base price. The automatic price extension now covers every active and upcoming promotion for the item and store, and extends the price to the end of the last one. The extension still stops where a following price for the same item and store group begins. Prices are also set up in the same way when a new price is created automatically for promotions targeted at selected teams or stores. Prices that have no active or upcoming promotion ending after their end date are not changed. Prices that were already cut short before this fix are not corrected automatically.
Import: run DetectChanges once per SaveChanges instead of ~9 times (RTC-63494)
Item and Price Import
Importing items and prices is now faster. The improvement is most noticeable when many small import files are queued one after another, and for chains with a large number of stores, where each import used to spend a lot of its time on extra processing that grew with the number of stores. Import queues now drain more quickly, so changes from your ERP system reach the system sooner. This applies both to imports sent as files and to imports sent directly through the item and price import interfaces. The imported data and the import results are unchanged.
IM: Export suppliers and sub-suppliers in JSON (Gateway.ItemChanges and Item.ItemStoreGroupOverride.Export) (RTC-63317)
Supplier Export
The item export includes each item’s main supplier and alternative suppliers, and its main sub-supplier and alternative sub-suppliers, at chain level. The store group export (profile, price zone, and store) also includes alternative suppliers and alternative sub-suppliers. When the main supplier or main sub-supplier of a store group is changed in Item Management, that store group’s item is exported again. Deleted suppliers are no longer included in the store group export.
IM: Allow an Exclude group without an Include group (RTC-62950)
Exclude-Only Segments
A segment can contain only Exclude groups, allowing it to match everything except certain items — for example, all items except those in a given item group — without requiring an Include group first. A segment with only Exclude groups returns every item in the catalogue except those the groups match, including deleted and inactive items, unless filters are added to the Exclude group to remove them. The last Include group can also be removed from an existing segment. Segments that already have an Include group return the same results as before.