Shopify Plus stability during high traffic or a promotion cannot be summarised by one “orders per second” number. Reliability depends on platform boundaries, theme and app scripts, caching, third-party APIs, inventory and payment workflows, and an operating team with monitoring and degradation paths. Define what a customer must be able to complete, then test with representative devices and traffic instead of relying on a marketing statement.
Define critical paths
List home, collection, product, search, cart, checkout, payment, order notification, and support paths. Record acceptable errors, latency, stock behaviour, and payment recovery for each. Separate visits, carts, checkout, purchases, refunds, and support events from business outcomes; page speed is not the same as revenue.
Govern themes, apps, and third-party calls
Remove unnecessary apps, blocking scripts, heavy images, and fonts and document the purpose, owner, and removal condition of each third-party request. Add timeout, retry, and human hand-off for payments, tax, delivery, and CRM. Freeze risky changes before a promotion and keep a rollback version.
Test and monitor in layers
Use real devices, networks, key markets, and representative products rather than a developer laptop alone. Monitor errors, checkout failures, payment declines, stock anomalies, support questions, and refunds. During an incident, protect orders and customers first, then disable non-critical scripts or channels in stages. Do not publish unverified concurrency, speed, or availability guarantees.
FAQ
Does Shopify Plus guarantee stability under any traffic level?
No absolute guarantee is appropriate. Theme, apps, third-party services, products, and operations also affect reliability.
What should be checked before a traffic spike?
Critical paths, app scripts, payment, stock, caching, third-party timeouts, monitoring, and rollback.
Are page speed and order success the same?
No. Speed is one experience signal; payment, inventory, checkout, refunds, and support also matter.
Can many apps be installed shortly before a promotion?
Avoid it. Test high-risk changes in a low-risk environment and retain a rollback version.
Can a stability case publish orders per second?
Only with complete test environment, period, request type, architecture, and permission; otherwise publish method and boundaries.