Keep the lesson for the next incident
Keep the availability promise
Record filter, product, variant, location, index age, label, and destination behavior. State whether “available” meant searchable, sellable, or region-specific. This prevents a later reviewer from silently strengthening the original promise.
Compare later states
Review a fresh and older index, another location, and a parent with mixed variants. Look for the same misleading label or a copy change that hides uncertainty. Preserve a working sample so the lesson stays bounded.
Refine one review check
Require future availability reviews to record timestamp, variant scope, location, and the action after selection. Assign ownership and revisit date. Define the observation that would show the check prevented a stale or overbroad availability claim.
What to carry forward
The learning record connects one availability promise to later evidence and a reusable freshness-and-scope check. Stop when another reviewer can apply it to a new product family. Carry forward uncertainty where search data cannot establish fulfillment or regional inventory.
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