Chain Web 2.10.453
Released 22 September 2026
Version requirements can be found in this Jira: (RTC-63352)
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.452
Released 26 May 2026
Version requirements can be found in this Jira: (RTC-58935)
Fix: Documents in stores with no logo (RTC-58714)
PDF documents are rendered correctly for stores with no logo set.
Chain Web 2.10.451
Released 22 April 2026
Version requirements can be found in this Jira: (RTC-58347)
Support for order line structured notes (RTC-54597)
Added the ability to view and edit structured notes on individual order lines in the Dispatch Order details view. Chain Web. Structured notes display a non-editable key (name) alongside an editable value field (max 512 characters).
Picking order export (RTC-54601)
The PickingOrder export file (JSON) includes the field StructuredNotes.
The field contains additional information related to the order. The value is transferred from POSLog to the database and included in the exported PickingOrder file.
The Swagger documentation for all PickingOrder export contracts describes the StructuredNotes field, making it clear how the field appears in the export format.
Chain Web 2.10.450
Released 16 March 2026
Version requirements can be found in this Jira: (RTC-57077)
Updated Klarna API connection for Kustom partner support (RTP-46000)
The Klarna payment integration has been updated to support Klarna’s new Kustom partner API connection. A new parameter “KlarnaKustomPartnerId” has been added and related configuration updates have been made in POS, POS Services, POS Master database, and Chain Web Backoffice.
These improvements ensure the POS continues to connect correctly with Klarna and process Klarna payments without interruption.
Get customer orders through relay (RTC-52752)
A new method ‘GetCustomerOrdersByCustomerNumber’ allows retrieving all customer orders for a given customer number, regardless of which store the order was placed in. Results are sorted by date (newest first) and include only active customer orders (deleted/cancelled orders are excluded and all offers are skipped as well). Each order includes: Store Number, Order Id, Order Number, External Order Number, Order Source, Project, Amount, Sales Channel, Status, Delivery Address, Pickup details, and more.
Large result sets can be paged using offset and limit parameters. Limit supports values from 1 to 1000. When no paging is specified, all matching orders are returned.
The Customer Order service can now be exposed over Azure Relay for secure remote access. Enable via the BackOffice.CustomerOrder.EnableRelayEndpoint configuration setting - by default disabled (<add key="BackOffice.CustomerOrder.EnableRelayEndpoint" value="false" />).
Relay credentials (namespace, SAS key) are preserved during AppServer upgrades.
Web order is locked after failed attempt to do an item return (RTC-55934)
Previously, if a payment failed while processing an item return or refund on a web order, the order became locked and inaccessible.
Now, payment failures are handled gracefully — the order remains accessible, and the return or refund can be retried once the payment is assigned to the order.
Picking order export (RTC-54601)
The PickingOrder export file (JSON) includes the field StructuredNotes.
The field contains additional information related to the order. The value is transferred from POSLog to the database and included in the exported PickingOrder file.
The Swagger documentation for all PickingOrder export contracts describes the StructuredNotes field, making it clear how the field appears in the export format.
Carrier name display in delivery method selection (RTC-50084)
When selecting delivery methods to offer in the webshop, the list shows both the carrier name and the delivery method name. This gives a clearer overview of each option and makes it easier to choose the correct delivery methods for the webshop.
Set Payment to OK from Order view (RTC-55716)
Authorized users (Admin role) can set an order’s payment status to OK directly from the order view.
The “Set as paid” button marks all active order lines as fully paid, helping resolve payment issues quickly and complete the order workflow. Deleted and non-sale order lines remain excluded from the payment check.
Block access to "Create store" view through link (RTC-54517)
Access to the "New store" view in Chain Web is now fully restricted based on the user's store level and the DisableNewStoreButton system parameter. Only users with HQ-level access and DisableNewStoreButton set to False can open the view - regardless of how they navigate to it. Users who do not meet these conditions are automatically redirected to the Stores grid.
POS Configuration - Configuration of mandatory Line notes for selected POS functions (RTP-45742)
POS Chain Web configuration includes parameters to control if a line note is required for selected POS functions:
Manual Return – AddLineNoteToManualReturn
Manual Deposit Refund - AddLineNoteToManualDepositRefund
Manual Line Discount – AddLineNoteToManualLineDiscount
Each parameter is set independently. All parameters are deactivated by default for new installations.