Shopify Alternative: Building a Storefront Instead of Paying the Subscription

Weighing a Shopify alternative? See what Shopify costs each month in fees and apps, what you take on by building your own store, and when it pays off.

Aram Shatakhtsyan
Aram ShatakhtsyanCo-Founder, Modelence
Last updated
Reading time8 min
Shopify Alternative: Building a Storefront Instead of Paying the Subscription

TL;DR

Key takeaways

  • Payment processing remains a cost whether you use Shopify or build your own storefront.
  • Shopify's plan fee may be modest compared with the cost of apps or custom workflows, but leaving means taking responsibility for hosting, tax, shipping, security, and maintenance.
  • Building is easiest to justify when the business needs a non-standard checkout or operating model, not when it only wants to remove a subscription.
  • Headless Shopify offers storefront flexibility while keeping Shopify's commerce backend.

Ask AI about this post:

If you are reading this, you are likely in one of two situations:

  • You already use Shopify and are wondering whether the recurring bill is still worth it.
  • You are launching your first store and deciding whether to pay for the platform from day one or build an online store you control.

Either way, the subscription price tells only half the story.

Shopify bundles hosting, checkout, security, catalog management, and routine operations.

Building your own storefront may reduce some platform fees, but it replaces them with development, maintenance, and operational work.

This guide compares the full monthly costs, explains the work each option requires, shows when building can pay off, and outlines practical ways to launch.

Ways to Build Your Own Store

“Building your own store” can describe four different projects:

  1. Headless Shopify: You build the customer-facing storefront but keep Shopify for products, orders, and checkout.
  2. A self-hosted commerce platform: Open-source software such as WooCommerce or Medusa supplies commerce foundations, while you arrange hosting and integrations.
  3. A custom agency or developer build: A team creates the store around your exact workflows and maintains it under an agreed scope.
  4. An AI-built app with code you control: An AI app builder can help create the first version, but someone must still review the code, test integrations, and operate the production system.

These routes differ more in ownership and operational responsibility than in page design.

Before comparing quotes, ask who controls the code, data, hosting account, payment integration, and deployment process.

What You Pay Shopify Each Month

Consider a US store with $20,000 in monthly sales and 400 domestic consumer-card orders.

At 2.9% plus 30 cents per transaction, card processing for Shopify Basic and Stripe is $700. Shopify Grow’s lower processing rate brings that figure to $660.

Based on Shopify’s published US pricing, the monthly totals before apps would be:

OptionPlan BasisPlan FeeCard ProcessingTotal Before Apps
Shopify BasicAnnual billing$29$700$729
Shopify GrowAnnual billing$79$660$739
Stripe standard pricingNo monthly payments fee$0$700$700

The Stripe row covers payment processing only. It does not include a storefront, hosting, catalog management, security, or other commerce operations.

On monthly billing, Shopify lists Basic at $39 and Grow at $105, bringing the totals to about $739 and $765. These figures exclude premium cards, international cards, currency conversion, taxes, disputes, and other services.

The more useful number may be the app subtotal. If bookings, subscriptions, wholesale pricing, or product configuration require several paid apps, include every invoice in a 12-month total.

Shopify also lists an additional transaction fee of 2% on Basic and 1% on Grow when a merchant uses a third-party payment provider instead of Shopify Payments.

Pricing and availability were verified in September 2026 and may change.

The Work Shopify Does for You

Shopify does more than render product pages. None of the following jobs is especially difficult on its own, but together they make up much of the work of running an online store.

Price each one before treating the plan fee as avoidable overhead.

Payments and Card Security

A hosted checkout or provider-controlled payment form keeps raw card data away from your application.

Stripe's standard US pricing is 2.9% plus 30 cents per successful domestic-card transaction, with no setup or monthly payments fee. Stripe also says its payment libraries can collect details without sensitive card data hitting your servers.

That reduces your Payment Card Industry Data Security Standard (PCI DSS) scope, but does not remove your obligations.

You still need secure account access, verified webhooks, which are automated messages sent between services, protected keys, software updates, and the correct annual compliance process.

Sales Tax

The store owner determines where the business must register, collect, and remit tax. A tax service can calculate the amount at checkout, but it cannot make the legal determination for you.

Stripe Tax Basic, for example, lists a 0.5% fee per transaction for its no-code integrations where the merchant is registered to collect tax. Confirm your obligations with a qualified tax adviser.

Shipping, Returns and Order Emails

A usable store needs shipping rates, label creation, tracking updates, returns, order confirmations, and shipping emails.

Each function can come from a specialist service, but the connections must agree on order status, addresses, refunds, and inventory. Test the full workflow, not just the checkout page.

Uptime, Backups and Security Updates

On a self-hosted platform, the owner or technical partner manages capacity, backups, security updates for third-party software dependencies, monitoring, access controls, and incident response.

An agency may include those jobs in a maintenance contract.

With an AI-built app, they still belong to the owner unless a hosting or support provider explicitly accepts them. Fraud screening is another separate decision tied to the payment stack.

When Building Your Own Store Pays Off

Fee savings alone rarely justify building a production-ready store. A custom build makes more sense when at least one of these applies:

  • You need checkout fields, steps, or logic that standard Shopify plans cannot support.
  • Your business model requires several apps or awkward manual handoffs.
  • Control over the code, data, hosting, and migration path is important.

One strong reason may be enough to justify a build. If none applies, Shopify is likely the better fit.

Control of the Checkout Flow

Shopify allows many checkout customizations, but apps that change the information, shipping, and payment pages are limited to Shopify Plus. Shopify lists Plus from $2,300 per month on a three-year term.

A custom checkout can support additional fields, approval steps, and business logic. However, the team operating it also becomes responsible for testing and compliance.

Non-Standard Business Models

Template stores can become restrictive for business models involving:

  • Product configurators or made-to-order workflows
  • Bookings sold alongside products
  • Multi-vendor marketplaces
  • Customer-specific business-to-business pricing
  • Memberships

If supporting the business requires several paid apps or awkward handoffs between systems, a custom store may simplify the operating model.

Ownership of Your Data and Code

Shopify can export products, customers, and orders, but migration is not a complete copy operation.

Its product export guidance says product images are not included in the comma-separated values (CSV) file. They can be regenerated during import only while their public uniform resource locators (URLs) remain accessible.

Themes, app data, and customer authentication may require separate migration work.

Owning the application code can make it possible to change hosts without rebuilding the storefront.

However, that portability also depends on controlling the repository, data export, configuration, and deployment documentation.

Who Should Stay on Shopify

Stay on Shopify if you have a standard catalog, limited technical support, and no workflow that clearly requires custom software.

At Shopify’s published US rates, Grow’s lower card rate offsets its higher annual-billing plan fee compared with Basic at roughly $25,000 in monthly domestic card sales, before other plan differences are considered.

For these stores, a custom build adds vendor management, maintenance, and launch risk without necessarily reducing total cost.

A clear monthly bill can be better than a lower-looking infrastructure bill plus unpredictable engineering work.

Headless Shopify for a Custom Storefront

Headless Shopify sits between using a standard theme and leaving the platform.

You can build a custom storefront with Shopify’s Hydrogen framework and Storefront application programming interface (API) while Shopify continues to manage catalog data, orders, and checkout.

This option suits merchants that want more control over navigation, content, or product experiences without rebuilding payments, tax handling, and other core commerce operations.

It does not remove the Shopify subscription, and it introduces frontend development and deployment work.

How to Build a Storefront Without Shopify

Whichever build route you choose, the same six-step process takes the storefront from planning to launch.

Step 1. Map Your Catalog and Order Flow

Document products, variants, stock rules, discounts, fulfillment, cancellations, and returns.

Include every staff action and customer notification. This becomes the data model and build brief for an agency, developer, or AI builder.

Step 2. Set Up Payments With a Hosted Checkout

Use a hosted checkout or provider-controlled payment form so raw card data does not pass through your server. In test mode, cover a successful order, a decline, a refund, a duplicate click, and an interrupted payment.

Step 3. Connect Tax, Shipping and Email Services

Connect tax calculation, shipping rates, labels, confirmations, and tracking messages. Run a test order from checkout through refund, then confirm that the payment, inventory, tax, and email records all match.

Step 4. Move Products, Customers and Orders

If you are leaving Shopify, export products, customers, and orders as CSV files, and download copies of product images separately.

Decide whether customers will reset their passwords or receive account invitations. First-time sellers can skip migration but should still test bulk imports and backups.

Step 5. Redirect Old URLs Before Moving the Domain

Map each old product, collection, and content URL to its new location. Put permanent redirects in place before changing the domain so bookmarks, campaign links, and search visits do not land on errors.

Step 6. Launch With Monitoring and a Rollback Plan

Soft-launch to a small group. Turn on error alerts and uptime monitoring, confirm backups can be restored, and document how to reverse a bad deployment. Run a realistic traffic and order test before a promotion.

Host Your Custom Storefront With Modelence

Once your custom storefront has been built and tested, it needs a reliable production environment.

Modelence Cloud provides production hosting for storefronts that meet its technical requirements.

Before launching, confirm that the storefront uses the Modelence framework and that its database setup, payment webhooks, background tasks, security controls, backup process, and expected traffic fit the available hosting configuration.

Modelence Cloud can provide the hosting layer for a storefront that meets these requirements. Payments, tax, shipping, and email remain connected through their respective providers.

After confirming these requirements, create a Modelence Cloud account.

Frequently asked questions (FAQs)

Can I start on Shopify and move to my own store later?

Yes. Plan the migration around exports, product images, app data, customer authentication, redirects, and a period when both systems can be checked.

Do I need a developer to build and run my own online store?

Not always to create the first version, but you need someone able to validate security, integrations, deployment, monitoring, and recovery. That person may be an employee, agency, or support provider.

Is a store I build myself as secure as a Shopify store?

It can be, but security is an ongoing operating responsibility. Use hosted payment collection, access controls that give each person or service only the permissions needed, prompt patching, backups, monitoring, and independent review before launch.

How long does it take to launch an online store without Shopify?

The timeline depends on the catalog size, migration work, checkout logic, integrations, compliance requirements, and testing. Scope each area before setting a launch date.

Can I sell on Instagram, TikTok or Amazon without using Shopify?

Yes, if your store and accounts meet each channel’s country, catalog, and integration requirements. Decide which system will be the source of truth for inventory and orders.

Can I keep my domain if I move off Shopify?

Yes, if you control the domain registration or can transfer it. Prepare the new hosting records and URL redirects before changing the domain's Domain Name System settings.

What happens to customer accounts when I leave Shopify?

Customer records can be exported, but passwords generally cannot be migrated as readable credentials. Plan an invitation or password-reset flow and explain the change to customers.

What happens to data stored in my Shopify apps when I leave?

It depends on each app. Request exports and retention details from every provider before cancellation, then verify that required business and compliance records are complete.

Build your next app on a framework you actually own

Modelence generates a production-ready full-stack app from a prompt, on an open-source TypeScript framework with auth, database, and deployment built in.

Get started for free