Aglet

Verify availability filters across variants and locations

Verification should prove that an availability filter means the same thing in the result row, selected state, and next action. Test representative variants and locations, then inspect freshness or scope copy. Keep a partial result when fulfillment remains outside search evidence.

Check whether the outcome improved

  1. Check representative products

    Filter for available items and compare parent, variant, and unavailable examples. Confirm visible labels and selected facets reflect the defined state. Record timestamp and location so a result is not treated as universal.

  2. Check boundary changes

    Repeat with another region, older index sample, and a parent whose variants differ. Verify the product row does not imply every variant is available. Test fallback when the filter cannot establish the next action.

  3. Review the promise

    Inspect copy, URL, empty state, mobile layout, and destination behavior. State tested freshness and location limits. Leave the result provisional if search and fulfillment disagree or if one variant path could not be exercised.

What to carry forward

Verification passes when filters, labels, variants, and next actions agree within the defined freshness and location scope. If fulfillment is not directly verified, say so. A result that is searchable is not evidence that the promised product can be obtained.

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