When a shopper asks a Maltepe store to tell them that an item is back in stock, the request can be for one size or finish. A message for a different option sends them back to a product they still cannot buy. Use two similar variants to check what the form promises and what the buyer eventually receives.
Name the option before collecting an address
Set one fictional finish as unavailable and leave the other in stock. Open the product from a saved link and select the unavailable option. Put its name and reference beside the alert field. State what message the shopper is requesting. Give any newsletter its own choice with wording that lets the tester distinguish the two.
Restock the other option first
Make a test request for the unavailable finish. Change stock for the other finish and check the test inbox and notification history. Then restock the requested finish and verify that the alert names the correct option. Open its link in a signed-out browser and look for the same finish and current price on the page.
Reopen an older alert after stock has sold again
Set the requested finish as unavailable after the test message goes out. Open the alert link again. Show current availability and explain how the shopper can request another stock notice if the shop offers one. Confirm that a shopper can tell whether an alert is still active and what to do if they want to stop it.
Compare the sample request across languages
Record the selected reference, alert wording, stock change, message received and final product URL. Repeat with English and French addresses in the test system. Keep the same variant so any difference in the visitor view can be spotted.
Checklist before publishing
- Alert identifies the selected size or finish
- Stock change for another option does not trigger it
- Message points to the requested option
- Existing message opens current availability