Build a useful investigation brief
Reconstruct the calculation
Write the arithmetic sequence from line-item price through quantity, discount, tax, shipping, and final total. Compare each intermediate value with the server's serialized fields. Look for rounding after each line, at the subtotal, or only at the final currency precision.
Check stale inputs
Compare timestamps and version markers for the cart, discount eligibility, tax response, and shipping selection. Re-run after an edit and after an idle interval. A cached browser value, delayed recalculation, or stale server snapshot is a possibility to test, not a conclusion.
Follow persistence
Match the payment summary to the saved order and any receipt-facing amount. Identify which record the confirmation screen reads. If fields disagree, capture the request and response sequence, redact identifiers, and state whether the mismatch is present before or after payment authorization.
What to carry forward
The investigation is ready when another engineer can reproduce the divergent totals from the recorded inputs and locate the first inconsistent field. Deliver a brief with arithmetic, timestamps, request boundaries, and open hypotheses; avoid prescribing a fix until the authoritative source is agreed.
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