Establish what is happening
Capture every amount
Save the cart's line items, quantities, discount code, tax result, shipping choice, currency, and displayed total with a timestamp. Use a synthetic cart or redacted identifiers. Record both the browser value and the server response that supplied it; never copy payment credentials into the report.
Reproduce the changing state
Repeat the path after a quantity edit, refresh, back navigation, and a second tab. Note whether the total changes before payment, during a recalculation, or only after the order is created. Keep one cart state per attempt so observations remain comparable.
Name the boundary
Compare the client calculation, cart response, payment summary, and persisted order fields side by side. Check decimal precision, tax inclusion, discount ordering, and currency conversion. Mark each value as observed, expected, or unknown instead of selecting a cause prematurely.
What to carry forward
A useful triage result identifies the first boundary where two observed totals diverge, the cart state that triggers it, and the values involved. Stop when the mismatch is reproducible or explicitly intermittent, with missing calculations listed for the investigator to obtain.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow