Opens in a new tab
Deliver toTennessee
0 0 0Cart
Get a Project Quote

Athenian Notify Back In Stock

v1.1.0 October 6, 2026
Back-in-stock signup, stock watching, and customer notification foundations for WooCommerce.

Overview

Product overview

Out-of-stock products usually create one of two bad outcomes: the shopper leaves, or the merchant has to manage restock demand manually. Standard WooCommerce out-of-stock states do not provide a built-in, branded system for capturing demand, confirming subscriber intent, tracking signups, and sending timely restock alerts at the product or variation level.

Athenian Notify Back in Stock solves that by adding a storefront-native notification workflow directly into WooCommerce. It displays a theme-aligned signup form on out-of-stock product pages, stores subscriber records with product and variation context, supports consent and double opt-in flows, and dispatches notification emails automatically when inventory changes to in stock.

Customer signup and product/variation notification records.
Stock watcher, mailer, admin table, and CLI surfaces.
WooCommerce stock events, options, and delivery boundaries.
A baseline for later stock-transition, email, and unsubscribe verification.

Use cases

  • Stock alerts
  • Waitlists
  • Inventory notifications
  • Customer re-engagement

Developer

Developer starting point

This baseline documents the Notify Back In Stock architecture. It does not claim that a live signup, stock transition, email delivery, or unsubscribe path has been exercised.

Ecosystem integration story

WooCommerce

Athenian Notify Back in Stock is built directly on WooCommerce product and stock events. It uses WooCommerce product context to determine whether the form should render, whether the signup applies to a parent product or variation, and when notification delivery should occur.

Athenian Site Theme

The plugin is theme-token aware, allowing stores to style the waitlist experience using existing Athenian design tokens instead of duplicating design decisions inside plugin CSS. That keeps the storefront experience visually coherent across branded commerce surfaces.

Email infrastructure

The plugin does not replace a broader CRM or lifecycle marketing system. Its role is to handle the transactional restock notification workflow cleanly inside WordPress and WooCommerce, with configurable sender details, subject lines, body templates, confirmation emails, and unsubscribe links.

Store operations

By storing subscriber records and surfacing them in the WordPress admin, the plugin gives operations, support, and merchandising teams visibility into demand for unavailable products. That creates a more actionable signal than a passive out-of-stock state alone.

Install

Source and dependencies
  • Reviewed source folder: athenian-notify-back-in-stock
  • Plugin version reviewed: 1.1.0
  • Local source inventory: 23 files (temporary, test, and Git metadata excluded).
  • GitHub baseline: https://github.com/Athenian-Brands/athenian-notify-back-in-stock at main / 11d7c5dbf77b4ca75ddf83a06cbc5465cc9c1543.
  • WordPress, WooCommerce, and the configured mail transport.
  • Stock transitions, subscriber identity, email delivery, opt-out behavior, and variation handling require separate target verification.

Configuration

Implementation reference sections
  • Working positioning — see the linked technical reference excerpt.
  • Executive summary — see the linked technical reference excerpt.
  • Core marketing message — see the linked technical reference excerpt.
  • The problem it solves — see the linked technical reference excerpt.
  • What Athenian Notify Back in Stock does — see the linked technical reference excerpt.
  • Ecosystem integration story — see the linked technical reference excerpt.
  • Why this matters commercially — see the linked technical reference excerpt.
  • Key differentiators — see the linked technical reference excerpt.
  • Suggested messaging pillars — see the linked technical reference excerpt.
  • Short-form copy options — see the linked technical reference excerpt.
  • Sales narrative — see the linked technical reference excerpt.
  • Best-fit use cases — see the linked technical reference excerpt.
  • Positioning statement — see the linked technical reference excerpt.
  • Platform-focused primary functionality copy — see the linked technical reference excerpt.

Usage

Detected extension surface
  • Shortcodes detected in local PHP source: 2
  • Static action/filter hooks detected in local PHP source: 18
  • REST route registrations detected in local PHP source: 0

Shortcodes

Detected shortcodes
  • athenian_notify_back_in_stock — includes/Frontend.php
  • cc_notify_back_in_stock — includes/Frontend.php

REST Endpoints

Detected REST routes
  • No register_rest_route calls were detected by the baseline scanner.

Hooks

Detected hooks
  • admin_enqueue_scripts — includes/Admin/AdminController.php
  • admin_menu — includes/Admin/AdminController.php
  • admin_post_cc_nbis_bulk — includes/Admin/AdminController.php
  • admin_post_cc_nbis_create — includes/Admin/AdminController.php
  • admin_post_cc_nbis_delete — includes/Admin/AdminController.php
  • admin_post_cc_nbis_save_settings — includes/Admin/AdminController.php
  • admin_post_cc_nbis_send — includes/Admin/AdminController.php
  • admin_post_cc_nbis_update — includes/Admin/AdminController.php
  • init — includes/Plugin.php
  • plugins_loaded — athenian-notify-back-in-stock.php
  • woocommerce_after_add_to_cart_form — includes/Frontend.php
  • woocommerce_product_set_stock_status — includes/StockWatcher.php
  • woocommerce_single_product_summary — includes/Frontend.php
  • woocommerce_variation_set_stock_status — includes/StockWatcher.php
  • wp_ajax_cc_nbis_subscribe — includes/Frontend.php
  • wp_ajax_nopriv_cc_nbis_subscribe — includes/Frontend.php
  • wp_enqueue_scripts — includes/Frontend.php
  • wp_mail_failed — includes/Mailer.php

Data Model

Persistence and integration boundary
  • Ecosystem integration story — described in the local technical reference.

API Reference

Source inventory and provenance
  • Local source digest: eacb2f8a71f23ba0b3d766225d154d0fface875ba0d33e95247602b27f344f4d
  • Repository URL: https://github.com/Athenian-Brands/athenian-notify-back-in-stock
  • Repository reference: main
  • Repository commit: 11d7c5dbf77b4ca75ddf83a06cbc5465cc9c1543
  • Source files include: assets/css/admin.css, assets/css/frontend.css, assets/js/admin.js, assets/js/frontend.js, athenian-notify-back-in-stock-icon.png, athenian-notify-back-in-stock.php, athenian-notify-back-in-stock.zip, docs/athenian-platform-marketing.md, docs/athenian-platform-technical.md, docs/notify-back-in-stock-marketing-document.md, docs/technical-marketing.md, includes/Admin/AdminController.php, includes/Admin/SignupsTable.php, includes/Autoloader.php, includes/CLI/Commands.php, includes/Frontend.php, includes/Installer.php, includes/Mailer.php, includes/Options.php, includes/Plugin.php, includes/Repository.php, includes/StockWatcher.php, includes/Util.php

Troubleshooting

Baseline review boundary
  • This baseline documents the Notify Back In Stock architecture. It does not claim that a live signup, stock transition, email delivery, or unsubscribe path has been exercised.
  • Confirm the deployed plugin version, active dependencies, and current repository tree before using implementation details as a release contract.
  • Treat payment, carrier, vendor, shipment, inventory, account, credential, tax, AI, and external-provider behavior as integration-dependent until exercised in the target environment.

FAQ

What is this page intended to establish?

A versioned, product-linked starting point for iterative developer documentation. It combines the local implementation reference with a detected-code inventory and a committed GitHub baseline.

Is the linked repository baseline verified?

Yes. The repository URL, ref, and commit recorded on this page were verified from the clean GitHub baseline prepared for this documentation pass. That does not by itself prove fleet deployment parity.

What remains for release-grade documentation?

Reconcile the recorded source baseline with the deployed plugin version, then exercise the relevant authenticated, store, provider, payment, tax, carrier, or generated-artifact paths in the target environment.

Changelog

1.1.0 2026-10-06