A waiting room for Shopify drops — in development, and open for early access

Where this actually stands

Shopify support is in development. It is not shipping, and there is no date on this page — not because we are being coy, but because a roadmap position published on a marketing page is a promise, and we would rather be useful than early.

What ships today is a Cloudflare edge connector and a WooCommerce plugin. If you are on Shopify and you need a waiting room this week, the honest answer is that CrowdHandler and Queue-it both have Shopify products and we do not. Go and look at those. We would rather tell you that here than three emails into an evaluation.

If your drop is further out, read on — and tell us, because the order these things get built in is decided by who asks.

What you would be getting

The argument is not “another queue app”. It is a different shape:

You set the admission rate, and there is no floor. This is the specification that decides whether a queue can run a drop at all, and it is where the category is weakest. A Cloudflare waiting room cannot admit fewer than 200 people a minute — that minimum is in their own configuration documentation and cannot be lowered — so a 500-unit drop is over in two and a half minutes. CrowdHandler’s entry tier caps outflow at 60 a minute, which you also cannot change. Ours is a dial, from a trickle to unthrottled, identical on every plan including the cheapest.

A presale drop is drawn at random, not raced for. Registration opens over a window, nobody gets a position while it is open, and every position is assigned by keyed pseudorandom permutation the moment the drop starts. Someone who registers in the first millisecond and someone who registers 47 minutes later have identical expected position. It is standard here rather than an enterprise event feature. (Queue-it also ships randomisation at event start — we are not unique in having it.)

Bundled, not gated. Cryptographic fairness, bot defence and the branding studio are included at the entry price. In this category those are routinely separate SKUs. (Order-level spent-pass enforcement is also standard — on WooCommerce. It is the one part that would have to be rebuilt for Shopify, and the next section says why.)

Your store keeps selling if we have a bad day. The system fails open by design, and enforcement runs inside your own stack rather than in front of it.

What is genuinely harder on Shopify

Worth saying, because it explains the order of the roadmap rather than dressing it up.

On WooCommerce the enforcing code runs inside the store — a plugin in your PHP, verifying a signed pass locally with no network call, and enforcing one order per pass at checkout. Shopify does not offer that seam. Checkout is Shopify’s, not yours, and the order-level enforcement that stops one admission becoming five orders has to be built differently there.

That is the interesting part of the problem and the reason it is not a two-week port. It is also why we would rather talk to a handful of Shopify merchants first than ship the shallow version.

Tell us you need it

Email hello@dropify.dev with what you sell and roughly what a drop looks like — unit counts, how much traffic you see, whether bots are already a problem. Early access means you get it before it is public and your problems shape what it does.

No form, no sequence, no drip campaign. One of the people writing the code reads it.