Chain Web 2.10.432
Released 22 September 2026
Version requirements can be found in this Jira: (RTC-63343)
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.413
Released 22 September 2026
Version requirements can be found in this Jira: (RTC-63339)
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.407
Released 22 September 2026
Version requirements can be found in this Jira: (RTC-63335)
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.394
Released 22 September 2026
Version requirements can be found in this Jira: (RTC-63328)
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.393
Released 24 June 2026
Version requirements can be found in this Jira: (RTC-60031)
Export invoice journal - remaining amount on lines (RTP-48432)
The total lines in VismaGlobal and VismaBusiness invoice exports display the remaining amount instead of original total amount.
The partial lines for VAT groups in VismaGlobal and VismaBusiness invoice exports display the remaining amount instead of total amount.
Chain Web 2.10.392
Released 26 May 2026
Version requirements can be found in this Jira: (RTC-55316)
Customer order - Return OrderVariant in GetCustomerOrders3 (RTC-54857)
The order variant is now stored at the order level in the database for customer orders. The GetCustomerOrders3 method in both Chain Web Backoffice and POS Services has been enhanced to include the order variant in the response, ensuring this information is available for POS systems.
Customer order - Return OrderVariant in GetCustomerOrders3 (RTC-40332)
The order variant is now stored at the order level in the database for customer orders. The GetCustomerOrders3 method in both ChainWeb Backoffice and POS Services has been enhanced to include the order variant in the response, ensuring this information is available for POS systems.
Backofficeintegrationsubscriber - Notificationsubscriberjob (RTC-55352)
The management of SignalR hub connections in the NotificationSubscriber, KitchenNotification, and FullTextReindexingNotification jobs has been refactored. Notification handling and SignalR communications are now more efficient and reliable, resulting in better overall performance and reduced risk of resource leaks. This update provides users and administrators with more stable, responsive, and consistent notification delivery.
BackOfficeIntegrationSubscriber - Notificationsubscriberjob (RTP-44056)
The management of SignalR hub connections in the NotificationSubscriber, KitchenNotification, and FullTextReindexingNotification jobs has been refactored. Notification handling and SignalR communications are now more efficient and reliable, resulting in better overall performance and reduced risk of resource leaks. This update provides users and administrators with more stable, responsive, and consistent notification delivery.
OrderSubmitter (BackOfficeIntegrationSubscriber) failing on empty orders (RTP-49104)
OrderSubmitter no longer throws an exception when processing customer orders where all lines have been deleted. Empty orders are now skipped with a warning, and the job completes normally alongside any valid orders in the batch.
POS Replication Setup (RTC-52787)
The Activation log is correctly stored and displayed, also the 'Activate Subscribers' button is enabled, after each operation - activation performed on Subscribers.
Improved availability of invoice logos through caching (RTC-54462)
Store logos are now correctly displayed on invoice PDFs.
Fix: Documents in stores with no logo (RTC-58714)
PDF documents are rendered correctly for stores with no logo set.
Chain Web 2.10.411
Released 10 April 2026
Version requirements can be found in this Jira: (RTC-58208)
Backofficeintegrationsubscriber - Notificationsubscriberjob (RTP-44056)
The management of SignalR hub connections in the NotificationSubscriber, KitchenNotification, and FullTextReindexingNotification jobs has been refactored. Notification handling and SignalR communications are now more efficient and reliable, resulting in better overall performance and reduced risk of resource leaks. This update provides users and administrators with more stable, responsive, and consistent notification delivery.
Chain Web 2.10.423
Released 4 March 2026
Version requirements can be found in this Jira: (RTC-57060)
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.
Chain Web 2.10.422
Released 2 February 2026
Version requirements can be found in this Jira: (RTC-56173)
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.