Saved-item recovery in motion

Keep wishlist actions attached to the item users intended

Show how removal, undo, and changing card order affect the next action in your saved-product experience.

  • ✓Cards shift during recovery
  • ✓Undo messages omit identity
  • ✓Sold-out actions look inconsistent

Wishlist findings beyond the product tile

Recovery tied to an item

Keep the removed product identifiable when an undo changes the visible list.

Focus decisions with evidence

Give design the before-and-after state needed to approve a predictable next control.

Separate saving and display questions

Distinguish visible restoration from account persistence that needs its own checks.

Review a list that changes shape

Wishlist management becomes confusing when removing one card rearranges the remaining products. In your product, prepare a safe list with several items, a long title, a sold-out variant, and two visually similar products. Capture the list before editing, the active sort, and any saved variant details. Note whether the visitor is signed in and whether the product promises temporary or account-based saving. The screenshot cannot establish that persistence contract by itself.

Capture removal and its recovery

Record removing the middle card, using Undo, and then moving another item to the cart through the supported interface. An example issue is Undo restores the card but leaves the next item's remove label focused. Show the card order and focus indicator before and after restoration. Keep an unavailable move-to-cart action separate from the undo concern. A restored card does not prove the wishlist was saved correctly across devices or sessions.

Make the intended recovery explicit

Bring supported screenshots or recordings into Retick, or capture the browser journey. Check AI candidate issues against the card sequence, edit mistaken product identities, reject assumed persistence failures, and annotate the mismatched focus. Example acceptance criteria: undo restores the intended item in the product-approved position; the recovery message names that item; and the next keyboard action targets a predictable control. Ask design to approve focus placement rather than treating any visible highlight as automatically correct.

Follow up beyond a single card

After implementation, manually repeat removal with the last item, a sorted list, and a sold-out item that cannot move to cart. Inspect the empty state and restoration from it. Use separate application tests to check account persistence, cart creation, and availability rules. Retick does not maintain wishlists, synchronize shopping accounts, or verify inventory. Use sample products and omit private account information before recording; sensitive material in the media is not automatically concealed.

Download accepted findings for a file handoff, or export selected issues from the individual media item to an accessible Trello board and list. Include the initial ordering and recovery action so developers can reproduce the card movement instead of assuming the report concerns a static product tile.

Review a wishlist recovery moment

Bring the removal, undo, and resulting card order together.