Decide where the work belongs
Rank the failed choice
Describe what action the filter enabled and where the promise broke. Compare a stale count, a parent product with one unavailable variant, and a region mismatch. Keep a display inconsistency separate from a failed fulfillment expectation.
Compare repair scope
Set label copy, freshness timestamp, variant grouping, location context, filter logic, and fallback behavior beside one another. Consider whether a narrower filter reduces useful results. Prefer a change that makes the boundary visible without implying live confirmation.
Choose the queue move
Name product family, region, owner, and revisit evidence. Decide whether to investigate data freshness, adjust grouping, or clarify the filter. Preserve a contradictory sample and a working control so the decision remains grounded.
What to carry forward
Prioritize availability work where a misleading filter changes a meaningful product choice and the scope can be corrected safely. The decision should state freshness and variant boundaries. If the search layer cannot prove fulfillment, prioritize truthful wording and recovery over a stronger promise.
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