Shopify Starter is no longer available to new stores. Existing Starter stores can remain on the plan, but Shopify says they cannot return to Starter after switching to another plan. That current availability rule is the starting point for any review of older “$5 Shopify store” advice.
The rule is documented in Shopify’s Starter plan guide. This article now focuses on merchants already using Starter. New merchants should read Starter versus Basic for a first store.
Review the business you have today
Do not upgrade because another store uses a more expensive plan. Identify the requirement your current setup cannot meet. It might involve storefront organization, team access, an app, or another operating workflow.
Write the problem in observable terms: “Customers cannot browse the product grouping we need,” or “A second person needs a supported way to do this task.” Then check the destination plan’s current documentation. A higher price alone is not proof that the feature exists.
Separate limitations from assumptions
Starter has a simplified selling model and does not support collections or additional staff accounts, according to its plan documentation. Verify any other feature individually rather than relying on an old tutorial’s list of exclusions.
Use Shopify’s plan selection guide to compare current options. For market-specific costs and billing terms, use the pricing page and your store’s account information.
Do not use a blanket comparison of “5% versus 2%” as if it represented every payment cost. Processing rates, third-party transaction fees, provider choice, and location must be considered separately when estimating a bill.
Build an upgrade worksheet
| Item | Current store | Proposed destination |
|---|---|---|
| Required customer journey | What works today | What will change |
| Missing capability | Concrete limitation | Documentation confirming support |
| Platform cost | Actual current bill | Normal price after any promotion |
| Payment costs | Current provider and rate treatment | Relevant destination terms |
| Apps and services | Existing dependencies | Additions, removals, or migrations |
| Operating work | Manual tasks | Expected time saved or added |
| Reversibility | Current Starter access | Cannot return to Starter after leaving |
Keep promotional savings separate from the continuing cost. Use actual order counts as well as revenue because per-order fees affect the calculation.
Make the transition a small project
Before switching, record important settings, customer-facing pages, product organization, and connected apps. Plan how the people running the store will verify the new workflow. Check the store’s customer journey after the change rather than assuming every existing integration behaves identically.
A reasonable acceptance list includes product presentation, checkout eligibility, delivery or fulfillment, customer contact information, and the tasks staff need to perform. The first physical-store app guide provides a framework for reviewing software dependencies.
When staying can be reasonable
If the current plan still supports the way you sell, and its full cost is acceptable, staying can be reasonable. Document the limitation that would trigger another review rather than upgrading preemptively.
If a required workflow is blocked and another plan demonstrably supports it, compare the added cost with the value of removing that block. Avoid claiming a universal revenue threshold: two stores with different order values, payment providers, and operational needs can reach different decisions.
Update note: The September 9, 2026 revision removes obsolete new-store signup advice and unsupported claims about Linkpop, typical upgrade timing, and universal fee comparisons. The original URL remains available so older links lead to current guidance.