Back To Online Store 2.0, Should You?
In 2015, all we talked about was going headless. Fast forward to 2023, all we talk about is going back to Online Store 2.0.
Going back to OS is a logical choice for many use cases. However, you don’t simply go back from Headless to OS. Just like you don’t simply find a solution first, and then a problem later.
Don’t get me wrong, hashtag#backtoOS has its merits.
Headless used to be hard and expensive. In the past, it came with a huge tradeoff: You have a performant, flexible, content-rich storefront, but you also have to bear a hefty server expense. For instance, deploying on Next Commerce meant using Vercel, and the costs escalated rapidly as you scale. Additionally, the monthly charges for headless CMSs like Sanity or Contentful were not budget-friendly, at all.
Going back to OS made even more sense when Shopify rolled out a horde of powerful features like Section Everywhere, Native Metafields definition, and metaobjects.
Making a content-rich Shopify store is suddenly easier. You don’t need to go headless unless you have really niche requirements, or you prioritize speed like no one else. You also save a fortune on server hosting and maintenance because Shopify Oxygen does this for free. Section Everywhere can do what most headless CMS can do when combined with metaobjects and meta fields. So you save another fortune. More importantly, merchants now have theme customize to manage content.
There seems to be no reason not to go back to OS 2.0.
But it’s not that easy. Staying on OS is easy. Staying on OS is likely a good choice, but that doesn’t mean going back from headless is also a good choice. The migration process is especially burdensome for Plus merchants with a huge amount of content. Converting from React to Liquid also equals clipping the Product team’s wings: They are used to balance creativity with optimal performance, and now they have to choose one. Going back from headless to OS meant a momentous shift in workflow, architecture, and team collaboration. It takes time, effort and resources. It’s never the no-brainer as the trend portrays.
If you want to move back to OS, but without bearing the cost, what do you do?
Shameless plug here: This is a problem I thought about a lot before building Weaverse, and now I really believe merchants can ripe the benefits from both worlds, by using Weaverse with Shopify Hydrogen and Oxygen.
-
With Weaverse, you have a theme customizer that works just like OS 2.0. Same effort, but with superior output, you have a Hydrogen storefront that’s lightning-fast and versatile.
-
You can also define Section Schema just like Liquid, making Weaverse friendly to developers who eat and sleep Liquid.
-
Migration from React to React is more straightforward and cost-effective than from React to Liquid. - Deployment to Oxygen is free. Plus, when you use Weaverse, you no longer have to bear the financial burden of server expenses and headless CMS tools.
Of course, even this solution is not a silver bullet. Every solution means you give up some to gain some, but sometimes it might be best to opt for the one with the least amount of trade-off. :)
Reactions
Join the Discussion
Continue Reading
More insights from the Weaverse team
Shopify’s CEO Used a Coding Agent to Make Liquid 53% Faster — What That Means for Shopify Teams
Shopify’s CEO Used a Coding Agent to Make Liquid 53% Faster — What That Means for Shopify Teams When Shopify CEO Tobi Lütke shared that work on Liquid had delivered 53% faster parse + render and 61% fewer allocations, the obvious takeaway was simple: Liquid just got faster. That matters. But the bigger signal is more important: AI coding agents are now producing meaningful improvements inside mature commerce infrastructure. This was not a toy demo or a greenfield side project. It was a serious optimization effort on one of Shopify’s most battle-tested open-source systems — with public benchmarks, a real pull request, and dozens of iterative experiments behind it. For Shopify teams, that is the real story. The takeaway is not just that Liquid got faster. It is that the workflow behind the gain — benchmarks, tests, and agent-driven experimentation — is becoming a practical advantage for teams building across the Shopify stack. Shopify CEO Tobi Lütke publicly shared the Liquid performance work via X, while the linked pull request documents the result: 53% faster parse + render and 61% fewer allocations. The more interesting takeaway is not the headline number alone — it is that AI-assisted optimization is now working on production-grade commerce infrastructure. Source: Tobi Lütke on X and Shopify’s public Liquid PR #2056. The actual news The public Liquid pull request shows a serious optimization effort: 93 commits around 120 autonomous experiments 53% faster parse + render 61% fewer allocations This was not magic. It was a disciplined workflow: define the benchmark give the agent a measurable target let it test many ideas quickly keep the safety net tight with tests That combination matters. The AI did not replace engineering judgment. It accelerated the search space. And that is exactly why this is a bigger story than “Liquid got faster.” Why this matters beyond Liquid Liquid is one of the most mature codebases in the Shopify world. It has been touched by hundreds of contributors, hardened over years, and optimized in ways most teams never reach. So when a coding agent still manages to find meaningful gains there, it tells us something important: AI-assisted optimization is no longer theoretical. It works best when three things already exist: a strong test suite a clear benchmark a codebase worth improving That applies far beyond Liquid. It applies to: Shopify themes Hydrogen storefronts internal apps data transformation pipelines storefront rendering bottlenecks ecommerce developer tooling In other words, this is not just a Ruby templating story. It is a workflow story. The real unlock is not “AI writes code.” It is faster experimentation against benchmarks and tests. Liquid is not dead. Shopify is still investing in it There is a lazy narrative in headless commerce that goes something like this: Liquid is legacy. Hydrogen is the future. Reality is more useful than that. Shopify is still clearly investing in Liquid because Liquid still powers a massive share of real storefronts. Faster Liquid benefits merchants immediately. It improves the baseline for Online Store 2.0 teams. And it reminds everyone that themes are still the default for a reason: simpler operations lower implementation cost fewer moving parts stronger guardrails That matters. For many brands, the right answer in 2026 is still not “go headless.”It is “make the current storefront better.” This update strengthens that case. What Hydrogen teams should learn from this If you work on Hydrogen, the lesson is not “Liquid won.” The lesson is: the cost of optimization is changing. Hydrogen still gives teams things Liquid cannot easily match: more custom UX control richer interactive storefront patterns deeper architectural flexibility better fit for complex multi-surface commerce experiences stronger alignment with custom React workflows That has not changed. But this story does highlight a new reality: Teams that know how to combine benchmarks + tests + agents will improve faster than teams that do not. That matters just as much in Hydrogen as it does in Liquid. Because the bottleneck for many headless teams is not just framework choice.It is iteration speed. How fast can you: identify a real bottleneck test a hypothesis run experiments safely keep code quality high ship improvements without blowing up the roadmap AI agents are getting very good at exactly that layer of work. The real takeaway: Liquid vs Hydrogen is still the wrong fight A lot of Shopify discourse still wants a clean winner. Liquid or Hydrogen.Themes or headless.Simple or modern. That framing misses the point. The more useful mental model is: Liquid gives you guardrails Hydrogen gives you leverage AI lowers the cost of improving both That is the shift. For a standard storefront with a small team, Liquid remains the safer default.For teams that need custom experiences, deeper control, or more ambitious frontend capability, Hydrogen can still be the right move. But now there is a new force compressing the gap: AI-assisted development is making optimization cheaper on both sides. That does not erase tradeoffs.It just changes the economics of improvement. The story is bigger than Liquid vs Hydrogen. AI is lowering the cost of improving both. What Shopify teams should do now Instead of treating this story as a Liquid-vs-Hydrogen argument, use it as a prompt to improve your own workflow. If you are on Liquid Do this first: audit app bloat review script load trim media weight benchmark core templates identify repeated render bottlenecks Then ask: what can be measured clearly? what can be tested safely? where can agents help us search for improvements faster? You may not get a 53% gain. But you may find meaningful wins that were too tedious to chase manually. If you are on Hydrogen Do not dismiss this as irrelevant because it happened in Liquid. Instead ask: where are our real rendering bottlenecks? what parts of the storefront are slow but measurable? what repetitive optimization work keeps getting deprioritized? do we have the tests and benchmarks needed to let agents help? The teams that benefit most from coding agents will not just be the teams with the newest stack. They will be the teams with the clearest feedback loops. Why this matters for modern Shopify teams At Weaverse, we care about Hydrogen because merchants need more than raw frontend flexibility. They need a way to move faster without turning every storefront change into a developer bottleneck. That is why this moment matters. The future is not just “AI writes code.” The future is: better workflows tighter feedback loops safer experimentation faster implementation lower cost of iteration across the storefront stack That applies whether you are optimizing Liquid or building on Hydrogen. And it is exactly why the best Shopify teams in 2026 will not just choose the right stack. They will choose the right development system. Final thought Tobi’s Liquid optimization story is not just impressive because of the number. It is impressive because it shows what happens when AI is used the right way: clear goal measurable target strong tests lots of rapid experimentation That pattern is bigger than Liquid. It is a preview of how serious Shopify teams will build and optimize from here. The future is not Liquid versus Hydrogen. It is teams using AI to make both better. FAQ Does this mean Liquid is better than Hydrogen? No. It means Liquid is still improving, and that AI-assisted optimization can create real gains in mature systems. Hydrogen still makes sense for teams that need more control, flexibility, and custom UX. Does this prove AI can optimize production code safely? It shows AI can contribute meaningfully when the workflow is disciplined. The key ingredients are benchmarks, tests, and human review. Why does this matter for Shopify merchants? Because the economics of improvement are changing. Teams may be able to ship better performance and faster iterations without needing the same amount of manual optimization effort. What should merchants do right now? If you are on Liquid, improve the existing storefront before assuming headless is necessary. If you are on Hydrogen, invest in stronger benchmarks and test coverage so your team can use agents safely and effectively. What is the bigger strategic takeaway? The biggest shift is not one framework beating another. It is that AI is reducing the cost of experimentation across the Shopify stack. Sources Tobi Lütke on X Shopify/liquid PR #2056 Simon Willison: 53% faster parse+render, 61% fewer allocations
AI Coding Agents Just Raised $9B — Here’s What That Means for Headless Commerce Builders
AI Coding Agents Just Raised $9B — Here’s What That Means for Headless Commerce Builders Replit just raised $400 million at a $9 billion valuation. That’s not just a startup funding headline. It’s a market signal. AI coding agents have moved from novelty to infrastructure. They are no longer just autocomplete tools. They can now scaffold apps, debug code, ship features, and increasingly manage larger chunks of the software workflow with minimal human input. Latent Space framed it well: coding is becoming “approximately solved.” But for commerce builders, that does not mean the hard part is over. It means the bottleneck is moving. The new challenge is no longer just writing code faster. It’s turning AI-generated code into storefronts that actually perform, convert, and stay maintainable inside a fast-changing commerce ecosystem. That is where headless commerce builders need to pay attention. The $9B signal is bigger than Replit A $9B valuation on an AI coding platform tells you something important: software creation is becoming agent-driven. That changes expectations for everyone building digital products. Soon, more founders, marketers, merchants, and operators will expect to: describe a product in plain language generate an app or storefront scaffold instantly deploy quickly iterate with AI as the default workflow This is what people call vibe coding. And yes, it’s real. But in ecommerce, generated code is only the starting point. Because a storefront is not just an app.It is a revenue system. Why generic AI coding breaks down in commerce AI coding agents are getting better at: generating React apps wiring CRUD flows producing UI components deploying prototypes speeding up iteration loops What they still do poorly is understanding commerce-specific complexity. A generic agent can scaffold a storefront. It usually cannot reason deeply about: Shopify Storefront API patterns SSR and edge caching strategy product and variant architecture collection and merchandising logic section-based visual editing market-aware storefront behavior conversion-sensitive UX decisions long-term maintainability for merchant teams That gap matters. Because in headless commerce, speed alone is not the advantage.Useful speed is. Shipping the wrong architecture faster is still a loss. Shopify is making the stack more powerful — and more demanding At the same time AI coding agents are getting stronger, Shopify is pushing deeper into a full-stack commerce platform model. The platform is evolving across: APIs checkout discounts identity analytics fulfillment personalization AI-facing commerce infrastructure That means builders need to keep up with a stack that is not getting simpler. For headless teams, this raises the bar. You are not just building a frontend anymore.You are building on top of a moving commerce operating system. In practice, that means AI-generated code needs to work with: Shopify API changes Hydrogen conventions real merchant workflows structured data requirements performance expectations ecosystem constraints That is why generic code generation is not enough. The real shift: from code generation to domain execution This is the part most people miss. The future is not AI replacing builders.The future is AI compressing low-level implementation work so the real differentiator becomes domain judgment. For headless commerce, that means the winners will combine: AI speed Shopify-specific expertise production-ready architecture merchant usability conversion understanding That combination is much more valuable than raw code output. A merchant does not actually want “an app generated by AI.” They want: a storefront that launches faster a stack that is easier to manage pages that convert flexibility without chaos better collaboration between developers and operators That is a different problem. Why this matters for Hydrogen builders Hydrogen teams are in an interesting position. On one hand, AI coding agents make it easier than ever to scaffold headless storefronts, prototype layouts, and speed up frontend implementation. On the other hand, Hydrogen projects still require real decisions around: route structure server rendering data loading API boundaries component architecture storefront performance content operations merchant editing experience This is exactly where many AI-generated builds fall apart. They look fine in a demo.They become expensive in production. That is why the next phase of headless commerce is not about replacing builders with AI. It is about giving builders better leverage. Where Weaverse fits This is why Weaverse matters more in the age of AI coding agents, not less. If AI can generate storefront code faster, the last-mile problem becomes even more important: How do you turn generated storefronts into merchant-friendly, production-ready commerce systems? That is where purpose-built headless tooling wins. Weaverse gives teams: a Shopify-native headless workflow section-based visual editing a stronger bridge between developers and merchants reusable Hydrogen storefront patterns faster iteration without giving up structure In other words: AI helps generate.Weaverse helps operationalize. That is the real leverage. Because merchants do not want infinite frontend freedom if it creates maintenance debt. They want: speed and control flexibility and structure AI acceleration and commerce readiness The winning stack in 2026 The best stack for headless commerce teams is starting to look clear: 1. AI coding agents for speed Use them to: scaffold prototype refactor generate repetitive implementation work accelerate build loops 2. Shopify APIs for infrastructure Use Shopify for: commerce primitives catalog checkout identity discounts markets ecosystem reliability 3. Purpose-built headless tools for execution Use platforms like Weaverse to: make Hydrogen stores merchant-friendly reduce implementation drag preserve structure support production workflows that generic AI tools do not understand This is the stack that closes the gap between “it was generated” and “it actually works.” Practical playbook for teams right now If you are building Shopify storefronts in 2026, here is the move: Use AI coding agents for: initial scaffolding boilerplate generation rapid experiments repetitive component work debugging and iteration support Do not rely on them alone for: architecture decisions storefront performance strategy merchant editing systems data modeling conversion-critical flows long-term maintainability Pair them with Weaverse when you need: visual editing on top of Hydrogen reusable section architecture a cleaner developer-to-merchant handoff faster launches without custom-theme chaos That is how you turn AI speed into real commerce output. Final takeaway Replit’s $9B moment matters because it confirms something bigger than one company: AI coding is becoming table stakes. But in commerce, code generation is not the moat. The moat is knowing how to turn generated code into storefronts that sell, scale, and stay operable. That is why the future is not AI or human expertise. It is AI speed × domain knowledge. And that is exactly where headless commerce builders should focus next. Want to turn AI-generated storefront momentum into production-ready Hydrogen builds?Try Weaverse free at https://weaverse.io. Sources Replit funding / valuation coverage Latent Space on coding agents moving up-stack Shopify developer changelog Additional agentic commerce market coverage
Agentic Commerce on Shopify: How to Make Your Hydrogen Store AI-Agent-Ready in 2026
Agentic Commerce on Shopify: How to Make Your Hydrogen Store AI-Agent-Ready in 2026 AI agents are no longer just helping customers research products. They’re starting to shop for them. That changes what it means to optimize a Shopify storefront in 2026. If a customer asks ChatGPT, Gemini, Copilot, or Perplexity to find the best product for a need, the winning store may not be the one with the prettiest homepage. It may be the one with the cleanest product data, the clearest schema, and the most machine-readable storefront. Shopify sees where this is going. Agentic Storefronts are now live. Universal Commerce Protocol (UCP), co-developed with Google, gives merchants a new path to become discoverable and transactable in AI-driven buying flows. For Hydrogen teams, this shift is not a threat. It is an advantage. Because headless storefronts already separate presentation from data, they are in a better position to serve both humans and machines—if the implementation is done right. The shift: from browse-first to ask-first commerce Traditional ecommerce assumes a human visits your site, clicks around, compares options, reads reviews, and decides. Agentic commerce compresses that flow. Now the customer says: Find me leather boots under $300 Compare the best protein powders without artificial sweeteners Reorder the best moisturizer I bought last time An AI agent handles discovery, comparison, filtering, and, increasingly, transaction steps. In that world, your storefront still matters for human trust and conversion. But your discoverability layer changes completely. Instead of competing only on: branding design merchandising ad creative you also compete on: structured product attributes variant completeness stable identifiers machine-readable policy and offer data feed quality schema quality storefront and API reliability If AI systems cannot parse your catalog confidently, they will simply recommend someone else. Why Shopify merchants should care now This is not theoretical anymore. Shopify has already started building for agentic commerce through: Agentic Storefronts Shopify Catalog UCP stronger machine-readable commerce surfaces improved developer tooling around modern Hydrogen builds The strategic message is clear: commerce interfaces are expanding beyond the browser. Your customer may still buy from a human-facing storefront. But the path to that purchase may begin inside an AI interface that never sees your hero banner, campaign landing page, or carefully tuned homepage flow. That means the old optimization stack is incomplete. A store can look premium and still be invisible to AI-driven discovery. The real bottleneck: bad product data Most merchants do not have an AI-readiness problem. They have a product data discipline problem. This is where many catalogs break down: vague product titles inconsistent variant naming missing GTINs incomplete metafields missing dimensions, materials, or care specs untyped custom data weak or missing Product schema broken canonical relationships across variants For humans, you can sometimes get away with that. For AI systems, you usually cannot. Agents work better when they can rely on structured, typed, normalized inputs. That includes: brand product type size color material dimensions availability price condition fulfillment details review signals return policies If those fields are incomplete, the agent has less confidence. Less confidence means less visibility. Why Hydrogen stores have an architectural advantage Hydrogen teams are better positioned than legacy storefront teams for one reason: the architecture already separates content and data from presentation. That matters because AI readiness is mostly about the quality of the data layer. A well-built Hydrogen store can: output clean JSON-LD from server-rendered routes expose typed metafield data consistently support structured product and collection pages generate machine-readable manifests and feed layers keep storefront UX flexible without compromising data integrity In other words, Hydrogen makes it easier to build a storefront that works for humans on the surface and machines underneath. That is exactly the direction commerce is heading. Where Weaverse fits This is also why Weaverse has a natural position in the shift to agentic commerce. The real opportunity is not choosing between beautiful storefronts for humans and structured storefronts for machines. The opportunity is building both from the same source of truth. With the right Weaverse implementation, teams can: keep merchant-friendly visual editing preserve a structured section architecture flow metafield data into storefront rendering support stronger schema outputs reduce the gap between merchandisers and developers That matters because AI readiness cannot depend on engineers manually patching every product page forever. The system has to be maintainable by the actual team running the store. The 2026 AI-agent-readiness checklist for Shopify + Hydrogen teams If you want your storefront to stay visible in AI-driven shopping flows, start here: 1. Tighten product titles Every title should clearly communicate: brand product type key differentiator Avoid vague naming. Keep titles precise and scannable. 2. Complete variant-level data Every variant should have: accurate size, color, and material data availability price SKU GTIN where applicable 3. Populate critical metafields At minimum, make sure structured data exists for: material dimensions weight care instructions certifications compatibility or use case shipping or fulfillment constraints where relevant 4. Implement JSON-LD properly Support: Product Offer ProductGroup where relevant review and aggregate rating where valid 5. Clean up internal product data logic Make sure data is consistent across: PDP collection cards search results feeds structured data outputs 6. Enable Shopify’s discovery surfaces Where relevant, prepare for: Shopify Catalog Agentic Storefront pathways UCP-compatible discovery patterns as they mature 7. Validate what machines actually see Do not just inspect the page visually. Test structured outputs and rich result eligibility. The mistake merchants will make A lot of brands will hear “agentic commerce” and respond with content theater. They will publish hot takes, add “AI-ready” to landing pages, and bolt on a chatbot. But that is not the hard part. The hard part is cleaning the data model. Because AI visibility is not a branding claim. It is an operational outcome. The winners will be the teams that treat: product data schema identifiers merchandising structure storefront architecture as revenue infrastructure. Final takeaway The future of commerce is not humans versus AI. It is structured backend for machines and compelling frontend for humans. That is the middle ground Shopify is moving toward. And it is exactly where Hydrogen and Weaverse can win. If your storefront cannot pass the AI-agent parse test, you will lose demand long before a customer ever reaches your site. Want to make your Hydrogen store AI-agent-ready without sacrificing visual control? Build it with Weaverse. Start free at https://weaverse.io.
Never miss an update
Subscribe to get the latest insights, tutorials, and best practices for building high-performance headless stores delivered to your inbox.
