Plain-English arithmetic on "Run my numbers"
▎ The calculator now asks how many people are typically waiting when something comes back, instead of quietly assuming one. Leave it at one and every figure reads exactly as before
Changelog
What we have shipped.
Restock Notify is built and maintained by one person, in the open. Every change that reached a shop is listed here, newest first.
We corrected what we said about how restock alerts go out
Our own pages said a restock alert goes to "only as many people as there are units on the shelf." That was wrong. The alert invites about two people per unit that came back, on purpose — inviting exactly as many people as you have stock assumes every one of them comes in, and most do not, so the stock sits while the rest of the list waits. Anyone not invited keeps their place and hears on the next delivery. Our pages now say that, and a test fails if they ever drift from what the software does again.
Two new pages: everything the product does, and how your data is handled
A Features page listing what Restock Notify does, with anything not yet live marked as such on the line itself rather than in a footnote. And a security page describing where your shop's data is stored and who can reach it.
The customer page opens faster on a large book
Opening a single customer used to read your whole customer book first — every customer, every purchase — to answer three shop-wide facts alongside that one person. On a large book that was close to a second, paid on every view. It now builds the one profile it needs and answers the rest from summary queries.
Merging two duplicate customers no longer fails
Tidying up duplicate customer records could fail partway through, leaving the merge half-done. Two tables were missed when the merge walked your account's data. Both are handled now, and the customer's totals rebuild correctly afterwards.