Release Notes 11/2025
Updates Related to Customer Handling
This software release contains a number of new features and improvements to existing features to facilitate customer handling both in the Back Office, POS, as well via API.
Custom Identifiers for Customers
In addition to the default identifiers in Solteq Commerce Cloud, you can now create custom identifiers which can be added to customer profile information.
You can view and manage customer identifiers in the Customer Identifiers view of the Back Office. To access the view, click Customers in the Back Office menu, and select Customer Identifiers.

Customer Identifiers view (example)

Settings for a new customer identifier
For more information, see Customer Identifiers.
Changing Company Customer’s Tax Code
You can now change company customer’s tax code in the Back Office, if needed.
You can only change the tax code if the Validate tax codes for company customers setting is not enabled in Company Configurations | Settings.
Click Edit to edit the tax code (as well as other details as needed).

Editing the Tax Code of a Company Customer
Click Submit to save your changes.
Extended Customer Search in POS
POS users can now search for customers in POS using any the following criteria:
Name (First, Last and Company Name)
Phone number
City
Postal code
Customer Identifier
If the Type of the identifier is Number, you can use just one character as the search criteria.
Email
Tax code

Customer search fields
The same search criteria (with the addition of Reference) can also be used in Parked Orders.
This feature can be used if the Use extended order park search on POS setting has been enabled in Company Configurations.
Press the new Find by Customer tile to display the Find Customers view.

Find by Customer tile in Parked Orders

Customer search fields in Parked Orders
Defining Allowed Products for Customers
It is now possible to limit the products that customers can buy, if needed. You can do this by defining Allowed Products in the (private or company) customer’s profile information. You can select single product(s), or product category/several categories.

Allowed products
If the customer tries to purchase a not allowed product, an error message will be displayed in POS, and the product is not added to the Basket.
Last Purchase Date in Customer Details
Customer’s last purchase date is now included in both Customers list and customer profile information (both private and company customers).

Last purchase date in Customers list
Before last purchase date and After last purchase date can also be used as filtering criteria for the customers.

Filters

Last purchase date in customer’s profile information
Additional Information in POS Customer Details
The following details are now visible in customer information in POS:
Customer’s last purchase date
Last Purchase Date is set for orders made on POS. Other applications (for example Contract Catering) do not set it.
Customer creation date
User who has added customer to Solteq Commerce Cloud
Company Customer details displayed in POS now include contact phone numbers.

Editing Customer Details in POS
Customer Details in POS now include a Go to Back Office button. When pressed, it will display the customer’s profile information in the Back Office, if the POS user belongs to a user group with Read Customers permissions. If the POS user belongs to a group with Modify Customers permissions, the user can also edit the customer profile data.
After you have changed customer details in the Back Office, press the Refresh button to display the updated information in the POS.

Go to Back Office and Refresh buttons in customer details
Editing Customers' Credit Allowed Information
You can now define in user group permissions whether the users of a particular group are allowed to
change a (private or company) customer’s Credit Allowed setting from Yes to No or vice versa
modify company customer contact details if the customer has Credit Allowed set to Yes in its details
modify (private or company) customer’s all details, if the customer has Credit Allowed set to Yes

Credit-related settings in user group permissions
Defining Regular Prices for Customers and Customer Groups
When creating price lists, you can now define that the new regular price(s) for the product(s) are only available for certain customers or customer groups: the Regular Price view contains a new section where you can select the customers and/or customer groups.

Selecting customers/customer groups for a regular price
CustomerCard support for Fast Contract Meals
CustomerCard type identifiers can now be used with FastContractMeal feature.
Preventing Anonymizing/Restricting Customers on an Open Order
Customers cannot be anonymized or restricted, if they have been assigned to an open order.
Excel Template for Importing Customer Information
Customer Excel templates for both private and company customers are now available for downloading in the Customers view. The templates can be used for importing customer data to Solteq Commerce Cloud.

Download Templates icon in the Customers view
For more information, see Exporting and Importing Customer Information with Excel.
New POS Features
Several new features are available for POS users in this software update.
Adding a Custom Note to a POS Basket Row
POS users can now add free text to a specific basket row by pressing the row and entering the test in Custom Note field. The custom note can also be included in the receipt, and will be visible in the order in the Back Office.

Adding a custom note to a Basket row
Delivery Statuses on POS Basket Rows
POS Users can now mark delivery statuses on Basket rows. You can enable/disable this feature in Company Configurations.

Enable POS Product delivery statuses setting in Company Configurations
Merge Products must be disabled in Store Configurations (separately for all Stores) in order to use this feature. If you try to enable this feature without disabling Merge Products, an error message will be displayed.

Merging products must be disabled error message
The two possible statuses and their corresponding icons are the following.
Icon | Status |
|---|---|
![]() | Ready to be delivered |
![]() | Delivered |

Setting a product to Ready to be delivered status

Changing the delivery status for multiple product rows
For more information and instructions for use, see Setting the Delivery Status for Product Row(s).
Manual Price Increase in POS
Whereas before it was only possible to create reason codes for discounts, it is now possible to create reason codes for price increases as well. In addition, the same reason code can be used for both discounts and price increases.
Only reason codes whose type is Discount or Both types can be selected for reason codes when creating a new discount.
You can create new reason codes in the Reason Codes view (formerly Discount Reasons) of the Back Office, and select whether the reason code type is Both, Discount, or Price Increase.

Reason Codes
Price increase can be manually applied in the POS if the user belongs to a user group which has Allow price increase permission.

Allow price increase checkbox in user group’s POS action permissions
When the permissions are in place, POS users can apply price increase to individual Basket rows or Basket total price by entering the price increase in amount of currency or percentage of the price, and then pressing Minus tile. The price is then adjusted accordingly.

Entering a price increase
After the appropriate reason code has been selected, the price increase is then applied to the Basket contents.

Price increase applied to the Basket contents
For more information and instructions, see Applying a Product-Row Specific Price Increase and Applying a Price Increase to the Basket Total Price.
Reason Code POS Display Improvements
Visual improvements have been made to the POS UI in regards to the reason code selection for both discounts and price increases.

New Choose reason code window
Changes Related to Order Parking
Parking Partially Paid Orders
It is now possible to park orders which have been partially paid (one or more rows). This feature can be used for orders coming from an external interface (such as webshop) which may contain paid rows, for example.
If an order has been partially paid, it can be modified only after the payment has been removed.
This feature needs to be separately activated by Solteq. Please contact Solteq Customer Service for more information.
Blocking Parking Orders without a Customer
It is now possible to prevent parking orders in the POS if an customer has not been selected for the order. You can enable/disable this feature in Company Configurations.

Block parking orders without a customer setting in Company Configurations
When the setting has been enabled, the error message below will be displayed in POS if you try to park and order without an customer,
Error message
Cash Settlement-Related Updates
Bank Import Form
It is now possible to generate a bank import form which can be attached to cash deliveries which will be delivered to the bank. To use this feature you must enable Use bank import form in Settlements.

When Bank Import form has been activated, and POS user presses Accept after finalizing the daily cash settlement, a separate PDF document is generated.
Cash Breakdown Schemes
To facilitate Daily Cash Settlements, you can define a cash breakdown scheme for the main currency in Currency view of the Back Office.

Cash breakdown scheme example

Cash breakdown scheme in POS
Support for New Devices
With this software release, new types of devices can be taken into use with Solteq Commerce Cloud.
POS/FCM App Info Light
You can configure POS info lights into use in Workstation Configurations. They can be used with
the regular POS functionality to inform your customers about the state of the POS (closed or available), or
with the Fast Contract Meal app to indicate whether the Fast Contract Meal payment was successful.
One info light per workstation can be used at a time. Solteq Commerce Cloud currently supports using Kuando Busylight Omega devices.
Example videos below.
POS
FCM App
For more information and instructions, see Configuring POS/FCM Info Lights and POS Info Lights.
Zebra Shelf Label Printer
Solteq Commerce Cloud supports printing shelf labels with Zebra Link-OS label printers which contain a wide range of features and options. The printers are connected wirelessly to Solteq Commerce Cloud; you can activate shelf label printing from any location you wish, using Back Office via a web browser.
https://youtu.be/BgQRJ8olzRchttps://youtu.be/G6N2usfsG-4https://youtu.be/CyUQDQkWNfc
For more information, see Configuring Zebra Shelf Label Printers for Solteq Commerce Cloud Usage and Printing Shelf Labels with a Zebra Printer.
Allow Giving Discount on the Cheapest Product in Advanced Buy X Get Y Discount
When creating Advanced buy X get Y type discounts, you can now define that the discount will be applied to the cheapest product: when creating the discount, select the Give discount from the cheapest product checkbox in the discount settings.

Give discount from the cheapest product checkbox
New Service Industry Related Functionalities
This release contains a number of new features to facilitate providing various services such as laundry services, or (garment, shoe, bike, electronics…) repair services to your customers. These features are available when Services have been enabled in Company Configurations, and the Back Office users have been given the required permissions.
Create Method Codes and Place Codes
When the feature has been activated, the new Services menu item is added to the Back Office menu. It also contains Method codes and Place codes subitems.
You can add new method codes corresponding to service methods, as well as modify and delete existing ones in the Method Codes view of the Back Office.

Service Method codes (example)
For more information and detailed instructions, see Method Codes.
In addition to Method Codes, you can create Place Codes corresponding to service facilities, as well as modify and delete existing place codes in the Place Codes view of the Back Office. When you add a new Place Code, you must also define the amount of time it will take to complete the order: That is, when the customer can collect their items after dropping them off.

Service Place Codes (example)
For more information and detailed instructions, see see Place Codes.
Service Information in Product Settings
When method codes and place codes are in place, you use them to define default service information for an individual product (such as Suit Cleaning) in its settings.

Services settings in Product Details
Services View
In the Services view of the Back Office you can define settings for individual drop-off service locations.

Services view (example)
The following details can be defined:
Store used as the drop-off location.
Available Products (services available in the location.
If needed, you can also change the Method and Place Codes for these products for the purposes of this particular location.
If needed, the delivery times defined in Place Code settings can also be modified for the purposes of this particular location.

Service drop-off location settings (example)
For more information and detailed instructions, see Services
Tagging
By using the new Tagging feature, POS Users can add tags to the various items (shoes, garments, bikes, electronic devices etc.) that customers drop off to the Store.
In order to use this feature, Tagging must be enabled in Company Configurations and a separate Add tag tile must have been added to the POS layout.
Tags can be added to Basket contents after you have added all the products into the Basket. It is also possible to add tags first, and then add the products to the Basket.

List of tag numbers entered for the Basket
When an order containing tags has been parked, the order can be found using tags as search criteria.

Tag in the Parked Orders search filters
For more information and instructions, see Tagging.
Category Name Updates to Product Information
When changing the name of a category, the name change will now be reflected also in products/stock items which have the category already assigned to them.
Danish Language Support for Kiosk
Danish translations are now supported in Kiosk.
Customers can select Danish as a language from the top-right corner language selector in the Kiosk screen.
Danish translations are displayed for static UI texts, including buttons, dialogs, basket summary, and payment flow.
Danish translations for product names and descriptions are displayed, if defined in the product details.
Danish translations can be configured for messages in the Kiosk Service settings, including "Order ready" message and "Order" button.
Importing Danish translations in Translations view is yet supported.
API Updates
See https://apimanual.solteqpos.com/arn/release-notes-30-10-2025 for the latest updates to the Solteq Commerce Cloud API documentation.
Other Improvements and Fixes
Variant products whose variants have SKU identifier defined for them can now be sold even if Stock Handling is not in use.
Corrected the problem which appeared when the VAT percentage of a variant product was changed after a new stock item linked to the variant product had been created using a transaction order. If the purchase price was changed in the following transaction order, the VAT percentage information of the stock item was lost, and this was also updated to the selling product info.
The problem did not reappear when the stock item VAT was updated to the correct value on the stock item, and did not occur when the stock item was created by using the Excel import function for the transaction order.
Corrected the following problem: When partially refunding an order that had discount on it, no discount was applied. This resulted in the refund being a bigger sum than the original sum.
Corrected the following problem related to custom products: When the quantity of an extra ingredient was changed in POS, a new row appeared in the Basket resulting in multiplied (and also incorrect) information for this custom product.
Corrected the problem which caused that when a customer was added to the Basket and gift card was used as the payment method, information about such customer was not actually linked to the order and was not present on the receipt, or included in the Back Office order details.

