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.

What's coming?

Prev Next

Planned changes

The features below are available on TEST environment.

IM: Export complaints value in store group contract (RTC-59955)

Complaint Handling Recommendations Export

Recommended complaint handling values configured at the store group profile level — including service code, action code, service location, technician, and FAQ recommendation — are included in the store group override export.


Change of profile net price not trigger change to store net price (RTC-57521)

Net price component cascade

Changes to supplier discount, freight on Profile and PriceZone prices automatically cascade to related store prices in the same way as wholesale price changes. Store retail prices remain unchanged, margins are recalculated automatically, and new store prices are created when required for already active prices.


IM: Set Highlighted text on item (RTC-58336)

Highlighted text for items 

A Highlighted Text field is available on items, allowing a short configurable label drawn from a predefined register to be assigned. The field can be overridden per store group via local attributes,  without affecting the base item setup.


[Item Management] A5-5 products label (RTC-48001)

Label type Price sign A5-5

A Price Sign A5-5 label type is available for printing labels with up to 5 products on a single A5 half-page, mirrored onto A4 paper in portrait orientation. Items added via the label list appear in the order they were added. Each slot displays the item name (with dual-language support where applicable), sales code, and price — promotion prices in red, regular prices in black. Mix offers and club/member pricing are fully supported. When fewer than 5 items are selected, empty slots are left blank; larger batches are automatically split into multiple sheets. The standard label assignment flow is also supported — assigning the label type to an item will trigger automatic label generation. Printing from item details is additionally available, accompanied by an informational message directing to the label list as the recommended workflow.


IM: Myhrvold and Strongpoint as label types (RTC-57462)

Myhrvold and Strongpoint label types

Myhrvold and Strongpoint were added as new independent label types that can be managed through the Label Type Register like other label types in the system. They can be assigned to individual stores or chain-wide, managed in both the register and item details. Existing Scale functionality remains unchanged and continues to work independently.


[COOP#][Store Routines] - Export excel file from Store routines grid (RTC-49346)

Export excel file from store routines grid

Store Routines supports exporting the current grid view to Excel. The exported file reflects the user’s current view, including visible columns, column order and active filters, and is generated as a {{.xlsx}} file. Column names are exported using the user’s selected language, and empty results export as an empty file.


[Item Management] Export Myhrvold and Strongpoint automatically for items with 20-codes (RTC-43317)

Automatic Myhrvold and Strongpoint labels for EAN-20 items

Myhrvold and Strongpoint labels are automatically generated for items with EAN-20 GTINs when these label types are configured for a store in the Label Type Register. Labels are created only for items that are active in the store assortment and have a valid store price, and they are processed through the standard label export flow without requiring manual assignment on the item.
 
 
 


IM: Multiple suppliers/sub-suppliers at the same level (contract) (RTC-58951)

Multiple suppliers and sub-suppliers 

An item has a main supplier and an optional list of alternative suppliers, with the same structure applied to sub-suppliers. The main and alternative suppliers are defined at the chain (common) level and at the profile, price zone and store group level.

Note: This release introduces the API contract only. End-to-end behaviour — including item management UI, imports and exports — will be delivered in subsequent releases.


IM: Store and store group values cannot be exported at the same time to excel (RTC-58580)

Export items to excel

When exporting items to Excel user can choose either 'Values per store' or 'Values per store group', but not both at the same time. Picking one will automatically clear and grey out the other. This prevents the confusing Excel file that previously mixed store columns and store-group columns together in the same row. verything else on the export screen works as before — including the existing rule that 'Export store prices' turns off the two store-level options when selected.


IM: Cleanup expired promotions (RTC-49316)

Cleanup expired promotions in item mangement

Item Service janitor allows deleting old promotions. Promotions that expired at least a month ago will be deleted by the job.


Migration script: sync PriceCalculation to StorePrices where WholesalePrice is NULL (missed by buggy trigger) (RTC-59937)

Price Calculation

A defect in a previous database migration caused price calculation details — including wholesale price, supplier discount, freight, net price, and retail price — to remain incomplete for some tenants. This has been corrected: all affected prices have now been recalculated and populated using the same logic as the original migration, ensuring the pricing data is consistent and complete across the system.


IM: Validate quantity as whole number in recipe ingredient add/edit modal (RTC-59096)

Quantity validation in recipe items

Improved validation for the ingredient Quantity field in Item Management. The system enforces whole-number input on the client side, preventing decimal values from being entered or submitted. Users will receive a clear validation message if a non-integer value is provided, eliminating backend errors and improving the overall user experience during ingredient creation and editing.


IM: Ecological flag for Debio store (RTC-56780)

Ecological flag on labels
For organic-certified stores, the ecological flag set on an item is applied as-is to label exports — ecological items are marked accordingly, and non-ecological items are not. For stores without organic certification, the ecological flag is never displayed on labels, regardless of how individual items are configured. This behaviour applies to all label exports and is the new standard for how ecological information is represented on labels going forward.


IM: Tooltip with information to Ecological flag (RTC-58623)

Ecological flag in labels

A tooltip has been added to the Ecological flag to inform users that organic certification from the store level is used in labels. 


Fix default filtering in Item list (RTC-55384)

Fix for: default filtering in item list

Fixed inconsistent filtering behavior in the Item List grid for code and identifier fields such as Item No, Supplier No, and Group No.
The default filter operator is aligned with the main Items grid by using 'Is equal to' instead of 'Starts with.' This ensures more accurate and expected filtering results for users while maintaining consistency across the application, with changes applied purely on the frontend.


IM: Application windows in store routines (RTC-58275)

Store routinest application windows

Enhanced Store Routines window management to improve usability and consistency. Open windows are reused instead of duplicated, with dynamic titles reflecting the selected item(s). Navigation arrows allow seamless movement between grid items, updating all open windows simultaneously. Introduced improved docking behavior where maximized windows snap to the right and share space intelligently, while still supporting independent movement, resizing, and closing of all windows. These improvements provide a more intuitive workflow while preserving user context and efficiency.


IM: Set default assortment code when removing price manually (RTC-57461)

Price Deletion – Automatic Assortment Code Assignment

One assortment code in the Assortment Code register can be designated as the price deletion code using a dedicated flag. Only one code can hold this designation at a time.

When a price is deleted at profile or price-zone level, the system automatically applies the designated assortment code to the affected item or store group — including deletions scheduled for a future date. If an item has no active prices remaining at any level, the assortment code is also set at the item level.
Price deletion at the store level does not affect the assortment code on the parent profile or price zone.
If no price deletion code is configured, price deletion behaves without automatic assortment code assignment.


IM: Ingredients are not removed from recipe item (json file) (RTC-59931)

Fix for: Ingredients are not removed from recipe item

The export process correctly reflects the current state of the recipe, ensuring that only active ingredients are included after any deletions.


IM - Finnish and Danish missing in 'Edit user profile' language list (regression after @lrs/ngx-cloud-chain v4 upgrade) (RTC-59606)

Fix for:  Finish and Danish missing in 'Edit user profile' language list'

User can select from all five languages — English, Norwegian, Swedish, Finnish, and Danish — right inside Item Management and change the interface language. 


IM - Store group values are not editable. (RTC-59432)

Fix for: Store group values are not editable

Store-group local values in Item Management can be edited directly. The following fields in the edit window are fully editable: Assortment Code, Warranty Type, ID Requirement, Sales Purpose, Highlighted Text, Special Group, Is being phased out, and Bonus.


IM - Registers - When we deactivate and activate and click on save button, no action happens. (RTC-59356)

Fix for: Registers data activation/deactivation
When editing a register entry in the Registers section of Item Management — such as Highlighted Text or Allergens — clicking Save after using the Activate or Deactivate action saves the change and closes the edit window.


Checking top-level group does not select sub-items (RTC-60161)

Fix for: Group Selection – Select All Children

When a parent group is selected, all child items beneath it are automatically selected.


IM: Recipe item cost price not auto-calculated from ingredients when creating store price (RTC-60276)

Fix for: Recipe cost price suggested calculation

The cost price is pre-filled with the calculated total from the ingredient prices.

 


IM: Add store local properties to ItemStoreGroupOverride contract (RTC-57772)

Local attributes contract

Extended the StoreGroupLocalAttributes contract to include all store-level local attribute fields currently available in StoreLocalAttributes, enabling a unified payload structure for ItemStoreGroupOverride exports and Fast Lane API responses. The change is fully additive, preserves existing functionality, and prepares the platform for future local attribute migration.


Incorrect translations in Hide Item attributes (RTC-60226)

Fix for:  Hide Item attributes translations in system parameters page

The translations have been corrected to include the correct text


IM: Bring back FI and DA languages preferred content language dropdown in user edit modal (RTC-60220)

Fix for:  Finish and Danish missing in 'Edit user profile' language list'
User can select from all five languages — English, Norwegian, Swedish, Finnish, and Danish — right inside Item Management and change the interface language. 


IM - The text name for delete should be changed. (RTC-60169)

Store prices: 'Delete price' menu now shows the correct text

The menu shows 'Delete price' in user selected language, and the text updates correctly if user switch language while staying on the page.


Item service: Refactor storage for prices - use new field for prices (RTC-53975)

Store Price Management

The store price calculations overview has been extended with additional cost columns. Supplier discount, freight, margin, and VAT are now available as optional columns (both as percentage and amount) in the store price grid. These columns are hidden by default and can be enabled through the column picker.

The screens for creating and editing prices have been substantially modernized. The interface is now noticeably more responsive, and day-to-day price work feels markedly faster and smoother. All existing functionality remains in place.

In this release the underlying engine for saving store prices has been significantly simplified. When a price is saved — whether a single price or a bulk update — the change is committed faster and the downstream effects (export to POS, shelf label generation, and price suggestions for franchise stores) now propagate more reliably.

!image-2026-06-16-09-07-54-709.png!


IM: Ingredient isDeleted field exported as NULL causing JSON import to crash (RTC-60184)

Fix: Item Import Failure for Items with Ingredient Data

Importing items with ingredient data no longer fails when the exported data contains a null value in the {{isDeleted}} field. The import process handles this case correctly and completes successfully.


Enable EAN7388 Conversion (RTC-58918)

EAN7388 Conversion

A new Enable EAN7388 conversion parameter is available under System Parameters → Item Identifiers (disabled by default). When enabled, EAN7388 GTINs are automatically mapped to their base GTIN during import — the item is stored under the base GTIN, with the EAN7388 retained as an additional GTIN on the same item. No duplicate items are created. Searching by EAN7388 resolves to the correct item.

If a manually entered EAN7388 maps to a base GTIN already in use by another item, the system blocks the action and displays a uniqueness validation error.


IM: Display owner of locally created items (RTC-58952)

 
Item Origin Tracking in New Item Creation
When the Item Originating From system parameter is enabled, users creating a local item can optionally select a store group level (Profile or Price zone) and a corresponding group as the item's origin. Available options reflect the user's access rights. The selected origin is stored permanently and remains read-only for the lifetime of the item. For local items with a defined origin, the Originating From field is visible in item details as a read-only value. The Item Originating From system parameter controls the visibility of this functionality — when disabled, the origin fields are hidden throughout the system.

!https://jira.eg.dk/rest/tests/1.0/attachment/image/235073!


IM: Stop exporting expired prices as deleted in Json Export (RTC-56916)

ItemPrice export

The Deleted status is assigned only when a price record is explicitly deleted from the database. Expired prices are not marked as Deleted.

 


IM: Changing organic flag trigger export (RTC-59239)

Ecological Label Re-export on Organic certification change

When a store's Organic certification status changes, the system automatically re-exports shelf labels for all ecological items in that store. The Originating From field on labels reflects the current certification status, ensuring only certified stores display organic designation. No manual intervention is required.