Running a limited product drop page: before, during and after
A drop is a small product launch with a clock on it. The page goes through three states: a waitlist that builds demand, the live product with a checkout at the stated time, and a sold-out note that keeps the interest for next time. Prepare all three before the day, so drop time is one restore and one publish, not a frantic rebuild.
The three states of the page
| State | What it shows | What it asks |
|---|---|---|
| Before | The product, photos, the drop date and time with a time zone, how many exist | Join the list to get the link first |
| Live | The same, plus price, sizes and what's left in plain words | Buy now (opens your checkout) |
| After | Sold out, what sold, when the next one might be | Join the list for the next drop |
Weeks before: set up the waitlist
- Build the waitlist version. Ask for "a single product page for a limited run of 150 enamel mugs dropping on 14 November at 10:00 UK time, with a newsletter sign-up". The newsletter form asks for an email only.
- Send sign-ups to your email tool. Connect Kit or Mailchimp so each sign-up joins the Kit form or Mailchimp audience you use for this drop. Mailchimp asks each subscriber to confirm first. Anticode doesn't email the list; your tool sends the drop announcement.
- Set up the product at your provider. In Shopify, Gumroad, Lemon Squeezy, Whop or Stripe, create the product with its price and a quantity limit, if your provider supports one, so the provider stops selling when stock runs out. Keep the product unpublished or hidden there until drop time.
- Publish the waitlist version and share it.
Days before: prepare the live version
- Note the version number of the waitlist page in version history.
- Make the live version with change requests: "replace the sign-up with a buy button and add the price and sizes". Add your checkout link in Connectors if it isn't there. There's one payment link per account, so if other sites in the account already use it, every buy button there will open this drop too; plan around that or use a separate account for drops.
- Note the live version's number, then restore the waitlist version so the builder holds what the public sees. Restoring adds a new version; nothing is lost.
- Draft the sold-out version the same way and note it, or plan to make it with a single change request on the day.
- Write the announcement email in Kit or Mailchimp and schedule it there for drop time.
Drop time
Anticode has no scheduled publishing, so someone presses the button. A few minutes before the time, make the product live at your provider. At the time, restore the live version in the builder and publish it. Open the live page on a phone and buy one item yourself, or have a friend do it, to prove the path works. Your email tool sends the announcement on its own schedule. Watch orders in your provider's dashboard: Anticode doesn't see payments.
Sold out
When your provider shows zero left, publish the sold-out version. Keep the sign-up form on it, pointed at the list for the next drop. The page then keeps working for people who arrive late from a shared link. Thank buyers from your email tool and tell them when to expect delivery.
What goes wrong
- People buy after it's gone
- The site doesn't know your stock. Rely on the provider's quantity limit, not the page, to stop overselling.
- The page goes live late
- Have two people able to publish. In a Team workspace, members can publish.
- Everyone asks what time zone
- Write the time with its zone, and the equivalent for your biggest other market.
- Sign-ups don't reach the list
- Each sign-up is sent once, without retries; compare the project's saved submissions with your list before the day.
How you know the drop worked
The live page went up within a minute of the stated time, the first order came through the checkout, nothing sold beyond the run, and the sold-out page went up the same day. The waitlist for the next drop already has names on it.
Limits
No countdown timer (published pages run no scripts), no scheduled publish, no stock counts, no cart, no queue for heavy traffic beyond what your provider's checkout handles. Anticode builds the pages, holds the versions and passes sign-ups on. See waitlist launch strategy, taking pre-orders online and version history.
Questions people ask
Can the page switch to the live version by itself at drop time?
No. There's no scheduled publish. Prepare the version in advance, then restore and publish it at the time.
Can I show a countdown on a limited product drop page?
Not a live one, since published pages run no scripts. Write the date and time with its time zone instead.
How do I stop overselling?
Set a quantity limit at your payment or commerce provider, if it offers one. The website can't count stock.