Decide where the work belongs
Describe the decision changed
Name the filter choice the count supports and what a person infers from it. Compare a count off by page scope with a count that hides available products. Keep parent-product and variant differences visible rather than averaging them away.
Compare remedies
Set count recalculation, scope copy, refresh timing, and product grouping beside one another. Consider whether a fast display fix would conceal stale data. Choose the smallest remedy that makes the count’s universe and freshness truthful.
Set position and trigger
Record owner, query family, filter scope, and a revisit trigger such as a refreshed index or a newly observed impossible count. Keep a reconciled control case attached. Do not prioritize from one visually surprising number without checking the selection it affects.
What to carry forward
Prioritize count work where the number changes a product choice or makes the filter promise false. The decision should identify scope, data confidence, and remedy size. If the mismatch is only a presentation ambiguity, queue copy clarification rather than rebuilding result counting.
Technical background: Adobe developer documentation.
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