September 26, 2026 · Muhammad Rehan · More by Muhammad Rehan
Shopify's 500,000-Variant Rate Limit — and the Plus Exemption
Once a Shopify store passes 500,000 variants, a second rate limit kicks in — unless the store runs on Shopify Plus.
Two Separate Throttles, Not One
Every GraphQL Admin API call is subject to the familiar cost-based leaky bucket: a per-second point budget that scales with plan — 100 points per second on Standard, 200 on Advanced Shopify, 1000 on Shopify Plus, and 2000 on Shopify for enterprise (Commerce Components). A single query can't exceed 1,000 points regardless of plan, and the bucket refills continuously, so short bursts are fine as long as the average stays under the restore rate.
What's less obvious is that this cost-based limit isn't the only throttle in play. Shopify's docs describe a second, separate mechanism — a resource-based rate limit — that only activates once a store's catalog crosses a specific size.
What Triggers at 500,000 Variants
Once a store has 500,000 product variants, no more than 10,000 new variants can be created per day, on any API — not just GraphQL. Within the GraphQL Admin API specifically, three mutations are named as subject to this daily throttle: productCreate, productUpdate, and productVariantCreate. An app that hits it gets a 429 Too Many Requests response with a message that a throttle has been applied.
For a systems integrator scoping a catalog migration or a bulk-import pipeline, that's a concrete planning constraint distinct from the cost-based budget: a store approaching half a million variants needs its import cadence designed around a daily variant-creation cap, not just a per-second query budget.
Why Shopify Plus Is Exempt — and Bulk Operations Aren't
Shopify states plainly that these additional limits don't apply to stores on the Shopify Plus plan. That's a documented, concrete difference in how Plus stores can be integrated versus standard-plan stores. Worth noting: Plus still runs under its own cost-based limit of 1000 points per second; the exemption is specifically from the extra 500,000-variant throttle, not from rate limiting altogether.
It's also worth being precise about bulk operations. The docs note that bulk operations don't have the max cost limits or rate limits that single queries have — but that exemption is stated for the cost-based system, not the resource-based one. Nothing in the documentation carves bulk imports out of the 500,000-variant threshold, so a large catalog migration built on bulk operations still needs to budget for that daily cap explicitly, rather than assume bulk exempts it from every limit on the platform.