Establish what is happening
Capture one availability sample
Record query, filter, product or variant, location, index timestamp, visible label, and next action. Include an available result, an unavailable result, and a parent with variant differences. Keep the freshness boundary attached to each observation.
Define the promise
Write what the filter claims and what the result actually supports. Compare sellable, in-stock, reservable, and region-specific states. Mark any fulfillment conclusion as unknown when the search index cannot prove the next action will succeed.
Set confidence limits
State scope, freshness, variants, locations, and fallback copy. Preserve a stale or contradictory case for investigation. Stop when the team can explain what “available” means in the tested context without promising a real-time guarantee it cannot support.
What to carry forward
The triage output is an availability definition with sample records, timestamp, scope, and confidence limits. Stop when the filter’s promise and next action are distinguishable. If inventory freshness is unknown, keep the label provisional and route the evidence gap instead of claiming stock accuracy.
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