Should You Build or Buy Per-Customer Drop Limits on Plus?
Per-customer drop limits are a BUILD on Shopify Plus: a Cart and Checkout Validation Function plus free Launchpad scheduling costs $8,000–$20,000 (Deploi estimate, illustrative). The one purpose-built drop app costs $299.99–$999.99/month and carries 2 App Store reviews (verified Sep 2026). Only Plus stores can install custom apps containing Function APIs. Buy a waiting room instead when fairness under load, not the limit, is the problem.
Your profile — see how the verdict shifts
- Confidence
- High — Browsed the App Store's checkout order-limits and checkout categories on 2026-09-05 and fetched the two purpose-built listings in full. Droppable (5.0★, 2 reviews, Built for Shopify) is the only listing that combines drop queuing with per-customer purchase limits, at $299.99–$999.99/month (verified Sep 2026) with hard caps of 3 to 12 drops per billing cycle and 2 to 8 items per drop. CrowdHandler Waiting Room (5.0★, 1 review, Built for Shopify) meters entry at $1,500–$5,600/month and has no purchase-limit feature at all. The order-limits category's best-reviewed option, Minmaxify Order Limits at 4.8★ on 179 reviews, caps quantities per cart and has no drop or queue mechanics, so it covers half the requirement. Two listings with three reviews between them is thin evidence for a category, which is why the build lane scores where it does. Shopify's docs state that only stores on a Shopify Plus plan can use custom apps that contain Function APIs, that a function input query is capped at 3,000 bytes and a calculated cost of 30, and that function network access must be enabled by Shopify and is unavailable on development stores or in a feature preview. Shopify's own flash-sale guidance names private mode, manual payment capture, custom flat rates and Shopify's carrier accounts, and never mentions bot protection, waiting rooms or checkout throttling as merchant-facing settings.
- Reference scenario
- $20M–$100M GMV · Shopify Plus · 6–12 timed drops a year · 200–2,000 units per drop · customer accounts required at checkout · agency or in-house dev bench
- As of
- September 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Under 500 units per drop, no resale pressure | BUY | A cart-quantity limit app from the order-limits category is enough, and the best-reviewed option there carries 4.8★ on 179 reviews. A per-cart cap stops honest over-ordering. A per-cart cap does not stop one buyer checking out five times in four minutes. |
| Plus · resellers clearing inventory across repeat orders | BUILD | The fork this page exists for. A validation function that reads a running unit count from a customer metafield enforces the cap across orders instead of inside one cart, for $8,000–$20,000 (Deploi estimate, illustrative), and Launchpad opens and closes the window at no extra cost on Plus. |
| Plus · tens of thousands arriving in the first minute | CUSTOMIZE | Load and fairness are a different product from a purchase cap. A waiting room meters 300 to 1,000 customers a minute at $1,500–$5,600/month (verified Sep 2026), and the validation function still does the limit behind it. Buy the queue, build the rule. |
| Not on Plus (Basic, Grow or Advanced) | BUY | Only Plus stores can install custom apps containing Function APIs, so the build lane isn't available to you. Public App Store apps containing functions work on any plan, which means the limit has to come from a vendor at $299.99–$999.99/month for the purpose-built option (verified Sep 2026). |
What Drop Purchase Limits Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Revenue — direct | High | A cap that holds across orders spreads a limited release over more buyers, which converts more first-time customers per unit of inventory than one reseller clearing the drop. |
| Customer experience | High | Loyal buyers who queue and lose to a bulk order stop showing up for the next release, so the enforcement quality of the limit is the drop's reputation. |
| Operational efficiency | Medium | Automated caps and scheduled windows remove the manual order-cancellation pass that support runs for two days after every unprotected drop. |
| Data & insight | Medium | Per-customer unit counts written to your own metafields give merchandising a clean read on who buys every release and who is reselling it. |
Spend ceiling: Size the spend against the inventory a drop protects, not the subscription. A 1,000-unit release is a single-day revenue event, and the difference between a per-cart cap and a per-customer cap is how much of it reaches actual customers. A $8,000–$20,000 build (Deploi estimate, illustrative) is justified by two or three drops a year; below that, buy.
What buying enables (top apps)
- + Queue and release mechanics live before your next calendar date, with drop analytics included
- + Entry metering at 300 to 1,000 customers a minute that no validation function can provide (verified Sep 2026)
- + A vendor-maintained storefront experience for the waiting room, including theme customization on higher tiers
- + No Plus requirement, since public App Store apps containing functions work on any plan
What building additionally unlocks
- + A cap counted across a customer's orders inside the drop window, not just inside one cart
- + Rules no packaged tier expresses: different caps per SKU, per customer segment or per hour of the window
- + Per-customer purchase history in your own metafields, feeding segmentation and reseller review
- + A drop calendar unbounded by tier limits on drops per cycle or items per drop
Find Your Verdict in 3 Questions
Is the store on Shopify Plus?
Yes: Go to question 2.
No: Your verdict: BUY. Only Plus stores can install custom apps containing Function APIs, so buy the limit from a vendor and require customer accounts at checkout to make the cap mean something.
Does the cap have to hold across a customer's separate orders, not just inside one cart?
Yes: Go to question 3.
No: Your verdict: BUY. A cart-quantity app from the order-limits category covers a per-cart cap, and its best-reviewed listing carries 4.8★ on 179 reviews.
Is the drop-day risk about load and fairness rather than one buyer taking too many units?
Yes: Your verdict: CUSTOMIZE. Buy a waiting room at $1,500–$5,600/month to meter entry (verified Sep 2026), and build the validation function behind it for the cap.
No: Your verdict: BUILD. A validation function reading a customer metafield counter costs $8,000–$20,000 (Deploi estimate, illustrative), and Launchpad opens the window free on Plus.
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | The drop app installs and configures inside a week, while the function, the metafield counter and the fixtures run an estimated 4–7 weeks (Deploi estimate, illustrative). | ||
| Recurring fees | $299.99–$999.99/month bills every month of the year for six or twelve drops (verified Sep 2026), and the tiers cap drops per cycle; the function carries upkeep only, and Launchpad is free on Plus. | ||
| Maintenance & upgrades | The vendor absorbs API versions for everyone, while your function needs roughly 15–20% of build cost per year (Deploi estimate) for version bumps and each new drop rule the merchandising team invents. | ||
| Switching & exit | Drop configuration and queue history live in the vendor's admin and leave with it; your rule lives in a function repository and a customer metafield you keep. | ||
| Risk | |||
| Vendor risk | The two purpose-built listings carry three App Store reviews between them, so there is little public evidence of either surviving a bad drop day; a first-party function has no vendor to lose. | ||
| Security & compliance surface | A drop app reads customer and order data under its own permissions and often injects a storefront script, while a validation function runs inside Shopify's sandbox with only the input query you wrote. | ||
| Platform-deprecation exposure | Drop apps that lean on storefront scripts inherit every theme change, and Shopify Scripts stopped executing on June 30, 2026; validation functions sit on a versioned Function API with a published upgrade path. | ||
| Value | |||
| Fit to requirement | A packaged app caps items per drop by tier, while your function expresses the actual rule: two units per customer per drop window, counted across orders and keyed to whatever identity you trust. | ||
| Time to market | Days versus one to two months, which matters when the drop calendar is already published and the next date is three weeks out. | ||
| Performance & scale | Validation functions run server-side inside an 11 million instruction budget for carts up to 200 line items, with no script on the storefront; a waiting room still wins on raw entry metering. | ||
| Data ownership & AI-readiness | Drop-by-drop unit counts written to your own customer metafields become queryable buyer history for segmentation and fraud review, instead of a report inside a vendor dashboard. | ||
| Focus & opportunity cost | Checkout rules are nobody's favorite project, though a bounded function that protects six to twelve revenue events a year pays for the attention it takes. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Droppable | Queue and Releases | Live — flagged — 5.0★ from two reviews; Built for Shopify. Priced by releases rather than by concurrency: Starter covers up to 3 drops with 2 items each, Growth up to 6 drops with 5 items and multiple integrations, Pro up to 12 drops with 8 items plus queue customization and analytics. Annual plans save 8%. Check the per-cycle drop caps against your release calendar before the tier price (verified Sep 2026). | Starter $299.99/month or $3,299.89/year; Growth $599.99/month or $6,599.89/year; Pro $999.99/month or $10,999.89/year; 7-day free trial on Starter (verified Sep 2026) | A published drop calendar that needs queue and limit mechanics live before the next release date |
| CrowdHandler Waiting Room | Live — flagged — 5.0★ from a single review; Built for Shopify. A dedicated virtual waiting room with a permanently free tier and a very steep step up between tiers: Lite holds 100 waiting customers at 10 users per minute, Plus holds 20,000 at 300 per minute, Enterprise holds 100,000 at 1,000 per minute. Size the tier by first-minute concurrency, not by monthly traffic (verified Sep 2026). | Lite free (1 waiting room, 1 store, 100 max waiting customers, 10 users/minute); Plus $1,500/month (5 waiting rooms, 2 stores, 20,000 waiting customers, 300/minute); Enterprise $5,600/month (20 waiting rooms, 5 stores, 100,000 waiting customers, 1,000/minute) (verified Sep 2026) | Drops where tens of thousands arrive at once and fairness of entry is the product |
| Checkout order-limit apps (App Store category) | Category — The checkout order-limits category holds general cart-quantity tools, and its best-reviewed option, Minmaxify Order Limits, carries 4.8★ on 179 reviews. These apps cap units per cart or per order by product, collection or customer tag. None of them schedules a drop, meters entry, or counts what a customer already bought earlier in the same window, so they cover the limit half of the requirement and none of the drop half (verified Sep 2026). | Low monthly tiers that vary by listing; confirm on the current listing (illustrative) | A per-cart cap on a normal sale where nobody is checking out five times |
| Validation Function plus Launchpad (custom) | Build lane — A Cart and Checkout Validation Function in your own custom app blocks a checkout that exceeds the cap, reading a per-customer unit count from a metafield that Flow or an order webhook updates after each order. Launchpad, free on Plus, publishes the products, swaps the theme and opens the window at the scheduled minute. Custom apps containing Function APIs are Plus-only (verified Sep 2026). | $8,000–$20,000 one-time plus roughly 15–20% of build cost per year in upkeep (Deploi estimate, illustrative) | Plus merchants whose limit has to hold across orders, not just inside one cart |
The Build Path
- Count units in a customer metafield, enforce in the function: The function sees the cart and the buyer, not order history. Write drop units purchased to a customer metafield with a Flow workflow or an order-created webhook, then read that metafield in the input query and block the checkout when cart quantity plus the stored count exceeds the cap. Keep the query under 3,000 bytes and a calculated cost of 30, and remember that metafields over 10,000 bytes aren't returned.
- Decide what a customer is before you write a line of code: A limit is only as strong as the identity behind it. Require customer accounts for the drop so the cap keys to a customer record rather than an email a buyer can vary. Decide in advance how you treat a repeat address with a new account, and accept that the metafield update lands after the order, which leaves a short race window when two checkouts complete seconds apart.
- Let Launchpad own the schedule and the function own the rule: Launchpad publishes products, applies the launch theme, sets inventory and starts the window at the scheduled minute, free on Plus. The validation function holds the cap and the shopper-facing message. Splitting the two keeps the drop repeatable: merchandising schedules the next event without a deploy, and the rule only changes when the rule changes.
- Rehearse against real load before the calendar drop: Test with the CLI's function run against fixture carts, then replay logged production inputs from a smaller release. Shopify's flash-sale guidance is worth following on the same day: private mode until the start, manual payment capture, custom flat shipping rates, and Shopify's own carrier accounts rather than yours. Rehearsal is where you find out the metafield write is slower than your buyers.
- Effort band
- $8,000–$20,000 for the validation function, the metafield counter, the shopper-facing message and drop-day fixtures — Deploi estimate (illustrative); lands in the $10–25K contact-form band
- Typical timeline
- 4–7 weeks, with a rehearsal drop before the first calendar release (Deploi estimate, illustrative)
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): roughly $1,200–$4,000/yr (Deploi estimate, illustrative) for API version bumps, new limit rules per campaign, and re-testing the counter each time the drop mechanics change.
- What you own — and what you take on
- You own: the cap rule, the per-customer counter in your metafields, the error message shoppers read, and the drop-day runbook. You take on: the identity question behind per customer, the race window between two near-simultaneous checkouts, and a Plus dependency, because the custom app stops being installable if the store leaves Plus.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $0–$1,000 (configuration and theme work) | $8,000–$20,000 |
| Years 1–3 (recurring) | $10,800–$36,000 (subscription across three years) | $3,600–$12,000 (upkeep and new rules) |
| 3-year total | ≈$10,800–$37,000 | ≈$11,600–$32,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Buy column assumes the mid tier of the purpose-built drop app held flat, billed all twelve months for six to twelve drops.
- † Build column covers the validation function, the metafield counter, fixtures and a rehearsal drop; three-year horizon.
What the Sticker Price Hides
On the buy path
- — Tiers cap what you can run, not just what you pay: 3 drops per billing cycle and 2 items per drop at the entry tier (verified Sep 2026), so the calendar has to fit the plan
- — The subscription bills all twelve months whether you run three drops or twelve, which is the real cost of six revenue events a year
- — Three App Store reviews across the two purpose-built listings means almost no public evidence of behavior under load; rehearse on a small release before trusting one
- — A waiting room meters entry and does not cap purchases, so the fairness product and the limit product are two separate buys
On the build path
- — The metafield counter updates after the order, which leaves a race window when two checkouts complete seconds apart during the first minute
- — Guest checkout defeats any per-customer rule, so requiring customer accounts for the drop is part of the build, not an option
- — Custom apps containing Function APIs are Plus-only, so the rule stops being installable if the store ever leaves Plus
- — ~$1,200–$4,000/yr in upkeep (Deploi estimate, illustrative)
What Merchants Say
The pattern merchants describe after a bad drop is the same every time: the per-cart limit held, and one buyer still took eleven pairs across six checkouts in four minutes.
Low-star reviews on limit apps cluster on enforcement gaps rather than bugs: guest checkout sidesteps the customer-level cap, and the tag the rule reads updates too slowly to matter during a drop.
If You Change Your Mind Later
If you bought and outgrow it
Drop configuration, queue settings and release history live in the vendor's admin, and uninstalling removes the limit the same minute. Export what the plan allows, write the rules down before you cancel, and sequence the exit against whatever replaces the cap rather than removing it between drops.
If you built and want out
Nothing strands on exit. The rule lives in your function repository and the unit counts in customer metafields you own, so leaving means uninstalling your own custom app. A retreat to a vendor is a configuration week, and the metafield counts convert to customer tags any limit app can read.
When This Answer Changes
We're watching for:
- ▸ Shopify adding native per-customer purchase caps to checkout settings, which would move the build lane to WAIT
- ▸ Function network access becoming generally available, since it is currently enabled by Shopify only and unavailable on development stores or in a feature preview, and it would let the cap query a live service instead of a precomputed metafield
- ▸ Review counts on the two purpose-built drop listings crossing 30, which would turn a thin category into a real buy option
Verdict change log:
No changes since first publication (September 2026).
Common Questions
Can a Shopify validation function limit purchases per customer across separate orders?
A validation function limits purchases across orders only when the customer's running total is stored where the function can read it. Validation functions see the cart and the customer, not order history, and the input query caps at 3,000 bytes with a calculated cost of 30. Write drop units to a customer metafield after each order, then have the function read that metafield.
Do per-customer drop limits require Shopify Plus?
Custom per-customer drop limits require Shopify Plus. Shopify's docs state that only stores on a Shopify Plus plan can use custom apps containing Function APIs, and Launchpad is a Plus-only app. Stores on any plan can install public App Store apps that contain functions, so a merchant below Plus buys the limit from a vendor at $299.99–$999.99/month for the purpose-built drop app (verified Sep 2026).
What does a per-customer drop limit build cost?
A per-customer drop limit build costs $8,000–$20,000 one-time plus roughly 15–20% of build cost per year in upkeep (Deploi estimate, illustrative). Scope covers the validation function, the customer-metafield counter written by Flow or a webhook, the shopper-facing error message, and fixtures. Launchpad schedules the drop window at no extra cost on Plus. Three years of the purpose-built drop app runs $10,800–$36,000 (illustrative).
Your Next Steps
If you're going with BUILD(matches your selected profile)
- Decide what a customer is for this drop, and require customer accounts at checkout so the cap has something to key on
- Write the counter first: a Flow workflow or order webhook that adds drop units to a customer metafield
- Build the validation function to read cart quantity plus the stored count, keeping the input query under 3,000 bytes
- Write the shopper-facing message before coding, because a blocked checkout with a vague error costs you the sale twice
- Rehearse on a smaller release and measure how late the counter lands under real concurrency
If you're going with BUY
- Map your published drop calendar against the tier caps on drops per cycle and items per drop
- Ask the vendor for a reference merchant at your order volume, since two reviews is not evidence
- Confirm whether the cap applies per cart or per customer across orders, in writing
- Run one small drop on the app before a flagship release, with private mode and manual payment capture per Shopify's flash-sale guidance
- Diary a re-decision once the app's annual cost passes the build estimate
Official Docs & Sources
- Cart and checkout validation functions — shopify.dev
- Shopify Functions overview and the Plus gate — shopify.dev
- Function limits and input query budgets — shopify.dev
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Cart Transform vs. a Bundle App: Who Owns Pricing?
Overriding a bundle line's price, title and image with Cart Transform's lineUpdate works only on development stores or Shopify Plus; bundle apps cover the rest.
Should You Run a Custom Cart Transform Alongside an App's?
Shopify caps cart transform functions at one per app rather than one per store, and runs every app's function, so a custom one can sit beside a bundle app's.
Branding API vs. the Free Checkout Editor: Do You Need Code?
The free checkout and accounts editor covers most branding on every plan; Plus API overrides add precision, and the Checkout Blocks branding editor ends 2026-12-31.
Checkout Extension Network Access: What Shopify Actually Allows
Checkout UI extensions declare four capabilities in the extension TOML file, and network_access is the one Shopify makes you request before publishing.
Should You Build or Buy Your Shopify Scripts-to-Functions Migration?
A Scripts-to-Functions migration is a build for any store whose checkout logic still earns money — unported rules have already gone silent.
Ready to make your drop limit hold across orders?
We start with the identity question, because a cap keyed to something a buyer can change is decoration. Then we scope the validation function, the customer-metafield counter and the shopper-facing message, wire Launchpad to open and close the window, and rehearse the whole thing on a smaller release before your calendar date.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing carries its verification date and gets re-verified quarterly. Platform gates and function limits quoted from shopify.dev as of September 2026. Full scoring anchors: see the TCC methodology.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.