Chain Web 2.10.471
Released 22 September 2026
Version requirements can be found in this Jira: (RTC-63360)
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.470
Released 18 June 2026
Version requirements can be found in this Jira: (RTC-60150)
Store data sync from POS Master
A new periodic job "PosMasterStoresToStaging" in the BackOfficeImport package. It syncs store data from the POS Master database to Retail. The job detects changes using IdentityTime tracking across stores, contacts, and store groups, then maps the data to the StoreService contract and writes it to staging tables for processing by the existing store import pipeline.
Prerequisites:
Chain Classic must be the master for stores.
Store and StoreGroup SSIS packages must be disabled - this job replaces them
Key behaviors:
Full initial sync on first run, incremental sync on subsequent runs.
Maps store fields (name, store numbers, address, contact info, open/close dates).
Embeds Team, Profile, and Region group assignments in store events.
Links related stores.
Falls back to Profile StoreGroup country code when contact country is empty.
Deactivates stores no longer assigned to any store group.
Completes with no effect when nothing has changed.
Picking order export
Picking order exports include short-pick information, customer details, and order status. Each order line contains both the quantity originally ordered and the current quantity, making it possible to identify reduced quantities during the picking process.
Exports also include customer address and contact information, such as name, customer number, mobile number, email address, postal address, and country code. Delivery address and delivery contact information continue to be included separately.
Order status is included in the export, making it easier to track the current state of an order and support customer communication and fulfilment processes.
If customer address or contact information is not available, the export is still generated with the available data.
New parameter ItemGroupRequirementConfig
New parameter called “ItemGroupRequirementConfig” has been implemented.
Thanks to it given Item groups will be allowed to be sold in given time window. If Item group is not set, it can be sold all the time.
POS Configuration
ItemGroupRequirementConfig parameter (default value: blank)
Restricts the sale of items in specific item groups to a set time window.
Improvements
Customer remarks are limited to 1000 characters (RTP-46329)
The customer remarks field in BackOffice Customer Management accepts a maximum of 1000 characters. The edit form stops input at the limit and validates the length when the customer is saved, so the limit is visible to the user while editing.
Customer updates received from integrations, such as POS or member systems, are processed even when the remarks text exceeds the limit. The text is shortened to the first 1000 characters and the rest of the customer data is saved. This ensures customer updates from external systems are applied reliably instead of being rejected.
Reliable member updates during busy periods (RTC-59126)
Member changes from Lindbak Loyalty flow through to downstream systems smoothly, even when the loyalty database is under heavy concurrent load. The integration handles brief database contention automatically and delivers pending member updates on the same cycle whenever possible, keeping member data fresh and consistent across the platform.
Automatic release of pre-orders once stock arrives (RTC-57324)
Pre-orders placed by customers stay in a holding location until inventory is confirmed at the central warehouse. As soon as stock is available for every item in the order, the order is released to the central warehouse for picking and fulfillment without manual handling.
CustomerPublisher fails for business customers with no address (RTC-58440)
Fixed CustomerPublisher failing on business customers with null or incomplete address data, preventing those customers from syncing to BackOffice.