Release 26 May 2026
Access Customer Group (B2C) in POS Customer Service (RTP-46740, RTP-46741)
The POS customer service includes a CustomerGroupB2C field that retrieves customer group information from Voyado. This makes it possible to access and use B2C customer group data directly in POS, supporting more accurate customer handling and segmentation.
Release 26 February 2026
Voyado Gateway Error Details in POS Customer Service Logs
ErrorCode, ErrorMessage, and ErrorContent for relevant error status codes are included in logs in Azure Application Insights. This makes it easier to understand errors and identify their cause.
Release 19 February 2026
Authentication Between UAT and Production
Authentication for Loyalty uses separate secure contexts for UAT and Production. This keeps the environments isolated and prevents authorization errors when working across environments.
Release 7 November 2025
Support for multiple loyalty programs
POSCustomerService allows retailers to manage different loyalty programs across countries, store groups, or stores without needing separate tenants. Retailers can set up to 3 loyalty programs, with the option to expand this number in the future. This provides flexibility for businesses operating in multiple regions or with varied loyalty program configurations.
POS Configuraiton
Existing POS parameter:
'LoyaltyProgramID' (default blank) - is used to specify what loyalty program to use. Values 0, 1 and 2 point to different loyalty programs or configurations configured in tenant admin. Leaving the parameter blank will default to LoyaltyProgramID = 0.
Multi-county VoyadoSupport in POS and POSCustomerService
POS supports retailers with stores in multiple countries by allowing multiple separate Voyado instances for managing customer and member data under a single tenant. POS uses 'PosCustomerService' and the new 'VoyadoGateway2' integration to connect with the Voyado Engage API. Communication is routed through the LoyaltyProgramId parameter, enabling seamless handling of members across different countries when using Voyado.
Digital receipt flag on member
Member profiles in POS now include support for digital receipt consent flag. The system stores the date when a customer agrees to receive digital receipts. This makes it possible to track consent and use it in services that rely on customer preferences for digital communication.
Searching for H&ME members using SapCRMID
Member searches in POSCustomerService using the Hybris provider now include SapCRMID. This ensures consistent search results for both H&ME and T&ME members across the Hybris integration.
Release 11.04.2024
New provider 'Hybris' added in POSCustomerService
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.
POS Configuration
Existing parameter 'PosCustomerServiceUrl' must be set to the corresponding environment TEST or PROD. Values are 'https://poscustomerservice.egretail-test.cloud/' or 'https://poscustomerservice.egretail.cloud/' respectively.
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'.
Release 21.11.2023
Trigger IDP onboarding from POS
When searching in POS by mobile phone number for a member that do not exist in the configured member master (in this instance Voyado), POS will now enable IDP onboarding of that member triggered from the unknown member dialog. For instance, if Vipps is selected as onboarding method by the cashier, POS will trigger this by sending a "performIdpOnboard" flag to PosCustomerService. A "dummy member" containing only the mobile phone number is created in Voyado, and the registration process continues in Vipps. The member is finally updated from PosCustomerService to Voyado when registartion in Vipps is completed. For the time being we only have Vipps as an option for IDP onboarding but this should work for other identity providers as well. The same goes for member masters (providers) for POSCustomerService. For the time being we only support onboarding to Voyado, but in theory this should work the same way for other providers in the future.
When searching for members from Voyado in POS where the identifier used result in multiple matches in Voyado, POS will now fetch the member with then newest member number and add that member to the receipt. This goes for both manned POS and SCO. Previously an error message was show to the cashier saying that the member could not be added because of the duplicate values in Voaydo. In self checkout no member would be added.
Release 04.09.2023
Refactored API to enable member lookups with multiple matches
POSCustomerService has been refactored to enable handling of multiple matches for member lookups. We now use the term "Contacts" instead of "POSCustomer" although the calls to the old url's will still work as before.