One requested alert does not define every future message
A person asks to hear when a variant is sellable again. The expected outcome is the requested availability information. Ongoing promotional SMS involves a separate purpose and subscriber review. Retain what was actually requested; do not infer an unrestricted audience from a stock-alert form.
Inspect the differences
Scroll horizontally to read all columns.
| Question | Requested restock alert | Ongoing SMS programme |
|---|---|---|
| Why this person? | They requested an alert for a specified item | A separate documented subscription relevant to the purpose |
| Why this message? | The reviewed availability event occurred | The message fits the reviewed subscriber purpose |
| When does it end? | At the defined fulfillment or withdrawal of the request | According to preference, suppression and programme rules |
| What can fail? | Wrong variant, unavailable item or repeated alert | Incorrect audience, frequency or exclusion propagation |
Rehearse the boundary
- Create separate controlled records for an alert-only request and an ongoing subscriber.
- Trigger an unrelated variant change; the alert-only record should not receive that alert.
- Change the appropriate preference and check connected paths.
- Confirm that completing one requested alert does not silently establish another subscription.
Match the product investigation to the work
Notify Me! is a restock and store-alert research route; Postscript is an SMS marketing research route for Shopify. Review each exact account, plan, channel and location. A proposed preference test does not establish legal permission, delivery or incremental sales performance. Keep orders, clicks and message events separate when evaluating a later trial.