The problem
Shoppers arrive with a question about fit, shipping, or stock, and the store cannot answer it until a person reads the inbox the next morning. By then the order went to whoever answered first.
What goes wrong
- The store goes headless for the wrong reason. A custom front end on top of Shopify costs weeks and buys nothing when the catalog is small and a theme would have done the job.
- The checkout, the signup form, or the order email breaks in a deploy and the build log says nothing. The missing orders stay invisible until someone asks why the week was quiet.
- The chat widget can talk but cannot see the catalog or the policies. It answers in generalities, and the shopper leaves anyway.
The approach
- Start on Shopify with a theme unless there is a specific reason to go headless: a content-heavy site, a catalog with complex configuration, or a front end you need to own.
- Treat the catalog as the content. Product pages, variants, and policies are written once, structured for search and AI assistants, and the AI reads from the same source.
- Connect payments, inventory, shipping, and email, then place real test orders on every shipping class and every payment method before launch.
- Put the AI in the funnel, not beside it. It reads the same catalog and policies as the product pages, runs in shadow on the preview while your team corrects it, and goes live only after you sign off.
When it works
When the catalog is real, the policies are written down, and someone on your side owns the inbox the AI hands off to. A store with ten products and no written shipping rules needs a theme, not a headless build.
Shopify first, headless when it earns it
Most stores belong on Shopify with a theme. Checkout, payments, taxes, and the app ecosystem are solved, and a good theme with real content beats a late custom front end.
Headless earns its keep in three cases. The site is content-heavy, with guides and editorial pages the catalog has to live inside. The products are configured, not picked: sizes, materials, bundles, and rules a theme cannot express. Or you need to own the front end outright, with your own design system and performance budget. In all three, Shopify still runs the money. The custom part is what the shopper sees.
What the funnel needs
The catalog is the content
Product pages are where search engines and AI assistants read your store. Titles, variants, care, shipping, and returns, written once in your voice so a machine can quote them. The same text feeds the AI, so there is no second copy to drift.
Shipping rules checked against real orders
Shipping is where margin leaks. Free shipping set on a threshold that no longer matches the cart. A heavy item that ships at a loss because it sits in the same class as a t-shirt. If the store already sells, we check the rules against real orders before launch, sort every product into a shipping class by size and handling, and set the rules so the shopper sees the right number and you keep the margin. If it is new, we start from your carrier rates.
The AI in the funnel
An AI that only chats is a widget. One that works reads the catalog and the policies, answers the sizing and shipping questions that stall a purchase, recommends from the catalog, and hands a ready buyer to checkout. When a question needs a person, like a damaged order or a wholesale request, it hands off with the transcript so your team does not ask the shopper to start over.
How we build it
First we agree the pages, the catalog shape, and the voice, and decide theme or headless on the three cases above. Forms, analytics, and order notifications are wired from the first commit.
Next the pages and product content go up on a private preview you review.
Then the catalog, payments, inventory, and shipping are connected and tested with real orders on every shipping class. The AI reads the catalog and policies and runs in shadow on the preview while your team corrects it.
Last, DNS moves on your written approval. Then we place a real order and submit every form on the live domain, and confirm each one reaches your inbox. The first monthly report shows what is being found and what is selling.
When it does not work
It does not work as a way to skip writing product content. The AI can only answer what the store knows, and a thin product page gives it nothing to say. It also does not work without an owner: someone on your team has to read the handoffs and turn the questions it could not answer into page edits.
Where to start
If the store is the first thing to fix, start with the Storefront. If you make or distribute what you sell, manufacturing and distribution covers the orders and invoices behind the store. If you are not sure, ask Roo, Webaroo's AI: Is a Shopify theme enough for our store, or do we need headless?
Book 15 minutes with Connor