Capture the request at variant level
A request for navy in size M should not become an alert for any navy dress. Check product and variant identifiers, selected size and colour, market, language and requested channel. Verify the confirmation state and prevent misleading duplicate submissions. Klaviyo’s documented subscription model links the profile and channel to a catalog variant. The owner should validate that mapping with controlled test profiles before relying on it for real shoppers.
Source: Klaviyo: variant subscriptions and channel requirements ↗
Verify sellable stock and notification pacing
An incoming shipment or stock in an unsuitable location may not be available to this shopper. Reconcile catalog freshness, market availability and the live product page. In Klaviyo, restock minimums and notification batches have account-wide settings: changing them can affect other back-in-stock flows. Review current values with the owner and the other affected journeys. Choose a proportionate release plan for limited stock; a notification must not imply that an item has been reserved.
Keep the requested alert and other marketing separate
Keep a record of the request, its channel and the relevant eligibility and suppression settings. Email and SMS do not have identical platform requirements; Klaviyo documents explicit SMS consent for SMS restock notifications. Do not silently turn the product request into a general marketing subscription. Have the responsible team review the actual form wording and sending setup for its market, including how withdrawn requests and undeliverable contacts are handled.
Source: Klaviyo: variant subscriptions and channel requirements ↗
Test the entire route before release
Using authorised test profiles, verify signup, the variant match, waiting state, restock event, message rendering and the final product link. Include two sizes with different availability, a sold-out-again state and a retired variant. Recheck price, image, selected size and stock after opening the message on mobile. A successful signup or queue entry is not a successful send. Record the owner, tested configuration, approval and activation status separately.
Measure service quality and the purchase outcome
Review valid requests, notification attempts, delivery, clicks and qualifying purchases with explicit denominators and windows. Track complaints such as a wrong size or an unavailable destination, then include later return context. A waitlist describes observed demand under the current form and exposure, not guaranteed orders or total unconstrained demand. Keep attributed revenue separate from causal lift. Faccelerate can support a reviewed brief within confirmed workspace scope; activation and sending remain explicit steps in the chosen platform.
Navy, size M returns; size L does not
Illustration: eight saleable navy dresses in M arrive, while L remains unavailable. There are sixty valid M requests and thirty-five L requests. The owner checks stock freshness and account-wide notification settings, then approves the release plan for M. The L queue stays separate. Test messages must open M without claiming a reservation. Later reporting separates notifications, purchases and retained purchases; none of these illustrative counts is a promised conversion rate.
Use this at work
- Match the request to variant, market, language and channel.
- Verify saleable stock and review account-wide release settings.
- Review request handling, eligibility and suppression rules.
- Test the real mobile destination and record activation separately.
- Measure the purchase outcome with complaints and return context.
Reference material
Platform guidance checked 4 October 2026. The definitions, examples and review steps below are Faccelerate editorial proposals.