PosCustomerService now support new provider 'Hybris' for fetching member info to POS. The integration can search for members via mobile phone number or member id.
Existing parameter 'LoyaltyHeaderInSaleView' should be configured to show only relevant information for the cashier. Available values from Hybris is 'MemberNumber, 'MemberName', MemberEmailAddress' and 'MemberMobileNumber'
Existing parameter 'CustomerViewSetupWhenLoyalty' should be configured to show only relevant information for the cashier. Available values from Hybris is 'LoyaltyNumber', 'CustomerFirstName', 'CustomerLastName', 'CustomerEmailAddress' and 'CustomerCellphoneNumber'.
Improvements POS
Area
Description
Bank integration
Bank Integration - POS opens for card to be read/scanned twice (RTP-29298)
Changed that EndOfSale towards payment terminals is not run in special cases.
Order
Fixes for SMS notifications for click and collect orders (RTP-29418)
The following fixes were introduced:
If SmsENewCustomerOrderReadyToCollectTemplate is setup with a value in POS Configuration, SMS will be sent using the template right after picking is completed or registered. If this parameter is left blank, no SMS notification will be sent.
If SmsENewCustomerOrderExpiredTemplate is setup with a value in POS Configuration, SMS will be sent using the template right after the order expires. If this parameter is left blank, no SMS notification will be sent.
If SmsENewCustomerOrderDeletedTemplate is setup with a value in POS Configuration, SMS will be sent using the template right after the order deleted in POS (both before and after picking is completed). If this parameter is left blank, no SMS notification will be sent.
Required
POS Master v. 3.0.0.148 or higher. Chain Web 2.10.286 or higher (with Lindbak Retail Database 2.10.0.79 or higher).
This integration replaces the old integration EG POS has for Ruter, Paygoo, and EnTur.
Price calculation
Improvements in price calculation for mix types with effect items (RTP-26452)
Improvements has been made to price calculations in POS to ensure faster calculations for mixtypes with effect items. Example mix types that use effect items are: 4, 5, 6, 8, 10, 13, 27, 30, 31, 33, 35, 39 and 41.
Improvements in price calculation performance (RTP-27379)
Generic improvements has been made to performance of price calculations in POS. Some mixtypes will be significantly faster than before with many items in the mix/receipt.