Chain Web 2.10.460
Planned next main version
Version requirements can be found in this Jira:
New parameter to determine the status on the created Service order
The action code numbers configured in the new POS Configuration parameter “ActionCodeServiceOrder” determine if the created Service Order has status Active or Done.
POS Configuration
New parameter:
ActionCodeServiceOrder - default value: blank.
The action code numbers configured in this parameter determine if the created Service Order has status Active or Done.
Chain Web 2.10.411
Released 10 April 2026
Version requirements can be found in this Jira: (RTC-58208)
Order Picking sorting (RTM-13122)
The Order Picking view resets to the default sorting after reload, even when a different sorting is selected.
The OrderPickingDefaultSorting parameter (InStore App) defines the default sorting in the Order Picking view. Supported values are CreatedDate (default) and PickUpDate, allowing the sorting to match store workflows.
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.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.
Chain Web 2.10.441
Released 18 February 2026
Version requirements can be found in this Jira: (RTC-55619) and (RTC-56708)
Support passing query parameters customer number and store number in creation of the order (RTC-51985)
Added support for passing customer number and store number as query parameters when opening link to new customer order view. Common customers will not be supported for now.
Example:
/CustomerOrder/customerorder/neworder?customernumber=0000001097&storenumber=222
Fetch reporting parameters from service for existing subscriptions (RTC-53803)
New stores can now be added to existing report subscriptions.
Newly created stores are available for selection without recreating the subscription.
Set items as picked on picking order line (RTC-55712)
Authorized administrators or support employees with Support Dispatch Orders permission can set the picking status of a customer order line to Picked. This action is available on the picking order line and is intended for orders that are stuck in an incorrect picking status and cannot be corrected by other means.
Order message update for Norwegian returns (RTC-55581)
Norwegian dispatch email templates present correct and consistent information by removing incorrect return details and the “Vanlige spørsmål” button/link. This ensures customers do not receive misleading return information in order-related emails and reduces confusion around returns.
The change applies to the following templates:
Order confirmation,
Order sent,
Pay & Collect dispatched,
Split order,
Split order picked
Order dispatch emails – Finnish return information (RTC-54991)
Order dispatch emails for Finland present correct and consistent return information. Incorrect return details are removed, and the link behind “täällä” leads to the correct return information without changing the visible text. This helps customers understand the return process and reduces confusion when reading order-related emails.
This applies to the following email templates:
Order sent
Pay & Collect dispatched
Split order picked
Improved handling of anonymized orders in invoicing (RTC-54631)
Invoices and receipts linked to anonymized orders now work correctly. Customer data is handled safely during invoicing, crediting, and customer updates, preventing errors and ensuring proper invoice and PDF generation.
Improved availability of invoice logos through caching (RTC-54462)
Store logos are now correctly displayed on invoice PDFs.
Stocktaking - Model matrix changes are now visible immediately after saving (RTC-55493)
Previously, when editing counted quantities for multiple sizes in the model matrix, only the selected row would update in the grid. Other sizes required a page refresh (F5) to show the changes. Now all affected rows update automatically after saving.
Fetch data from new created receipt, when correcting the original one (RTC-55223)
When a credit sale is corrected, the system now ensures that the database reflects the actual recalculated prices from the new receipt, rather than carrying over potentially outdated data from the original transaction.
Export net cost with picking order line (RTC-45651)
Per unit net cost of articles on picking order line is exported with ‘PickingOrderExport’ blob type, as well as other picking order derived export types.
Fix: Merge error when two the same cashier numbers in import (RTC-55351)
Cashiers are imported on users without merging errors. When we get the pair cashierNumber, storeId for more than 1 user, we set it on the later imported user.
POS Configuration - New function in ButtonConfig to check voucher balance (RTP-39417)
It is possible to configure a button with the new function Check Voucher Balance in ButtonConfig.
Thanks to it access to checking voucher balance feature will be available after clicking a button.
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.
POS Configuration - Repair and FAQ configuration parameters (RTP-45103)
For a complaint flow functionality, we have POS Chain Web includes two configuration settings: CreateServiceOrderBaseUrl and ProductCatalogBaseUrl.
CreateServiceOrderBaseUrl defines the URL used to create service orders.
ProductCatalogBaseUrl defines the URL used to retrieve product information.
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.