Replace Shopify With Claude? How to Build a Store on Tagada, Step by Step
Claude writes the storefront, Tagada runs checkout and payments. The steps from Tagada's docs, what the AI can't do, API key safety, and costs.
Article summary
TL;DR
Claude can't run a store on its own: it writes code. In Tagada's setup, Claude generates the storefront (pages, cart, checkout form) and Tagada's Headless SDK connects it to Tagada's checkout, payment routing, upsells and subscriptions. Shopify isn't involved. You still need a payment processor, a host, and someone who checks the code before customers see it.
- Tagada's home page links this guide as "Replace Shopify with Claude". In practice, Claude writes the storefront code and Tagada is the backend for checkout and payments.
- Tagada's docs give the path: get an API key, create a store and a product, prompt Claude with the Headless SDK hooks, test with a sandbox card, then deploy.
- Claude can also connect to a Tagada account through MCP. The Config MCP diagnoses a store and can edit a funnel; the Studio MCP edits Studio pages and never deploys.
- The API key from Tagada's onboarding has org:admin scope. It belongs in your .env and setup scripts, never in browser code or a chat window.
- If you sell a few products and want a hosted admin, Shopify may still fit better. Tagada also runs alongside Shopify instead of replacing it.
On this page
Tagada's home page has a section called "Build your store with Claude, Lovable, or code", and its link to this guide reads "Replace Shopify with Claude".1Tagada, home page (Build your store with Claude, Lovable, or code), read October 14, 2026 This page explains what that means in practice: Claude writes the storefront, Tagada runs the checkout and the payments behind it. Every step comes from Tagada's public documentation, and every statement about Claude, MCP or Shopify comes from Anthropic's or Shopify's own pages. By industry: Shopify checkout for supplement brands, Shopify checkout for skincare brands, Shopify checkout for online pharmacies, Shopify checkout for telehealth companies, Shopify checkout for fitness brands and Shopify checkout for info product businesses, Shopify payments for supplement brands, Shopify payments for skincare brands, Shopify payments for online pharmacies, Shopify payments for telehealth companies, Shopify payments for fitness brands and Shopify payments for info product businesses.
What "replace Shopify with Claude" actually means
Claude is an AI model. It can write a storefront, but it can't take a payment, store an order or host a site. A store needs a backend for those jobs. In Tagada's setup, Claude writes the user interface and Tagada is that backend. Tagada's docs put it this way: "You bring an AI coding tool (Claude, Lovable, v0). It writes your storefront UI. TagadaPay is the headless backend."2Tagada Docs, Build a Store with AI + TagadaPay
Fig. 1Who does what
approved declined or closed routing step
- ClaudeWrites the pages, cart and checkout form
- generatesYour storefrontReact, Next.js, Astro or plain HTML, on your host
- callsHeadless SDKCheckout session, card tokenization, 3DS, offers
- runs onTagadaRouting to your processor, upsells, subscriptions
Claude writes the code, Tagada runs the money
The headless part matters. The storefront and the backend are separate, so you own the front-end code and can host it where you like. Shopify offers the same split for its own platform: "Headless commerce separates your storefront's frontend from its backend," with Hydrogen as its toolkit and the Storefront API handing customers off to checkout.16Shopify Dev Docs, Headless storefronts So "without Shopify" is a choice of backend, not the only way to get a custom storefront. Our guide to headless commerce solutions compares the options.
| Job | In a Shopify store | In a Claude + Tagada store |
|---|---|---|
| Storefront | Shopify theme, or a headless Hydrogen storefront16Shopify Dev Docs, Headless storefronts | Code Claude generates, on your own host2Tagada Docs, Build a Store with AI + TagadaPay |
| Catalog | Shopify admin | Products created in the Tagada dashboard or with the Node SDK2Tagada Docs, Build a Store with AI + TagadaPay |
| Checkout | Shopify checkout | Tagada checkout session, called from your pages4Tagada Docs, Headless SDK |
| Payments | Shopify Payments, or a third-party provider with third-party transaction fees15Shopify Help Center, Third-party payment providers | Routing across TagadaPay, Stripe, NMI and Airwallex, cascade when a processor is down or times out9TagadaPay, home page, read October 14, 2026 |
| Upsells, order bumps, subscriptions | Check your Shopify plan and the apps you would add | One-click upsells, order bumps, subscription billing and dunning listed as included8Tagada, Pricing (Everything included), read October 14, 2026 |
| Hosting | Hosted by Shopify; Oxygen for Hydrogen16Shopify Dev Docs, Headless storefronts | Tagada's CDN, Vercel, Netlify or Cloudflare Pages2Tagada Docs, Build a Store with AI + TagadaPay |
What you need before you start
Tagada's tutorial lists three prerequisites: Node.js 18 or later, an AI coding tool, and a Tagada account with an API key. The docs add that no credit card is needed for the account.2Tagada Docs, Build a Store with AI + TagadaPay
You also need to know which of Tagada's names does what. The docs split them clearly:2Tagada Docs, Build a Store with AI + TagadaPay
- Tagada (app.tagada.io) is the CRM: your account, stores, products, API keys and the payment orchestrator.
- TagadaPay is a payment processor you can plug into that account, next to Stripe, Checkout.com or NMI. Becoming a TagadaPay merchant requires a separate business review (KYB), applied for at hub.tagada.io.
- You can "ship a fully-working store with just Tagada (CRM) + your own Stripe." TagadaPay is optional.
Which Claude to use
| Option | What it does | Fits |
|---|---|---|
| Claude chat (claude.ai, desktop, mobile) | Writes code you copy into your project files | First test, small changes |
| Claude Code | "Reads your codebase, edits files, runs commands", in the terminal, an IDE, the desktop app or the browser12Claude Code Docs, Overview | Building and maintaining the store |
| Claude API | Calls Claude from your own software | Agencies generating many stores |
Claude Code is the closest match to this tutorial, because it can run the npm commands and edit the files itself. Anthropic's docs say most Claude Code surfaces require a Claude subscription or an Anthropic Console account.12Claude Code Docs, Overview Plans are on Anthropic's pricing page.
How to build the store, step by step
This is the order of Tagada's Build a Store with AI guide.2Tagada Docs, Build a Store with AI + TagadaPay
- Get an API key. Run
tagada-initwith your email, or create a key in the dashboard under Settings, then Access Tokens. - Create the store. Either clone Tagada's example storefront, which comes with a seeded demo store, or run a setup script that creates a processor, a payment flow, a store and a product.
- Prompt Claude. Paste Tagada's prompt with your store ID. Claude generates the product list, cart, checkout, payment and thank-you pages.
- Test. Pay with the test card
4242 4242 4242 4242in sandbox mode, any future expiry, any CVC. - Connect a real processor. Add your Stripe keys, or TagadaPay once approved, to the payment flow.
- Deploy. On Tagada's CDN for a single-page app, or on Vercel, Netlify or Cloudflare Pages for server-rendered frameworks.
Steps from Tagada's docs. The sandbox account and test card let you try the whole flow without a real processor.
Step 1: get an API key from the terminal
The fastest path in the docs is three commands. tagada-init emails you a 6-digit code, creates a sandbox account, seeds a demo store (a sandbox processor, a payment flow, two demo products, a checkout upsell and a shipping rate) and writes TAGADA_API_KEY, TAGADA_STORE_ID and TAGADA_ACCOUNT_ID to a .env file.3Tagada Docs, Get an API key from code
git clone https://github.com/TagadaPay/examples.git cd examples/headless-react-store npx -p @tagadapay/node-sdk@latest tagada-init you@example.com pnpm install pnpm dev
Two details from the docs worth knowing. Each successful run creates a fresh sandbox account, even with an email that already has one, so keep track of the keys you generate. And Tagada built this flow because AI coding tools "can't click through a signup form", so Claude Code can run it for you; you only paste the code from your inbox.3Tagada Docs, Get an API key from code
Step 2: create the store yourself (optional)
If you start from an empty folder instead of the example, the docs give a setup script. It creates a processor, a payment flow that routes to it, a store and a product. Here is the shape of it, with the key read from .env:2Tagada Docs, Build a Store with AI + TagadaPay
import Tagada from '@tagadapay/node-sdk';
const tagada = new Tagada(process.env.TAGADA_API_KEY!);
// 1. Processor: Stripe test keys, or type 'sandbox' for testing const { processor } = await tagada.processors.create({ processor: { /* ... */ } });
// 2. Payment flow: routes transactions through that processor const flow = await tagada.paymentFlows.create({ data: { /* ... */ } });
// 3. Store, using that flow const store = await tagada.stores.create({ name: 'My AI-Built Store', baseCurrency: 'USD', presentmentCurrencies: ['USD', 'EUR'], chargeCurrencies: ['USD'], selectedPaymentFlowId: flow.id, });
// 4. Product with a price per currency await tagada.products.create({ storeId: store.id, /* name, variants, prices */ });
console.log(Store ready: ${store.id});
Run it with npx tsx setup.ts and copy the store ID it prints. The full field list is in Tagada's guide. A payment flow's strategy can be simple (one processor) or cascade (try the next one on failure).2Tagada Docs, Build a Store with AI + TagadaPay The logic of cascades is explained in our guide to dynamic payment routing.
A headless store doesn't need a Tagada funnel. The docs explain that funnels drive Tagada's no-code Studio pages; in a headless setup "your React/Next/Astro app owns the routing."2Tagada Docs, Build a Store with AI + TagadaPay
Step 3: prompt Claude
Tagada's docs give a prompt to paste into Claude. Here it is, with the store ID left as a placeholder:2Tagada Docs, Build a Store with AI + TagadaPay
Build me a modern e-commerce store using React + Tailwind CSS.
The store uses @tagadapay/headless-sdk for ALL backend operations (catalog, checkout, payment, upsells) — no custom API needed.
Architecture:
- Wrap the app in <TagadaHeadlessProvider storeId="STORE_ID" environment="production">
- Use these hooks from '@tagadapay/headless-sdk/react': • useCatalog() — load products • useCheckout(checkoutToken, sessionToken) — manage checkout session • usePayment() — tokenize cards and process payments • useOffers() — load and accept upsell offers • useGoogleAutocomplete({ apiKey }) — address autocomplete
Pages to build:
- Product listing — grid of products from useCatalog()
- Cart — line items, quantities, totals
- Checkout — email, name, address (Google autocomplete), shipping, promo
- Payment — card form (number, expiry, cvc), tokenize then pay
- Thank-you — order summary from useOrder() (main order + relatedOrders) + one-click upsell via useOffers()
Style: dark theme, clean, minimal, mobile-first. Use shadcn/ui-like patterns. Store ID: STORE_ID_FROM_STEP_1
Notice what the prompt gives Claude: the store ID, not the API key. In the docs' examples, the browser code only receives the store ID, and the API key stays in the Node scripts.2Tagada Docs, Build a Store with AI + TagadaPay If Claude gets an SDK call wrong, the guide lists the exact calls to paste back into the conversation.
What the SDK does behind the pages
| Hook or module | What it does, per Tagada's docs |
|---|---|
useCatalog | Loads products, variants and prices from your Tagada store |
useCheckout | Customer, address, shipping rates and promo codes on a checkout session |
usePayment | Tokenizes the card and processes the payment; 3D Secure handled automatically |
useOffers | Previews and charges a post-purchase offer on the same card |
customer, portal | Profiles, orders and subscriptions; your own customer account area |
Sources: Tagada Docs, Headless SDK and Build a Store with AI.4Tagada Docs, Headless SDK2Tagada Docs, Build a Store with AI + TagadaPay
The payment step is where the one-click upsell depends on the backend: the offer charges the card used at checkout, without a new card entry. 3D Secure is covered in our guide to payment authentication.
Step 4: test, then connect a real processor
Pay with 4242 4242 4242 4242 on a sandbox processor or in Stripe test mode.2Tagada Docs, Build a Store with AI + TagadaPay Test the whole path: a declined card, an accepted upsell, a refused upsell, a promo code, a shipping address in each country you sell to. Then swap the sandbox for your live processor in the payment flow.
Things the tutorial doesn't cover
Tagada's guide covers catalog, checkout, payment, upsells, hosting, pixels and webhooks. It doesn't cover sales tax or VAT, your terms, privacy and refund pages, or cookie consent for the pixels. Check these with your accountant and Tagada before you open to real customers.
Step 5: deploy
The docs call the storefront "just static files" and give three hosting options:2Tagada Docs, Build a Store with AI + TagadaPay
| Your app | Host suggested by Tagada's docs | How |
|---|---|---|
| Single-page app (React, Vue, Svelte, plain HTML) | Tagada's edge CDN | tagada.plugins.deployDirectory() in a small Node script |
| Server-rendered (Next.js, Astro, Remix, SvelteKit) | Vercel, Netlify or Cloudflare Pages | vercel --prod, netlify deploy --prod, wrangler pages deploy |
| App with its own backend (webhooks, database, jobs) | Fly.io, Railway or Docker | fly launch && fly deploy |
On Tagada's CDN, the docs list a custom domain with automatic TLS and built-in A/B testing, weighted or geo-based, on the same URL. Running the deploy script again puts the new version live.2Tagada Docs, Build a Store with AI + TagadaPay
Inside Tagada
One backend for checkout, routing and subscriptions
Your Claude-built storefront calls Tagada's checkout. Behind it, payments route across TagadaPay and processors such as Stripe, NMI and Airwallex, with a cascade to another processor when one is down or times out, and subscriptions keep charging when you move between processors.

Connecting Claude to your Tagada account with MCP
Writing the storefront is one use of Claude. The other is letting it look at your Tagada account. That runs through MCP, which its maintainers define as "an open-source standard for connecting AI applications to external systems."11Model Context Protocol, What is MCP? Tagada documents two MCP servers, and they do very different things.
| Config MCP | Studio MCP | |
|---|---|---|
| What it's for | Inspect how your stores are configured and find why a store isn't taking payments5Tagada Docs, Config MCP: Get Started | Edit Studio page templates live in the open editor7Tagada Docs, Studio MCP Server |
| Where it runs | Hosted at https://api.tagada.io/api/mcp, nothing to install5Tagada Docs, Config MCP: Get Started | Local package @tagadapay/studio-mcp, WebSocket to your browser7Tagada Docs, Studio MCP Server |
| Sign-in | NoAPI key; you sign in, and it sees what your CRM role sees5Tagada Docs, Config MCP: Get Started | NoAPI key or store ID7Tagada Docs, Studio MCP Server |
| What it can change | Eight of nine tools only read; canvas_apply edits a funnel6Tagada Docs, Config MCP: Tools Reference | Page content only; it never deploys and can't edit funnel routing7Tagada Docs, Studio MCP Server |
How to connect Claude
For the Config MCP, Tagada's docs give one command for Claude Code:5Tagada Docs, Config MCP: Get Started
claude mcp add --transport http tagada https://api.tagada.io/api/mcp
Then run /mcp, pick tagada and sign in. Anthropic's docs describe the same flow: /mcp handles OAuth sign-in for remote servers, and "Clear authentication" in that menu revokes access.13Claude Code Docs, Connect Claude Code to tools via MCP In the Claude apps, you add the same URL as a custom connector. Anthropic's help center says custom connectors are available on Free, Pro, Max, Team and Enterprise plans, with Free users limited to one, and that on Team plans only Owners and Primary Owners can add them.14Claude Help Center, Getting started with custom connectors using remote MCP
The Studio MCP runs on your machine instead. Its setup and what an agent can do in the editor are in our page on TagadaStudio.
What Claude can and can't do once connected
What Claude can do
- List the stores you can reach, across your organizations
- Check catalog, shipping, payment flow and checkout, with the evidence for each error
- Find the case where the setup checklist is green but no processor can take a charge
- Read a funnel and, with
canvas_apply, add, remove or connect its steps - Edit Studio pages live while you watch (Studio MCP)
What it can't do
- See orders, customers or payments: the Config MCP is limited to configuration
- Read processor credentials, which "cannot reach the assistant even in an error path"
- Go beyond what your Tagada role allows
- Deploy a Studio page: you save it yourself
- Check processor monthly caps or shipping brackets, which the docs say aren't evaluated
Sources: Tagada Docs, Config MCP and Studio MCP.5Tagada Docs, Config MCP: Get Started6Tagada Docs, Config MCP: Tools Reference7Tagada Docs, Studio MCP Server
One warning from Tagada's own tools reference deserves a bold line: canvas_apply "edits a live funnel. It publishes on its own once the funnel compiles, so a command an agent sends is a change a customer can hit. Show the merchant what you are about to send."6Tagada Docs, Config MCP: Tools Reference Approve each of those calls yourself.
A good first use is the pre-launch check from Tagada's prompt library: ask Claude to run every diagnosis on the store and answer GO or NO-GO, with blockers, risks and what it couldn't verify. The docs note that "a store can pass the checklist at 5/5 and still be unable to take an order."6Tagada Docs, Config MCP: Tools Reference
Security: API keys, permissions and card data
Handing an AI the keys to a store is the step to slow down on. Here is what the sources say, and what to do about it.
- An API key from tagada-initTagada's docs say it has org:admin scope: stores, processors, payments, customers, webhooksKeep it in .env and in setup scripts. Never in browser code, a public repo or a chat message
- A storefront that only gets the store IDThat is how Tagada's examples are builtAsk Claude to keep it that way, and search the built files for the key before you deploy
- A card form Claude generatedCards are tokenized by core-js before your code sees themUse the SDK's tokenization; never let Claude write card numbers to logs or storage
- A prompt to connect a custom connectorAnthropic says custom connectors reach services it has not verifiedConnect only servers you trust and review the permissions requested
- A tool call that writes, such as canvas_applyIt changes a live funnelRead the command before you approve it; avoid always-allow on write tools
- A connector you no longer useIts access stays open until revokedDisconnect it, or use Clear authentication in /mcp
Sources: Tagada Docs (Get an API key, Build a Store with AI); Claude Help Center, custom connectors; Claude Code Docs, MCP.3Tagada Docs, Get an API key from code2Tagada Docs, Build a Store with AI + TagadaPay14Claude Help Center, Getting started with custom connectors using remote MCP13Claude Code Docs, Connect Claude Code to tools via MCP
A few more points from the sources:
- Prompt injection. Anthropic warns that "malicious MCP servers may include hidden instructions that try to make Claude perform unintended actions," and Claude Code's docs say servers that fetch external content add that risk.14Claude Help Center, Getting started with custom connectors using remote MCP13Claude Code Docs, Connect Claude Code to tools via MCP
- Card data. Tagada's docs say "your store never sees or stores raw card data."2Tagada Docs, Build a Store with AI + TagadaPay That covers the card form when it uses the SDK. It doesn't make the rest of the code safe: read our page on PCI compliance for what stays your job.
- Roles. The Config MCP sees "exactly what your CRM role lets you see" and can only change what your role allows.5Tagada Docs, Config MCP: Get Started Give the person who connects Claude the narrowest role that does the job.
What it costs
There are no prices on this page, because each of them changes and none is ours to quote for another company. These are the bills to compare with your Shopify invoice:
| Cost | Where to check |
|---|---|
| Tagada platform | Tagada pricing |
| Payment processing | Your processor's pricing page, or TagadaPay's |
| Claude | Anthropic's pricing page: Claude plans, and API prices if you use the API |
| Hosting | Tagada's CDN, or the plans of Vercel, Netlify or Cloudflare |
| Your time | Reviewing code, testing, fixing what breaks |
On the Shopify side, check Shopify's pricing page and your apps. If you use a payment provider other than Shopify Payments, Shopify's help center says "third-party transaction fees apply to all transactions processed through third-party and alternate payment gateways."15Shopify Help Center, Third-party payment providers
When Shopify is still the better choice
A store Claude builds is a codebase you maintain. That suits some brands and not others.
| Your situation | Better fit |
|---|---|
| A few products, no developer, you want a hosted admin and a theme | A hosted platform such as Shopify |
| You like your Shopify storefront but want multi-processor routing or subscriptions in the checkout | Keep Shopify and add Tagada; it runs standalone, with Shopify, WooCommerce or headless10Tagada, Tagada vs Funnelish |
| You want full control of the storefront code and someone to review it | Claude + Tagada Headless SDK |
| You want drag-and-drop funnel pages, not code | TagadaStudio pages on a Tagada funnel |
| You sell subscriptions or upsells and route across several processors | Tagada as the backend, with either storefront |
How to read this table
"Replace Shopify" is a choice about who owns the storefront code and who runs the checkout. Claude makes the code cheap to write, not free to maintain. If nobody on the team will read what Claude changed, a hosted storefront is the safer start.
For a wider view of what AI does in ecommerce today, read our guide to AI ecommerce tools. For the payment layer behind any of these setups, see payment orchestration.
Where Tagada fits
How Tagada helps
Claude writes the storefront, Tagada runs what's behind it
Tagada's home page presents it as the headless backend for stores built with Claude, Lovable or code, through the Headless SDK. Payments route across TagadaPay and processors such as Stripe, NMI and Airwallex, with one logic and a cascade to another processor when one is down or times out, with native 3DS2. The checkout includes one-click upsells, order bumps, A/B tests, and Apple Pay and Google Pay; subscriptions come with dunning; purchases are tracked server-side for Meta, Google and TikTok. Tagada runs standalone or with Shopify, WooCommerce or a headless store. Plans are on the pricing page.

Frequently asked questions
Can I really replace Shopify with Claude?
Do I need to know how to code?
Is it safe to take card payments on a store Claude wrote?
Can Claude change my live store on its own?
Can I keep Shopify and still use Tagada?
How much does it cost to build a store with Claude and Tagada?
Sources
Checked October 14, 2026- Tagada, home page (Build your store with Claude, Lovable, or code), read October 14, 2026
- Tagada Docs, Build a Store with AI + TagadaPay
- Tagada Docs, Get an API key from code
- Tagada Docs, Headless SDK
- Tagada Docs, Config MCP: Get Started
- Tagada Docs, Config MCP: Tools Reference
- Tagada Docs, Studio MCP Server
- Tagada, Pricing (Everything included), read October 14, 2026
- TagadaPay, home page, read October 14, 2026
- Tagada, Tagada vs Funnelish
- Model Context Protocol, What is MCP?
- Claude Code Docs, Overview
- Claude Code Docs, Connect Claude Code to tools via MCP
- Claude Help Center, Getting started with custom connectors using remote MCP
- Shopify Help Center, Third-party payment providers
- Shopify Dev Docs, Headless storefronts
Tagada
Let Claude write the storefront, keep checkout and routing on Tagada
Funnels, one-click upsells, subscription billing and payment routing, on one customer record.
- 01Create your free account
- 02Connect your store or build a checkout
- 03Launch funnels, upsells and subscriptions
