Stock-alert request context

Make stock-alert requests name the variant people chose

Review the request form as part of your customer's storefront, with the selected size and color still visible in the story.

  • ✓Forms retain the previous variant
  • ✓Generic confirmations lose context
  • ✓Validation disrupts the request

Clearer evidence for notification-request UI

Variant-aware confirmations

Show whether request wording follows the shopper's latest option selection.

Careful subscription language

Have the commerce owner approve what a confirmation promises before it becomes acceptance scope.

Delivery assumptions removed

Keep visible request feedback separate from notification scheduling and receipt.

Begin with the unavailable variant

A back-in-stock request belongs to a particular item and often a particular size or color. Review your storefront using a sample unavailable variant and a safe test address. Capture the selected options, the alert entry point, and the form heading. Include the required consent explanation if your product presents one. Write down the intended request scope, because a generic Notify me label does not establish whether the request covers one variant or the entire product.

Show selection changes around the form

Record opening the request form for a blue medium item, closing it, choosing a different unavailable variant, and reopening it. A distinctive issue is Confirmation repeats the first variant after the shopper changes size. Preserve both selections and the submitted confirmation in the recording. Do not claim that the wrong notification was scheduled from confirmation text alone. Keep invalid-address feedback separate from variant identity so each problem has an independent expected outcome.

Review the request language carefully

Upload supported screenshots or recordings to Retick, or capture the browser interaction. Inspect AI candidate issues, edit any inferred notification behavior, reject delivery guarantees, and annotate the stale variant wording. Example acceptance criteria: the form and confirmation name the current variant; returning to the product preserves an understandable selection; and validation feedback does not erase the address without explanation. Have the commerce owner approve wording about what the request means and what it does not promise.

Check repeat and unavailable states

After implementation, manually repeat with a previously requested variant, a long product name, and an item that becomes available in your controlled test setup. Check keyboard access to the close control and the location of confirmation feedback. Verify request storage, consent handling, and notification delivery in your own systems outside Retick. Retick does not subscribe shoppers, monitor stock, send stock alerts, or establish legal sufficiency of consent text. Remove real addresses before capture; redaction is not automatic.

Download the approved findings for file handoff, or export selected issues from the individual media item to a connected Trello board and list. Include the exact option change so the receiving team can investigate stale request context rather than treating the task as a general email delivery problem.

Review a back-in-stock form

Capture the unavailable variant and the confirmation that follows it.