The back-in-stock notification flow is the delivery engine for the Back-in-Stock module. When a customer subscribes to an out-of-stock variant through the storefront widget, this automation sends them a WhatsApp message the moment that variant’s inventory is replenished — no manual intervention required. This is the simplest recipe in terms of flow structure: a single trigger connected directly to a single action. Its power is in the precision of the delivery — every customer receives a notification only for the specific variant they subscribed to, at the exact moment it becomes available.Documentation Index
Fetch the complete documentation index at: https://docs.digifist.com/llms.txt
Use this file to discover all available pages before exploring further.
Flow structure
Node-by-node breakdown
Trigger — Back in Stock
Trigger:BACK_IN_STOCK
Source: Galantis — fires when a subscribed product variant’s inventory_quantity changes from 0 to a positive value.
This trigger fires only for variants that have active Back-in-Stock subscribers. If a variant is restocked but has no active subscribers, the trigger does not fire. If a variant has 50 active subscribers and is restocked, the trigger fires and the action is executed for all 50 customers.
The trigger is detected via Shopify’s products/update webhook. When Galantis receives the webhook and detects an inventory change from 0 to > 0, it identifies all ACTIVE subscriptions for that variant and begins executing this flow for each subscriber.
Recommended frequency cap: 24 hours — protects against edge cases where inventory fluctuates around zero multiple times in the same day, which could otherwise trigger multiple notifications to the same subscriber for the same restock event.
This automation is tightly coupled to the Back-in-Stock widget and subscription system. For the trigger to fire, customers must have subscribed through the widget and their subscription must be in
ACTIVE status. See Back-in-Stock — Notification Logic for the full pipeline.Action — Restock notification template
The restock notification is a high-intent message — the customer explicitly asked to be notified. The template should be direct, confirm the specific product is back, and include a clear link to the product page. Effective restock notification template elements:- Confirm what is back in stock (product name and ideally the specific variant — size, color, etc.)
- Create urgency where genuine — if the restock quantity is limited, say so
- A direct link button to the product page using a
URLbutton type
No delay required
Unlike most other recipes, this flow deliberately omits a delay node between the trigger and the action. The customer subscribed specifically to receive this notification the moment the product is available. A delay would reduce the value of the notification — if inventory is limited, customers who subscribed later in the day benefit from a faster notification.Consent and subscription guardrails
Before sending, Galantis automatically enforces two guardrails:- Subscription status — Only customers with
ACTIVEsubscription status receive the notification. Customers withCANCELLED,NOTIFIED, orPENDINGsubscriptions are excluded. - Consent status — Customers with
UNSUBSCRIBEDorREDACTEDmarketing_stateare skipped even if they have anACTIVEsubscription.
NOTIFIED. A notified subscription does not receive a second notification if the same variant is restocked again in the future — the customer would need to re-subscribe.
Templates required
| Template | Purpose |
|---|---|
| Restock notification | Alerts subscriber that their product variant is back in stock |
Related guides
- Back-in-Stock — Notification Logic — Full pipeline from inventory webhook to message dispatch
- Back-in-Stock — Subscription Lifecycle — Subscription statuses and how they interact with this flow
- Triggers — BACK_IN_STOCK trigger source and behavior