Back in stock
When to use it
Section titled “When to use it”- Items sell out and come back, and shoppers ask to be told.
- Your store can send an event for each waiting shopper when an item is restocked.
Where the data comes from
Section titled “Where the data comes from”| How | What |
|---|---|
| A form people fill in | The "tell me when it's back" form on sold-out product pages. |
| Events from your app or website (needs a developer) | Your store sends one restock event per waiting shopper. |
What it sets up
Section titled “What it sets up”| Kind | Name | What it does | Lands |
|---|---|---|---|
| Form | Back in stock alert | "Tell me when it's back": email or phone, with the product id from the link. | Draft, not published |
| Template | Back in stock (email) | The back-in-stock email. | Ready |
| Template | Back in stock (SMS) | The back-in-stock SMS. | Ready |
| Follow-up | Back in stock | Email (and SMS if they have a phone) when the restock event arrives. | Off |
The questions it asks
Section titled “The questions it asks”| # | Question | Default | Fills in |
|---|---|---|---|
| 1 | What's your shop called? | none, must answer | org_name |
| 2 | What will your store call the event it sends to each waiting shopper on restock? Properties product_name and product_url. | Back In Stock | restock_event |
| 3 | Do you want an Origamy form for "tell me when it's back", or does your store have its own button? | Yes | use_form |
| 4 | Send an SMS as well, when the shopper gave a number? | Yes | send_sms |
| 5 | Which address should emails come from? | none, must answer | email_from |
Other settings
Section titled “Other settings”These have defaults. Change any that don’t fit.
| Setting | Default | Key |
|---|---|---|
| Greeting when a first name is missing | there | greeting_fallback |
Timings
Section titled “Timings”- The email goes as soon as Back In Stock arrives; the SMS 10 minutes later.
- A shopper can be told about each product once (every event is a new product, so re-entry is allowed).
Channels
Section titled “Channels”| Channel | Needed for | Before it can send |
|---|---|---|
| The back-in-stock email | A verified sending domain for ‹Sender address›. | |
| sms | The back-in-stock SMS (optional) | An SMS provider, or Origamy managed SMS after business verification (KYC). |
What you need to do
Section titled “What you need to do”- When an item is restocked, have your store send Back In Stock for each shopper who asked (with product_name and product_url), for example from the same job that updates stock.
- If you use the form, publish it and link it from your sold-out product pages with ?product=<product id> in the link.
- Verify the sending domain; for SMS, connect a provider or finish business verification.
- Switch the follow-up on and test with your own email.
This playbook is synthesized: no customer has run it with us yet. If you build it, tell us what you changed, and we’ll replace it with the real version.
Copilot eval
Section titled “Copilot eval”The request used to test the copilot on this playbook (a live eval):
Shoppers can ask to be told when a sold-out product is back. When it's restocked, email them a link to the product, and text them too if they gave a phone number.
It passes when every piece is a valid draft and everything lands off, with at least: workflow, message_template.