--- title: "2026-11-17 - Chain ItemManagement 2026-11.3" slug: "2026-11-17-chain-itemmanagement-2026-11-3" updated: 2026-11-17T09:49:23Z published: 2026-11-17T09:49:23Z canonical: "products.egretail.cloud/2026-11-17-chain-itemmanagement-2026-11-3" --- > ## Documentation Index > Fetch the complete documentation index at: https://products.egretail.cloud/llms.txt > Use this file to discover all available pages before exploring further. # 2026-11-17 - Chain ItemManagement 2026-11.3 # Released 17 Nov 2026 ### IM: Scale local attributes follow their own Manage permissions [(RTC-63992)](https://jira.eg.dk/browse/RTC-63992) **Scale Attribute Permissions** The nine scale-related local attributes — Tara, Scale label, Shelf life (days), Weight declaration, Best before, Origin, Country of origin, Weight control, and Self-service weights — can each be managed individually, with their own dedicated permission, independent of the general Manage store local attributes permission. A user granted only a specific attribute’s permission can edit that attribute in Local values, Store Routines → Local values, and Item declaration, while all other local attributes remain read-only unless Manage store local attributes is also granted. Manage store local attributes no longer allows editing these nine attributes on its own; a new role created with only that permission, rather than the full Manage group, will not be able to edit them. Deleting a local value row, resetting values, and saving at profile or price zone level all follow the same rule, requiring the relevant permission for every attribute stored in that row. Viewing continues to require only View store local attributes, as before, and existing roles and users with all permissions see no change in behavior. ### IM: Remove support for unused planning attributes [(RTC-65083)](https://jira.eg.dk/browse/RTC-65083) **Item Planning Attributes** Five planning attributes that are not in use have been removed from Item Management: Base Assortment, Collection, All Seasons, Marketing Exclusivity and Service Level. They no longer appear on items, in the item attribute view, in the item export to Excel, or as filter options when building item segmentations. The Collections, Marketing Exclusivities and Service Levels registers have also been removed from the Registers menu. Item import no longer reads these five attributes. If your import files or integrations still send them, the values are simply ignored and the import is not rejected. Item exports (file and Excel) no longer contain values for these attributes, so any fields your downstream systems read for them will be empty. Existing items have not lost any other data, and all other planning attributes work as before. ### IM: Fix design for edit order points modal [(RTC-65050)](https://jira.eg.dk/browse/RTC-65050) **Edit Order Point Window** The Edit order point window fits the screen and matches the appearance of other windows in Item Management. Deleting an order point now requires confirmation, so a single click no longer removes it. ### IM: Store/Store Group columns at the beginning of the excel file [(RTC-64922)](https://jira.eg.dk/browse/RTC-64922) **Excel Export Column Order** In item Excel exports, the Store, Profile, and Price zone columns (and their name columns) appear first in the file, regardless of their position in the column picker. This applies to exports from the items grid, a single item or model, item lists, active assortment, segmentations, the store price list, and the Pricat “Active items” export. All other columns keep their existing order, the column picker and saved export templates are unchanged, and re-importing an exported file works as before, since import reads columns by header rather than position. ### IM: In stock segmentation filter (Inventory section) [(RTC-62940)](https://jira.eg.dk/browse/RTC-62940) **Segmentation — In Stock Filter** Item segmentation includes a new Inventory section with an In stock filter, allowing items to be selected based on whether they are in stock in a particular store, team, or profile, rather than only anywhere in the chain. ### Promotion and Reporting iframe/links break for users without permissions in those modules [(RTC-64859)](https://jira.eg.dk/browse/RTC-64859) **Module Links and Embedded Windows** Links and embedded windows to Promotion Management and Reporting Management open the correct page for every user, resolving a case affecting users without permissions in those modules — including the promotion price and sales windows in Store Routines, the sales window in Item overview, and Promotion Management links in Item details, Item lists, Item group lists, and Store prices. Opening the target page still depends on the user’s permissions in that module. ### Generic export: avoid restarting store group triggered export from scratch after a failure [(RTC-64069)](https://jira.eg.dk/browse/RTC-64069) Generic Export The Generic Export processes only the store groups and export types that have pending changes, rather than re-processing all data on every run. When a failure occurs mid-run, the export resumes from where it stopped on the next scheduled run - no data is lost and no rows are re-exported unnecessarily. Changes queued during a failure window are picked up on the next run. Exports triggered by items or item lists are unaffected by this behaviour.