Project

General

Profile

Edit Copy Actions

Testing #8465

closed

Test the pos tax related things

Added by Sai Mahananda 10 days ago. Updated 9 days ago.

Status:
Closed
Priority:
High
Assignee:
Target version:
-
Start date:
03/30/2026
Due date:
03/30/2026
% Done:

100%

Estimated time:
4:00 h
Spent time:
Tested Date:
03/30/2026
Page/ Module (POS):
POS

Description

cehck the tax related things for entire pos page
product qoutationa


Add

Subtasks


Add

Related issues

Actions #1

Updated by Sai Mahananda 9 days ago

  • Status changed from New to In Progress

Updated by Sai Mahananda 9 days ago

test the tax related wioth discounbt percentae and amount
Title: Clarification on Discount Distribution Logic (Item-level vs Net Total)

Module: POS / Discount Calculation
Priority: Medium (Functional Clarification)


Description:

During testing of discount and tax calculation in POS, I validated the discount distribution based on item-level proportional logic.

However, the development team has implemented the discount based on net total (cart-level) as per client requirement.


Test Scenario Executed:

Products in cart:

  • Product A → $100
  • Product B → $50

Discount Applied: $10 (Flat)


My Tested Approach (Item-Level Distribution):

Discount distributed proportionally:

  • Product A → (100 / 150) × 10 = $6.67
  • Product B → (50 / 150) × 10 = $3.33

Final:

  • A → 100 - 6.67 = 93.33
  • B → 50 - 3.33 = 46.67

👉 Tax calculated per item after discount.


Current Implementation (As per Dev/Client):

  • Total = $150
  • Discount = $10
  • Net Total = $140

👉 Discount applied at overall cart level, not distributed per item.


Observation:

  • System is calculating discount on net total, not at item level
  • This impacts:
    • Item-level tax calculation
    • API response (discount may appear uneven per item)

Impact:

  • Tax calculation differences at item level
  • Difficulty in validating per-item tax from API response
  • Potential mismatch in edge cases (low-price items)

Conclusion:

Both approaches are valid:

  • Item-level distribution → Standard accounting/tax accuracy
  • Net total discount → Implemented as per client requirement

Request:

Please confirm:

1. Whether item-level discount distribution is required for tax accuracy
2. Or current net total approach should be considered final


Note:
Tested calculations and API responses align with current implementation (net total based).
Title: Clarification on Discount Distribution Logic (Item-level vs Net Total)

Module: POS / Discount Calculation
Priority: Medium (Functional Clarification)


Description:

During testing of discount and tax calculation in POS, I validated the discount distribution based on item-level proportional logic.

However, the development team has implemented the discount based on net total (cart-level) as per client requirement.


Test Scenario Executed:

Products in cart:

  • Product A → $100
  • Product B → $50

Discount Applied: $10 (Flat)


My Tested Approach (Item-Level Distribution):

Discount distributed proportionally:

  • Product A → (100 / 150) × 10 = $6.67
  • Product B → (50 / 150) × 10 = $3.33

Final:

  • A → 100 - 6.67 = 93.33
  • B → 50 - 3.33 = 46.67

👉 Tax calculated per item after discount.


Current Implementation (As per Dev/Client):

  • Total = $150
  • Discount = $10
  • Net Total = $140

👉 Discount applied at overall cart level, not distributed per item.


Observation:

  • System is calculating discount on net total, not at item level
  • This impacts:
    • Item-level tax calculation
    • API response (discount may appear uneven per item)

Impact:

  • Tax calculation differences at item level
  • Difficulty in validating per-item tax from API response
  • Potential mismatch in edge cases (low-price items)

Conclusion:

Both approaches are valid:

  • Item-level distribution → Standard accounting/tax accuracy
  • Net total discount → Implemented as per client requirement

Request:

Please confirm:

1. Whether item-level discount distribution is required for tax accuracy
2. Or current net total approach should be considered final


Note:
Tested calculations and API responses align with current implementation (net total based).

Updated by Sai Mahananda 9 days ago

  • % Done changed from 0 to 100
  • Estimated time set to 4:00 h
Actions #4

Updated by Sai Mahananda 9 days ago

  • Status changed from In Progress to Closed
Edit Copy Actions

Also available in: Atom PDF