Practical guides on per-customer limits, guest checkout, HPOS, variations, and fairer launches. We explain the free and manual options first — then show where a plugin actually earns its keep.
Two rules people constantly confuse — core enforces one of them, not the other. A clear side-by-side, plus how to enforce a true lifetime per-customer limit.
Read →Why “Sold individually” isn’t a per-customer limit, and three solutions ranked from quick snippet to production plugin.
Read →Guests have no account to track. Here’s the only reliable pattern — matching at checkout by billing email — and exactly where it breaks down.
Read →A working snippet you can copy today, an honest list of everything it doesn’t handle, and the point where a plugin is the cheaper choice.
Read →Why per-cart limits reset every order, the architectural reason behind it, and what core could do but probably won’t.
Read →A practical playbook for chase variants and limited runs — per-customer caps, queueing, bots, and the trade-offs of each tactic.
Read →What High-Performance Order Storage changes for any plugin that reads order history — and what to check before you flip it on.
The honest re-order: same customer, two orders, no malice. How to stop it without annoying real buyers.
One shared cap for all colors, or a separate cap per variation? When you want each, and how to set it up.
DropLock enforces lifetime per-customer limits in one toggle. 14-day refund.
