Chain Web 2.10.482
Released 28 September 2026
Version requirements can be found in this Jira: (RTC-63613)
Freight lines on Pay & Collect and Click & Collect orders (RTC-63609)
Chain Web supports customer orders that contain a freight (shipping charge) line. When a Pay & Collect or Click & Collect order has a freight line, the picking order is created in the picking store as normal, and the freight line is stored on the order with the article type Freight.
Chain Web 2.10.481
Released 22 September 2026
Version requirements can be found in this Jira: (RTC-63269)
Required: Integration Platform 3.1.1
Improvements in Chain Web
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.
Picking order export extended (RTC-57390)
Exported picking order data now carries full price and tax details, the discounts applied to each item, the payment methods used with their amounts, and a delivery tracking link for each item. This gives receiving systems everything needed for customer messages, delivery follow-up and payment reconciliation without looking up the order again.
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.
Order Message Integration package 1.18.0 (RTC-63481)
A new version of the Order Message Integration package is available. It works with the AMQP-based Service Bus connection, so order messages to customers keep being generated and sent after the retirement of the old Service Bus protocol. Each order message request is processed once, and a message that repeatedly fails is still set aside for manual follow-up instead of blocking the queue. Functionality is unchanged.
Install Order Message Integration package v. 1.18.0 before upgrading Integration Platform to 3.1.1. The package works with both the current and the new Integration Platform version.
SAFT receipt export package 1.2.0 (RTC-62964)
A new version of the SAFT receipt export package is available. It works with the AMQP-based Service Bus connection, so the SAF-T audit file export keeps running after the retirement of the old Service Bus protocol. Each export request is handled once, and exports covering a long date range complete without restarting from the beginning. The content of the exported file is unchanged. Deployment requires Integration Platform 3.1.1.
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.
BackOffice Batch Generator package 1.12.0 (RTC-63324)
A new version of the BackOffice Batch Generator package is available. It works with the AMQP-based Service Bus connection, so event-triggered generation of customer, store, store group and picking order batches keeps running after the retirement of the old Service Bus protocol. Each incoming message is acknowledged once, so batches are generated as expected without being reprocessed or left unhandled. The generated batches are unchanged. 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
Improvements - InStore App on-prem
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.
"Pending arrival" status removed in Order Picking after goods receival increases available quantity (RTC-62824)
Order Picking now automatically re-evaluates a picking order's status once the available-quantity job runs after a goods receival, moving the order from Pending arrival to To be picked as soon as enough stock is available. This happens automatically, with no manual action needed from the user.
Improvements in Loyalty
Loyalty Campaign package 2.14.0 (RTC-63368)
A new version of the Loyalty Campaign package is available. It works with the AMQP-based Service Bus connection, so campaign management, member event handling and winning variant processing keep running after the retirement of the old Service Bus protocol. Each request is processed once, so members receive their campaign messages once and scheduled runs finish instead of stalling. Functionality is unchanged.
Install this version before upgrading Integration Platform to 3.1.1. The package works with both the current and the new Integration Platform version.
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.
MailChimp integration package 2.10.0 (RTC-63369)
A new version of the MailChimp integration package is available. It works with the AMQP-based Service Bus connection, so the export of member segments and newsletter subscriptions to MailChimp keeps running after the retirement of the old Service Bus protocol. Each export request is processed once, so members are synchronized once and scheduled runs finish instead of stalling. Functionality is unchanged.
Install this version before upgrading Integration Platform to 3.1.1. The package works with both the current and the new Integration Platform version.
Apsis marketing integration package 1.12.0 (RTC-62965)
A new version of the Apsis integration package is available. It works with the AMQP-based Service Bus connection, so campaign distributions and member updates sent to the marketing solution keep running after the retirement of the old Service Bus protocol. Each batch is handled once, also when a large batch takes a long time to process. Functionality is unchanged. Deployment requires Integration Platform 3.1.1.
Bonus Voucher Distribution package 2.3.0 (RTC-63367)
A new version of the Bonus Voucher Distribution package is available. It works with the AMQP-based Service Bus connection, so bonus voucher calculation, voucher distribution and automatic bonus rollouts keep running after the retirement of the old Service Bus protocol. Each request is processed once, so members receive their vouchers once and scheduled runs finish instead of stalling. Functionality is unchanged.
Install this version before upgrading Integration Platform to 3.1.1. The package works with both the current and the new Integration Platform version.
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.
Payment time included in the picking order export (RTC-58739)
The time a payment was made at the POS is now read from the receipt and stored with the order. Connected systems receive it through the extended picking order export delivered with RTC-57390, so they can show or reconcile when the customer actually paid. No configuration or user action is required.
Chain Web 2.10.480
Released 15 September 2026
Version requirements can be found in this Jira: (RTC-62705)
Deactivation of users removed in the cloud
Users that are no longer active in the cloud (marked ‘Inactive’ or ‘Deleted’) are now automatically deactivated on-prem when the import runs. Their account is locked and all of their cashiers are set to Inactive, so access is removed without any manual intervention. Users who remain active are unaffected.
Automatic language and region
The user's language and region are now brought in from the cloud export and applied on-prem automatically, so they no longer need to be set by hand:
Language controls the user interface language. Supported languages are English, Swedish, Norwegian and Finnish. Any other language is left as-is.
Region controls date, number and currency formatting. Supported regions are Norway, Sweden, Finland, Denmark, United Kingdom and the United States.
If an export does not include a language or region, the user's existing setting is kept — nothing is cleared or overwritten. Imports that don't carry these values continue to work exactly as before
Payment for Pay & Collect orders is captured once the full order is delivered
For Pay & Collect orders, payment capture waits until every order line has reached Delivered status, including lines where the ordered quantity was reduced to match a short picked delivery. Capture then starts automatically without a separate payment step, so the customer is charged once for the completed order instead of being charged in stages as items are picked up.
POS Configuration:
“CaptureOnFullDelivery” should be enabled for stores using this flow.
Improvements
Accounts receivable (RTC-61797)
The invoice wizard checks a user's store access before showing invoice suggestions, generating previews, or creating invoices. A user sees and manages receipts and customer invoices only for the stores assigned to their account.
If a user tries to invoice or preview receipts from a store outside their access rights, the system blocks the action and shows a message stating that the store is not accessible. This applies to single invoices, previews, customer lookups, and multi-selected batches of receipts — a batch containing even one receipt from an unauthorized store is rejected in full, so no invoices from that batch are created.
Customer groups are not regenerated when Customer price rules are modified or new items are added (RTP-50916)
When you add, change, or remove a price rule for a customer group's discount setup, Chain Web updates the group's Modified date and sends the update to POS.
BackOffice reports fail to load due to duplicate recently used tracking entries (RTC-62464)
Recently used reports should not been saved as a duplicates in the database, therefore should not fail when entering the report.
Export of shipping status (RTC-58354)
Picking order export files carry the shipping status of each ordered item, such as sent to store, received at store, or sent to the customer. Retailers pass this on to their notification service so end customers stay informed about where their order is on its way to them.
Finish a partially delivered dispatch order (RTC-55707)
Authorized support users finish a dispatch order directly from the dispatch order details, even when some items are still waiting to be picked. Finishing the order completes picking for the delivered items and generates the customer receipt.
Mark dispatch order items as delivered (RTC-55715)
Support users can mark a single line, or every line on a dispatch order at once, as delivered directly in the Dispatch Order view. The action is available only to authorized support roles and updates each line's delivered quantity.
Web orders - Retry a failed return/refund payment (RTC-57073)
If the payment step of a return or refund on a web order fails, the order is no longer left stuck. The line changes are kept, the order stays open, and a Retry Payment button lets the operator re-run the payment once the issue is resolved. On success the order completes and the credit is registered; on failure it stays flagged so it can be retried again.
Note: the Retry Payment button is available only to HQ users whose role has the new "Retry pending action" permission.
Support functions in configuration mode (RTC-58963)
Extended support actions on dispatch orders, such as setting items as picked, delivered or paid, removing items and finishing incomplete orders, stay hidden until an administrator switches them on in configuration mode. Each action is enabled separately as either fully usable or read-only, and users also need the matching support permission to see it.
Fix configuration in Chain Web to fetch PDF receipts from Receipt Service (RTC-58522)
Obsolete settings (‘AuthorityUrl’, ClientId, ClientSecret) are removed.
Chain Web system parameters “BaseUrl” and “TenantId” remain.
Fix: Audit information in customer orders (RTC-60697)
The audit information (Last modified) in customer order details is displayed correctly.
Improvements - Loyalty
Loyalty campaign cleanup (RTP-50030)
Campaign cleanup completes successfully when removing expired campaigns. Related campaign data is cleaned up correctly, preventing cleanup failures while preserving offers that belong to active campaigns.
Send test newsletter in Marketing distribution (RTC-59892)
Users can send a test version of a newsletter to a chosen email address before starting the full distribution. This makes it possible to check content and formatting in advance, helping to ensure accurate previews and reduce errors in campaigns.
Improvements - InStore App on-prem
Received goods automatically made available for picking (RTC-61066)
Quantities registered on a goods receipt are now automatically added to the available quantity on the matching customer picking order line, per item and per customer order. This keeps the picking process aligned with what has physically arrived, so orders can be picked as soon as the goods are on hand without any manual follow-up. The job runs on a scheduled basis as part of the standard on-prem installation, so no configuration or user action is required.
Orders removed from picking list after full replacement (RTC-60854)
Once all items in an order are fully replaced and the replacement process is completed, the order is now automatically removed from the order picking list of the specific store. This gives store staff an accurate view of only the orders that still require picking.