Document status: RELEASED
Date:
Prerequisites are located in the menu on the left.
Print cancelled payment transactions on separate receipt
Cancelled payment transactions of type CreditDebit, i.e. pay terminal payments and mobile payments, may now be printed on a separate receipt (configurable). This will make the printed sales receipt shorter and easier to understand for the customer.
Improvements POS
Area | Description |
|---|---|
| Kivra gateway | Changes in Kivra receipt (RTP-22256) Made changes in text linked to discount on item lines. This to better reflect the type of discount given. |
| Loyalty | Improvements in loyalty header in sale view (RTP-22491) POS will now display the members mobile phone number in the loyalty header in sale view when a mobile number is registered in Voyado. If the mobile number is not registered in Voyado the text "Missing" will be displayed. Previously the text "Don't ask" was displayed even if the mobile phone number was fetched from Voyado. A change has also been made to the member level displayed in the loyalty header. The member level is displayed even if the member has been edited in POS. Previously the member level would disappear from the loyalty header for the active transaction if the cashier edited the member. Personal data lookup from Bisnode through Voyado integration (RTP-22475) When creating a new member in POS, we are now using the correct country code when doing the lookup for personal data in Bisnode through Voyado, Previously the country code was hard coded to 'NO' causing the lookup for Swedish social security numbers to fail. When creating a new member in POS, we are now using the correct country code when doing the lookup for personal data in Bisnode through Voyado, Previously the country code was hard coded to 'NO' causing the lookup for Swedish social security numbers to fail. New member registration (RTP-22170) Member identifier copies correctly from search dialog to registration dialog for new member. Adding member to receipt in Self-service (RTP-21971) A problem was fixed with adding member to receipt in self-service when using the new Voyado integration through POSCustomerService in EG Cloud. (POS now supports adding members to a receipt in self-checkout (SCO) even if the 'SupportedMemberLookupIdentifiers' type in PosCustomerService is set to type 'any'. Previously the member search in SCO used 'Mobile' as identifier even if this was not configured in PosCustomerService. This caused the member search to fail.) |
| PLU List | Page up and Page down buttons (RTP-21826) Page up and Page down buttons are now shown in PLU List when added to function set. |
| Price calculation | Combination of coupon with mixtype 1004 and Stampcard (RTP-21843) Combination of a digital coupon using mixtype 1004 and stamp cards has been improved. The mix will now always trigger, regardless if the stamp card gives a free item or not. And all Stampcards will create a stamp. |
| User interface | FullHD resolution improvements (RTP-20440) FullHD resolution (1920x1080) improvements have been implemented in item search detail view, PLU List and buttons with images. |
Improvements POS Server
Area | Description |
|---|---|
| POS API Cloud | SetDigitalReceipt can fail running on multiple instances (RTP-22840) A problem that could cause SetDigitalReceipt to fail when POSAPI is running on multiple instances has been fixed. Incorrect configuration used when refunding payment (RTP-22888) An issue that could cause incorrect configuration to be used (in this case when refunding payment) has been fixed. The problem happened when editing the cart from a different POS API instance (using multiple instances in cloud or multiple installed instances of POS WCF on-prem). Incorrect configuration used when editing cart (RTP-21705) An issue that could cause incorrect configuration to be used when editing a cart has been fixed. The problem happened when editing the cart from a different POS API instance (using multiple instances in cloud or multiple installed instances of POS WCF on-prem). |
| POS API on-prem | Incorrect configuration used when refunding payment (RTP-22888) An issue that could cause incorrect configuration to be used (in this case when refunding payment) has been fixed. The problem happened when editing the cart from a different POS API instance (using multiple instances in cloud or multiple installed instances of POS WCF on-prem). Incorrect configuration used when editing cart (RTP-21705) An issue that could cause incorrect configuration to be used when editing a cart has been fixed. The problem happened when editing the cart from a different POS API instance (using multiple instances in cloud or multiple installed instances of POS WCF on-prem). |