Product Alerts (Headless)

VIDEO WALKTHROUGH

Product Alerts — Headless: setup guide

2:11

Recorded on version 1.0.2 · Narrated walkthrough · English captions

Jump to a chapter 7 chapters

1. 0:00Set up Product Alerts — Headless
2. 0:15Use Magento’s native alert settings
3. 0:36Enable the alert types you offer
4. 0:54Review the email schedule
5. 1:12Connect the signed-in customer flow
6. 1:33Save and test a controlled alert
7. 1:51Your setup checklist

Read the full video transcript

Product Alerts — Headless 1.0.2 — Magento Admin setup

00:00:00 — Set up Product Alerts — Headless
Welcome to the Agentic Ecom Product Alerts — Headless guide. We'll use Magento Admin to review the setup and explain the handoff to your headless storefront. This walkthrough covers stable version 1 point 0 point 2 and assumes the extension is installed.

00:00:15 — Use Magento’s native alert settings
Open Stores, Configuration, Catalog, Catalog, Product Alerts. There is no separate Agentic Ecom configuration form. This extension exposes Magento's native product alerts to a headless storefront through Graph Q L; Magento still manages the subscriptions and email processing.

00:00:36 — Enable the alert types you offer
Allow Alert When Product Price Changes enables price alerts. Allow Alert When Product Comes Back in Stock enables stock alerts. Turn on the types your storefront offers. Review the matching email templates and sender identity, and check the configuration scope before saving.

00:00:54 — Review the email schedule
Open Product Alerts Run Settings. Review Frequency and Start Time, plus the error-email settings used to report processing failures. Your server must also run Magento cron correctly. A saved subscription does not prove that an alert email has been sent.

00:01:12 — Connect the signed-in customer flow
Your storefront calls subscribe Product Alert with the product S K U and the PRICE or STOCK alert type. It must use the signed-in customer's token; guests need to sign in first. Show the returned success or error message to the shopper. Pair this with Headless Email URLs so the email returns to the correct storefront.

00:01:33 — Save and test a controlled alert
Save the settings on your staging store. Use a test customer and product to subscribe, trigger the relevant price or stock change, and check cron processing and email delivery. Follow the email's product and unsubscribe links. This walkthrough does not create a subscription or send mail.

00:01:51 — Your setup checklist
Your next steps are to enable the required native alert types, confirm customer authentication and cron, test delivery and storefront links. Use a staging store for the end-to-end check. The complete installation and integration reference is at user guides dot Agentic Ecom dot net.

Download videoEnglish captionsDownload transcript

Magento has a quietly high-converting feature built in: Product Alerts. A shopper can ask to be emailed when a product’s price drops or when it’s back in stock — and the day that email reaches them, they can return to the product. But the signup UI ships only for the Luma frontend, so the moment you go headless it disappears. Product Alerts puts it back: a single GraphQL mutation your storefront calls to subscribe the signed-in customer, while Magento’s own engine does the rest.

It rides Magento's native engine

This module is deliberately thin: it exposes the subscribe action over GraphQL. Magento_ProductAlert keeps doing the heavy lifting — the product_alert tables, the catalog_product_alert cron job and the alert emails themselves. Nothing parallel to maintain, nothing to drift.

Install

Install Product Alerts with Composer using your AgenticEcom licence key (find it on your My Licences page — one key unlocks every module you own):

# 1. Register the AgenticEcom repository (once per store)
composer config repositories.agenticecom composer https://repo.agenticecom.net
composer config --global --auth http-basic.repo.agenticecom.net <YOUR-LICENCE-KEY> x

# 2. Require this module
composer require agenticecom/module-product-alerts

# 3. Apply it
php bin/magento setup:upgrade && php bin/magento setup:di:compile && php bin/magento cache:flush

Have the whole platform?

Install every module in one command with composer require agenticecom/suite — see Install the complete suite.

Compatibility

Magento

Check the exact release against your Magento Open Source version.

PHP

Check the exact package requirements and test your PHP version.

Frontend

Any GraphQL storefront — Astro, Hyvä, PWA Studio, custom.

Engine

Magento’s native Magento_ProductAlert (cron + emails).

The GraphQL mutation

Call this when a signed-in shopper taps “alert me”:

mutation {
  subscribeProductAlert(input: { sku: "ABC-123", alert_type: PRICE }) {
    success
    message
  }
}

Field	Notes
input.sku	SKU of the product to watch.
input.alert_type	PRICE (notify on price drop) or STOCK (notify when back in stock).
success	true when the subscription was created.
message	Human-readable status you can show the shopper.

The customer must be signed in

Magento’s product_alert tables key on customer_id, so the mutation requires an authenticated customer — send the customer token. Prompt a guest to sign in or register before showing the “alert me” control.

How it works

1. A signed-in shopper taps “Notify me on a price drop” on a product page.

2. Your storefront calls subscribeProductAlert with the SKU and PRICE (or STOCK).

3. The module writes the subscription to Magento’s native product-alert table for that customer.

4. Magento’s catalog_product_alert cron detects the price drop (or restock) and sends the email through your configured mail transport.

5. The email links the shopper back to the product. Pair with Headless Email URLs so that link points at your storefront, not the backend.

Configuration

There’s no module-specific config — it uses Magento’s standard Product Alerts settings:

Stores → Configuration → Catalog → Catalog → Product Alerts — enable Allow Alert When Product Price Changes and/or Allow Alert When Product Comes Back in Stock, set the email templates and sender, then make sure cron is running (the catalog_product_alert group sends the emails).

Deliverability

Use SMTP to route alert emails through a configured provider, and Headless Email URLs so their links point at your storefront.

FAQ

Does it support back-in-stock as well as price-drop?

Yes — pass alert_type: STOCK for back-in-stock, PRICE for price-drop. Enable the matching option under Catalog → Product Alerts.

Who sends the emails?

Magento does — its native catalog_product_alert cron job. This module only handles the subscribe step, so there’s no parallel mail system to maintain.

Can guests subscribe?

No — alerts are tied to a customer account (Magento keys them on customer_id). Prompt guests to sign in first; your headless account area handles the auth.

How does a shopper unsubscribe?

Magento’s alert emails include the native unsubscribe link, and subscriptions appear under the customer’s account in the admin — all standard Magento behaviour.