Released 11 March 2026
Store prices - Delete prices in user interface (RTC-48359)
Store prices support deleting both active and future prices directly from the user interface. Delete button is added to the store prices view, opening a modal with a date picker to control the deletion behavior. Deleting an active price sets its valid-to date to the next day by default but it is possible to choose another day and hour, while deleting a future price performs a soft delete.
Store Price Calculations - Store prices (RTC-53969)
StorePriceConverterHandler has been developed to handle the updating of new fields on store prices. When the BackgroundWorkers job is triggered, the new fields in store prices are updated in batches without triggering store price export or causing heavy database load. The StorePriceConverter table is updated with the latest processed StorePrice ID, and a new row is added to track the job execution status.
Store price calculations - Edit future prices (RTC-55295)
Editing future prices is possible in new user interface (accessible through hyperlink 'Details' next to the price). Prices modified in this view update exclusively the new data in Price.StorePrice table, and edit mode can be enabled using the Edit button within the planned price view. In edit mode, values are calculated using the most recent data such as VAT and currency rates corresponding to date of the valid from date of the planned price.
Store price calculations - Create new prices (RTC-54008)
Creating new prices is possible in new user interface (accessible through button on the bottom in the Store Prices grid). In the top section, there is store group selection, supplier currency selection and valid from selection. In the price element there is wholesale price, cost price section (supplier discount, net wholesale price, freight and net price), sales price (margin, retail price and vat). When user changes relevant things in the user interface (e.g. changes the date of the price, currency, or store), they are recalculated and correct values are fetched.
Store price calculations - user interface for prices (RTC-55290)
New user interface was added for displaying and managing store prices in Item Management, using only the new price fields and excluding prices that have not yet been migrated. The new view is accessible via a separate button.
It is visible only to users with the “Access to system tasks and information” permission, and opens after selecting a row. The price calculation rule dropdown is hidden, and a new translation for “Supplier currency” was added.
Sales code in item search (RTC-53641)
Item Search now allow users to search items using a sales code in addition to existing search parameters.
Store routines - Default columns (RTC-55345)
The columns visible in the store routines grid are displayed in the following order by default: GTIN, item text, supplier item number, supplier name, brand name, quantity in package, item area name, item group number, item group name, item subgroup name, store group level, store group code, promotion, promotion price, wholesale price, profile price, retail price, gross profit, gross profit%
Sorting and filtering in Item list (RTC-56078)
Item subgroup (number and name ) and sub-supplier (number and name) columns are visible in the Item list -> item. It is possible to filter the grid by these columns .
Food items - Ingredients (RTC-56148)
A “Remove” option has been added to the three‑dot menu in the Manage Ingredients → Alternative Items tab.
When selected, the alternative item is removed from the list, unlinked from its associated default ingredient, and its Item details page is automatically updated with the entire Convenience section cleared.
The Remove action is disabled for any active alternative item, preventing their deletion.
Food items - Item hyperlinks (RTC-56150)
GTIN values in the Ingredients, Recipe Items, and Menus grids are clickable links that take the user directly to the Item Details page for the corresponding item, making it faster to browse and verify data without manual searching. In the Menus grid, the Item Name column also works as a hyperlink. For Alternative Items, the existing link in the ItemText column has been corrected to properly navigate to the Item Details page as well. As part of these changes, breadcrumbs have been updated across all affected pages, and a bug has been fixed where navigating to Item Details via the GTIN hyperlink did not correctly maintain the breadcrumb structure.
Excel import / export of ingredient (RTC-53571)
The system supports enhanced Excel import capabilities for ingredient management, allowing users to import all ingredient types - including regular and base/default ingredients - mark items as ingredients, and update existing ingredient records.
During import, comprehensive validation ensures data integrity: each Ingredient Info entry must include mandatory values such as Quantity per Unit and Number of Units, and the item must have an active store price.
Ingredient numbers are automatically generated when missing, or used to update existing ingredients when provided. Additional safeguards prevent referencing ingredient numbers from items that are not valid alternatives of the current item. Alternative item rules have also been strengthened: an item can only be marked as an alternative if it contains exactly one default YieldsIngredient with net = 1 and gross = 1; otherwise, the import fails.
Price control - Keep margin suggestions (RTC-53896)
Keep margin suggestion is deleted when active price from which the suggestion was created becomes outdated or has passed its validity.
Correct breadcrumb navigation (RTC-55343)
When users open an item via a hyperlink from any grid (e.g., Store Routines, Item List), the breadcrumb now navigates back to that same grid, not the generic item grid. Instead of always showing “Items”, breadcrumbs now display the appropriate label e.g., Item, Item Segmentation, Item lists, Label Printing, Label lists, Store Assortment, Price Control, Store routines, Store prices, or any custom list name.
Shelf label printing layout (RTC-54852)
For specific shelf label types, there is a default and not changeable layout for printing labels from all views. Shelf label 4, Shelf label 4 streamer, A4 price sign are always printed in Landscape layout, while A5 price sign in Portrait layout. In printing window, the option to change layout is not visible. For other label types, options are available. Additionally yellow background for labels for items with sales purpose is always visible and printed no matter if 'Background graphics' checkbox is selected or not.
Planned import for Excel files (RTC-53891)
It is possible to create a planned mass update for a future date. When creating a mass update, future date can be set in order to schedule an import. If no data is set, a usual mass update is performed with immediate import.
Store group local values Import and Export (RTC-54247)
Store group local attributes can be exported/imported for both Profile and Price Zone in a format with sub-columns, and this applies to all values that are supported in Store Group Local Attributes. Based on the permissions, we will show only the sub-columns for profiles that the user has access to via the "View Store Local Attributes" permission. This is a "breaking" change for users who have the "Use Assortment Code per Profile" setting enabled. In the user interface, Values per Store Group is allowed to be checked/enabled along with Values per Store or Export Store Prices; however, Export Store Prices and Values per Store cannot be selected together.
Item details - Import items (RTC-53892)
The Imports tab is visible in Item details. This table displays imports that contain a given item. The data displayed includes the import ID, file name, planned import date, and status. Clicking on the name will take the user to import details.
Item Import of EAN 20 barcodes (RTC-57291)
When importing items identified by EAN 20 barcodes, a crash could occur during batch import processing, causing the entire import to fail with an unexpected error. This happened when an item could only be found through EAN 20 barcode conversion rather than a direct barcode match. The issue is now resolved - items identified via EAN 20 barcodes are handled correctly during batch import, and the import completes as expected.
Item Import (RTC-57303)
Fixed an issue where reimporting an existing article with a changed VAT code caused the import to fail with an error, leaving the article unchanged. This occurred during both Excel imports and approval-based imports. The import will now complete successfully when a different VAT code is specified for an article that already has one assigned.
Price import - Override status (RTC-47445)
When a price with Override status is imported, prices on lower levels, such as store or store group level, no longer apply. Active store-level prices stop overriding the price zone price by ending at the start date of the imported price. Future store-level prices are removed.
If the imported Override price starts in the future, an active store-level price remains valid until the imported price becomes active. This ensures the correct price applies at each point in time and prevents outdated store-level prices from overriding centrally managed prices.
Import suppliers and sub-suppliers per store group (RTC-48925)
Supplier, sub-supplier, and their respective item numbers can be imported per store group, allowing the main supplier to remain the default while defining actual supplier relationships at store group level. Fields are mapped to the new data structure and supported across JSON and Excel imports, including automatic placeholder creation if a sub-supplier does not exist. The legacy [ItemSuppliers] structure is now obsolete, exports use the new fields, and imports also allow removing supplier (only per store group) or sub-supplier assignments by sending null for entire structure (JSON) or null external numbers (Excel).
Store Prices - Valid to date in import (RTC-53226)
Price imports support an end date for each price. This applies to Excel, JSON, and RIGAL imports. System checks that prices for the same item and store group do not overlap in time. If an imported price overlaps with another price, the affected row is marked with a validation error and is not imported. If a price has an end date in the past, it is ignored and warning is displayed in import.
Export items from Item list (RTC-55080)
A button is added in the bottom panel of the Item list, and when clicked, it exports all the data about items in the same way how it is possible to export from the item grid. Data are exported for all the items inside the created Item list.
Export/Import Consumer Unit item linked to Trade Unit item (RTC-54532)
Users can now link a Consumer Unit (CU) item to a Trade Unit (TU) item directly through Excel import, as well as specify the Qty in Package (equivalent to “Quantity in Supplier Package” in the user interface) for each linked CU.
Excel export has been extended to include CU item identifiers - CU SKU, Product ID, Item Number, and GTIN
User can link the CU item to TU item using at least one of its item identifiers. If the item with given identifiers doesn't exist, it will be automatically created.
Supplier/sub-supplier per store group (RTC-56735)
The search functionality in item supplier management uses a contains search pattern, allowing users to find store groups using any part of the name.
Fix for: Duplicated rows in import items view (RTC-56071)
Single, valid price entry is returned per timestamp. As a result, the “Import details” view now consistently displays one row per import item.
ItemService - Update Item/price via FastLane (RTC-57381)
FastLane option is added to item and price imports to allow urgent updates to reach cash registers much faster. When this option is used, updates are sent through a priority path while still going through the normal process as well, ensuring critical changes are delivered quickly without affecting standard imports. FastLane works only for existing items, and attempts to use it for new items return an error, while imports without FastLane continue to behave as before.
Item service - New ItemService endpoint to fetch item identifiers based on the sales code (RTC-55657)
A new API endpoint that fetches item identifiers based on a Sales code.
Method: GET
Path: /v1/items/by-sales-code
Query Parameter: salesCode (required)
Request:
Query Parameters
salesCode (string, required) — The sales code to resolve
Headers
Authorization: Bearer <token>
Accept: application/JSON
Successful Response (HTTP 200)
Returns one or more matching item identifier records.
Response fields per item:
DKU (string)
productId (string | number depending on your domain - example uses string)
useItemIdentifiersOnlyForIdentification (boolean)
GTIN (string)
externalItemNo (string)
Item import - Food items (RTC-54128)
A isDeleted property has been introduced for JSON imports to enable controlled ingredient removal within the YieldsIngredients section.
Ingredient Number is mandatory when performing delete operations, and the system will prevent deletion of default ingredients by returning the error message.
Delete ingredient column has been added to Excel imports, allowing users to delete ingredients directly through the spreadsheet interface while following the same validation rules.
Items on Promotions - Promotion data in elastic export (RTC-56100)
All relevant promotion-related data are exported properly to Elasticsearch.
Items and prices via API - Detailed error message (RTC-56929)
When invalid JSON file (type mismatch or incorrect file structure) or incorrect identity header is sent, error response contains a clear message with details regarding the specific issue.
Item hierarchy - Fix: Nullable object error (RTC-57374)
When opening views with item groups, fields on item details with item groups and subgroups, there is no server error.
Fix for: Base ingredient dropdown in Convenience grid displays multiple duplicate default ingredients (RTC-56703)
Base Ingredient dropdown displays default base ingredients with no duplicate entries when creating an item as an alternative item.
Label printing - Fix: Store local values on labels (RTC-56744)
When label is generated and possible to print from Label printing, if Store local values exist for particular store group, they are used for label generation.
Suppliers - Fix: Missing suppliers on copied item (RTC-57186)
When copying an existing item, the created item has correct suppliers ad sub-suppliers set - common and on store groups (and copied from the source item).
Item search - Fix: Preferred language of user is not always applied (RTC-55314)
Users with different preferred languages can now always search for items in their own language, and search results will match their personal language settings instead of another user’s.
Fix: Empty grid in price control retail price is zero (RTC-56909)
Price suggestion queries now handle cases where retail price is zero without failing. When a zero retail price appears, the calculation safely skips division instead of throwing an error, so the grid returns results normally and price updates are no longer missed.
Fix: The Column adder in the ingredient grid shifts out of view when the grid is scrolled down (RTC-54246)
The Column Adder, Add Ingredient section and grid header section are now fixed at the top of the interface, ensuring they remain visible at all times. The remaining portion of the grid is now scrollable.
Fix for: Do not create storeGroupLocalAttributes when upserting suppliers on common level (RTC-57082)
Group local attributes are not created when the supplier is added to the common level via user interface.
Export to elastic - Fix: Support for 429 errors (RTC-55849)
The export process to Elastic handles 429 "Too Many Requests" errors automatically. When large exports run, the system retries based on the guidance returned from Elastic. This prevents failed exports caused by temporary overloads and ensures that all data is sent successfully.
Released 28 January 2026
Automatic update of recipe wholesale price (RTC-53107)
Recipe item prices now update automatically when an ingredient’s price changes, when the recipe’s composition is modified, or when any factor affecting the recipe’s net price calculation changes.
Updates are applied only in store groups where all included ingredients are available and where an active price for the recipe item already exists.
The calculated recipe net price is used as the wholesale price in the store currency; the sales price remains unchanged. Price updates run across all applicable stores, respecting store-level pricing.
A new default LIP job has been added to perform these updates automatically, with logic to avoid creating a new price if it matches the existing one.
Planning workflows are streamlined: when a user creates a planned price for an ingredient, a planned recipe price is created automatically; if an ingredient’s net price changes and a planned recipe price exists, the planned wholesale price is updated accordingly.
At all times - including for future-dated prices - the recipe-level wholesale price equals the sum of the net prices of its ingredients.
System parameters - Hide attributes (RTC-49268)
A new system parameter was added under a dedicated section called “Hidden item and price attributes,” allowing configuration at system level. Using checkboxes, retailers can hide sections such as Recommended Retail Price, Limit Control Group, Measures, Shelf Locations, Store Assortment, Bundle, Serial Number, Season, and the Bonus flag on item level. Functionality to hide the fields will be added in upcoming stories.
Store group local attributes (RTC-55744)
Store group local attributes section was added to the “Export” view. This blob type can be manually triggered to be exported, and both the last export section and the export history tab are visible and correctly refreshed.
Item supplier setup per store group (RTC-53427)
Item suppliers are defined per store group, including the common store group. Each item has one supplier per store group, ensuring a clear and consistent supplier setup. Supplier and sub-supplier information is imported only on the common store group. Supplier setup does not use a main supplier flag. Export format stays the same, so no visible changes appear for customers.
Store routines - Fix: Store picker improvements (RTC-55342)
Users with access to only one store are automatically taken to the “Store Routines” view with that store preselected, and the store picker is no longer shown. The selected store is remembered when refreshing the page or navigating between views, and the picker remains hidden as long as a store is already selected, while the selected store is still displayed above the grid. In addition, the store picker modal can no longer be confirmed without a selected store, preventing the grid from disappearing.
Fix: Approving price suggestion creates price with null wholesale price (RTC-55332)
Approving price suggestions created from prices with different wholesale supplier and retail price currency always creates a price with correct currency, The wholesale price in supplier currency is copied from the existing profile or store price, depending on the suggestion level.
Released 14 January 2026
Store prices - Price calculation (RTC-53966)
All price calculation fields are updated when store prices are created or modified. The implemented logic sets values for both new and existing fields. These fields are updated when prices are created or modified via UI and import, and when price suggestions are approved.
Fix: Notifications when import of campaign flag (RTC-55708)
When importing RIGAL file with campaign flag in field 5 ( K,M,A), user is notified only once that there is error in the row or in some rows in the imported file.
Fix: Nullable object must have a value exception (RTC-55376)
User with scoped permissions or limited store access can go through Item Management accordingly to his permissions without any errors. All store and store group dropdowns are now properly filtered according to user permissions, and grid filtering behaves as expected.
Released 13 January 2026
Package code column in Items overview (RTC-54534)
A new Package code column has been introduced to the Items grid.
This column reflects the package information from Item Details → Package section and supports two values: TU and CU. By default, the Package code column is not visible in the grid and must be manually enabled through the “+” (column selector).
When the column is first added, it automatically applies a default filter of CU, displaying only CU‑packaged items.
Users can clear the selected value to remove the filter, allowing both TU and CU items to be displayed simultaneously.
Item area (RTC-52884)
Item area number is a column possible to be visible and filtered on in Items overview. Item area number and name can be exported to Excel.
Attributes per store group - Label creation (RTC-54055)
When exporting labels, field values are determined using a hierarchy. If a value exists at the store group level, it is used. If not, the system follows this priority order: Store / Price Zone / Profile / Item.
The yellow background associated with a sales purpose is applied based on the same hierarchy. A label displays the yellow background when a sales purpose value is defined at any applicable level (store, price zone, profile, or item).
Profile price filter (RTC-47358)
The Net price column now displays ingredient prices based on the selected profile, along with the correct currency.
The previous column filter has been replaced with a Profile drop-down, with the first profile in the list selected by default. Profiles shown are filtered by the user’s “View prices” permission, ensuring only authorized profiles are visible.
Ingredient prices are sourced from the most recent store price within the selected profile. If an ingredient does not have a price for the chosen profile, its ‘Net Price’ field remains blank. Currency is displayed next to each price.
Profile price filter in Edit recipe grid (RTC-53766)
Net prices for individual ingredients and totals are now displayed in the currency of the selected profile, with the currency clearly shown next to each value.
In Edit Recipe, the previous “Net Price” column filter has been replaced with a Profile drop-down, which defaults to the first available profile and lists only profiles for which the user has “View prices” permission.
Prices are sourced from the most recent store price matching the selected profile.
If any ingredient lacks a price for the chosen profile, the ‘Total net price’ field will remain blank; similarly, if prices span multiple currencies, totals will not be displayed.
Item export - Export labels for item (RTC-31537)
When triggering export of item from item grid user interface, active exportable labels are exported. GenericExport job takes care of export of all other blobs, where LabelExport processes labels.
Filtering in export view (RTC-31540)
In Export view, user is able to apply filter on start date, end date and number of elements columns to provide flexible filtering. Currency sales rate and currency cost rate are grouped under a single entry as "Currency".
Fix: Default ingredient quantities shouldn't be editable (RTC-54635)
When using the Edit button in the Ingredients grid, Manage Ingredients grid, or Item details, users can now only modify the name of default ingredients. The net and gross quantity fields have been removed from the edit modal for default ingredients.
Fix: Incorrect recipe item displayed on Edit recipe page (RTC-55262)
Instead of first recipe item in the grid, the “Edit recipe page” now correctly displays the details of the recipe item selected by the user.
Fix: Content is not refreshed after changing language (RTC-53504)
After changing content language, the application is automatically refreshed to be visible in selected language.
Fix for: Country of store is updated when country is changed in profile (RTC-54966)
When a country is changed on a profile in Store service and store is Imported to Item management the country code on the private store group for store is updated to the changed country.
Released 17 December 2025
Store routines grid (RTC-48812)
The Store routines grid shows the effective price for each item in a store. The grid shows one row per item and presents the price that the store actually uses. The grid also shows if the price comes from a profile or the store, and if the price is a promotion price or a member price. The grid opens for one selected store. The store dropdown shows only stores the user can view by 'View Prices' permission. The last chosen store is stored for each user. Area access controls which items appear in the list. Promotion price column shows only offers that are promotion price.
The grid shows these columns by default: GTIN, item name, store group level, store group number, ordinary price, promotion price, member only, item group.
Hidden columns include: item number, net price, promotion start, promotion end, all optional columns from the store price grid (except external model number), margin, and profile price.
ValidTo date on store prices in elastic search (RTC-53131)
Elastic Search uses the ValidFrom and ValidTo dates to identify which price is active for each item and store. Export includes the effective price at the time the job runs. A store price replaces a profile price while it is active. When the store price ends, SearchIndexing job exports the profile price again if it exists.
Store price calculation (RTC-53950)
Store price is extended with new price calculation fields: WholesalePriceInSupplierCurrency, WholesalePrice, SupplierDiscountAmount, FreightAmount, NetPrice, MarginAmount, RetailPriceExVat, VatAmount, RetailPrice, RecRetailPrice. They are not yet visible or usable by the user.
Hyperlink to active base item (RTC-54039)
In Convenience section, for non-active base items, INGREDIENTS section is now replaced with an ACTIVE BASE ITEM section.
This section includes a hyperlink that redirects users to the active base item’s Item details page. The hyperlink displays the active base item’s name, localized according to the user’s preferred content language.
Item saving through bulk updates (RTC-54993)
Saving items using bulk updates correctly stores all related data.
Export of assortment code to 3rd party (RTC-54279)
Assortment code, when set on item, is exported in item.gatewaychanges blob in separate field 'assortmentcode'. When set on profile or price zone, it is exported in both item plannings section as well in item.storegrouplocaloverride.export blob. Removing assortment code from an item/ store group triggers export of according blobs with value null in field.
Import Procurement rule code (RTC-46494)
Value from field 73 in RIGAL file is mapped to procurement rule code and set on item in import.
Mark item as an ingredient via JSON import (RTC-53937)
Using import user can:
Mark item as an ingredient - in IngredientInfo: Quantity per unit and Number of units must be provided, first YieldsIngredients must be base ingredient (netQuantity = 1, grossQuantity = 1)
Add alternative item - first YieldsIngredients must be base ingredient (ingredienNo must be provided)
Add regular ingredients to ingredient items
Not yet an ingredient items - first YieldIngredients must be base ingredient, the remaining will be imported as regular ingredients
Ingredient items - all YieldIngredients will be imported as regular ingredients
Ingredient numbers are auto generated if missing, while provided numbers update existing ingredients. Any YieldsIngredient referencing multiple items must be valid alternatives; otherwise, an error is thrown.
For new ingredient entries with both net and gross quantities equal to 1, the first occurrence is treated as the default, and a warning is displayed if multiple such entries exist.
Fix: Cannot print label from label lists (RTC-52942)
It is possible to print all label types from label lists.
Fix: Return link in the breadcrumb (RTC-54119)
Return link is added in the breadcrumb to return from Store price details page to Item details page or to store price grid view.
Fix: Add label to label list, ecological flag (RTC-53484)
Swedish translation for adding labels to label list has been corrected. As well as translations for the name of the 'ecological' column in item grid.
Released 9 December 2025
Item hierarchy - Bonus flag per profile (RTC-47469)
Bonus flag is added to the item group. This value is per profile. Selecting the entire flag enables the bonus flag on all profiles. The user can select the profiles on which the flag should be set or not. The item group view displays the first 5 profiles for which the flag is enabled, with a notification informing user if there are more. The user can manage bonus only for profiles to which they have access based on their permissions. The display of active profiles is also based on user access, which means that a flag in an item group will be marked or not depending on whether the user has access to profiles managed by another user.
The quick edit panel has also been removed from the group item register.
Item Management - New language support (RTC-53330)
The Item Management application includes Danish and Finnish language support. Users can operate all Item Management features in Danish or Finnish by selecting their language in “Edit user profile”.
Scale labels - Fix: Shelf life declaration store level not working (RTC-53142)
When store local values of shelf life and best before flag are used, values from common level are overwritten. Therefore, changes in common level values are not triggering label generation, and only store level values are visible. When not both of the values are store local, then the missing value falls back to the common level.
Label printing - Labels with promotion (RTC-53036)
For item with sales steering and promotion price, the promotion/campaign prices are displayed in red text/red price, overriding the yellow background until the promotion period has ended. This applies to the following label types: Price Sign A4, Price Sign A5, Shelf Label 4 Streamer, and Shelf Label 4.
Update active base item for ingredient (RTC-50823)
In Manage ingredients (Alternative items tab) users can set a base item as active either during addition (via a new "Set as active" checkbox in the Add panel) or from the row options menu ("Set as active" option in three-dot button). When a new base item is activated, the previous active item is automatically marked as inactive.
Additionally, a confirmation modal has been introduced to approve changes when switching active base items (it provides info on how many ingredients and recipes will be affected by the change).
Extended "Manage base ingredient quantities" permission (RTC-53572)
User without "Manage base ingredient quantities" permission additionally: cannot add alternative items - “Add panel” in "Alternative items” tab (on Manage ingredients page) is hidden for the user.
Logging in integrations (RTC-54294)
Improved the performance summary for all kinds of integration jobs that execute in the background, so that it's easier for us to investigate any performance issues.
Import/Export - LotteryId item attributes (RTC-52683)
LotteryId can be exported to Excel. It is also possible to import this value by JSON and Excel file. The value needs to be unique and max 3 characters long. If these conditions are not met, the user will be notified via a message in the import view.
Import and map units of measure (RTC-46708)
When importing RIGAL file with code 1-15 in field 14, the code is mapped to a correct unit of measure and set on item. If unit does not yet exist in Item Management, it will be created. The same goes for importing code 1-15 in field 92, where the code will be mapped to correct unit price unit (unit price factor value must be present in the file or on the item already).
RIGAL import - Support import on price zones (RTC-48450)
The system supports importing RIGAL files with prices on price zone level from third-party systems. The import reads the value in field 54 and maps it to the external store group number. When the same value exists for both price zone and store in field 54, the price zone value applies. When the file includes an assortment code in field 47, the import handles the assortment code based on the system parameter assortment per profile. When the parameter is disabled, the assortment code imports on common level. When the parameter is enabled, the assortment code imports on the item on profile. The import places the assortment code on the profile when the profile is present in the file, in the file name, or specified in the import. When the file includes a price zone or store, the assortment code imports on the parent profile of the store group.
RIGAL import - Fix: Campaign flags omitted in manual import (RTC-54372)
When importing file, with rows where flag on field no. 5 is K, M or A, these rows are omitted.
Fix: Validation import when importing item with unit price (RTC-50517)
The Excel import accepts items when the file includes both Unit Price Unit and Unit Price Factor, or when both fields are missing. A validation error appears only when one of the fields is missing while the other contains a value.
Fix: Item having profile and price zone with same reference file export fails (RTC-54293)
File can be correctly exported to excel when the item has assortment code and both profile and price zone share the same reference.