When to Switch eCommerce Platforms: 7 Measurable Warning Signs

Most advice on switching platforms says some version of your store is growing, it might be time. That is not a signal, it is a feeling.

A real trigger has a number attached: your platform cost crosses a specific percentage of revenue, your page load crosses a specific second count, your catalog crosses a specific product threshold your platform was never built to handle.

This covers seven of those numbers directly, each one measurable against your own store’s actual data, not a general sense that something feels off.

A note on the numbers themselves: some, like Google’s own Core Web Vitals target, are published standards.

Others, like the specific revenue percentage and dollar thresholds below, are practical benchmarks worth testing your own numbers against, not published industry standards from any platform or analyst, treat them as a reasonable starting point for judgment, not a hard official rule.

Key Takeaways

• Platform cost above roughly 5% of monthly revenue is a reasonable benchmark worth testing, not a published standard, add your subscription, transaction fees, and required apps together and divide by revenue to see where your own store lands.
• Average page load above 3 seconds is a reasonable practical benchmark, not itself a Google-published figure, though it sits close to Google’s own Core Web Vitals threshold of 2.5 seconds for the largest content element on a well-performing page.
• Crossing your platform’s real catalog ceiling, roughly 10,000 products for WooCommerce without serious infrastructure investment, or Shopify’s 100-variant practical cap per product, are hard technical limits, not soft inconveniences.
• Paying for 3 or more apps that replicate one feature a bigger platform includes natively is a real, addable cost most store owners never total up in one place.
• If your transaction fee alone would cover a migration within 12 months, the math already favors switching, the only question left is timing and execution risk.

The Quick Verdict

Run your own numbers against these seven signs before reading further. One crossed threshold is worth watching, not acting on immediately. Two or more crossed at once is where a real evaluation becomes worth the time.

Sign	What to Check	Real Trigger
1. Platform cost	Subscription + fees + apps, divided by revenue	Above roughly 5%
2. Page load	Real, measured average on live pages	Above 3 seconds
3. Catalog ceiling	Your platform’s real product or variant limit	Ceiling reached, not just approaching
4. App stacking	Cost of 3+ apps replicating one feature	Around $50+/month per feature category
5. Transaction fee	Annual fee vs. realistic migration cost	Fee matches or exceeds migration cost
6. Feature gap	A genuine hard wall, not a settings issue	No app fully replicates the missing feature
7. Support cost	Hourly revenue × degraded-performance hours	A real, recurring dollar figure

Sign 1: Platform Cost Exceeds 5% of Monthly Revenue

The formula:

• Monthly subscription
• Plus transaction fees
• Plus required app subscriptions
• Divided by monthly revenue

The threshold:

• Once this crosses roughly 5 percent, a commonly used benchmark rather than a figure published by any platform, the cost is worth comparing honestly against a cheaper structure elsewhere
• Treat this as a starting point for your own judgment, not a hard rule

A real example:

• A store doing $20,000 a month on Shopify Basic
• Paying the plan fee, standard processing, and three add-on apps for features a fee-free platform includes natively
• Can easily land at 6 to 8 percent once everything is totaled
• Run this calculation on your own numbers before assuming your platform cost is reasonable

Sign 2: Average Page Load Exceeds 3 Seconds

The threshold:

• Google’s own Core Web Vitals guidance sets 2.5 seconds as the published target for Largest Contentful Paint on a good-performing page, this specific figure is a real, cited standard
• A practical benchmark worth watching is your real, measured average crossing 3 seconds, past that point minor optimization commonly stops being enough on its own

Why this is platform-relevant, not just a settings problem:

• You have already compressed images, enabled caching, and reviewed your app or plugin stack
• Load times are still consistently over 3 seconds despite that
• At that point, the platform’s underlying architecture or your hosting’s ceiling within it is the actual constraint, not a fixable setting

How to check this properly:

• Use a real tool, Google PageSpeed Insights or a similar Core Web Vitals report
• Measure your actual live pages, not a generic homepage speed test alone

Sign 3: You Have Crossed Your Platform’s Real Catalog Ceiling

This threshold is platform-specific, know your own platform’s real number before assuming it applies to you.

• WooCommerce: performs well under roughly 5,000 products with standard hosting. Past 10,000 SKUs with complex attributes, real infrastructure investment becomes necessary. Past 50,000 products, WooCommerce hits genuine architectural limits even with strong hosting.
• Shopify: caps native product variants at 3 option types and roughly 100 variant combinations per product. A catalog needing more than this per product hits a real, hard technical wall, not a workaround-able inconvenience.
• BigCommerce and Adobe Commerce: built for larger catalogs natively, if you are hitting real limits on either of these specifically, the trigger is closer to Sign 6 below than a catalog-size issue.

Sign 4: You Are Paying for 3 or More Apps to Replicate One Native Feature

The calculation:

• List every app or plugin you currently pay for specifically to add a feature
• Group them by the underlying capability, abandoned cart recovery, customer segmentation, wholesale pricing
• Total the monthly cost per group

The threshold:

• There is no official figure for this, but once a single feature category costs somewhere around $50 or more a month across multiple apps stacked together, it is worth comparing that total honestly against what a platform offering it natively would cost instead
• The math frequently favors switching once you actually add the numbers, rather than treating each app subscription as a small, separate cost

Sign 5: Your Transaction Fee Alone Would Cover a Migration Within 12 Months

The calculation:

• Take your current platform’s transaction fee percentage
• Multiply it by your annual revenue
• Compare that single number against a realistic migration cost estimate for your catalog size

A real example:

• A store doing $500,000 a year
• Paying a 2 percent platform-side transaction fee on top of standard processing
• Pays $10,000 a year in that fee alone
• A migration for a catalog that size commonly runs in a comparable range or less

Once the ongoing fee matches or exceeds the one-time migration cost, the financial case for switching is already made, the remaining decision is about timing and execution risk, not whether it makes sense.

Sign 6: You Need a Feature Your Platform Actually Does Not Offer

Not every feature gap justifies switching, but some are real, hard walls rather than inconveniences.

• Multi-storefront or multi-currency support your platform does not provide natively, and no app fully replicates
• B2B functionality, customer groups, negotiated pricing, requisition lists, your platform requires stitching together through multiple third-party apps rather than offering natively
• A specific compliance or security requirement your platform’s architecture cannot meet, not just a setting you have not configured yet

Sign 7: Support Response Time Is Costing You Measurable Revenue

The formula:

• Your average hourly revenue
• Multiplied by hours of degraded performance or downtime per month
• Directly tied to support response delays, not your own team’s issue

The threshold:

• If this calculation produces a real, meaningful dollar figure, not a vague frustration, on a recurring monthly basis
• That is a measurable cost your current platform’s support structure is imposing on your business
• Worth weighing directly against a platform with a support tier that matches your actual revenue

Putting the Numbers Together

No single sign here should trigger an immediate migration on its own. Two or more of these crossing their thresholds at the same time is a much stronger signal than any one in isolation, since it usually means the platform is actually undersized for where the business actually is now, not just showing one isolated weak point.

Cross-checking your revenue and catalog size against the platform tiers most stores fall into is a useful sanity check alongside these seven signs, since a platform that fit at launch is not automatically the wrong one now, sometimes it is simply time to move up a tier rather than switch to a completely different platform.

If You Have…	The Real Signal
One sign crossed	Worth monitoring, not yet a strong trigger on its own
Two or more signs crossed	A real case for evaluating alternatives seriously
Cost and catalog-ceiling signs both crossed	The financial and technical case are aligned, this is usually the clearest trigger to act on

FAQ for When to Switch eCommerce Platforms