Build a Shopify store with AI: the eight steps

Building a Shopify store with AI is eight steps, and the AI does one of them. Shopify holds the products, the checkout and the payments; you pull the theme to disk; your AI (Claude Code, Cursor, ChatGPT with a connector, Lovable) writes the sections; the Shopify CLI previews and pushes. The step people skip is handing the AI the selling sections by name, and it is the one that decides whether the store converts or merely exists.

This is the rebuild path, for a store that does not exist yet. If you already have a store, do not follow it: Improve an existing Shopify store with AI keeps your page and adds only what is missing. That rule, improve before rebuild, is the MCP's default and is written at /docs#improve.

What the AI cannot do, so you do it first

The discounts row is the one to notice. A page that shows 3 for $48 while the cart charges $57 is a page the AI built and you did not finish. Shopify's discount types are amount off, Buy X get Y and free shipping, and the ones that apply automatically do so when the cart meets their requirements; the section only displays what the discount will do.

The eight steps

1. Set the store up in Shopify. Products with real photos, variants, prices, weights, shipping rates, taxes, a payment provider. None of this is theme work and no AI shortens it.
2. Decide the arithmetic. Which tier do you want most buyers on, at what price, and where does free shipping unlock. The threshold is your shipping cost divided by your gross margin rate, added to your median order — worked through in free shipping threshold bar. Create those discounts now.
3. Pull a theme to disk. shopify theme pull --store your-store.myshopify.com. Start from a stock theme, not a blank folder: layout, cart, collection and search pages are solved problems.
4. Give your AI the documentation. Shopify's Dev MCP, locally, so the agent writes Liquid and schema fields that exist: claude mcp add --transport stdio shopify-dev-mcp -- npx -y @shopify/dev-mcp@latest. Cursor, VS Code and Codex CLI are documented too.
5. Give your AI the selling sections. Either name each one with its rule, or connect a sections MCP so it requests them: claude mcp add --transport http uxgen https://www.uxgen.ai/mcp hands it 172 store sections as HTML to port into Liquid. Then build one page at a time — product page first, in the order set out in the section order of a high-converting product page.
6. Preview on a phone. shopify theme dev gives a URL; open it on a real phone at 390 px, not a narrowed desktop window. The sticky add-to-cart bar, the tier cards and the cart drawer all break there first.
7. Push unpublished, then publish from the admin. shopify theme push --unpublished. Click through to checkout with a test order before the publish button.
8. Audit the live page. Paste the URL at /audit. It scores the page out of 100, pins each missing mechanic where it belongs and returns the prompt to give your AI for the next pass.

The sections to ask for, by name

An AI asked for a product page writes a hero, a description and a button. Ask instead for these, one file each, with the rule attached:

• Quantity tiers with the unit price under each pack price, the middle tier preselected, the cart total on the button.
• The bundle that points at one choice, not a builder with twelve options.
• The free-shipping bar in the cart, showing the remaining amount in currency, hidden in an empty cart.
• The cart add-on, one item, unticked, priced, below the lines.
• The guarantee, as a sentence with a number of days, next to the add button.
• The comparison, your product against the alternative the buyer already has.
• The FAQ, five questions the buyer actually asks, one paragraph each.
• The sticky add-to-cart on mobile, carrying the price and the button.

Each of these is a section file with a {% schema %} and a presets entry, so the merchant can move or remove it in the theme editor without code. A section without a preset is invisible there.

What to leave out

No countdown that resets on reload, no only 3 left the inventory does not back, no review stars before there are reviews, no compare-at price nobody paid. Each of those is a fabricated claim under EU consumer rules and each one is something an AI will write if asked for urgency. uxgen refuses them at the source, and the list of refusals is public at /docs#refuses.

FAQ

How do I build a Shopify store with AI?

Set the store up in Shopify (products, prices, shipping, discounts), pull a stock theme to disk with shopify theme pull, open the folder in your AI (Claude Code, Cursor, Codex), give it the Shopify Dev MCP for documentation and a sections MCP or a named list for the selling sections, build one page at a time, preview with shopify theme dev on a phone, push with shopify theme push --unpublished, publish from the admin, then audit the live page.

Which AI is best for building a Shopify store?

Any agent that edits files on disk works on a theme: Claude Code, Cursor, Codex CLI. The difference is not the model but what it is handed. With the Dev MCP it writes Liquid that exists; with the selling sections named or served, it writes a page that sells rather than a page that displays.

Can I build a Shopify store with AI for free?

The AI part can be free or cheap; the Shopify plan is not, and neither are your products. The free part that matters is the audit: uxgen.ai/audit reads any public Shopify product page and returns a score, the missing mechanics and the prompt, with no account.

Do I need an app for bundles and free shipping bars on a store an AI built?

No. Both are a section file the AI writes plus a native Shopify discount you create in the admin. The section shows the tiers or the remaining amount; the discount makes the cart total match. The step list is in Shopify bundles and quantity breaks without an app.