Subject: | Increase Loyalty discount percentage to 4 decimal places |
Summary: | A customer requirement is to give a 1cents discount on a unit price of $2.50. We can achieve this by using a loyalty discount and providing a discount by total value. Example 1: - Product Diesel, Unit Price : $2.50, Customer Loyal Discount is 1cents per liter.
- We can use loyalty discount by total based on the formula: (Discount Amount / Unit Price ) x 100. See figure 1 below.
Figure 1: Test Plan and Example of Loyalty % to achieve discount by quantity.
Product | Qty | UnitPrice | Total | DiscountbyQty | DiscountedUnitPrice | LineTotal | LoyaltyDiscount% | LoyaltyDiscountTotal | Variance |
D0001 - Diesel | 1 | 2.61 | 2.61 | 0.01 | 2.60 | 2.60 | 0.3831 | 2.60 | 0.000 |
D0001 - Diesel | 56.879 | 2.61 | 148.45419 | 0.01 | 2.60 | 147.89 | 0.3831 | 147.89 | 0.000 |
D0001 - Diesel | 1000.876 | 2.61 | 2612.2864 | 0.01 | 2.60 | 2602.28 | 0.3831 | 2602.28 | -0.001 |
D0001 - Diesel | 5000 | 2.61 | 13050 | 0.01 | 2.60 | 13000.00 | 0.3831 | 13000.01 | -0.005 |
Change Required: - In Menu Point of Sale>>Loyalty Maintenance, increase the discount to show 4 decimal places.
- Increase loyalty discount calculation to use 4 decimal places.
|
Audit Notes: | Edited by sanjay on 28/04/25 14:33. Edited by sanjay on 03/04/25 11:24. Edited by vineet on 01/04/25 15:07. |
03 Apr 2025 | 11:24AM Comment 1 by Sanjay (Link Technologies) Case L13132 added to project 15.70 |
23 Apr 2025 | 11:49AM Comment 2 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 02-05-2025 10:22 AM Time Taken: 8.00 Notes: ETC extended from: 01/04/2025 to 02/05/2025 |
| PART A - Development work for this case has been completed. 1. The change will be available in version: 15.61.250423 2. The following changes were made (Include Database object names, Program classes, and any other relevant information): - Changed Loyalty Discount (Menu: Point of sale ~> Loyalty Maintenance") from 2DP to 4DP
- Changed calculations to use 4DP in discount calculations
3. Affected Areas: - Changed Loyalty Discounts to allow 4DP in discount calculations
4. The issue was caused by: - Allow more granular discounts to Loyalty calculations
5. Other Relevant Notes: 6. Next Step (Review and System Test (Developer) -> UAT (Quality) -> Documentation): UAT |
|
24 Apr 2025 | 02:32PM Comment 3 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 02-05-2025 02:11 PM Time Taken: 1.00 |
| Additional Changes requested: - When customer code is changed to "CASH" from UTILITY MENU, loyalty discouts should be removed
- When Fleet case is applied, the customer is changed, therefore, Loyalty Discount should be applied
|
|
24 Apr 2025 | 03:56PM Comment 4 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 02-05-2025 03:54 PM Time Taken: 7.00 |
| PART A - Development work for this case has been completed. 1. The change will be available in version: 15.70 2. The following changes were made (Include Database object names, Program classes, and any other relevant information): - When the customer is changed to "POSCASH" from the "utilities" menu, we reset the Discounts
- When the FLEET card is scanned, we change the customer and apply any LOYALTY discounts the customer might have
3. Affected Areas: - POS Loyalty and Fleet card scan functions
4. The issue was caused by: - Change Request
5. Other Relevant Notes: 6. Next Step (Review and System Test (Developer) -> UAT (Quality) -> Documentation): UAT
|
|
25 Apr 2025 | 08:48AM Comment 5 by Vineet (Link Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 06-05-2025 12:00 PM Time Taken: 1.00 |
| Bula Sanjay Further to our meeting yesterday, please follow the steps below for testing. - Load the fuel transaction.
- Scan the fleet card.
- Enter the mileage and PIN
- When all is valid, the loyalty discount should apply
Note: This will be a cash sales transaction. The discount is only offered for Cash Sales Loyalty Card and Fleet Card must be scanned as the last step. Discounts will be applied to items scanned BEFORE the card is scanned, NOT after. This is to prevent cashiers from scanning the card and allowing other customers to take advantage of discounts after the customer has left Figure 1: Test Plan and Example of Loyalty % to achieve discount by quantity.
Product | Qty | UnitPrice | Total | DiscountbyQty | DiscountedUnitPrice | LineTotal | LoyaltyDiscount% | LoyaltyDiscountTotal | Variance |
D0001 - Diesel | 1 | 2.61 | 2.61 | 0.01 | 2.60 | 2.60 | 0.3831 | 2.60 | 0.000 |
D0001 - Diesel | 56.879 | 2.61 | 148.45419 | 0.01 | 2.60 | 147.89 | 0.3831 | 147.89 | 0.000 |
D0001 - Diesel | 1000.876 | 2.61 | 2612.2864 | 0.01 | 2.60 | 2602.28 | 0.3831 | 2602.28 | -0.001 |
D0001 - Diesel | 5000 | 2.61 | 13050 | 0.01 | 2.60 | 13000.00 | 0.3831 | 13000.01 | -0.005 |
Thanks Vineet Ram 222 0085 |
|
01 May 2025 | 10:48AM Comment 6 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 09-05-2025 10:10 AM Time Taken: 2.00 |
| *** Skype Discussion *** Morning Vineet, with Loyalty Discount, It feels a bit odd that we are asking for the card to be scanned at the end. I think it should be scanned any time during the sale, even before. Your thoughts?
I noticed it here at big supermarket chains, they let you scan any time during the sale |
|
01 May 2025 | 04:09PM Comment 7 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 09-05-2025 04:07 PM Time Taken: 8.00 |
| PART A - Development work for this case has been completed. 1. The change will be available in version: 15.62 2. The following changes were made (Include Database object names, Program classes, and any other relevant information): - Changed Fleet Card to apply Loyalty Discount if the customer has loyalty assigned
- Fleet Card can be scanned at any time. Items added after the loyalty card scan has Loyalty Discount applied
3. Affected Areas: - Fleet Card and Loyalty Discounts
4. The issue was caused by: - Feature change/Add
5. Other Relevant Notes: 6. Next Step (Review and System Test (Developer) -> UAT (Quality) -> Documentation): UAT
|
|
01 May 2025 | 04:09PM Comment 8 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 09-05-2025 04:09 PM Notes: ETC extended from: 02/05/2025 to 09/05/2025 |
| Changed to UAT |
|