...
Area | Description | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| General | Payment input field cleared correctly after member search (RTP-27435) When a member is searched for by registering SSN or mobile number or member number in payment input field in payment view, this field is now correctly cleared when search is done. Previously the registered number could still be present in the field when later adding e.g. Bank tender, making the payment fail. | ||||||||||
| Loyalty | Using CompanyID that generates the best bonus when doing member lookup (RTP-27347) Logic for using the CompanyID that generates the best member bonus, if member has several memberships, now works also when parameter 'MemberCardEAN29Codes' is deactivated. | ||||||||||
| Orders | Recipient's data (RTP-27150) When creating a Web Order/Reserve & Collect Order in POS, the recipients name is shown correctly in receipts with customer information, picking lists, order confirmations, Dispatch Order screen in Chain Web, and in orders in POS. Information such as customer name, address, phone Number, and e-mail corresponds to the recipient's data.
Fix for InvalidNumberFormat error (RTP-27421) InvalidNumberFormat error message is no longer entered when Customer Orders are created or during registration of picked Reserve & Collect orders.
|