Reference

The lists a Back In Stock configuration is built against. They are generated from the extension's own code, so they match what the version you installed does.

• Settings: every setting the module keeps, its shipped default and what it does, and what the module fixes on purpose and why.
• Email wording: what the two emails' wording may carry.
• The API: the one read resource an integration may call, every field on it, and what the promise covers.
• What this holds about a person: every table and column about a person, why it is there, how long it is kept and what an erasure does to it.
• Security verdict: each control in the shared security baseline, and whether Back In Stock meets it.
• What it costs: what the extension adds to nineteen stock pages, in queries, bytes and requests.

Three things those lists cannot tell you, because they are not lists:

• What a counter is. Back In Stock keys everything to a counter: one product, or one option value of it. That is the smallest thing a shopper can be alerted about and the smallest thing a stock figure exists for in OpenCart. Limits and guarantees writes out what follows from that, including the two cases where the form is deliberately withheld.
• What wakes the sweep. Nothing here is sent by a shopper viewing a page. A product save in the admin, or an order change that puts stock back, sends the first batch for those products at once; everything after that waits for the sweep, and none of the settings above changes that. Keeping the sweep running covers it, and the settings screen lists the same three ways in with your own store's paths filled in.
• What happens at the edges. What an update keeps, what an uninstall leaves behind, what a retention change reaches, and what is deliberately not built. All of that is on limits and guarantees; read it beside this page.