Astro vs Shopify
This is not a choice between two platforms. It is a decision about where the line goes between the site that explains the product and the store that sells it, and the answer for a working store is almost never to move the store.
Pick the one the job wants.
Read both columns. The one that describes more of your week tells you where the pressure is coming from.
Keep everything on Shopify when
- The whole site is the store, and the theme is doing the job.
- Nobody is blocked: whoever needs to change a page can safely change it.
- Marketing pages are few, and they rarely change.
- The app list is short and every one of them earns its script.
Move the marketing site when
- Campaign pages are theme templates only a developer can safely touch.
- Marketing is waiting on a deploy to publish a landing page.
- The app scripts are slowing every page, including the ones with no products.
- The content that explains the product has outgrown what a theme can hold.
Capability by capability.
| What is being compared | Shopify | Astro |
|---|---|---|
| Design control | Shopify A Liquid theme, and the sections it defines | Astro Components, styled in code |
| Content model | Shopify Products, collections, pages, metafields | Astro Product data from Shopify, page content from a CMS |
| Where the cart lives | Shopify Shopify, end to end | Astro Shopify, still, reached through the Storefront API The most important row on this page. Whatever else moves, the cart and the checkout should not: PCI scope, fraud, tax and the payment integrations are Shopify doing work nobody should volunteer to redo. |
| Who can edit a landing page | Shopify Whoever can safely edit the theme | Astro Marketing, in a CMS, without touching the store |
| Where campaign pages go | Shopify Theme templates, or an app that injects them | Astro Routes in the codebase, or entries in the CMS |
| Who maintains it | Shopify Shopify, plus whatever the app list is doing | Astro Your team owns the front end; Shopify still owns commerce |
Architecture
Four things that change when the site becomes a codebase.
Differences in how the site is worked on, not reasons on their own. If the case for staying on Shopify above still describes you, none of them is worth a migration.
Estimate your migration cost Compare Astro to every platform
-
Checkout
The commerce backend and checkout do not move
This is the whole design of the project rather than a caveat in it. Product data, cart state and storefront interactions can surface through the Astro front end. PCI scope, fraud, tax and the payment integrations are Shopify doing work nobody should volunteer to redo.
Shopify stays the system of record for products, inventory and commerce, Shopify Checkout stays responsible for completing the sale, and the store keeps selling throughout. A migration that touches the money is a different and much worse project.
-
Publishing
Marketing gets a publishing system separate from the store
A well-built theme gives marketing real control. The constraint shows up when campaign content starts needing structures the theme was never designed to provide.
With Astro and a CMS, marketing content gets its own model and its own publishing workflow, without changing the storefront theme or anything responsible for commerce.
-
App weight
The pages that sell nothing stop paying for the store
Commerce themes accumulate storefront scripts for reviews, loyalty, chat and recommendations, and some of that code ends up loading on pages where the feature contributes very little.
Separating the marketing front end lets those pages ship only what they need, while commerce code stays on the surfaces that actually use it.
-
Product data
Product data is read rather than copied
Prices, stock and variants stay in Shopify and are read from it, so there is never a second version of a price to disagree with the first.
How stale a price may be before somebody is upset becomes an explicit caching decision, made by the merchant rather than discovered by a customer.
Integrations
Changing the frontend doesn't mean changing your stack.
The site is one part of a marketing stack, and a migration that leaves the rest of it broken has not finished. Each of these is a deliberate integration with a guide behind it, rather than a script pasted into a header somewhere.
-
HubSpot
Forms that land in the CRM as records, confirmed by the server rather than by the browser.
CRM
-
Sanity
A content model the marketing team edits and the build renders, with no second copy of anything.
CMS
-
Google Analytics
Traffic and conversions measured against the routes the site actually has.
Analytics
-
Stripe
Checkout handled by Stripe, with the webhook as the record that decides what happened.
Payments
-
Mailchimp
Signups that reach the audience exactly once, whatever the visitor clicks.
Email
-
Zapier
Site events handed to the automations the team has already built.
Automation
Shopify and Astro, answered.
Should I move my store off Shopify?
Almost certainly not. Shopify is doing genuinely hard work around payments, tax, fraud and inventory, and rebuilding that to save on a theme turns a marketing problem into a payments problem. What is worth moving is the marketing site in front of it.
Will my checkout still work?
Yes, because it is still Shopify's checkout. The new front end hands off to it, which is why the store keeps selling while the project runs and why nothing about compliance or payment integrations changes.
What happens to my Shopify apps?
Each becomes a decision. Reviews, bundles, upsells and loyalty inject script into the theme, and on a new front end each is a deliberate integration, replaced, or dropped. Some exist only as theme extensions, which means the feature is replaced rather than moved, and that list is worth having before anybody quotes.
Do my product URLs change?
No. The /products/ and /collections/ prefixes are load bearing for search and they keep working. What typically changes is /pages/about becoming /about, which is a redirect rather than a loss.
How long does it take?
Three to six weeks. Most of the first week goes into deciding the boundary, which is the part that determines everything after it: draw it badly and you have either rebuilt a checkout for no reason or split a product page across two systems that disagree about the price.
Reach out and see if we are a good fit.
Currently booking two to four weeks out.