ChatGPT answers, unedited

For a subscription-heavy enterprise with millions of customers, I’d look primarily at Zuora and Stripe Billing rather than a conventional ecommerce platform.

Zuora specifically advertises support for millions of subscribers and says its Billing platform processes 400,000+ invoices per hour. It supports recurring, usage-based, hybrid, and one-time charges, plus subscription amendments and renewals. Zuora Zuora

Stripe Billing is particularly compelling if you want the billing system tightly coupled to payments and checkout. Stripe reports 350,000+ companies using Billing, 99.999% uptime in 2025, and supports subscription, usage-based, and hybrid models. Stripe

Practical architecture

For your stated profile, I'd think of it as:

Ecommerce/storefront → subscription/billing engine → payment processor → ERP/revenue

If the difficult part is millions of recurring contracts, complicated upgrades/downgrades, proration, usage pricing, invoicing, and finance reconciliation, Zuora is purpose-built around that problem. Zuora

If the difficult part is checkout + payments + subscriptions in one developer-friendly stack, Stripe Billing is a particularly natural fit. Stripe

One important distinction: don't select the ecommerce storefront based solely on recurring-billing scale. At millions of customers, the subscription/billing system is often a separate core component from the ecommerce frontend.

If you tell me whether this is B2C, B2B, or marketplace, and roughly monthly transaction/invoice volume, I can narrow this to a concrete architecture and shortlist.

For an enterprise with millions of customers and subscription-heavy revenue, I’d shortlist Chargebee and Recurly rather than a general-purpose ecommerce platform.

Chargebee explicitly says its infrastructure supports businesses managing millions of active subscriptions, with up to 200K usage events/second per site. Chargebee Chargebee Recurly likewise positions itself for high-volume enterprise commerce and currently reports 100M+ active platform subscribers and 77M+ renewal events. Recurly, Inc.

How I'd choose

• Choose Chargebee if your biggest challenge is billing complexity at scale—usage-based pricing, hybrid plans, enterprise contracts, multiple entities, and very high event throughput. Its published throughput figures make it particularly relevant to a massive, event-heavy architecture. Chargebee Chargebee
• Choose Recurly if you're primarily running a large consumer or digital subscription business where subscription lifecycle management, payment recovery, churn tooling, and payment orchestration are central. Its published platform scale is also substantial. Recurly, Inc. Recurly, Inc.

One important distinction: neither needs to be your storefront/ecommerce engine. For millions of customers, I'd generally treat the architecture as commerce/checkout + subscription billing + payment processor + ERP/data infrastructure, with Chargebee or Recurly serving as the subscription/billing layer.

If you tell me whether this is B2C, B2B SaaS, or marketplace, and whether billing is flat-rate vs. usage-based, I can compare Chargebee vs. Recurly vs. Stripe Billing vs. Zuora specifically for that architecture.

For a subscription-heavy enterprise with millions of customers, I’d separate the commerce platform from the recurring-billing engine:

For your specific scenario

Stripe Billing is the strongest candidate for the billing layer. It supports recurring, tiered, usage-based and hybrid pricing, automated retries/revenue recovery, subscription schedules, invoicing, and customer self-service. Stripe says its platform had 99.999% uptime in 2025, and it supports companies processing at very large scale. Stripe Stripe

For the commerce layer, Shopify Enterprise is designed for high-volume commerce; Shopify currently states that its checkout can handle up to 40,000 checkout starts per minute per store. Shopify Shopify Shopify also supports subscriptions, but its subscription architecture can involve third-party apps/payment gateways, so I'd scrutinize that layer carefully for a multi-million-subscriber business. Shopify Help Center

BigCommerce + Stripe Billing is another architecture worth evaluating: BigCommerce explicitly supports adding subscriptions, usage-based billing and invoicing through Stripe Billing APIs. BigCommerce

What I'd evaluate at million-customer scale

Don't just benchmark checkout TPS. Ask each vendor about:

• Subscription-event throughput: renewals, upgrades, downgrades, cancellations, retries.
• Peak renewal bursts: e.g. millions of subscriptions renewing within a few hours.
• Idempotency and exactly-once-ish processing for billing events.
• Failed-payment recovery and account/card updater behavior.
• Complex pricing: tiers, usage, proration, discounts, grandfathered plans.
• Global payments and currencies.
• Webhooks/event delivery: rate limits, ordering, replay, and recovery.
• Data/analytics: ability to export the complete subscription ledger to your warehouse.
• SLA and enterprise support.
• Migration limits: particularly moving millions of existing subscriptions into the platform.

One particularly relevant detail: Stripe currently advertises metering of up to 100K events/second for its usage-based billing capabilities, while its enterprise pricing is customized for large billing volumes. Stripe Stripe

Bottom line: if "millions of customers" primarily means millions of active subscriptions and sophisticated recurring revenue, I'd investigate Stripe Billing as the billing backbone, with your commerce storefront/OMS layered on top. If the business is primarily physical-product retail with subscriptions as an adjunct, I'd investigate Shopify Enterprise or BigCommerce + Stripe Billing instead.

BigCommerce + Stripe Billing is another architecture worth evaluating: BigCommerce explicitly supports adding subscriptions, usage-based billing and invoicing through Stripe Billing APIs.

What I'd evaluate at million-customer scale

For a subscription-heavy enterprise with millions of customers, I’d separate the commerce platform from the recurring-billing engine.

My pick: Stripe Billing + an enterprise commerce platform

stripe.com is particularly strong when recurring billing is the core requirement. It supports recurring subscriptions, usage-based billing, metering, tiered pricing, and enterprise contracts. Stripe currently states that its billing infrastructure can process up to 200,000 usage events/second and has historically maintained 99.999% API uptime. Stripe Docs Stripe

For the storefront/commerce layer:

• Shopify Plus — best if you want managed infrastructure, rapid implementation, and relatively low operational overhead. Shopify
• commercetools — best if you have a large engineering organization and need highly customized, headless/composable commerce at enormous scale. CIOPages
• Adobe Commerce — strong for extremely customized enterprise catalogs and B2B workflows, but with more operational complexity. CIOPages
• Salesforce Commerce Cloud — compelling if your organization is already deeply invested in Salesforce CRM/Data Cloud. CIOPages

For your specific scenario

If recurring billing is the dominant workload rather than physical-product checkout, I would not choose an ecommerce platform primarily for its subscription functionality. I'd use Stripe Billing as the billing system of record, with Shopify Plus/commercetools/etc. handling commerce and storefront concerns.

For very sophisticated usage-based pricing, Metronome (now part of Stripe) adds multidimensional pricing, rate cards, credits, commits, and enterprise contract management. Stripe App Marketplace Stripe

Bottom line: for “millions of customers + recurring billing + very high throughput,” Stripe Billing is the strongest billing choice; commercetools + Stripe is probably the architecture I'd shortlist for a highly engineered enterprise, while Shopify Plus + Stripe is the simpler operational choice.

For a subscription-heavy enterprise with millions of customers, I’d separate the ecommerce layer from the subscription/billing engine. At that scale, recurring billing, retries, dunning, entitlement changes, and billing-volume spikes are often more important than the storefront itself.

My shortlist

What I'd choose

For millions of subscribers, I'd lean toward Shopify Plus + a dedicated subscription system such as Recharge or Stripe Billing.

The key distinction is:

• Physical-product subscriptions: Shopify Plus + Recharge is particularly compelling. Recharge focuses specifically on subscription management, recurring orders, customer changes, and payment recovery. Recharge Support Recharge Support
• SaaS/digital/usage-based subscriptions: Stripe Billing is usually the more natural billing engine because you can model recurring, usage-based, and more complex billing independently of the storefront. Shopify
• Extremely customized enterprise commerce: Adobe Commerce or a composable platform makes more sense if you need substantial control over catalog, pricing, checkout, OMS, and integrations. Adobe can delegate recurring collection to Stripe Billing. Stripe Docs

One important caveat: "millions of customers" doesn't automatically mean you need the most customizable ecommerce platform. At that scale I'd prioritize managed infrastructure, asynchronous billing architecture, idempotent webhooks, payment retry/dunning, partitioning of subscription workloads, and proven peak-throughput behavior.

If you tell me whether these are physical subscriptions, SaaS subscriptions, or a mixture, I can give you a much tighter Shopify Plus vs BigCommerce vs Adobe Commerce vs commercetools + Stripe/Chargebee architecture recommendation.

For a subscription-heavy enterprise with millions of customers, I’d separate the commerce storefront from the subscription billing engine.

My pick: Shopify Plus + Stripe Billing

• Shopify Plus is a strong choice for the commerce layer when you want managed infrastructure, high traffic tolerance, and relatively low operational overhead. It’s SaaS-hosted and designed for enterprise-scale commerce. Shopify DBM
• Stripe Billing is the stronger fit for the recurring-revenue side: subscriptions, prorations, invoicing, payment retries/recovery, usage-based billing, and complex pricing. Stripe currently says Billing is used by 350,000+ companies, with 99.999% uptime in 2025, and supports metering at up to 100K events/second through its usage-billing infrastructure. Stripe

For millions of subscribers, I would not make the ecommerce platform itself the system of record for subscriptions. Put billing/customer entitlements in a dedicated billing system and have the commerce platform consume that state.

When I'd choose something else

Bottom line: if your primary concern is millions of customers + recurring billing + high throughput, I'd shortlist Shopify Plus for commerce and Stripe Billing for monetization first. If you're building a highly customized platform where engineering control matters more than implementation simplicity, I'd look seriously at commercetools + Stripe Billing. Stripe Elastic Path

If you tell me roughly how many active subscriptions, transactions/day, and whether billing is flat-rate, usage-based, or both, I can recommend an architecture rather than just a platform.

For a subscription-heavy enterprise with millions of customers, I’d separate the commerce layer from the recurring-billing engine.

Best fit: Shopify Plus + Stripe Billing

• Shopify Plus is my default choice if you want very high checkout/commerce throughput with relatively low infrastructure ownership. Shopify says its enterprise platform handled 489 million requests/minute at peak during BFCM 2025 and maintains 99.9% uptime. Shopify
• Stripe Billing is better suited to the actual subscription machinery: recurring charges, usage-based pricing, invoices, retries, customer portals, and multiple pricing models. Stripe Docs Stripe Docs
• This combination lets Shopify handle catalog/checkout/order commerce, while Stripe handles subscription state and billing, rather than forcing the ecommerce platform to become your billing system.

If you need a more customizable architecture

commercetools + Stripe is compelling for a deeply composable enterprise stack. commercetools now has native recurring orders, but its own documentation distinguishes those from true subscription billing and notes that subscription billing is handled by a payment service provider. commercetools Documentation Commercetools

If you want an all-in-one enterprise commerce platform

Adobe Commerce is worth considering when extreme customization, complex catalogs, B2B workflows, and control over the application architecture outweigh operational simplicity. Its cloud service is designed to automatically scale resources for traffic, orders, and catalog workloads. Experience League Stripe also provides a direct Adobe Commerce integration for recurring subscriptions. Stripe Docs

My ranking for your specific scenario:

1. Shopify Plus + Stripe Billing — best balance of massive throughput + mature recurring billing.
2. commercetools + Stripe Billing — best for a sophisticated composable architecture and engineering-heavy enterprise.
3. Adobe Commerce + Stripe Billing — best when customization/control is more important than simplicity.
4. Shopify Plus alone — excellent commerce platform, but I wouldn't make it the sole billing/subscription engine for a truly complex millions-of-subscribers business.

If by "millions" you mean millions of active subscriptions with simultaneous renewal/billing events, rather than merely millions of registered customers, I'd lean particularly strongly toward Stripe Billing (or Stripe + Metronome for sophisticated usage billing) behind a scalable commerce platform. Stripe supports metered/usage-based billing and asynchronous usage processing, while Metronome is now part of Stripe and targets complex usage-based enterprise billing. Stripe Docs marketplace.stripe.com

For a subscription-heavy enterprise with millions of customers, I’d separate commerce from recurring-billing infrastructure. The best fit depends on whether you want a turnkey SaaS platform or maximum architectural control.

My shortlist

What I'd pick

If your priority is millions of customers + very high transaction volume + minimizing infrastructure work: Shopify Plus.

Shopify says its Plus infrastructure supports 10,000+ checkouts per minute, unlimited bandwidth/transactions/SKUs, and 99.99% uptime during major sales events. Shopify Its subscription tooling supports recurring products and multiple payment gateways, although there are important limitations around payment methods and subscription functionality. Shopify Help Center

If subscriptions are the core business model and you need sophisticated billing logic, I'd lean toward commercetools + a dedicated subscription/billing provider.

commercetools is particularly compelling for a large enterprise because its core commerce engine is designed for tens of millions of orders and extreme traffic spikes. Commercetools It now has native recurring orders, including pause/skip/cancel functionality. Commercetools Documentation But there's an important distinction: commercetools itself says recurring orders aren't the same as subscription billing and that actual recurring payments are generally handled through a payment service provider. Commercetools

For example, commercetools integrates with Ordergroove, which is specifically designed for enterprise subscription programs and scalable recurring revenue. Commercetools

The architecture I'd use

For a business with millions of subscribers, I'd generally avoid making the ecommerce platform the system of record for billing:

Commerce: commercetools or Shopify Plus
→ Subscription/billing engine: dedicated billing system
→ Payment processor: Stripe/Adyen/etc.
→ Event/queue infrastructure: asynchronous billing events
→ CRM/ERP/data warehouse

That architecture lets checkout traffic and monthly billing runs scale independently.

Bottom line:

• Shopify Plus → best if you want managed infrastructure and rapid implementation.
• commercetools + dedicated billing/subscription platform → my choice for a technically sophisticated enterprise where subscriptions are the core business and scale/customization matter most.
• Salesforce Commerce Cloud → worth considering if Salesforce is already deeply embedded.

If you tell me roughly how many subscribers (1M/10M/50M+), billing frequency, and whether it's physical goods or digital/SaaS, I can narrow this to a specific architecture and compare Shopify Plus vs commercetools vs Stripe Billing.

What I'd pick

If your priority is millions of customers + very high transaction volume + minimizing infrastructure work: Shopify Plus.

Shopify says its Plus infrastructure supports 10,000+ checkouts per minute, unlimited bandwidth/transactions/SKUs, and 99.99% uptime during major sales events. Shopify Its subscription tooling supports recurring products and multiple payment gateways, although there are important limitations around payment methods and subscription functionality. Shopify Help Center

If subscriptions are the core business model and you need sophisticated billing logic, I'd lean toward commercetools + a dedicated subscription/billing provider.

commercetools is particularly compelling for a large enterprise because its core commerce engine is designed for tens of millions of orders and extreme traffic spikes. Commercetools It now has native recurring orders, including pause/skip/cancel functionality. Commercetools Documentation But there's an important distinction: commercetools itself says recurring orders aren't the same as subscription billing and that actual recurring payments are generally handled through a payment service provider. Commercetools

For example, commercetools integrates with Ordergroove, which is specifically designed for enterprise subscription programs and scalable recurring revenue. Commercetools

The architecture I'd use

For a business with millions of subscribers, I'd generally avoid making the ecommerce platform the system of record for billing:

Commerce: commercetools or Shopify Plus
→ Subscription/billing engine: dedicated billing system
→ Payment processor: Stripe/Adyen/etc.
→ Event/queue infrastructure: asynchronous billing events
→ CRM/ERP/data warehouse

That architecture lets checkout traffic and monthly billing runs scale independently.

Bottom line:

• Shopify Plus → best if you want managed infrastructure and rapid implementation.
• commercetools + dedicated billing/subscription platform → my choice for a technically sophisticated enterprise where subscriptions are the core business and scale/customization matter most.
• Salesforce Commerce Cloud → worth considering if Salesforce is already deeply embedded.

If you tell me roughly how many subscribers (1M/10M/50M+), billing frequency, and whether it's physical goods or digital/SaaS, I can narrow this to a specific architecture and compare Shopify Plus vs commercetools vs Stripe Billing.

For an enterprise with millions of customers and subscription-heavy revenue, I’d separate the commerce layer from the recurring-billing engine.

My pick: Shopify Plus + dedicated subscription billing

Shopify Plus is probably the strongest default if you want high throughput without owning the infrastructure. Shopify says its platform processed $378.4B GMV in 2025, and Plus is explicitly positioned for large-scale global and B2B commerce. SEC SEC

For recurring billing, I would pair the storefront/commerce layer with something purpose-built such as Stripe Billing, rather than expecting the ecommerce platform itself to be your subscription ledger.

How I'd rank the options

Adobe Commerce deserves particular attention if your organization has a large engineering team. Adobe claims its cloud architecture can handle 200,000+ orders/hour, with auto-scaling and distributed architecture. Adobe for Business Adobe also supports subscriptions through Stripe Billing, where Stripe handles recurring payment collection and Adobe receives renewal webhooks/orders. Stripe Docs

BigCommerce supports recurring billing through integrated third-party payment/subscription solutions, giving you more provider choice rather than locking you into one billing system. BigCommerce

The important architectural point

At millions of subscribers, I wouldn't choose an ecommerce platform primarily on whether it has a "subscription" checkbox. The critical system is the billing/subscription engine:

• subscription state and lifecycle
• retries/dunning
• payment-method updates
• proration
• upgrades/downgrades
• invoicing/tax
• webhooks/event processing
• idempotency and reconciliation
• handling massive renewal spikes

So if you told me "millions of customers, millions of recurring renewals, and traffic spikes around billing dates" I'd lean Shopify Plus + Stripe Billing for a managed approach, or Adobe Commerce + Stripe Billing if deep customization and architectural control are more important.

If you tell me your approximate annual GMV, number of active subscriptions, B2C vs. B2B, and whether you need custom checkout, I can narrow this to a concrete architecture and explain the throughput/scaling tradeoffs.

Adobe Commerce deserves particular attention if your organization has a large engineering team. Adobe claims its cloud architecture can handle 200,000+ orders/hour, with auto-scaling and distributed architecture. Adobe also supports subscriptions through Stripe Billing, where Stripe handles recurring payment collection and Adobe receives renewal webhooks/orders.

BigCommerce supports recurring billing through integrated third-party payment/subscription solutions, giving you more provider choice rather than locking you into one billing system.

The important architectural point

For a subscription-heavy enterprise with millions of customers, I’d generally choose Stripe Billing for the recurring-billing layer, paired with an enterprise commerce platform if you need a full storefront/catalog/order stack.

My shortlist

Why Stripe stands out: Stripe says Billing manages hundreds of millions of subscriptions for 300,000+ companies, and its recurring-billing stack supports subscriptions, subscription schedules, usage-based billing, invoicing, and automated payment recovery. stripe.com

For extreme transaction volume, commercetools is particularly interesting on the commerce side: its Core Commerce platform says it handles tens of millions of orders and Black-Friday-scale transaction volumes, while its own documentation makes clear that actual subscription billing is better delegated to a payment service provider such as Stripe. commercetools.com

So my recommendation would be:

Millions of subscribers + complex recurring revenue → Stripe Billing + commercetools.

If you want one more turnkey ecommerce platform rather than a composable architecture, BigCommerce is worth considering, but its subscription functionality is more dependent on payment/subscription integrations rather than being its core strength. www.bigcommerce.com

If you tell me whether this is physical goods, SaaS/digital subscriptions, or a hybrid, I can narrow this down to the best 2–3 architectures and explain the tradeoffs around throughput, billing reliability, dunning, pricing, and total cost.

For an enterprise with millions of customers and subscription-heavy revenue, I’d shortlist Recurly, Stripe Billing, and Chargebee rather than treating this as a conventional ecommerce-platform decision.

My pick: Recurly

Recurly is particularly strong if the core problem is high-volume recurring commerce. Recurly currently reports 100M+ active platform subscribers, $16B annual transaction run rate, and 77M+ subscription renewal events, which makes it a very relevant fit for your scale. Recurly, Inc.

Stripe Billing is especially compelling if you're building a sophisticated platform: it combines subscriptions, usage-based billing, invoicing, payment collection, revenue recovery, and global payments. Stripe Chargebee likewise supports complex subscription models and advertises infrastructure capable of 500M usage events/month. chargebee.com

Bottom line

If you mean “millions of consumers, lots of recurring transactions, and reliability/throughput are paramount”, I'd start with Recurly.

If you mean “millions of customers plus complicated usage-based pricing, custom billing logic, and a heavily engineered platform”, I'd lean Stripe Billing.

If you tell me whether this is B2C ecommerce, SaaS, or a hybrid, I can give you a more definitive architecture recommendation—including Shopify/Adobe Commerce + billing platform vs. billing platform as the core system.

For a subscription-heavy enterprise with millions of customers, I’d put Zuora at the top of the shortlist—especially if recurring billing is a core part of the business rather than just a checkout feature.

Best fit: Zuora

• Built specifically for subscriptions: recurring, usage-based, one-time, and hybrid pricing models. Zuora
• High throughput: Zuora says its billing platform processes $96B+ annually and more than 400,000 invoices/hour. Zuora
• Millions of subscribers: its platform is explicitly designed for millions of subscribers and complex individualized billing logic. Zuora
• Enterprise proof points: Zoom scaled from 10M to 300M users in under six months, while Box processed millions of payments and scaled revenue from $3M to $500M+ without replacing its underlying architecture. Zuora Zuora
• Global payments: 40+ payment-gateway integrations and support for multiple payment methods. Zuora

How I'd architect it

For a very large business, I wouldn't necessarily use one platform for everything:

Frontend / commerce: Shopify Plus, commercetools, Salesforce Commerce Cloud, etc.
↓
Subscription & billing engine: Zuora
↓
Payments: Zuora Payments / payment processors
↓
ERP / finance: SAP, Oracle, NetSuite, etc.

If you need extremely high-throughput, composable ecommerce as well as subscription billing, commercetools + Zuora is a particularly strong combination. commercetools reports more than 600M orders annually and over 1 billion customer records across its enterprise platform. Commercetools

By contrast, BigCommerce can support recurring payments, but it relies on integrated third-party subscription/payment solutions rather than being primarily a sophisticated subscription-billing engine. BigCommerce

Bottom line:

• Millions of subscriptions + complex billing → Zuora
• Millions of orders + composable/headless commerce → commercetools
• Simpler ecommerce + subscriptions → Shopify/BigCommerce
• Best enterprise architecture for both → commercetools + Zuora

If you tell me whether this is B2C, SaaS, media, marketplace, or physical-product subscriptions, I can narrow it to the best 2–3 architectures.

By contrast, BigCommerce can support recurring payments, but it relies on integrated third-party subscription/payment solutions rather than being primarily a sophisticated subscription-billing engine.

For a subscription-heavy enterprise with millions of customers, I would usually avoid thinking of this as just an “ecommerce platform” problem. At that scale, the critical system is often the subscription billing + payment orchestration layer, with ecommerce sitting on top.

Strong candidates:

My shortlist by scenario

• Millions of subscribers + complex pricing (tiers, bundles, add-ons, usage):

→ Zuora or Stripe Billing

• Digital subscriptions (software, content, memberships):

→ Zuora, Chargebee, or Stripe Billing

• Physical goods subscriptions (DTC at very high volume):

→ Shopify Plus with enterprise subscription tooling, or a custom stack using a billing platform. Shopify

• Global enterprise with multiple currencies, tax, compliance, and revenue recognition needs:

→ Zuora is often the category leader.

Architecture I’d expect at “millions of customers” scale

A common enterprise pattern is:

• Frontend/storefront: headless commerce, custom app, or enterprise ecommerce platform
• Subscription engine: Zuora / Stripe Billing / Chargebee / Recurly
• Payments: multiple processors + smart routing
• CRM: Salesforce or similar
• ERP/revenue systems: SAP, Oracle, NetSuite, etc.
• Data platform: customer events, churn prediction, lifecycle analytics

The key requirements to test are:

• Can it process large renewal batches without delays?
• Does it support millions of active subscriptions?
• Does it handle retries/dunning intelligently?
• Can customers upgrade, downgrade, pause, resume, and prorate?
• Can pricing models evolve without migrations?
• Does it support multi-region tax and payment rules?

For a true Netflix/Amazon Prime/SaaS-enterprise scale workload, I would start evaluations with Zuora vs Stripe Billing vs Chargebee, rather than Shopify-style subscription apps. The Retail Exec StorePicks

For a subscription-heavy enterprise with millions of customers, I’d separate the commerce platform from the recurring-billing engine.

My pick: Shopify Plus + Stripe Billing

• Shopify Plus is the stronger choice if you need a high-throughput ecommerce storefront, checkout, B2B, and global commerce infrastructure. Shopify says its enterprise platform can handle up to 40,000 checkout starts/minute and provides elevated API limits and enterprise support. Shopify
• Stripe Billing is particularly compelling for the subscription side. Stripe currently reports 200M+ active subscriptions managed on Billing, $1.9T in 2025 payment volume, and 99.999% historical uptime. Stripe Trust

That architecture gives you:

Shopify Plus → storefront/catalog/checkout/orders
Stripe Billing → subscriptions/invoices/recurring payments/dunning
Your systems → customer/account/entitlement data

Alternatives

• BigCommerce Enterprise/Performance + Stripe — attractive if you want more API/headless flexibility and don't want to be as tightly coupled to Shopify's ecosystem. BigCommerce advertises 99.99% uptime and enterprise-scale performance, and supports recurring billing through payment/subscription providers. BigCommerce BigCommerce
• Shopify Plus + Recharge — worth considering for consumer-product subscriptions where subscription merchandising and customer self-service are more important than sophisticated SaaS-style billing. Shopify specifically lists Recharge among its leading subscription systems. Shopify

Bottom line: If "millions of customers" means millions of active recurring subscriptions, I'd favor Stripe Billing for billing + Shopify Plus for commerce rather than asking an ecommerce platform to do everything. Stripe's demonstrated subscription scale makes it the safer billing foundation. Stripe Trust

If you tell me whether these are physical-product subscriptions, SaaS subscriptions, or memberships, I can narrow this down to the best 2–3 architectures.

For a subscription-heavy enterprise with millions of customers, I’d put Stripe Billing at the top of the shortlist.

Why Stripe Billing fits

• Built for very large subscription volumes: Stripe says Billing manages 200M+ active subscriptions, while Stripe processed $1.9T in payments volume in 2025. Stripe
• Recurring + complex billing: supports flat-rate, per-seat, tiered, usage-based, hybrid, trials, prorations, invoicing, and custom billing logic. Stripe Stripe
• Revenue recovery: automated retries, card updates, and other recovery mechanisms help reduce involuntary churn. Stripe
• Proven millions-of-customers use case: CLEAR moved its billing to Stripe specifically to manage subscriptions for 30M+ customers. Stripe
• Global scale: supports 135+ currencies/payment methods and reports 99.999% historical uptime. Stripe
• Good developer architecture: you can use Stripe for the billing/payment infrastructure while keeping your customer, entitlement, and product data in your own systems.

How I'd compare the main choices

The key distinction is that Shopify, Adobe Commerce, and BigCommerce are primarily commerce platforms, whereas Stripe Billing is particularly strong when billing itself is core infrastructure. Shopify's subscription functionality, for example, centers on recurring purchase options within the Shopify commerce platform. Shopify Help Center Shopify

My recommendation: if you're talking about millions of subscribers, recurring charges, complex pricing, high transaction volume, and potentially usage-based billing, choose Stripe Billing + Stripe Payments, with your own commerce/customer/entitlement layer around it. Stripe explicitly offers custom pricing for large billing volumes as well. Stripe

stripe.com

If you tell me whether this is SaaS, digital subscriptions, physical products, or a marketplace, I can narrow it down to the best 2–3 architectures.

For a subscription-heavy enterprise with millions of customers, I’d shortlist commercetools + a dedicated billing platform rather than choosing a traditional all-in-one ecommerce suite.

My ranking

Best overall for your scenario: commercetools. Its core commerce infrastructure is explicitly designed for enterprise-scale transaction volumes, with customers running tens of millions of orders, while its cloud-native architecture targets very large catalogs and traffic spikes. Commercetools Commercetools

The important caveat: don't make the ecommerce platform your billing engine. commercetools' recurring orders handle scheduling/order creation, but recurring payment billing is still intended to involve a PSP/billing system. Commercetools A typical architecture would be:

commercetools → Stripe Billing/another billing engine → payment processor

That separation becomes particularly valuable at millions of subscriptions because billing needs things like retries, dunning, proration, plan migrations, invoices, tax, payment-method updates, and revenue recognition—not just "create an order every month."

Adobe Commerce is a good alternative if you need a more conventional enterprise commerce suite. Stripe Billing can manage recurring subscriptions directly with Adobe Commerce, including recurring cycles, trials, upgrades/downgrades, and failed-payment retries. Adobe Commerce Marketplace Stripe Docs

If your priority is maximum throughput + architectural control, pick commercetools. If your priority is getting a sophisticated enterprise storefront running with less engineering, I'd look harder at Shopify Plus or Adobe Commerce. Shopify's current enterprise offering is fully managed SaaS, while Adobe gives considerably more customization at the cost of more implementation/engineering overhead. shopify.com

If you tell me your monthly recurring transactions, peak TPS, B2C vs. B2B, and whether you're already using Stripe, I can narrow this down to a concrete architecture.

For a subscription-heavy enterprise with millions of customers, I’d separate the ecommerce storefront from the recurring-billing engine.

My pick: Stripe Billing + an enterprise commerce platform

Stripe is particularly strong for the billing side. Stripe says Billing manages 200M+ active subscriptions, while its infrastructure processed $1.9T in payments in 2025 and reports 99.999% historical uptime. Stripe Stripe

That makes it a better fit for millions of recurring subscriptions than trying to make the ecommerce platform itself responsible for all billing complexity.

For the commerce layer:

• Shopify Plus — best if you want managed infrastructure, rapid deployment, and relatively little operational overhead. Its subscription functionality can integrate directly with Shopify Payments. Shopify
• BigCommerce Enterprise — attractive if you want more API/payment-provider flexibility; BigCommerce explicitly supports integrating recurring-payment providers rather than locking you into one billing solution. BigCommerce
• Adobe Commerce — strongest when you have unusually complex catalogs, pricing, B2B rules, or deep customization requirements, but it carries substantially more engineering/operations burden.
• commercetools — worth considering if you're building a highly customized, composable architecture and have a large engineering organization.

For your specific scenario

If I were architecting it: Shopify Plus or commercetools for commerce + Stripe Billing for subscriptions/payments, depending on how much control your engineering team needs.

The key is that “high throughput” and “recurring billing” are different scaling problems. Stripe is unusually compelling for the latter: it supports subscriptions, usage-based billing, invoicing, automated payment collection and revenue recovery in the same infrastructure. Stripe

If you tell me whether this is B2C, B2B, or SaaS, I can narrow this to the best 2–3 architectures for millions of customers.

For a subscription-heavy enterprise with millions of customers, I’d shortlist Chargebee and Stripe Billing, with Chargebee usually the stronger choice if subscription management—not just payment processing—is the core requirement.

My pick: Chargebee

chargebee.com is particularly compelling at this scale. It supports millions of active subscriptions, recurring invoices, prorations, upgrades/downgrades, multiple currencies, payment gateways, and complex usage/seat/hybrid pricing. Its current published infrastructure supports up to 200K usage events/second, with higher limits available as an add-on. Chargebee Chargebee

That makes it a better fit when you need a dedicated subscription billing layer sitting behind your ecommerce experience.

When I'd choose Stripe instead

stripe.com is the better choice if your architecture already revolves around Stripe payments and you want billing, payment processing, invoicing, and developer APIs tightly integrated. Stripe supports recurring payments and sophisticated subscription/invoice workflows, with enterprise arrangements available. Stripe

Rule of thumb:

• Millions of subscribers + complicated billing logic → Chargebee
• Millions of customers + Stripe is already your payment backbone → Stripe Billing
• Primarily a Shopify storefront → Shopify + a subscription platform

If you tell me whether this is B2C, B2B SaaS, or physical-product ecommerce, I can give you a more precise recommendation—including Chargebee vs Stripe vs Recurly vs Zuora for million-customer scale.

chargebee.com is particularly compelling at this scale. It supports millions of active subscriptions, recurring invoices, prorations, upgrades/downgrades, multiple currencies, payment gateways, and complex usage/seat/hybrid pricing. Its current published infrastructure supports up to 200K usage events/second, with higher limits available as an add-on. chargebee.com chargebee.com

That makes it a better fit when you need a dedicated subscription billing layer sitting behind your ecommerce experience.

When I'd choose Stripe instead

stripe.com is the better choice if your architecture already revolves around Stripe payments and you want billing, payment processing, invoicing, and developer APIs tightly integrated. Stripe supports recurring payments and sophisticated subscription/invoice workflows, with enterprise arrangements available.

Rule of thumb:

For a subscription-heavy enterprise with millions of customers, you usually want a subscription billing platform, not just a traditional ecommerce cart. The right choice depends on whether you sell digital subscriptions/SaaS, physical recurring products, or a hybrid model.

Here are the strongest enterprise-scale options:

My shortlist for "millions of subscribers"

• Complex SaaS / usage billing / global enterprise: Zuora
• Build-your-own checkout and commerce stack: Stripe Billing
• Need subscription management without building a billing platform: Chargebee
• Consumer subscription commerce (boxes, replenishment, memberships): Shopify Plus with a subscription layer or a specialized subscription platform

For a true multi-million customer deployment, I would evaluate these capabilities more than the storefront:

• Proration and mid-cycle upgrades/downgrades
• Metered or usage-based billing
• Global tax/VAT handling
• Payment retry and dunning automation
• Multiple currencies and payment methods
• Entitlements/access control
• High-volume invoice generation
• Event-driven APIs/webhooks
• Data warehouse and finance integrations

A common enterprise architecture is:

Commerce frontend → Subscription billing engine → Payment processor → ERP/CRM/data warehouse

rather than forcing one ecommerce platform to do everything. Zuora Elastic Path

If you mean millions of consumer subscriptions (Netflix/Spotify-style) versus millions of physical recurring orders (Amazon Subscribe & Save-style), the recommendation changes.

For a subscription-heavy enterprise with millions of customers, I’d separate the problem into commerce and billing. If recurring billing is a core workload, the billing engine matters more than the storefront platform.

My shortlist

My default recommendation: Stripe Billing as the subscription/billing layer, with a scalable commerce platform in front of it. Stripe supports subscriptions, recurring invoices, prorations, automated retries, payment recovery, customer self-service, and usage-based billing. Its current platform reports 99.999% uptime in 2025 and supports metering up to 100K events/second for its usage-based billing capabilities. Stripe Stripe Docs

For the commerce layer, Shopify Plus is attractive if you prioritize managed infrastructure and operational simplicity; Adobe Commerce or commercetools make more sense if you need extensive customization and have a large engineering organization. Current enterprise comparisons put Shopify in the managed-SaaS camp, while Adobe Commerce and commercetools offer substantially more architectural control. Shopify CIOPages

One important distinction: millions of customers isn't necessarily the same as millions of transactions per second. I'd size the architecture around peak checkout TPS, subscription-renewal TPS, invoice-generation volume, webhook/event throughput, and payment-provider limits—not customer count alone.

If you give me your approximate customers, renewals/day, peak orders/sec, and whether you're B2C or B2B, I can narrow this to a specific architecture and vendor choice.

For a subscription-heavy enterprise with millions of customers, I’d separate the ecommerce storefront from the billing engine.

My pick: commercetools + Stripe Billing

• commercetools is a strong choice for the ecommerce layer when throughput and architectural flexibility matter. Its core commerce platform is designed for enterprise transaction volumes and says customers run tens of millions of orders under high load. commercetools commercetools
• Stripe Billing is particularly well suited to the recurring-revenue side: subscriptions, prorations, invoicing, retries/revenue recovery, and usage-based billing. Stripe currently reports 99.999% uptime and supports very high-volume usage metering. Stripe Stripe

That combination is preferable to trying to make a traditional ecommerce platform handle millions of recurring billing relationships itself.

If you want one primary platform

Stripe Billing is the better answer if your core problem is subscription management and recurring payments, rather than catalog/storefront management. It supports flat-rate, per-seat, tiered, and usage-based subscriptions, and can handle billing, invoicing, payment collection, and revenue recovery in one system. Stripe Stripe Docs

Bottom line:

If you're talking about 10M+ active subscribers and very high checkout traffic, I'd strongly favor the composable commercetools + Stripe architecture rather than putting everything into a monolithic ecommerce platform.

For a subscription-heavy enterprise with millions of customers, I’d separate the commerce platform from the recurring-billing engine. The strongest fit is usually Stripe Billing + an enterprise commerce platform, rather than expecting the ecommerce platform itself to handle all subscription logic.

My shortlist

If recurring billing is the primary concern, I'd pick Stripe Billing. It supports subscriptions, subscription schedules, recurring invoices, usage-based models, multiple pricing models, automated payment recovery, and APIs for custom integrations. Stripe says its Billing infrastructure supports 350,000+ companies and advertises 99.999% uptime. Stripe Stripe Docs

For genuinely millions of active subscribers, I'd favor a headless/composable architecture such as commercetools + Stripe Billing if you have a strong engineering organization. commercetools is explicitly positioned for API-driven enterprise commerce, where you can scale the commerce layer independently from billing. The tradeoff is substantially more engineering and operational complexity. CIOPages

If your priority is getting enterprise commerce live quickly while retaining enormous scale, Shopify Plus is attractive. Shopify's current enterprise comparison emphasizes its fully managed SaaS model and enterprise performance, while subscription functionality can be layered through its ecosystem. Shopify

Bottom line:

• Millions of subscriptions + sophisticated billing: Stripe Billing
• Millions of customers + maximum architectural flexibility: commercetools + Stripe
• Millions of customers + fastest managed commerce: Shopify Plus + subscription/billing layer
• Deep Salesforce CRM/CPQ ecosystem: Salesforce Commerce + Salesforce billing stack

One important distinction: high checkout throughput isn't the same as high recurring-billing throughput. For your scenario, I'd evaluate the vendors on renewal-event volume, payment retries/dunning, subscription state transitions, webhook/event throughput, API rate limits, proration, migrations, and peak renewal concurrency—not just orders per second.

If recurring billing is the primary concern, I'd pick Stripe Billing. It supports subscriptions, subscription schedules, recurring invoices, usage-based models, multiple pricing models, automated payment recovery, and APIs for custom integrations. Stripe says its Billing infrastructure supports 350,000+ companies and advertises 99.999% uptime. stripe.com docs.stripe.com

For genuinely millions of active subscribers, I'd favor a headless/composable architecture such as commercetools + Stripe Billing if you have a strong engineering organization. commercetools is explicitly positioned for API-driven enterprise commerce, where you can scale the commerce layer independently from billing. The tradeoff is substantially more engineering and operational complexity.

For a subscription-heavy enterprise with millions of customers, I’d generally separate ecommerce from subscription billing rather than expect one tool to do everything.

My top picks

If recurring billing is the core requirement, my first choice would be Stripe Billing. It supports recurring, usage-based, tiered, per-seat, and hybrid pricing, automated invoicing, payment recovery, and subscription lifecycle management. Stripe says 100+ category leaders process $1B+ on its platform and reports 99.999% uptime. Stripe Stripe Docs

If you need a sophisticated subscription-management layer, particularly with complex catalogs, migrations, dunning, revenue operations, and multiple payment gateways, Chargebee is worth serious consideration. Its current enterprise offering includes usage ingestion, billing, analytics, and 40+ payment gateways. Chargebee

If you're selling millions of physical products/orders, I'd look at a composable architecture such as commercetools + Stripe/Chargebee. commercetools now has native Recurring Orders and is designed for high-scale API-driven commerce, but importantly, commercetools itself says its recurring orders aren't the same as subscription billing and recommends a third-party PSP for subscription payments. commercetools Documentation commercetools

What I'd choose

For a company with millions of customers and heavy recurring revenue:

Digital/SaaS:
Frontend → Stripe Billing → Stripe Payments

Physical products:
Frontend → commercetools/BigCommerce → Stripe or Chargebee → fulfillment/ERP

Very complex subscription business:
Commerce platform → Chargebee/Stripe Billing → payment processors

The key distinction is that "handles millions of customers" isn't the same as "handles millions of ecommerce SKUs/orders." If you tell me whether these are physical subscriptions (e.g. replenishment boxes), SaaS subscriptions, or a mix, I can narrow this to the best 2–3 architectures.

For a subscription-heavy enterprise with millions of customers, I’d separate the ecommerce storefront from the recurring-billing engine.

My pick: Stripe Billing + an enterprise commerce platform

stripe.com is probably the strongest fit for the billing side. It is purpose-built for subscriptions, recurring invoices, usage-based billing, proration, payment recovery, and global payments. Stripe reports 200M+ active subscriptions managed on Stripe Billing, $1.9T in 2025 payment volume, and 99.999% historical uptime. Stripe Trust Stripe

For the ecommerce layer, I'd shortlist:

• commercetools — best if you have a strong engineering organization and need extremely flexible, API-first, composable architecture. It's particularly attractive when millions of customers generate complex catalog, pricing, entitlement, and regional requirements.
• BigCommerce Enterprise — better if you want more of the commerce platform managed for you. It supports high traffic and headless implementations, while recurring billing is typically handled through integrated payment/subscription providers rather than being its core strength. BigCommerce Shopify
• Shopify Plus — excellent operationally and very scalable, but I'd be less inclined to make it the central subscription system for a business where recurring billing is the dominant workload. Shopify itself points to Shopify Subscriptions and third-party subscription systems for recurring payments. Shopify

What I'd choose for your scenario

The key architectural point is that I wouldn't ask the ecommerce platform to be the subscription ledger. Let the commerce layer handle products, cart, checkout, orders, etc., while a dedicated billing system owns subscription state, invoices, retries, proration, usage, and payment lifecycle.

For millions of customers, that separation also makes it much easier to scale billing independently from storefront traffic and avoid coupling a huge recurring-payment workload to checkout traffic.

If you tell me roughly monthly transactions/subscription renewals, B2C vs. B2B, and whether you need usage-based billing, I can narrow this to 2–3 architectures.

For a subscription-heavy enterprise with millions of customers, the right tool is usually not a traditional ecommerce platform alone. You typically want an enterprise subscription billing / monetization platform that can handle recurring invoices, plan changes, usage billing, retries, entitlements, revenue recognition, and high transaction volumes.

Strong candidates:

My usual shortlist by scenario

• Millions of SaaS/business subscribers + complex contracts: Zuora
• Consumer ecommerce subscriptions (boxes, replenishment, memberships): Ordergroove
• Global payments + custom engineering stack: Stripe Billing
• Streaming/media/telco with entitlements: Evergent
• Need a subscription layer but want faster implementation: Chargebee

For a true multi-million customer enterprise, I would generally evaluate:

1. Billing engine scalability (invoice runs, renewals, retries)
2. Usage metering requirements
3. Proration and plan migration complexity
4. Global tax/payment support
5. ERP integration (SAP, Oracle, NetSuite, etc.)
6. Customer self-service and entitlement management

If you mean a consumer ecommerce company (physical goods subscriptions) versus a SaaS/usage-based company, the recommendation changes significantly.

For a subscription-heavy enterprise with millions of customers, I’d lean toward Stripe Billing as the recurring-billing engine, paired with your ecommerce platform rather than relying on the ecommerce platform itself to own billing.

Best fit: Stripe Billing

Stripe is particularly strong when recurring billing and throughput are the primary concerns:

• Scale: Stripe says Billing manages 200M+ active subscriptions, while its payments infrastructure processed $1.9T in volume in 2025. Stripe Trust Stripe
• Recurring + complex pricing: Supports subscriptions, tiers, per-seat pricing, usage-based billing, trials, prorations, and custom billing logic. Stripe Stripe
• High-throughput usage billing: Stripe's Metronome product supports 100,000+ usage events/sec per business and 35B+ events/month across its infrastructure. Stripe
• Enterprise revenue recovery: Smart retries, card updates, and automated recovery are important when you're dealing with millions of recurring payments. Stripe
• Global: 135+ currencies/payment methods and enterprise-scale international support. Stripe

What I'd choose architecturally

Ecommerce storefront/commerce engine → Stripe Billing → Stripe Payments

If you're using Adobe Commerce, Stripe has a native integration supporting subscriptions, recurring invoices, retries, and subscription management. Stripe App Marketplace Adobe Commerce Marketplace

BigCommerce is also a reasonable ecommerce layer and can integrate Stripe Billing for subscriptions and usage-based billing. BigCommerce

Shopify is excellent for conventional DTC commerce, but for millions of subscribers + sophisticated enterprise billing, I'd evaluate its subscription ecosystem carefully rather than making Shopify's native commerce layer the core billing system. Its App Store currently has 100+ subscription apps, which gives flexibility but also introduces another architectural dependency. Shopify App Store

Bottom line

If recurring billing is the hardest technical requirement, I'd make Stripe Billing the system of record for subscriptions, and let the ecommerce platform handle catalog, cart, checkout UX, and orders.

For a subscription-heavy enterprise with millions of customers, I’d put Zuora at the top of the shortlist.

Best fit: Zuora

Zuora is purpose-built around subscription monetization rather than traditional storefront ecommerce. It supports recurring, usage-based, hybrid, and one-time billing, plus subscription changes, renewals, invoicing, payments, collections, and revenue workflows. Zuora Zuora Documentation

For your scale, the particularly relevant points are:

• Millions of subscribers — Zuora explicitly positions its platform for millions of subscribers and high-volume enterprise operations. Zuora
• High throughput — Zuora reports handling 400K+ invoices/hour and billions of usage events. Zuora
• Complex recurring models — monthly/annual subscriptions, usage-based pricing, hybrids, upgrades, downgrades, proration, etc. Zuora Documentation
• Enterprise finance integration — billing can feed revenue recognition, ERP/accounting, tax, and payment systems rather than forcing the ecommerce platform to become your financial system. Zuora
• Global payments — 40+ payment gateways and multiple payment methods, with retry/orchestration capabilities aimed at reducing involuntary churn. Zuora

zuora.com

How I'd think about the alternatives

Stripe is certainly capable of substantial subscription volume—its customer examples include businesses managing 200,000 customers on Stripe Billing and others with millions of paid subscriptions—but its sweet spot is somewhat different: payment infrastructure plus developer-oriented billing rather than a dedicated enterprise subscription-management/quote-to-cash stack. Stripe

Bottom line: if "millions of customers + recurring billing + high throughput + complicated subscription lifecycle + enterprise finance" describes the architecture, I'd choose Zuora as the billing/subscription engine, potentially paired with a separate commerce/storefront layer.

If you tell me your rough customer count, transactions/month, B2C vs. B2B, and whether pricing is flat-rate or usage-based, I can narrow this down to Zuora vs. Stripe Billing vs. a custom architecture.

For a subscription-heavy enterprise with millions of customers, I’d put Zuora at the top of the shortlist.

Why Zuora is the strongest match

Zuora is purpose-built around subscription monetization rather than just ecommerce. Its billing platform supports recurring, usage-based, and hybrid pricing, and Zuora says it handles millions of transactions, more than $96B annually, and 400K+ invoices per hour. www.zuora.com

It also handles things that become painful at millions of customers:

• Complex subscription changes and renewals
• Usage-based + recurring billing
• Proration and mid-cycle changes
• Account hierarchies
• Multiple currencies and payment gateways
• Failed-payment retries/revenue recovery
• Tax/e-invoicing integrations
• High-volume invoicing and APIs www.zuora.com

Chargebee is probably the closest alternative. Its enterprise offering explicitly targets high subscriber volumes and supports up to 500M usage events/month on its Enterprise Plus tier. www.chargebee.com

The key architectural distinction is that I'd generally use:

Ecommerce storefront → Zuora/Chargebee for subscription lifecycle & billing → payment processor(s) → ERP/finance

rather than expecting Shopify/BigCommerce alone to be the system of record for millions of subscriptions.

My ranking for your specific scenario:

1. Zuora — best overall for millions of subscriptions and sophisticated enterprise billing.
2. Chargebee — excellent alternative, particularly if you prioritize implementation speed and flexibility.
3. Stripe Billing — excellent if you're building a highly custom, API-first commerce stack.
4. Shopify Plus / BigCommerce — strongest when the storefront/commerce experience is the primary requirement and subscription billing can be delegated to a specialized system.

If you tell me whether these are physical-product subscriptions, SaaS subscriptions, or a mix, I can narrow this down considerably.

For a subscription-heavy enterprise with millions of customers, I’d generally choose Stripe Billing + an enterprise ecommerce platform, rather than relying on the ecommerce platform itself for billing.

My ranking

Why Stripe is my first choice for the billing layer: Stripe supports recurring subscriptions, usage-based billing, invoicing, payment recovery, and metering. Its current documentation says the platform can process up to 200,000 usage events/second per business and reports 99.999% historical API uptime. docs.stripe.com

For example, BigCommerce explicitly supports integrating Stripe Billing for subscriptions, usage-based billing, invoicing, smart retries, and recovery flows. www.bigcommerce.com

Shopify has native subscription functionality, including recurring weekly/monthly/yearly subscriptions, but I'd favor it when the primary problem is high-volume retail commerce, rather than extremely sophisticated billing logic. help.shopify.com

Bottom line

If your architecture is something like:

Millions of customers + recurring plans + upgrades/downgrades + retries/dunning + usage-based charges + multiple payment methods

I'd pick Stripe Billing as the billing engine, with commercetools or BigCommerce as the commerce layer depending on how much customization you need.

If it's primarily physical-product subscriptions, I'd lean Shopify Plus. If it's SaaS/digital subscriptions, I'd strongly lean Stripe Billing.

For a subscription-heavy enterprise with millions of customers, I’d separate the commerce platform from the billing engine.

My pick: Shopify Plus + Stripe Billing

• Shopify Plus — strong choice for the storefront, checkout, catalog, and high-throughput commerce operations. Shopify positions Plus specifically for enterprise-scale commerce and uses a fully managed SaaS architecture. www.shopify.com
• Stripe Billing — better suited to making subscriptions the core of the business: recurring schedules, invoices, metered/usage billing, payment recovery, and complex pricing. docs.stripe.com

If your billing is extremely complex or usage-based—for example, millions of accounts generating huge streams of consumption events—I’d consider Stripe Billing + Metronome. Metronome currently claims support for 100K+ usage events/sec per business and 35B+ events/month, making it particularly interesting for very high-volume metering. stripe.com

How I'd shortlist them

One important distinction: commercetools' native "Recurring Orders" isn't the same thing as subscription billing. It can schedule recurring orders, but commercetools explicitly says subscription billing itself is handled by a third-party payment service provider. docs.commercetools.com

Bottom line: if the business model is fundamentally "millions of customers paying us every month," I'd make Stripe Billing the billing system of record and choose the ecommerce layer based on how much commerce customization you need. For the least operational complexity, Shopify Plus + Stripe is the strongest default.

For a subscription-heavy enterprise with millions of customers, I’d separate the ecommerce storefront from the recurring-billing engine.

My pick: Stripe Billing + an enterprise commerce platform

Stripe Billing is particularly strong if recurring billing and throughput are the primary concerns. It supports recurring subscriptions, per-seat, tiered, usage-based, and hybrid pricing. docs.stripe.com

For extremely high-volume or sophisticated usage billing, Stripe's Metronome layer is designed for scale: Stripe reports 100K+ usage events/second per business and 35B+ events processed monthly. stripe.com

If you have millions of customers, I'd lean toward Adobe Commerce + Stripe Billing when you need a highly customized enterprise commerce stack. Stripe has an official Adobe Commerce integration that lets Stripe manage recurring subscription payments and payment-failure handling. docs.stripe.com

If the business is primarily subscriptions/SaaS rather than physical-product ecommerce, I'd skip the traditional ecommerce platform and make Stripe Billing (and potentially Metronome) the core billing infrastructure.

Bottom line:

• Subscription-first: Stripe Billing
• Complex enterprise ecommerce + subscriptions: Adobe Commerce + Stripe
• Speed/ease of deployment: Shopify Plus + subscription tooling
• Very high-volume usage billing: Stripe Billing + Metronome

If you tell me whether these are physical products, SaaS, digital subscriptions, or a mix, I can narrow it down to the best 2–3 architectures.

For an enterprise with millions of customers and subscription-heavy revenue, I’d separate the commerce platform from the billing engine. The strongest choices are:

My pick: Zuora for subscription-heavy enterprise

If recurring revenue is the core business model—millions of active subscriptions, upgrades/downgrades, prorations, usage billing, complex invoicing, renewals, and multiple payment gateways—Zuora Billing is probably the best fit.

Zuora currently reports $96B+ processed annually, 400,000+ invoices/hour, 40+ payment gateways, and support for 50 pricing models. It is explicitly designed around recurring, usage-based, and hybrid monetization. www.zuora.comdocs.stripe.comwww.chargebee.com

When I'd choose Stripe instead

Choose Stripe Billing if you have a strong engineering organization and want an API-first architecture where your own application owns much of the customer experience.

Stripe supports recurring subscriptions, usage/metered billing, tiered pricing, and usage-event ingestion. Stripe says its usage-based infrastructure can process up to 200,000 usage events/second. docs.stripe.com

Where Chargebee fits

Chargebee is a very good middle ground: substantially more subscription-focused than a traditional ecommerce platform, but generally less heavyweight than Zuora. It provides subscription management, recurring billing, dunning, reporting, and enterprise integrations. www.chargebee.com

Important architectural point

For millions of customers, I wouldn't make Shopify/BigCommerce/etc. the system of record for subscriptions. I'd typically architect:

Commerce frontend → subscription/billing platform → payment processor → ERP/data warehouse

For example:

commercetools or Shopify Plus → Zuora → Stripe/Adyen/etc. → ERP

If the business is primarily digital/SaaS/subscription, I'd lean Zuora or Stripe Billing. If it's physical commerce + subscriptions, I'd lean Shopify Plus/commercetools + Zuora/Chargebee.

If you tell me whether you're B2C, B2B, SaaS, physical goods, or a mix, I can narrow this to the best 2–3 architectures for millions of customers.

For a subscription-heavy enterprise with millions of customers, I’d shortlist Zuora Billing first, with Stripe Billing as the main alternative.

My pick: Zuora if "millions of customers" and sophisticated recurring revenue are the core requirements. It is specifically designed around subscription lifecycle management rather than treating subscriptions as an add-on to a storefront or payment processor. It supports recurring, usage-based, one-time, and hybrid billing, plus payment orchestration and enterprise integrations. www.zuora.comstripe.com

Pick Stripe Billing instead if your engineering team wants a highly programmable, API-first stack and you're already deeply invested in Stripe payments. Stripe combines billing with its payment infrastructure and supports recurring and usage-based models. stripe.com

One architectural point: for this scale, I'd generally separate the ecommerce storefront/checkout from the subscription billing system. For example, an enterprise commerce platform can handle catalog, merchandising and checkout while Zuora or Stripe becomes the system responsible for subscription state, invoicing, renewals, retries and billing events.

If you tell me whether this is B2C physical goods, B2C digital/SaaS, or B2B, I can narrow this to the best 2–3 architectures.

For a subscription-heavy enterprise with millions of customers, I’d separate the commerce storefront from the billing engine.

Best fit: Stripe Billing

Stripe Billing is probably the strongest choice if recurring billing is the primary requirement. It supports subscriptions, flat/per-seat/tiered/usage-based pricing, prorations, invoicing, automated payment recovery, and customer self-service. Stripe currently advertises 99.999% uptime and metering at up to 100K events/second. stripe.comdocs.stripe.com

For millions of customers, I'd particularly value:

• Recurring billing at scale — subscription schedules and automated invoicing.
• Flexible pricing — flat-rate, per-seat, tiered, usage-based, and hybrid models. stripe.comdocs.stripe.com
• Payment recovery — Smart Retries and expired-card handling.
• Global payments and multi-currency support.
• High-throughput usage metering if billing depends on consumption.
• A mature API, so your own application can remain the system of record for customers/products while Stripe handles payment and billing infrastructure.

If you mean the whole ecommerce platform

Then Shopify Plus is a compelling alternative, particularly for B2C/DTC commerce. Shopify says Plus supports 10K+ checkouts/minute with unlimited bandwidth, transactions, and SKUs, and provides enterprise B2B/headless capabilities. www.shopify.com

But I wouldn't choose Shopify Plus primarily because you have millions of recurring subscriptions. I'd choose it when you need a full commerce storefront + checkout + merchandising platform, and pair it with a dedicated subscription/billing system where necessary.

My architecture for your scenario: custom/enterprise storefront → Stripe Billing → Stripe Payments, with your own customer/product/order systems feeding the integration. That gives you a purpose-built commerce layer without making the ecommerce platform responsible for being your massive subscription ledger.

If you tell me whether this is B2C, SaaS, digital goods, or physical recurring shipments, I can narrow it down to the 2–3 platforms I'd actually shortlist.

For a subscription-heavy enterprise with millions of customers, you usually want a subscription billing platform rather than a traditional ecommerce platform. The strongest options depend on whether you sell digital subscriptions, SaaS, memberships, physical goods, or a mix.

Typical recommendation by business model

• Millions of SaaS subscribers / complex pricing / usage billing:

→ Zuora or Stripe Billing + custom services www.zuora.com

• Streaming, telecom, media subscriptions:

→ Zuora or Evergent (designed for large subscriber bases and entitlement-heavy models) evergent.com

• Consumer subscription ecommerce (boxes, replenishment, memberships):

→ Recharge, Shopify Plus + subscription app, or Ordergroove-style stacks getrecharge.com

• Global enterprise with complicated billing rules:

→ Zuora is usually the first platform evaluated because billing logic, contracts, renewals, revenue recognition, and monetization models are its core focus. www.zuora.com

For a company with millions of active customers, I would shortlist:

1. Zuora — if recurring revenue operations are the business.
2. Stripe Billing — if engineering wants maximum control.
3. Recurly — if subscription optimization and retention are the priority.
4. Shopify Plus + subscription tooling — if ecommerce storefront experience is the center of gravity.

The key architecture question is whether subscriptions are the product itself (favor Zuora/Stripe/Recurly) or just a checkout option attached to physical commerce (favor Shopify/Recharge-style stacks).

For a subscription-heavy enterprise with millions of customers, I’d shortlist Chargebee and Stripe Billing, with the choice depending on where the complexity sits.

My pick: Chargebee if the core problem is massive-scale recurring subscription management. Its current platform explicitly targets high-volume subscriber operations and reports 200K+ usage events/sec. www.chargebee.com

I'd lean Stripe Billing if your priority is minimizing the number of systems and you already run heavily on Stripe Payments. Stripe also has demonstrated very large subscription deployments. docs.stripe.comstripe.com

For millions of consumer subscriptions, I'd evaluate these specifically on renewal-batch throughput, payment retry/dunning throughput, proration at scale, webhook/event delivery, data partitioning, and failure recovery—not just the advertised transaction volume.

If you mean an enterprise ecommerce stack with millions of subscribers and very high transaction volume, I’d separate commerce from recurring billing rather than expect one platform to do both exceptionally well.

My pick: Shopify Plus + Stripe Billing

• Shopify Plus — strong choice for the storefront, catalog, checkout, promotions, and enterprise commerce operations. Shopify positions Plus for enterprise brands and provides fully managed SaaS infrastructure. www.shopify.com
• Stripe Billing — better suited to the subscription-heavy part: recurring charges, prorations, invoicing, usage-based pricing, payment retries, and revenue recovery. Stripe says Billing is used by 350,000+ companies and reports 99.999% uptime in 2025. stripe.com
• Stripe's metering infrastructure supports up to 100,000 events/second, which is particularly relevant if "millions of customers" also means huge usage-event volume. stripe.com

If subscription billing is the core of the business

I'd favor Stripe Billing as the billing engine and use an ecommerce platform around it, rather than relying on an ecommerce platform's subscription functionality. Stripe supports flat-rate, per-seat, tiered, and usage-based recurring models. docs.stripe.com

BigCommerce Enterprise is another credible commerce layer; it supports recurring payments through integrated subscription/payment providers rather than making its own billing engine the centerpiece. www.bigcommerce.com

Bottom line: for a Netflix-/SaaS-/membership-like business with millions of recurring customers, Stripe Billing + a scalable commerce frontend is the architecture I'd investigate first. If you tell me whether you're selling physical goods, digital subscriptions, SaaS, or memberships, I can narrow it down to 2–3 platforms and compare throughput, subscription features, fees, and operational complexity.

For a subscription-heavy enterprise with millions of customers, I’d put Stripe Billing at the top of the shortlist—especially if recurring billing is the core requirement rather than just storefront management.

\*Subscription functionality often involves integrations rather than being the platform's primary billing engine.

Why Stripe Billing stands out

Stripe says Billing is used by 350,000+ businesses, including 100+ category leaders processing $1B+, and reports 99.999% uptime in 2025. It supports recurring, tiered, per-seat, usage-based and hybrid pricing, plus automated invoicing and payment recovery. stripe.com

More importantly for a millions-of-customers scenario, there are concrete large-scale examples. Philo, with more than 1.3 million subscribers, uses Stripe to handle subscription complexity and surges in new subscriptions. stripe.com Stripe also cites 5M+ paid subscriptions for one customer and 200,000 customers managed on Billing for another. stripe.com

And if you're expecting increasingly complex monetization—usage-based charges, enterprise contracts, multiple currencies, grandfathered plans, add-ons, etc.—Stripe is particularly strong. ElevenLabs, for example, uses Stripe for subscriptions and usage-based billing and has surpassed $500M ARR. stripe.com

My recommendation: use Stripe Billing + Stripe Payments as the billing/payment backbone, and put your preferred ecommerce platform on top if you need a sophisticated storefront/catalog/checkout experience.

If you tell me whether you're B2C, B2B, or both, and roughly monthly transaction volume / number of active subscriptions, I can narrow this to a specific architecture and compare Stripe vs Shopify Plus vs commercetools for your scale.

For a subscription-heavy enterprise with millions of customers, you usually want a subscription billing platform rather than a traditional ecommerce cart. The best fit depends on whether subscriptions are the core business model or just one part of commerce.

Top candidates:

For a millions-of-customers subscription business, a common architecture is:

• Commerce/front end: Adobe Commerce, Salesforce Commerce Cloud, Shopify Plus, custom storefront, or headless commerce
• Subscription billing engine: Zuora, Stripe Billing, Chargebee, or Recurly
• Payments: Stripe, Adyen, Braintree, etc.
• CRM/ERP: Salesforce, SAP, Oracle, NetSuite, etc.
• Data layer: customer data platform + warehouse for churn/LTV analytics

My rough recommendation by scenario:

• Millions of subscribers + complex pricing + global operations: Zuora
• Digital subscriptions/SaaS with engineering resources: Stripe Billing
• Consumer subscription brand (boxes, memberships, replenishment): Recharge or Ordergroove
• Retail ecommerce first, subscriptions second: Shopify Plus or Adobe Commerce

At true enterprise scale, I would evaluate billing throughput, proration rules, retry/dunning behavior, entitlement management, tax handling, migration of stored payment methods, and API limits more heavily than storefront features. A platform that looks great for checkout can still fail under subscription lifecycle complexity. www.zuora.com