How Brand42 Launches Timothy London’ Storytelling-Infused Storefront with Weaverse & Hydrogen
It is a truth universally acknowledged that a brand in possession of a great vision must be in need of a stellar digital experience.
Such was the case with Timothy London, a premium British travel goods brand, and their vision to immerse their customers into their world with beautiful storytelling and aesthetic finesse. It was an ambitious vision, by all means. This was where Brand42, a prominent London-based design and digital agency, came into play.
About Brand 42
Brand42 is a prominent London-based design and digital agency, well-known for delivering strategic branding solutions to premium brands like BBC, Johnnie Walker, Rakuten, and Top Gear. At the heart of their success is the innovative One-Team Approach.
With the One-Team Approach, Brand42 seamlessly integrates its creative and development teams from the outset, fostering a collaborative environment where developers contribute to functional decision-making early in the process. This ethos of collaboration enables Brand42 to deliver tailored, innovative solutions that transform their clients’ visions into immersive realities, driving impactful results.
Brand42’s commitment to customization is further exemplified by its technology-agnostic approach. They don't limit themselves to specific stacks like WordPress or Shopify. Instead, they choose the best tools for the job. For the Timothy London project, Brand42 knew that the complex requirements and unique brand personality required a headless approach.
The Challenges: Steep learning curve and Herculean development effort
Timothy London is building a one-of-a-kind brand for travelers. They combine superior design and engineering excellence to bring out a product that can truly be THE travel companion of a lifetime - offering comfort, ease of use, utility, and just a bit of flair, wherever the travelers go. With its new website, the brand wanted to find a way to translate these unique physical qualities into the digital space.
It’s a challenging goal for Brand42. How do you tell such a unique story in the digital space while keeping the shopping experience fast and functional, optimized for both desktop and mobile, supporting videos and 3D images, and enabling discovery through movement?
The answer is headless, and to be more precise,Shopify Hydrogen.
Yet, going headless is not the silver bullet. Despite how feature-rich and powerful Hydrogen is, it wasn’t all smooth sailing for the Brand42 team. They found quite a learning curve with Hydrogen and Remix as this is their first project using this framework. Additionally, the nascent state of Hydrogen meant a limited availability of 3rd-party apps and plugins. This meant they had to develop a lot of features from scratch.
Secondly, Brand42 development team also found Shopify Hydrogen to be particularly quite limited in the setup of page layouts, hindering their efforts to achieve a more flexible, fluid design layout that they’ve planned, for example, Hydrogen lacked the drag-and-drop module functionality that they are accustomed to in other Content Management Systems. In an ideal world, they should have the best of both worlds - the performance and extensibility of Hydrogen, and the user-friendliness that comes with a drag-n-drop editing experience.
Turned out the ideal world is just one app away.
Without Weaverse, we feel like Hydrogen was in beta.
— Harry F. Senior Designer at Brand42
They discovered Weaverse while researching alternatives that offered more flexibility than Shopify’s rigid structure. Weaverses allows development teams to build Hydrogen stores much faster by providing SDKs and pre-made templates, while also supporting a drag-and-drop framework, allowing Brand42’s clients considerable control over their content without the usual constraints.
The Solution: Weaverse, the first theme customizer for Hydrogen
Brand42 chose Weaverses as it’s the only solution on the market that could offer what they needed to meet project requirements:
-
A more CMS-like content editing experience within Shopify Hydrogen, which made it easier for everyone to manage and edit content.
-
SDKs and templates to facilitate easy development of components and seamless integration with Shopify's backend.
-
Flexible route structure that allows for custom nested pages, aligning perfectly with child pages in the site structure.
-
Custom markets and localization features, including an automatic copy-to-locale functionality developed at the development team's request.
These unique advantages made Weaverse the ideal solution for the Timothy website project. But that’s not all. What stood out to Brand42 was Weaverse's integrated support - echoing their own One Team Approach ethos.
When I found you guys, you only had one review. Five stars, but it’s just one review and for me, it was a bit suspicious.
But when I started and got all this kind of support to make all these pages really manageable, to build something new and custom, it made me feel confident that it’s possible to deliver this project.
— Jev S., Senior Web Developer
Weaverse team provided a dedicated Slack channel, offering quick problem-solving, continuous support, and 24/7 assistance. This close collaboration helped Brand42 quickly fix bugs, implement custom features on time, and stress-test new functionalities, allowing them to achieve the client’s requirements and meet deadlines.
Our experience working with Weaverse has been excellent!
What stood out to me very often when you're working with software as a service providers is that it can feel a bit like a faceless organization. There's no point of contact that you can get hold of. It was quite the opposite with you guys. You were quite happy to have face to face interactions, put a name to a support issue and were reactive in terms of requests.
There are other CMS we've used, and if you find a bug and it gets logged in the pipeline for 12 months before they'll even look at it. But it’s completely different with Weaverse. I think even the communication chain went from Jamie or I saying to Jev, can we achieve this? And then Jev saying, I'll speak to Paul. And then within 10 minutes or so we have a response, which was just unheard of in terms of our support response that we've been used to.
— Jamie H. Project Director at Brand42
The Result: Elevated brand experience went live in time for the international product launch
With Weaverse, building a Hydrogen storefront was faster and easier.
Brand42 team was able to streamline their workflow using Weaverse components. Additionally, they could easily improve the quality of their page layouts to match designs, thanks to Weaverse’s intuitive drag-and-drop functionality. This resulted in the successful launch of Timothy London’s storefront. The new website is fast, interactive, and pixel-perfect. The shopping experience feels immersive and smooth, allowing users to explore and discover the products effortlessly.
We've experienced major improvements in efficiency and productivity with Weaverse. The Pilot theme provided an excellent foundation for developing our Hydrogen theme, which saved us valuable time and effort!
[..]
We're very satisfied with our experience with Weaverse and certainly recommend their services. We look forward to continuing our collaboration to further enhance Timothy's website and for future projects.
— Jev S., Senior Web Developer
For development agencies like Brand42, diplomacy is of utmost importance.
Clients might change their minds, ask for last-minute iterations, or see a different option. The success of a development agency depends on how flexible it can adapt to these requests and feedback.
As an award-winning design agency, Brand42 team wants to manage clients’ expectations with tact and diplomacy. For that, they need a design tool that’s flexible enough, and Weaverse fits nicely into this vision. Weaverse allows the design team to quickly iterate the website in response to clients’s feedback, making it easier for the strategy team to live up to client expectations and build a long-term relationship.
As an agency, we like to be quite flexible.
Sometimes when a client changes their mind, or wants to see a different option, or wants to iterate, we won’t say no. We're not the sort of agency that says no, or brings out a timesheet to review and say why we're not going to do that.
So having the tools that allowed us to react to some of that feedback through the course of the project was really useful, especially when it doesn't limit the design team in terms of how they can respond to that feedback. From a client management perspective, it allows us to kind of live up to what our clients expect from us.
— Jamie H. Project Director at Brand42
Reactions
Join the Discussion
Continue Reading
More insights from the Weaverse team
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.
ChatGPT Quit Agentic Commerce. That Doesn't Mean You Should.
ChatGPT Quit Agentic Commerce. That Doesn't Mean You Should. Two posts this week confirm the same signal: Juozas Kaziukėnas: ChatGPT is abandoning agentic commerce after 5 months. Users researched products but didn't buy through the chatbot. Kelly Goetsch: OpenAI is losing ground to Anthropic and deprioritizing commerce because enterprise commerce is harder than they expected. The headlines say "AI commerce is failing." The real story is more nuanced. Why They Retreated Agentic commerce — AI agents that discover, compare, and complete purchases on behalf of users — hit three hard walls: 1. Catalog Normalization Is Brutal Product data (pricing, inventory, variants, availability) needs to be: Standardized across every retailer Constantly updated in real-time Accurate enough for AI to trust Only Google Shopping has done this at scale. ChatGPT couldn't. 2. Trust Gap: Research ≠ Purchase Users were happy to research products inside ChatGPT. But when it came time to buy, they didn't trust the chatbot with payment. This isn't a ChatGPT problem — it's a user behavior problem. Facebook Shops and Google's "Buy with Google" hit the same wall. 3. Fraud and Error Safeguards Commerce and payment firms need real safeguards against: AI initiating fraudulent transactions AI making erroneous purchases Liability when something goes wrong These safeguards don't exist yet at scale. Without them, platforms retreat to just driving traffic to retailer sites. What They're Not Saying This is a pause, not a permanent retreat. Kelly Goetsch explicitly predicts: "they'll re-prioritize commerce in a few months once they figure out the infrastructure layer." Juozas Kaziukėnas frames it as lack of conviction: Chinese AI platforms like Alibaba's Qwen are spending hundreds of millions to force the behavior change. ChatGPT gave up too early. Either way, they'll be back. The question is: will your store be ready? The Infrastructure Layer Wins Long-Term When AI platforms return to agentic commerce, the stores that win won't be the ones with the prettiest themes or the best brand storytelling. They'll be the ones with: Structured product data that agents can read and reason about Clean APIs that don't break under automation Checkout flows with real safeguards and clear liability boundaries Machine-readable manifests (like UCP's ucp.json) that broadcast capabilities to agents This is exactly what Hydrogen + Storefront API architectures are built for. Why Hydrogen Teams Have a Structural Advantage Monolithic Liquid stores have product data trapped in rendered HTML. AI agents have a hard time reasoning over server-rendered markup. Hydrogen stores built on the Storefront API already expose: Structured, queryable product data Stable cart and checkout mutations Clean authentication via Customer Account API Market-aware URLs for localized experiences Adding UCP support or similar agent-ready layers is an extension of the architecture, not a rewrite. What You Should Do While Big Platforms Regroup 1. Audit your data layer Can an AI agent query your product catalog via clean API? Or is your data trapped in theme templates? 2. Check your checkout safeguards Do you have clear boundaries for what automated systems can and can't do? Fraud detection? Liability clarity? 3. Make your capabilities machine-readable If you're on Hydrogen, you're most of the way there. The next step is declaring your capabilities in a format agents can discover. 4. Don't wait for platforms to figure it out The stores that win agentic commerce won't be the ones who waited for ChatGPT to solve catalog normalization. They'll be the ones who made their data clean, their APIs stable, and their checkout safe — before the next platform tries again. The Honest Take Agentic commerce is harder than the hype. The platforms with the biggest AI models just hit the wall. But the infrastructure layer still wins. If your store is machine-readable, API-first, and checkout-safe, you become the integration backbone for whichever platform eventually cracks it. The platforms quit early. That doesn't mean you should. Sources Juozas Kaziukėnas on ChatGPT abandoning agentic commerce: https://www.linkedin.com/posts/juozas_chatgpt-is-abandoning-agentic-commerce-its-activity-7435308306329473025-Ncy0 Kelly Goetsch on OpenAI deprioritizing commerce: https://www.linkedin.com/posts/kellygoetsch_feels-like-openai-is-quickly-losing-ground-activity-7435323329483460608-GgKK Shopify headless architecture: https://shopify.dev/docs/storefronts/headless
Never miss an update
Subscribe to get the latest insights, tutorials, and best practices for building high-performance headless stores delivered to your inbox.
