> For the complete documentation index, see [llms.txt](https://the-wishlist-documentation.gitbook.io/the-wishlist-documentation-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://the-wishlist-documentation.gitbook.io/the-wishlist-documentation-docs/notify-me-and-coming-soon/overview.md).

# Overview

TWC **Notify Me & Coming Soon** allow you to capture customer interest at product-variant level for products that are unavailable or not yet released.

Features include:

* Automatic notification when a product arrives back in stock
* Controlled release option to send notifications in batches rather than all at once
* For Coming Soon items, the option to manually trigger or schedule notifications 
* Customisable widgets for optimising your customer's web experience
* Prioritises Notify Me over Wishlist back in stock notifications if a customer qualifies for both
* Extensive reporting

## **Customer registration and matching**

Notify Me and Coming Soon let shoppers request an alert without logging in to Shopify or creating a customer account. They do not need to be an existing customer in the retailer's database. Additional customer details, such as first and last name, are optional.

If the submitted email matches an existing TWC customer for the same retailer tenant, the notification is stored against that customer. An existing database record does not mean the shopper is logged in.

Submitting contact details registers interest in the selected variant. It does not sign the shopper in, verify ownership of those contact details, or grant access to existing customer information. Access to customer information and account management requires customer login and appropriate authorisation.

## Notify me widget

The same JavaScript widget supports both the Notify Me and Coming Soon use cases. The implementation determines the experience using the `data-type` attribute.

| Use case                            | `data-type`   | Customer experience                                       | API flag           |
| ----------------------------------- | ------------- | --------------------------------------------------------- | ------------------ |
| **Notify Me**                       | `notify-me`   | Register for a back-in-stock notification                 | `notifyMe: true`   |
| **Coming Soon / Register Interest** | `coming-soon` | Register interest in a pre-release or coming-soon product | `comingSoon: true` |

## What the widget supports

The widget can be configured to:

* Capture email, mobile, first name and last name
* Capture the selected product variant/size
* Offer optional email and SMS marketing opt-in
* Display as either a modal or right-hand panel
* Capture Shopify Markets context such as market and country
* Show optional **Shop Similar Styles** recommendations using TWC or Athos recommendations
* Submit customer interest directly to the TWC Customer Interest API

The widget is distributed through the [`notify-me-wl` npm package](https://www.npmjs.com/package/notify-me-wl).

{% hint style="info" %}
**Documentation source of truth**

This GitBook documentation is the primary implementation guide. The npm package contains a compact package reference and installation information.
{% endhint %}

## Implementation paths

{% columns %}
{% column %}

### Use the JavaScript widget

Recommended when you want TWC to provide the customer-facing form, validation, variant selection and optional recommendation experience.

[Widget Installation & Configuration](broken://pages/dbcdfce79bff07bfed231168f6eb3b6920b494fb)
{% endcolumn %}

{% column %}

### Build a custom experience

Use the Customer Interest API if you want to build your own form or storefront experience while still registering Notify Me or Coming Soon interest with TWC.

[API / Custom Implementations](broken://pages/6ec1abf3a2937bf70afe114a479318034df5f863)
{% endcolumn %}
{% endcolumns %}

| Storefront      | Recommended authentication                                                                                                                   | Customer login required to register interest |
| --------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------- |
| Shopify         | Install and configure the TWC Shopify app proxy. The widget or custom integration obtains the retailer's tenant-scoped TWC token through it. | No                                           |
| Other platforms | Use TWC REST API bearer-token authentication through the retailer's backend or integration service.                                          | No                                           |

Choosing the standard widget or a custom form is separate from choosing the authentication method. A Shopify custom form can also use the app proxy.

## Related documentation

* [Widget Installation & Configuration](broken://pages/dbcdfce79bff07bfed231168f6eb3b6920b494fb)
* [Widget Authentication](broken://pages/9b99fb88bc804e74c65d77d79e367b649984aaf1)
* [Shopify Markets Support](broken://pages/2200f96f5cca5bff466ba75947d76efb24622607)
* [Product Recommendations & Integrations](broken://pages/ea38528eb92781511938bb60da9abf7467ca0596)
* [API / Custom Implementations](broken://pages/6ec1abf3a2937bf70afe114a479318034df5f863)
* [Troubleshooting](broken://pages/b4fb83ffa628453284ce0c6511f85ff645860e89)
* [notify-me-wl on npm](https://www.npmjs.com/package/notify-me-wl)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://the-wishlist-documentation.gitbook.io/the-wishlist-documentation-docs/notify-me-and-coming-soon/overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.