Chain Web 2.10.442
Released 22 September 2026
Version requirements can be found in this Jira: (RTC-63348)
Requires Integration Platform 3.1.1
Reliable processing of POS unit changes and POS configuration activation (RTC-62498)
Changes to POS units and activation of POS configurations are processed to completion in a single pass, also when configurations are activated for a large number of POS units and processing takes several minutes. Each change is applied once, so POS master data and the generated configuration files stay consistent, without an update being repeated or left unprocessed.
Order picking reliability verified (RTC-62629)
Order picking has been fully verified end-to-end, confirming that orders can be picked, delivered, and completed without interruption. This verification was carried out following underlying technical improvements to how picking orders are processed, ensuring no orders are lost, delayed, or left incomplete during fulfillment. The fix is applied automatically, so no configuration or user action is required.
Reliable export of picking orders created from customer orders (RTC-62497)
When a customer order is registered or updated in Chain Web, the resulting picking order is exported to the store and connected systems reliably. The export message is now sent in a way that works with the AMQP-based Service Bus connection, so picking orders reach the store as expected instead of being silently dropped. No configuration or user action is required.
Reliable export of picking order status changes (RTC-62628)
When picking orders are created, delivered or completed, the scheduled picking order job exports these changes to the store and connected systems reliably. The export messages are now sent in a way that works with the AMQP-based Service Bus connection, so status changes reach the receiving systems as expected instead of being silently dropped. No configuration or user action is required.
Loyalty and marketing jobs run exactly once (RTC-63477)
Scheduled loyalty campaigns, bonus voucher calculations and newsletter exports each complete a single time for every request they receive. Members get their campaign messages, vouchers and newsletters once, without duplicates, and scheduled runs finish instead of stalling. This keeps loyalty and marketing communication accurate and predictable for both the retailer and the member.
Reliable delivery of campaigns and member updates to the marketing solution (RTC-62648)
Campaign distributions and member updates sent to the marketing solution run to completion in a single pass, even when a large batch takes a long time to process. Each batch is handled once, which keeps campaign sending predictable and member data consistent between the loyalty solution and the marketing solution.
Reliable processing of campaign updates (RTC-62634)
Campaign updates sent from the back office are processed once from start to finish, even when a large update takes a long time to complete. Stores receive the resulting campaign data reliably, without repeated processing of the same update.
Reliable publishing of campaign changes (RTC-62630)
Campaign changes registered in Chain Web are published to the stores and connected systems reliably. The campaign messages are now sent in a way that works with the AMQP-based Service Bus connection, so campaigns reach the stores as expected instead of failing silently when they are sent. No configuration or user action is required.
SAFT receipt export (RTC-62500)
The SAFT receipt export runs to completion in a single pass, even when the export covers a long date range and takes a long time to produce. Each export request is
handled once, so the audit file is produced reliably, without the export restarting from the beginning or ending without a delivered file.
BackOffice batch generation (RTC-62500)
Event-triggered generation of customer, store, store group and picking order batches reads the incoming export message correctly regardless of the format it was published
in, and acknowledges each message once. Batches are generated as expected, without messages being reprocessed or left unhandled. Deployment requires Integration Platform 3.1.1.
Fix deprecated NuGet packages in ImportDBToBackoffice build (RTC-61737)
The Import DB to BackOffice job (cashier, retail customer and ARTS customer imports) runs on the Integration Platform 3.x libraries. Discontinued third-party components were replaced; the imports themselves are unchanged. Internal change, no customer impact.
Required: Integration Platform 3.1.1 and ImportDBToBackoffice 1.4.3
Chain Web 2.10.441
Released 18 February 2026
Version requirements can be found in this Jira: (RTC-55619) and (RTC-56708)
Support passing query parameters customer number and store number in creation of the order (RTC-51985)
Added support for passing customer number and store number as query parameters when opening link to new customer order view. Common customers will not be supported for now.
Example:
/CustomerOrder/customerorder/neworder?customernumber=0000001097&storenumber=222
Fetch reporting parameters from service for existing subscriptions (RTC-53803)
New stores can now be added to existing report subscriptions.
Newly created stores are available for selection without recreating the subscription.
Set items as picked on picking order line (RTC-55712)
Authorized administrators or support employees with Support Dispatch Orders permission can set the picking status of a customer order line to Picked. This action is available on the picking order line and is intended for orders that are stuck in an incorrect picking status and cannot be corrected by other means.
Order message update for Norwegian returns (RTC-55581)
Norwegian dispatch email templates present correct and consistent information by removing incorrect return details and the “Vanlige spørsmål” button/link. This ensures customers do not receive misleading return information in order-related emails and reduces confusion around returns.
The change applies to the following templates:
Order confirmation,
Order sent,
Pay & Collect dispatched,
Split order,
Split order picked
Order dispatch emails – Finnish return information (RTC-54991)
Order dispatch emails for Finland present correct and consistent return information. Incorrect return details are removed, and the link behind “täällä” leads to the correct return information without changing the visible text. This helps customers understand the return process and reduces confusion when reading order-related emails.
This applies to the following email templates:
Order sent
Pay & Collect dispatched
Split order picked
Improved handling of anonymized orders in invoicing (RTC-54631)
Invoices and receipts linked to anonymized orders now work correctly. Customer data is handled safely during invoicing, crediting, and customer updates, preventing errors and ensuring proper invoice and PDF generation.
Improved availability of invoice logos through caching (RTC-54462)
Store logos are now correctly displayed on invoice PDFs.
Stocktaking - Model matrix changes are now visible immediately after saving (RTC-55493)
Previously, when editing counted quantities for multiple sizes in the model matrix, only the selected row would update in the grid. Other sizes required a page refresh (F5) to show the changes. Now all affected rows update automatically after saving.
Fetch data from new created receipt, when correcting the original one (RTC-55223)
When a credit sale is corrected, the system now ensures that the database reflects the actual recalculated prices from the new receipt, rather than carrying over potentially outdated data from the original transaction.
Export net cost with picking order line (RTC-45651)
Per unit net cost of articles on picking order line is exported with ‘PickingOrderExport’ blob type, as well as other picking order derived export types.
Fix: Merge error when two the same cashier numbers in import (RTC-55351)
Cashiers are imported on users without merging errors. When we get the pair cashierNumber, storeId for more than 1 user, we set it on the later imported user.
POS Configuration - New function in ButtonConfig to check voucher balance (RTP-39417)
It is possible to configure a button with the new function Check Voucher Balance in ButtonConfig.
Thanks to it access to checking voucher balance feature will be available after clicking a button.
POS Configuration - PayTerminalType options (RTP-45153)
"AeroNexo" has been added as an option to configure in parameters using PayTerminalType as parameter type.
Thanks to it a new bank terminal integration will be possible to use in POS.
POS Configuration - Repair and FAQ configuration parameters (RTP-45103)
For a complaint flow functionality, we have POS Chain Web includes two configuration settings: CreateServiceOrderBaseUrl and ProductCatalogBaseUrl.
CreateServiceOrderBaseUrl defines the URL used to create service orders.
ProductCatalogBaseUrl defines the URL used to retrieve product information.