Chain Web 2.10.492
Released 30 October 2026
Version requirements can be found in this Jira: (RTC-64873)
Customer import improvements (RTC-64464)
Imported customers with address containing invalid or empty country code are saved with default country based on (DefaultCountryCodeWhenCreatingCustomerAddress system parameter, NO by default, please check if its correct per customer/ environment).
Customer language included in customer order exports (RTC-60103)
The customer's preferred language and the language of the product texts are saved on each customer order registered at the POS and included in all picking order exports, so customer notifications can be sent in the right language. If no language is registered on the order, the language fields in the export are left empty.
Invoice wizard improvements (RTC-64569)
In the invoice wizard, displaying a preview of selected invoice proposals no longer results in an error.
In the invoice wizard, creating invoices from invoice proposals no longer results in an error.
Picking order processing (RTC-62632)
Dispatch orders are created for new customer orders even when many other orders are on hold. An order is held back only while an earlier change to that same order has failed or is waiting to be retried, so each order's changes are applied in the right order.
IMPORTANT:
Minimal required SQL Server version: 2016!
DispatchOrders - Some orders are not possible to finish in POS (RTC-62309)
Pay-and-collect orders delivered from the central warehouse can always be found when scanned in POS at the pickup store, so staff can hand the goods to the customer, and orders that were stuck can be completed. Picking orders with nothing for the store to pick do not show in the store's picking list, and if staff try to reject a pickup order in a way that would leave the store with nothing to hand out, a message explains why this is not allowed.
DispatchOrders - Paid and delivered status keept regardless of the order in which these actions are used (RTC-61759)
Fixed an issue where a dispatch order reverted to unpaid after using "Set as paid" followed by "Set as delivered". The paid and delivered states are now kept regardless of the order in which these actions are used.
Remove items from delivered dispatch order lines (RTC-62158)
Support users can again remove an item from a delivered dispatch order line using "Remove Item (Support)" in the line's drop-down menu.
Customer order cleanup improvements (RTC-59514)
The performance of removing old customer orders is improved.
The order structured notes are correctly removed during cleanup.
Fixed-price transactions from invoice plans (RTC-63968)
Create fixed-price transactions creates one credit sale for each invoice plan line that is due. The number of sales matches the number of plan lines, even when the user who runs the function has more than one active cashier profile in the same store group. Each customer gets one invoice for each plan line.
Before the system creates a sale for a plan line, it checks the status of the line again. If the line is not "Not invoiced" at that point, the system skips it and moves on to the next line.
Customer updates reported as failed even though they were saved (RTC-60338)
Customer updates sent from Chain Web to Chain Classic could show as failed in the job log, even when the change had already been saved in Chain Classic. This happened when the Chain connection dropped while the job was closing.
The integration now handles this case. A completed customer update is no longer reported as failed. Customer updates sent while Chain Classic is unavailable are also retried and applied once it is back.
Improved reliability of automated campaign processing (RTC-59800)
Automated campaign processing uses an optimized database query to check member distribution limits. This reduces the risk of SQL timeouts that can cause the campaign job to fail and interrupt the generation of member coupons and campaign distributions.
Payments not reaching Chain Classic when the Chain connection drops (RTC-62879)
If the connection to Chain Classic was lost just as a payment was being sent from Chain Web, the payment could fail and was not retried. It never got registered in Chain Classic.
Now the integration retries the payment automatically and registers it once Chain Classic is available again. Each payment is registered only once. If Chain Classic stays unavailable after all retries, the job fails as before and the message is kept for follow-up.
Stocktaking cleanup - old stocktaking’s with pending results will be removed (RTC-54170)
The stocktaking cleanup job failed on stocktaking’s that still had pending stocktaking results, so those stocktaking’s were never deleted and the job kept failing. The job now removes pending results and basis requests along with the stocktaking. Stocktaking’s that failed in earlier runs are cleaned up on the next run after the upgrade.
Notification for delayed Chain updates now shows as a warning RTC-62879)
While a payment or customer update is waiting to be retried because Chain Classic is unavailable, the Chain Web notification now shows as an orange warning. Before, it was teal, which looked like a success. If the update still fails after all retries, the notification turns red. You get one notification for all retries, not one per attempt.
Chain Web character encoding issue (RTC-63827)
Swedish special characters (å, ä, ö) in product names, product groups and other product data (such as brands, manufacturers and suppliers) were in some cases shown incorrectly in Chain Web, while they were correct in Chain Classic. This has been fixed for all product data received after the update.
Products that are already shown with incorrect characters are corrected the next time they are updated.
StocktakingBasisProcessor / BackOfficeIntegrationSubscriber (RTC-63746)
Fixed an issue where a stocktaking could get stuck with status "Awaiting basis" and never become active. This happened when the stocktaking basis contained items that don't exist in the item register, and the first attempt to process the basis did not finish. Every later attempt then failed the same way, and the stocktaking stayed blocked until it was cleaned up manually. The retry now completes, and the stocktaking becomes active as expected.
StoreMerger improvements (RTC-63041)
LocalStoreNumber is correctly updated for existing stores.
Removal of all related stores for a store is handled correctly.
StoreMerger no longer creates duplicates if related store is created in the same processing batch.