Shopify Plus Alternatives: 7 Options and What Plus Really Costs

Two labels run through this whole page and the difference between them is the whole point. VERIFIED means read off the vendor's own page, or verified-by-absence at a vendor URL that LOADED (HTTP 200) and contains no price. A figure from ANY third-party aggregator (Vendr, PriceLevel, SelectHub, ITQlick, G2, Capterra, Software Advice, toolradar, any blog or competitor) is REPORTED, however good the data. ASSUMPTION means we chose the number ourselves, and every one of them is named and editable in the calculator. A fetch that failed never supports a VERIFIED label anywhere on this page; where a vendor page would not load, the row says so.

Read the table twice and the shape of the problem shows up on its own. Ten of the eighteen lines are VERIFIED, and every one of those ten is a Shopify line. Not one of the recurring costs that actually makes the difference between a $28,000 year and an $80,000 year is published by anybody, and the best public figures for them come from a company that sells a competing platform. That is not a scandal, it is just how the category works, and it is the reason a comparison built on platform fees alone will mislead you no matter which platform wins it.

The platform fee is the part you can see

Take the three year term at $2,300 a month. Over the commitment that is $82,800 of platform fee, and if you never added anything to it, Plus would be one of the better priced pieces of enterprise software a mid-market business buys. Nobody runs it that way. The realistic monthly picture for a brand doing between one and five million dollars of revenue, using the REPORTED bands from Swell rather than anything we invented, is a $2,300 platform fee, somewhere around $2,000 of apps and integrations, and an agency or a fractional developer somewhere between zero and several thousand dollars a month. Call it $5,800 a month at the conservative end of that, which is what the chart and calculator on this page use as their default. That is $69,600 a year of recurring spend, of which exactly $27,600 is the number on the rate card.

The gap between those two figures is the entire subject of this page. It is also why the negotiation most brands run at renewal produces so little. You can push on the platform fee, and Shopify may or may not move on it. You cannot push on the eleven other vendors at the same time, because they are not in the room and their renewal dates are all different.

Where the growth tax actually sits, and where it does not

Most enterprise software taxes headcount. Shopify Plus does not, and we are not going to manufacture a seat tax that is not there. shopify.com/pricing lists Plus with unlimited staff accounts, against up to 5 on Grow and up to 15 on Advanced. If your team doubles, the platform fee does not notice. That is a genuine advantage and if seats are your problem, Plus already solved it.

The tax in this category is levied on three other units, and all three are on Shopify's own page. Storefronts. Nine expansion stores are included, and beyond that the page says an extra $300 USD per month per store, or a revenue share across all stores. A brand that runs a US store, a Canadian store, a UK store, an EU store, a wholesale store, a clearance store and a handful of regional or partner storefronts finds the tenth one starts costing money, and the fifteenth costs $3,600 a year. Transactions. If you keep a processor relationship outside Shopify Payments, Shopify's page says you pay your processor fees plus 0.20% per transaction to Shopify for security and compliance costs. On $10,000,000 of processed volume that single line is $20,000 a year, paid to the platform for the privilege of using your own bank. Volume. The page reserves the right to price more complex, higher volume businesses on a variable platform fee, and it does not publish that rate.

We want to be precise about that last one, because it is the most important unpublished number on this page and it is exactly the kind of gap where a page like this would normally reach for a convenient figure. Third party sources report the variable rate variously at 0.20%, 0.25%, 0.35% and 0.40%, and they disagree with each other. Some also report a monthly ceiling. We are not going to pick the one that makes our own crossover chart look best. The honest statement is this: above a revenue threshold Shopify does not publish, the flat platform fee can be replaced by a percentage that Shopify also does not publish, and the third party estimates of that percentage are inconsistent. If your renewal quote arrives as a percentage rather than a dollar figure, you have crossed that line, and the model on this page understates your cost rather than overstating it.

The 2024 increase, and what it tells you about the next one

Shopify's own pricing pages carry no price history at all. We looked specifically, twice, on August 30, 2026, and there is no historical pricing, no change log and no announcement on either shopify.com/pricing or shopify.com/plus/pricing. So everything in this section is REPORTED and the outlets are named.

The consistent account across independent trade press, including inFlow Inventory, DynamicWeb, marketing4ecommerce and Liquify, is that the Shopify Plus base platform fee moved from $2,000 a month to $2,500 a month on the one year term during the first half of 2024, and that brands could hold the number at $2,300 a month by committing to a three year term. On the one year base that is an increase of 25%. Two of the sources we read describe the change as 33% or 34% instead. We think that discrepancy comes from comparing against a different starting basis rather than the same base to base move, and rather than print both numbers and let you sort it out, we use 25%, name the disagreement, and let you go and check.

What matters for a decision is not the historical percentage. It is the structure the increase revealed. The published number moved by a quarter in a single step, the cheaper version of the new number was available only in exchange for a three year commitment, and there was no contractual escalator anyone could have pointed to in advance because the pricing pages do not publish one. We deliberately do not model a future annual increase in the chart or the calculator on this page. There is no sourced escalation term for Shopify Plus, and inventing one would push the crossover earlier and flatter our own conclusion, which is precisely the move this page exists to argue against. The model below assumes Shopify's price never rises again. It still crosses over inside year two.

Cumulative spend, five years out, for one brand on one set of assumptions, every one of them stated. Shopify Plus at $2,300 a month on the three year term VERIFIED from shopify.com/plus/pricing. Apps and integrations at $2,000 a month, inside the $500 to $1,000 early to $3,000 to $5,000 enterprise band REPORTED by Swell. Agency time at $1,500 a month, which is deliberately below the bottom of the $3,000 to $10,000 retainer band REPORTED by the same source, because using the reported band would flatter our own conclusion and we would rather the argument survive the conservative version. Implementation at $20,000, the middle of the $10,000 to $30,000 band REPORTED for a brand moving up from Shopify Advanced, paid once at year zero. No additional storefronts. No annual price increase modelled at all, because there is no sourced escalation term for Shopify Plus and we will not invent one. Against that, a commissioned build at $80,000, a point inside our published $45,000 to $180,000 range rather than a quote for anybody, paid once, with maintenance at 15% of the build price a year as a stated ASSUMPTION that is nobody's published figure including ours.

Look at the first year before anything else, because that is the part a vendor chart hides by starting the axis somewhere convenient. The build line starts at $80,000 and the Shopify line starts at $20,000. For the whole of the first year, staying on Shopify is genuinely, substantially the cheaper decision, and at the twelve month mark it is still cheaper: $89,600 spent against $92,000. That is not a reluctant concession. It is the actual shape of the trade, and any brand that needs the money to work inside twelve months should stop reading here and go renegotiate the platform fee instead.

The lines cross at about twelve and a half months, roughly $92,500 of cumulative spend on each path. After that the gap opens every year without anything dramatic happening, because one line has a slope of $69,600 a year and the other has a slope of $12,000 a year. By the end of year three the difference is $112,800. By the end of year five it is $228,000. Nothing in the model bends the Shopify line back down, and nothing in the real contract does either.

Now the honest limits of the picture, because they are the difference between a model and a sales chart. First, the build line is a floor, not a ceiling: at $180,000, the top of our range, against this same brand, the crossover does not land until year four. Move the slider in the calculator below and watch it move. Second, the model excludes payment processing entirely on both sides, because Shopify does not publish its blended card rates and we are not going to guess them, and because a brand that commissions a build still pays a processor. Third, it excludes the staff time both paths consume, which is a real cost on both sides and unknowable from here. Fourth, it assumes Shopify never raises its price again over five years, which is the most generous assumption on the chart and it is generous in Shopify's favour on purpose.

What the chart is actually claiming is narrow and checkable: on a set of published and named third party numbers, with no invented escalator and a deliberately low agency figure, a brand at this size passes the point of financial indifference somewhere around the end of the first year, and every month after that is a widening gap. Whether that matters to you depends entirely on the next section, which is your own arithmetic rather than ours.

Every default below comes from the table above and every one of them is editable, because the Shopify lines are facts and everything else is somebody's estimate while your invoice is the only number that is true for you. Nothing is submitted anywhere. There is no email gate, the tool makes no external request, it stores nothing, and the arithmetic runs in your browser and stops there. If your inputs make the build lose, the tool says the build loses.

A word on the roster before the roster. The alternatives lists a brand finds for this decision are mostly written by companies inside the decision. The most detailed cost breakdown available publicly is published by a competing platform vendor. The most thorough roundup we could read is published by an implementation agency whose own service pages sell development work on Adobe Commerce, Shopify Plus and BigCommerce, which means it is paid to build whichever one you choose and discloses that nowhere. Software directories earn a fee when you request a demo. None of that makes those pages worthless; we cite two of them by name on this page. It does mean the shortlist you have been handed was assembled by somebody with a stake in the answer, and this page is no exception, so every number below carries its label and its source and you should go and check the ones that matter.

The six below are the platforms a mid-market brand realistically evaluates when leaving Plus, in the order it makes sense to evaluate them: closest substitute first, most distant last. The seventh is the one that does not appear on any of those other lists, and the reason it does not appear is structural rather than sinister. A comparison page written by a platform vendor cannot end with build it yourself and keep the reader.

1. BigCommerce (Performance and above)

What it is. A fully hosted SaaS commerce platform, the closest direct substitute to Shopify Plus in the market and the one most Plus refugees look at first. It covers the same ground: hosted storefront, hosted checkout, an app marketplace, multi storefront support and a B2B module. Architecturally it leans more open than Shopify, with fewer hard limits on things like custom checkout logic and API call ceilings, which is the specific reason technical teams tend to prefer it.

Price. VERIFIED. bigcommerce.com/essentials/pricing loaded on August 30, 2026 and publishes four plans: Core at $29 per month billed annually, Growth at $79, Scale at $299, and Performance at custom pricing starting at $1,499 per month, billed annually. Performance is the tier that competes with Shopify Plus, and $1,499 is the only published figure on this entire page that sits below the Shopify Plus floor of $2,300. Above Performance the page shows a demo request rather than a number, so anything larger than Performance is quoted, not published.

Best for. A brand whose complaint is genuinely and only the monthly number, that wants to stay in a fully hosted world with somebody else carrying the checkout and the uptime, and that is prepared to do a full replatform to save roughly $800 a month on the platform line.

Where it falls short. It is the same shape of arrangement with a different logo on it. The app ecosystem is smaller and less mature than Shopify's, which for a brand running eleven apps is not a detail, it is the migration. The Performance figure is a starting point with custom pricing attached, so your quote is a negotiation and not a rate card. And the structural problem this page is about, that your operating layer is assembled from other companies' subscriptions, is completely unchanged by the move.

Verdict. The honest first call if the platform fee is the whole complaint, and the wrong move if the app stack is.

Shopify Plus vs BigCommerce: which is actually cheaper?

Answered here as a section rather than spun into a separate page, because it is a question inside this decision and not a decision of its own. On published platform fees, BigCommerce wins and it is not close: $1,499 a month starting on the Performance tier VERIFIED at bigcommerce.com/essentials/pricing against $2,300 a month on the Shopify three year term VERIFIED at shopify.com/plus/pricing. That is roughly $9,600 a year of difference on the line you can see. On everything else the comparison gets murky fast and honesty requires saying so. Both figures are starting points with custom pricing above them. Neither company publishes what a large contract actually settles at. Shopify's third party surcharge of 0.20% per transaction is published; BigCommerce's own transaction fee posture is not something we read on the page we fetched, so we make no claim about it. Most importantly, the app stack does not get cheaper by moving, and in many cases it gets more expensive, because the Shopify version of a given app is often the vendor's flagship and the BigCommerce version is often the port. The realistic summary: BigCommerce saves you real money on the platform fee, costs you a full replatform to capture it, and leaves the larger recurring cost structure exactly where it was.

2. Adobe Commerce (Magento)

What it is. The enterprise incumbent, sold both as software you run yourself and as Adobe Commerce Cloud, with pricing licensed against your trailing gross merchandise value. It is the platform with the deepest native catalog and B2B capability on this list, and the one with the largest existing developer population, because Magento has been in the market long enough to have trained a generation of commerce engineers.

Price. REPORTED, and we want to be exact about why. Adobe publishes no pricing for Adobe Commerce. We attempted to fetch Adobe's own pricing page and the request timed out; a failed fetch is a failure to observe and it supports no claim at all, so we make no absence claim about Adobe's site. The figures in circulation, roughly $22,000 to $125,000 a year for the on-premise licence and roughly $40,000 to $190,000 a year on Adobe Commerce Cloud, banded by gross merchandise value, are REPORTED by Swell, the same competing commerce vendor cited elsewhere on this page, rather than published by Adobe. Treat them as a shape rather than a number.

Best for. Brands with genuinely hard catalog problems, complex B2B account hierarchies and quoting, multi-region tax and pricing rules, and an existing team or partner with real Magento experience. If you have those, this is a serious platform and the reason it has survived.

Where it falls short. The pricing opacity is not a side effect, it is the model, and it is precisely the problem a brand leaving Plus because of cost is trying to escape. Implementation is heavy, dev team dependency is permanent, and the total cost of ownership is dominated by engineering rather than licence. Swell reports the reverse migration, Magento to Shopify Plus, at $50,000 to $250,000, which is a reasonable proxy for how much work moving in this direction is too.

Verdict. The right answer for real B2B and catalog complexity, and a strange answer for anyone whose stated problem is that software costs too much and is too hard to price.

3. Salesforce Commerce Cloud

What it is. Enterprise commerce inside the Salesforce ecosystem, with the storefront tied natively to the CRM, service cloud and marketing stack a large organisation may already run. It is bought for the ecosystem tie-in far more often than it is bought for the storefront itself.

Price. REPORTED. Salesforce Commerce Cloud is priced as a share of gross merchandise value rather than a flat fee, and Salesforce does not publish the percentage. We attempted to fetch Salesforce's own commerce pricing page and it returned HTTP 403; that is a failed fetch, not an observation, and it supports no VERIFIED label and no claim about what the page does or does not say. Third party sources report the rate at roughly 1% to 3% of gross merchandise value for B2C and roughly 1% to 2% for B2B, tiering down as volume rises. Those are estimates from outside the company, one of them a competing vendor, and they should be treated as such.

Best for. Enterprises already committed to Salesforce, where the value of one customer record across commerce, service and marketing genuinely outweighs the cost of the commerce layer.

Where it falls short. Revenue share pricing has a property worth stating plainly: the platform gets more expensive precisely as the business succeeds, forever, with no ceiling that anybody publishes. For a brand leaving Shopify Plus because of cost, moving from a flat fee to a percentage of revenue is a move in the wrong direction unless the ecosystem value is very real. Implementation is enterprise scale and so is the sales process.

Verdict. A rational choice for a Salesforce enterprise and a poor one for a cost-driven escape from a flat monthly fee.

4. commercetools

What it is. The reference implementation of composable, API-first commerce. It gives you a commerce backend, cart, catalog, pricing, promotions, orders, exposed as APIs, and expects you to build the storefront and much of the experience layer yourself. It is the platform of choice for teams that have decided the front end is a competitive asset and should not be rented.

Price. VERIFIED BY ABSENCE. commercetools.com/pricing loaded normally on August 30, 2026 and publishes no dollar figure anywhere on it. The page describes an order-based pricing approach and directs buyers to contact the company for more information on pricing plans. So the page loaded, we read it, and there is no number on it. Note the difference between this row and the Adobe and Salesforce rows above: here the page loaded and contains no price, which is an observation. There, the fetch failed, which is not.

Best for. Organisations with a real engineering team, a real front end strategy, and a genuine need for commerce logic that no packaged storefront expresses. The order-based rather than revenue-share model is also a meaningful design choice for a high average order value business.

Where it falls short. This is worth saying carefully, because it is the alternative closest in spirit to the one this page argues for. Composable commerce does not remove the need to build and maintain a real software stack; it relocates it. You are still assembling and running an engineering effort, still integrating a search provider and a content platform and a payment provider, still owning the front end. The difference between commercetools and a commissioned build is not build versus buy. It is which parts you own and whether you pay a recurring licence for the parts you did not build.

Verdict. The most intellectually honest platform on this list about what modern commerce actually requires, and still a subscription underneath your own engineering effort.

5. WooCommerce

What it is. The open source commerce plugin for WordPress, and by store count one of the most widely deployed commerce systems in the world. You run it on hosting you choose, you extend it with paid extensions, and you own the installation.

Price. VERIFIED. woocommerce.com/pricing loaded on August 30, 2026 and publishes the core plugin as free with no monthly subscription and a revenue share of 0%, hosting at $25 to $350 a month for most stores scaling with traffic and performance needs, extensions at $29 to $299 a year per extension, and payment processing at roughly 2.50% to 2.90% plus 30 cents per transaction through WooPayments. That is the most transparent pricing on this page by a distance, and it deserves the credit.

Best for. Brands below the Shopify Plus threshold, brands already living in WordPress with content as a major acquisition channel, and brands whose catalogs and order volumes are modest enough that the operational burden of self-management is genuinely small.

Where it falls short. It is not a peer to Shopify Plus at real enterprise scale and pretending otherwise would be dishonest. Everything Shopify absorbs silently, security patching, performance under load, plugin conflicts after an update, PCI scope, uptime through a spike, becomes the merchant's problem or the merchant's agency's problem. For a brand doing serious volume that trade is usually bad, and the money saved on licences reappears as hosting, engineering and risk.

Verdict. Excellent value below the Plus threshold, and a step backwards for most brands who are actually paying for Plus today.

6. OroCommerce

What it is. A B2B-first commerce platform, built around the things consumer platforms treat as afterthoughts: corporate account hierarchies, contract pricing per customer, request for quote workflows, multi-buyer approval chains and complex payment terms. It ships as a free open source Community Edition and a commercial Enterprise Edition.

Price. REPORTED, with a caveat we will not paper over. OroCommerce's own pricing pages returned HTTP 403 on both attempts this session, so we could not read the vendor's own site and we make no claim about what it does or does not publish. A review platform reports the Enterprise Edition as quote-based and licensed against gross merchandise value bands, and reports the Community Edition as free and open source. Both of those are third party statements and neither is vendor-confirmed here.

Best for. Brands whose real business is wholesale or distribution wearing a DTC coat, where the B2B side is the majority of revenue and the consumer store is the smaller half. If your Shopify B2B module is the thing your team fights every week, this is the category-native answer.

Where it falls short. Same opacity as the other quote-based enterprise platforms, which is the exact complaint that sends people looking in the first place. The Community Edition is free the way a bare engine is free: it requires real developer resourcing to run, and if you had that team, several other options on this page open up too.

Verdict. The right shape for a genuinely B2B business, and priced with the same fog as the rest of the enterprise field.

7. A commissioned build you own

What it is. Not a platform. A one time engagement in which the merchandising and promotions engine, the operations and fulfilment workflow with its integrations, the reporting layer, the retention and lifecycle logic you currently rent as apps, and the back office tooling are built as software your business owns outright, and the hosted checkout stays where it is. You hold the code, the data and the roadmap. There is no licence, no per store fee, no revenue share and no renewal.

Price. One time, $45,000 to $180,000, set after a diagnosis call rather than before it, published on our own pricing page. Maintenance is a separate and optional arrangement, and the 15% of build price a year used throughout this page is a stated ASSUMPTION for modelling rather than a rate card. We are the vendor of this option, so treat this row with the same suspicion you should apply to the other six.

Best for. A brand whose app stack now costs more each month than its platform fee, whose team spends real hours bridging systems that do not agree, whose workflow has diverged from what any packaged tool expresses, and which expects to still be trading in five years.

Where it falls short. It is worse than every option above for at least the first year on cash, as the chart shows in detail. It requires you to have a stable enough process to describe, which brands still finding product-market fit generally do not. It does not replace payment processing or a PCI compliant hosted checkout, and it does not absorb your traffic spikes for you. And it needs somebody at your company to own the roadmap afterwards, because owning software means deciding what it does next.

Verdict. The only option on this list where the recurring cost stops going up, and the only one that is genuinely wrong for a brand in a hurry.

This section exists because the ownership case that follows is only worth reading if this one comes first. There is a version of this page that says own your commerce platform and leaves the reader to discover the exceptions during implementation. That version would be dishonest, and in ecommerce specifically it would be dangerous, because the exceptions involve card data.

What a commissioned build does not replace

Payment processing. Somebody has to be in a contractual relationship with a card processor, and that somebody is not a software build. A custom system integrates a processor. It does not become one. Whether you keep Shopify Payments, move to Stripe, Adyen, Braintree or anyone else, you are still paying interchange, scheme fees and a processor margin, and those costs travel with you to every option on this page including this one. Any comparison that shows processing costs disappearing when you build is either confused or lying.

PCI compliant hosted checkout. This is the important one. A hosted checkout keeps raw card data out of your systems entirely, which collapses your PCI DSS scope from something requiring a serious annual programme to something much smaller. Building your own checkout that touches card data pulls all of that scope back inside your company. There are legitimate architectures where a custom front end hands off to a hosted payment page and scope stays small, and that is what we would build. There is no architecture where owning your own card handling is cheaper or safer for a mid-market brand, and we will not pretend one exists to make a page tidier.

Storefront hosting through a demand spike. Shopify absorbs the day your ad works. If you move the storefront off it, that becomes your problem or your host's problem, with real infrastructure and real on-call implications. For many brands the sensible build keeps the storefront on Shopify entirely and owns everything behind it, which is a genuinely common and genuinely good answer that vendor comparison pages never mention because it does not fit either column.

The app ecosystem's breadth on day one. If your business genuinely uses eleven apps in ways that are each specific and each valuable, replacing all eleven at once is a bad plan. Replacing the two or three that cost the most and fit the worst is a good one.

What a commissioned build does replace, and owns permanently

The merchandising and promotions engine. Collection logic, bundling rules, tiered and contract pricing, promotional stacking rules, regional catalog differences. This is where most brands hit the wall of what a packaged system will express, and where the workarounds accumulate.

The operations and fulfilment layer, with its integrations. The connective tissue between orders, inventory, the warehouse or three party logistics provider, purchasing and the finance system. This is almost always the most expensive part of the stack when you count both subscriptions and the human hours spent reconciling it, and it is almost always the part with the weakest packaged options, because every brand's version is genuinely different.

The reporting and analytics layer. Contribution margin by SKU after returns, cohort behaviour by acquisition source, real inventory-aware forecasting. The reason brands buy a fourth analytics tool is that the first three answer a generic question rather than theirs.

Retention and lifecycle logic. Subscription mechanics, replenishment timing, loyalty rules, win-back sequencing. Today this is rented from several vendors at once, each holding a piece of your customer relationship in its own database, and it is one of the more expensive lines on a mature stack.

The back office and admin tooling. The internal screens your team actually lives in every day, built for the way your team works rather than for the average of every merchant on a platform.

The pricing model itself. No per storefront fee, no revenue share, no transaction surcharge, no renewal. That is the line item that stops compounding, and it is the only reason the crossover chart bends the way it does.

Held together, the honest sentence is this: the parts of commerce that are commodity and risky, payments, compliance, checkout, stay rented; the parts that are specific to your business and expensive to rent forever get owned. Anybody selling you the reverse arrangement is selling you the wrong half.

1. The math, restated with the number attached

The chart above is the whole argument in one picture, so here it is in one sentence: on the default scenario, Shopify Plus costs $159,200 by the end of year two and $368,000 by the end of year five, an owned build costs $104,000 and $140,000 over the same horizons, and the lines cross at about month thirteen. The reason is structural rather than clever. One path has a recurring slope and the other has a one time step plus a small flat line. There is no version of the arithmetic where a slope does not eventually beat a step, and the only real question is whether the crossover lands inside a horizon you care about. For a brand at this size, on these numbers, with no price increase modelled at all, it lands just after the first year.

2. An asset on the balance sheet, not an expense on the profit and loss

Five years of Shopify Plus at the default scenario is $368,000 of expense, and at the end of it you own nothing. The subscription was rent; when you stop paying it, the store stops. An $80,000 build is $80,000 of capitalised software that belongs to the company, appears on the balance sheet, and is still there in year six. This matters more than it sounds in one specific circumstance that a lot of DTC founders are actually heading toward: a sale. A brand that owns its operating system is selling a business with proprietary infrastructure. A brand that rents everything is selling a customer list, a supplier relationship and a set of subscription agreements that the acquirer has to assume. We are not going to attach a multiple to that difference, because we have not seen a defensible published figure for it and inventing one would be exactly the sin this page keeps calling out. The qualitative point stands on its own.

3. Built around your workflow, not the average of every merchant

A packaged commerce platform is a compromise between hundreds of thousands of merchants, which is what makes it cheap and what makes it fit imperfectly. Every brand at this size has a list of things it does in a spreadsheet, in a Slack thread, or by hand, because the platform does not express them: the way your pre-orders and backorders actually work, the way returns are graded and restocked, the way wholesale pricing is negotiated per account, the way a bundle's inventory is decremented, the way a drop is staged across regions. Each of those workarounds costs somebody hours every week, forever, and none of them appears on any cost comparison including the one on this page. A commissioned build starts from your process instead of ending at it. It is also the reason the build takes weeks rather than days: describing the real process is most of the work.

4. AI built on your data, not a general assistant bolted to a platform

We want to be precise here, because the usual version of this argument does not apply to Shopify and running it anyway would be dishonest. Many enterprise vendors sell AI as a premium per seat add-on, and on those pages we cite the add-on price. Shopify does not do that. Shopify Magic, its built-in assistant for product copy, images and support replies, is available across plans without a separate AI tier, and there is no Shopify AI upcharge for us to point at. So the honest argument is not about a tax; it is about what the AI is trained on and what it is allowed to touch. A platform assistant is built for merchants in general: it writes a decent product description and drafts a decent support reply. It does not know your margin structure, your returns history by SKU, your fulfilment constraints, your supplier lead times or your customer's four previous conversations, because it was never given them. AI inside a system you own starts from exactly those things, and it can act inside your workflow rather than beside it. That is a real difference and it does not require a fabricated price comparison to be worth something.

5. Growth stops being taxed, on the units that actually grow

Say the true thing rather than the convenient one: Shopify Plus does not tax seats. Staff accounts are unlimited on this tier, published on shopify.com/pricing, and a brand whose team doubles pays the same platform fee. If somebody tells you Plus charges per user, they have not read the pricing page.

What Plus taxes is the three things an ecommerce business grows by. Storefronts, at $300 a month each beyond the nine included, or a revenue share across all stores, on Shopify's own page. Transactions, at 0.20% each to Shopify on top of your processor's fees if you keep a processor relationship outside Shopify Payments, on the same page. And volume itself, through the variable platform fee that page mentions for more complex, higher volume businesses without publishing a rate. Every one of those is a tax on succeeding. A commissioned build has none of them: the tenth storefront is a configuration change, the millionth order costs the same as the first at the platform layer, and doubling revenue does not move the software line at all.

6. Your data, your export path, no exit negotiation

Credit where it is due first: Shopify's own pricing page states that Shopify does not charge you to migrate, and its export tooling and Admin API are genuinely good. This is not a category where the platform holds your catalog hostage, and we are not going to imply otherwise.

The lock-in in this stack is not at the platform. It is distributed across the eleven vendors sitting on top of it. Your subscription vendor holds your active subscription contracts and their billing schedules. Your loyalty vendor holds the point balances your customers believe they own. Your reviews vendor holds a corpus you spent four years accumulating and which is worth real money in conversion. Your helpdesk holds the conversation history. Each of those has its own export path, its own export quality, and its own answer when you ask for a full extract on your way out. That is the exit cost nobody models. In a system you own, all of it is in a database you have credentials to, and the export path is a query.

7. Vendor risk you stop carrying

Three flavours of it, all real in this category. Price changes you cannot see coming. The Plus base fee moved from $2,000 to $2,500 on the one year term during 2024, an increase of 25%, REPORTED consistently across independent trade press and disclosed nowhere on Shopify's current pricing pages, which carry no price history at all. We checked for one specifically. The change was not wrong of Shopify to make; it is simply a decision made outside your business that changed your cost base, and there was no published escalator to have planned against. App vendors that get acquired, repriced or shut down. This is the more frequent event and it is the one that actually breaks operations. A subscription or loyalty or bundling vendor sitting in your critical path is a single point of failure your customers experience as your failure. Roadmaps decided elsewhere. The feature you need may arrive, may arrive in a form that does not fit, or may never arrive, and you will find out in a release note.

8. Change speed, which is the argument operators care about most

The cost most operators actually feel is not the invoice. It is the eight weeks between deciding something should work differently and it working differently. On a rented stack the sequence is: find out whether the platform supports it, find out whether an app supports it, evaluate two apps, trial one, discover it conflicts with another app, file a feature request, wait. On a system you own the sequence is: describe it, schedule it, ship it. That difference compounds in a way no spreadsheet catches, because it changes what the team bothers to propose. Brands with owned systems try more things, because trying is cheap.

9. One fixed fee, scoped, once

$45,000 to $180,000, one time, set after a diagnosis call rather than before one, with the code and the data yours at handoff. No per store fee, no revenue share, no transaction surcharge, no renewal conversation, no term commitment traded for a discount. Where you land inside that range is a function of how many of the layers in the previous section you actually want built and how tangled the existing integrations are, which is a thing that can only be assessed by looking at your stack rather than by reading a page.

The proof, and only the proof we can stand behind

We are going to be short here rather than impressive, because inflated proof is the fastest way to lose a reader who is doing real diligence. What we can point at: Jim Glaser Law, a client we can name and who takes reference calls. The LELF platform, a commissioned system we built and shipped. More than 6,000 AI-handled calls through systems we have built. More than 40 commissions delivered. That is the list. There is no ecommerce case study with a revenue percentage attached on this page, because we do not have one we are contractually free to publish with real numbers, and a fabricated or anonymised one would be worth less than saying so. If you want to test whether we can do this specific work, the diagnosis call is where that gets tested, and it is free.

This is the section that makes the rest of the page believable, and it is not a token paragraph. A meaningful share of the diagnosis calls we run end with us telling the brand to stay where they are. Here is how to tell in advance whether you are one of them.

You are below the threshold, and the reviewers are right about where it is

Gregg C., a reviewer in sporting goods at an 11 to 50 employee company, wrote on Software Advice that if your online store is not selling $100,000 a month or more, it might make more sense to stick with the basic Shopify options. Garrick C., in retail and self-employed, wrote that the tier levels are a bit pricey a bit too soon and that the pricing structure is tailored towards larger small businesses. Both quotes were read verbatim on softwareadvice.com on August 30, 2026, and both are individual customer opinions rather than vendor statements. They are also correct in our experience. Below roughly that revenue line, the right move is usually down a tier rather than out of the platform, and a custom build at $45,000 is a serious percentage of a business that size. Go and look at Shopify Advanced at $299 a month before you look at us.

Your storefront is the product and the checkout is the moat

Some brands live and die on conversion rate at checkout, and Shopify has spent an enormous amount of engineering on exactly that surface, including the accelerated checkout paths that a customer already has stored. If a measurable part of your conversion advantage is the checkout itself, moving the storefront is a risk with an asymmetric downside: you can lose more in conversion in a quarter than you save in licence fees in three years. In that case the sensible architecture is to keep the storefront and checkout exactly where they are, and build only behind them.

You are still finding the process

Custom software encodes a process. If your process is still changing every quarter, because the product line is still moving or the channel mix is still being discovered, encoding it is premature and expensive. Packaged software's ability to be reconfigured badly but quickly is a genuine feature at that stage. Come back when a named person can describe how a wholesale order moves from email to invoice without hedging.

You need it working next month

A commissioned build takes weeks, and a phased migration off an app stack takes longer than the build. If the pain is acute and dated, a peak season eight weeks away, a contract that ends, a system that already failed, then the right answer is the fastest adequate one, which is usually an app or a platform move rather than a build. We would rather tell you that on the call than take a deposit against a timeline we cannot hit.

Your app stack is small and cheap

If you are running three apps that total a few hundred dollars a month, the ownership argument on this page barely applies to you. Its whole force comes from the gap between the platform fee and the total, and if that gap is small, so is the prize. Recheck in two years, or on the day you count the subscriptions and it surprises you.

Nobody at your company will own the roadmap

This is the failure mode that produces expensive, half-used custom software, and it has nothing to do with the quality of the build. Owned systems need an owner: one person, internal, who decides what it does next and cares whether it is used. If you cannot name that person today, buy a subscription, because a subscription comes with a vendor whose job is to keep improving it whether you engage or not.

A large multi-brand group with genuine enterprise negotiating leverage

If you are large enough that your renewal is negotiated rather than quoted, and your contract has already moved to structures the pricing page does not publish, then the published $2,300 figure on this page is not your number and the model here does not describe you well. You have leverage most readers of this page do not, and the first move is to use it. Build the model with your real contract terms before you decide anything, and if it still crosses over, the conversation is a different and larger one.

Answer these in sequence. Several of them end the exercise, and that is the point of writing it as a tree rather than a pitch.

1. Is your online revenue under roughly $100,000 a month? If yes, stop. Look at Shopify Advanced at $299 a month, published on shopify.com/pricing, and revisit this page when you have grown into the problem. If no, continue.

2. Add up every recurring line that exists only because of the store: platform fee, every app, every connector, every retainer. Is the platform fee more than half of it? If yes, your complaint really is the platform fee, and your move is either a hard renegotiation at renewal or a look at BigCommerce Performance at $1,499 a month starting, published on bigcommerce.com/essentials/pricing. Stop here and go do that. If no, continue, because you have the problem this page is actually about.

3. Does a named person on your team spend more than a few hours a week bridging systems by hand? If no, continue but discount everything below, because you are missing the largest hidden cost in the model. If yes, write down their loaded hourly cost times those hours times fifty. That number belongs in your total and it is not in the calculator above.

4. Can you describe your core operational process end to end without hedging? If no, stop. You are not ready to encode it and anyone who tells you otherwise is selling you a rebuild in eighteen months. If yes, continue.

5. Do you need the change working inside eight weeks? If yes, stop. Buy the fastest adequate thing. If no, continue.

6. Can you name the internal person who will own the system after handoff? If no, stop, and buy a subscription so that somebody else's product manager does that job. If yes, continue.

7. Run the calculator with your real numbers. Does the crossover land inside a horizon you actually plan against? If no, stay, and set a reminder to run it again at the next renewal. If yes, the remaining question is not whether to build but which layer to build first, and that is a forty-five minute conversation rather than a page.

Two branches worth naming explicitly, because they are the ones most readers land on and neither is the one this page is nominally selling. If you answered stop at question two, the honest answer for you is a renegotiation or BigCommerce. If you answered continue all the way through but your app stack is genuinely well fitted and cheap, the honest answer is a build of one layer, probably operations and reporting, sitting behind a Shopify storefront you keep. That hybrid is the most common outcome of these calls and it is nobody's headline.

Every alternative on this page has a migration behind it, including ours, and every vendor's migration page is written by someone who wants the migration to sound small. Here is the version that is useful to plan against.

The data is the easy part, and Shopify does not fight you

Start with the good news, since it is genuinely good and it is on Shopify's own page: Shopify does not charge you to migrate, though the same page notes that migration is your responsibility and that paid services exist for custom needs. Practically, the admin exports products, customers and orders as CSV, and the Admin API pages through the same objects with far more fidelity, including metafields, which the CSV export handles poorly. The objects you actually need are all reachable: product and variant records with their identifiers and inventory levels, customer records with their marketing consent state, full order history with line items and financial status, discount and price rules, and the metafields where most brands have quietly stored a decade of business logic. Budget days of senior engineering time rather than months, and budget for one careful person rather than a team.

The apps are the hard part, and nobody warns you

This is where migrations actually run over. Each app in your stack is a separate product with its own data, its own export path and its own quality of cooperation. Subscription contracts are the worst case in the category: they carry billing schedules, payment method tokens, discount states and customer expectations, and moving them means either a token migration negotiated with two processors or asking real customers to re-enter a card, which costs you churn measured in real subscribers. Loyalty balances are a promise to your customers that must survive the move exactly. A reviews corpus built over years is a conversion asset and its export fidelity varies enormously by vendor. Helpdesk history matters the first time an agent needs it. Plan the app migration before the platform migration, because it is longer, and sequence it so that any app whose data cannot be moved cleanly is either replaced first or kept.

The integrations get rebuilt, not moved

Whatever connects your store to a warehouse, a three party logistics provider, an ERP, a tax engine or a marketplace was written against Shopify's object model and webhook behaviour. None of that travels. Each connection has to be rebuilt against the new target and, more importantly, re-tested against the failure cases that only appear in production: the partial shipment, the split order, the cancelled line, the refund after fulfilment, the inventory adjustment that arrives out of order. Those edge cases are where the real work is and they are invisible in any plan written from a happy path.

Run in parallel, and define what would send you back

The pattern that works is the boring one. Keep the existing system running and authoritative. Stand the new system alongside it, reading the same data. Run one narrow slice for real, one channel, one region, one product family, or one workflow such as returns, and reconcile the two systems daily until they agree without anyone intervening. Only then move the next slice. Write down before you start what result would make you stop and go back, and give someone the authority to call it. Migrations fail far more often from nobody being willing to say this is not working than from the technology.

Timeline honesty

We are not going to publish a duration range for a full Shopify Plus exit, because we could not source a credible one for this specific move and the numbers circulating are guesses dressed as benchmarks. What we will say is what is inside our control and observable: a commissioned build in our shop runs four to seven weeks from signature to handoff, and that is the build, not the migration around it. The app and integration work sits on either side of it and is usually the longer half. For the reverse direction, moving onto Shopify Plus, Swell reports implementation at $10,000 to $30,000 coming from Shopify Advanced and $50,000 to $250,000 coming from Magento REPORTED, which is the only sourced sizing available in this category and gives you a floor for how much work a platform-scale move is in either direction.

The migration you probably should not do

Worth ending on. For a large share of the brands who read a page like this, the correct plan is not to leave Shopify at all. It is to keep the storefront and the checkout, which are the parts Shopify is genuinely excellent at and the parts a build should not touch, and to replace the two or three most expensive and worst fitting pieces behind them with software you own. That is a smaller project, a shorter migration, a much lower risk profile, and it captures most of the recurring saving because the recurring saving was never in the platform fee. It also happens to be the outcome that a page selling a full replatform would never recommend, which is the reason to trust it slightly more.

If your back office is the real problem rather than the storefront, NetSuite alternatives for retail and ecommerce runs this same sourced cost model on the ERP and inventory side, and Yotpo alternatives does it for the reviews, loyalty and retention layer that sits directly on top of a Shopify store. For what we actually build for brands at this size, custom AI systems for ecommerce and DTC lays out the five systems and what each one replaces. For the pricing evidence behind this page and every other category we track, the vertical software pricing index carries the dated ledger. For the underlying decision rather than the vendor comparison, renting AI versus owning it lays out what renting really costs over the same horizons, and off the shelf versus a custom commission is the five test framework we run on every diagnosis call, including the tests that send people back to buying. The full comparison library holds the rest, how the fixed fee is set explains where a number inside $45,000 to $180,000 comes from, and the process page walks through what the weeks after a signature look like.