Skip to content
Article

AI Shoppers Land on Product Pages: What Furniture Catalogs Need

A summary of Unofficial Shopify Podcast #636 with Shopify's Head of Growth, checked against Shopify's published data, plus a product-data audit for furniture retailers whose catalogs start in an ERP.

TLDR

  • In #636 of the Unofficial Shopify Podcast, Shopify's Archie Abrams said AI referrals convert at more than 2x other referral channels and land mostly on product pages.
  • Shopify's own Q2 2026 data shows AI-referred sessions up 197% year over year, with organic search still larger, and 2x conversion when AI used structured Shopify Catalog data.
  • Spec-heavy categories such as home goods are growing fastest, so furniture specs belong in structured fields, not PDFs or JavaScript-only accordions.
  • The hosts' own 10-store analysis put AI at about 0.1% of revenue, so treat this as product-data work that also helps organic search.
  • Run the audit: give several AI models a product URL, ask what they need, and fix the gaps from real product data.

When a shopper arrives from an AI assistant, the product page is usually the first page they see. That page now has to do the homepage's job too: confirm the product fits, tell the brand story, and offer the next thing to look at. If the AI couldn't understand the product from your page, the shopper probably never arrives at all.

That's the reusable lesson from episode #636 of the Unofficial Shopify Podcast (August 25, 2026), where host Kurt Elster interviewed Archie Abrams, Shopify's Head of Growth. For furniture retailers, whose products are bought on dimensions, materials and lead times, it turns out to be a product-data problem more than a marketing one. Below are the episode's main points, what Shopify's own published data adds, the counterargument worth hearing, and the audit I'd run on a furniture catalog this week.

What Archie Abrams said in episode #636

These are the guest's statements as made on the show. He works at Shopify and is describing Shopify's data and products.

  • AI referrals convert well. Asked for numbers, he said AI referral traffic converts at "more than 2x that conversion rate coming from another referral channel."

  • The channel is growing fast from a small base. He described the trend as "2, 3, 4x" year over year depending on category, and stressed more than once that it is "still a very small base."

  • Visitors land on product pages. Relative to other sources, more AI traffic goes straight to PDPs instead of the homepage. His advice: make sure the PDP can convert on the spot, and if it isn't quite the right product, offer category expansions, cross-sells and upsells so the shopper sees the wider assortment. Email, CRM and messaging then carry the brand story after that first purchase.

  • Spec-heavy categories are growing fastest. He named "electronics, home goods, things that require a lot of detail research" as the categories seeing the most growth in agentic search, with visual, taste-driven categories such as apparel growing more slowly.

  • Structured data is the baseline. Accurate inventory and pricing come first, then complete descriptions, descriptive titles, specifications and sizing in a well-structured format. He warned that content held in a CMS and injected with JavaScript can be hard for agents to read.

  • Prompts are getting longer. Shoppers describe a use case instead of typing two keywords, so pages need to say clearly why the product is different and for whom. Richer descriptions and reviews help a product match those longer prompts.

  • The quick audit. Give ChatGPT, Gemini or Claude a product URL and ask what data it would need to understand the product. Go back and forth, try several models, and see what's missing. "It might surprise you by how little it understands based on what it's seeing on the page."

He also suggested that direct and branded-search traffic probably rise with AI visibility, because people research in an assistant and then search for the brand. Kurt added an analytics caveat from his own testing: Claude links he saw carried no UTM tags and ChatGPT added them more often but not always, so some AI-referred visits show up as direct traffic.

What Shopify's published data adds

Shopify has since published two data posts that line up with the interview and add numbers you can cite. Note the baseline: these compare AI referrals with organic search, while Archie compared them with other referral channels.

  • In AI-referred shoppers convert better and spend more (Shopify, Q1 2026 data), Shopify reported that more than half of AI-referred sessions start on a product page, compared with about 20% for organic search. AI-referred sessions that started on a PDP converted at nearly 50% higher rates than organic search, and AI-attributed orders carried 14% higher average order values.

  • In AI and organic search are doing different jobs (Shopify, Q2 2026 data), AI-referred sessions to Shopify storefronts grew 197% year over year and orders roughly tripled. Organic search grew 12% on a much larger base and still referred more sessions than all tracked AI platforms combined. AI-referred shoppers converted about 80% better than organic overall and about twice as well in spec-led categories.

  • The same Q2 post says that when AI drew on structured Shopify Catalog product data, the shoppers it referred converted 2x better than those from AI sessions relying on scraped or third-party feeds.

That last finding is the one furniture teams should care about most. It ties the conversion advantage to the quality of the product data, which is the part of this you control.

The counterweight: it's still a small channel

The same podcast published a skeptical data episode two weeks earlier. In #634, Kurt and co-host Paul Reda analyzed 24 months of data from 10 established Shopify stores (94 million sessions, 2.2 million orders, $274 million in revenue) and found AI referrals at about 0.1% of revenue. They also said they didn't see the branded-search and direct-traffic lift that the halo theory predicts, while noting the sample is small.

Both things can be true. A channel can convert well and grow quickly while still being a sliver of revenue. My read is that this doesn't make the work speculative, because the fixes are the same ones that help organic search and human shoppers. Shopify's Q2 post makes the same argument. A furniture PDP that states seat depth, fabric content and delivery lead time clearly is a better page for everyone.

Why furniture is the category to watch

Furniture is about as spec-heavy as consumer retail gets. A shopper asking an assistant for "a performance-fabric sofa under 84 inches wide that fits through a 32-inch door" is asking for exactly the attributes a lot of furniture PDPs bury in a PDF, an image or a paragraph of copy: overall and seat dimensions, materials, fabric content and cleaning code, assembly, weight capacity, and lead time by variant.

Furniture catalogs also tend to start life in an ERP. In the Shopify and STORIS integration work we do, the ERP is the source of truth for SKUs, prices and inventory, but its product records are rarely written to sell. A few things we've built in 2026 show what closing that gap looks like:

  • Mapping a flat ERP catalog into Shopify's product and variant structure. For a furniture retailer's STORIS-to-Shopify program, we specified that ERP description fields become the product title and description defaults on first import only. Later syncs leave them alone, so merchandisers can improve the copy without the next sync wiping it out.

  • A metafield-driven highlights and specifications section. We built a PDP section that renders product highlights and key-value specifications entirely from metafields, with no hardcoded content, so specs live as structured fields instead of free text.

  • Dimension data that filters correctly. We fixed dimension filters in a specifications table where middleware writes the dimension values, because a spec that displays fine but filters wrong is still broken data.

The lesson from that work: treat the ERP as the source of operational truth and Shopify as the place where selling data gets structured and enriched. If your specs exist only in someone's head or a vendor PDF, no assistant will find them. There's more on that operating model on our furniture ecommerce page.

A furniture PDP audit you can run this week

  1. Run Archie's test on five hero products. Paste each PDP URL into two or three assistants and ask: "What information would you need to recommend this product confidently to someone furnishing a small apartment?" Write down what each model gets wrong or can't find.

  2. Check what's in the HTML. View the page source, or fetch the URL with a command-line tool, and confirm the dimensions, materials and price appear in the server-rendered markup. Specs that only appear after JavaScript runs are the case Archie warned about.

  3. Move specs into defined metafields. Overall width, depth and height, seat height and depth, materials, fabric content, cleaning code, assembly and lead time all belong in structured fields. If your data already lives in custom fields, Shopify's help center says Shopify Catalog Mapping can map metafields, metaobjects and tag prefixes so agents receive the right title, description and category.

  4. Make variant truth explicit. Price, availability and lead time should be correct per fabric and finish. If you use showroom-only or special-order states, make sure the storefront says so clearly. We wrote up one way that messaging breaks in keeping custom unavailable messages through variant changes.

  5. Write for the long prompt. Say who the piece suits, what room size it fits, and how the fabric holds up to pets or kids, but only where you can back the claim. Thin, generic copy gives an assistant nothing to match.

  6. Design the PDP as a landing page. Since this visitor skipped your homepage, give them coordinating pieces, swatch ordering, delivery information and a path to the nearest showroom from the product page itself.

  7. Check your agentic settings. In the Shopify admin, look under Sales channels > Agentic to confirm your Shopify Catalog eligibility and product count, as described in Shopify's agentic storefronts help docs.

  8. Measure honestly. Segment known AI referrers in analytics, expect an undercount, and watch direct sessions that land on deep product URLs. Don't set revenue targets for the channel until you can see it.

Where I'd push back

Don't ask a model to rewrite your catalog and publish the output. Models get facts wrong, and your product page is the source of truth you control. Use the audit to find gaps, then fill them from real product data. Our earlier post on preparing a catalog for AI shopping covers the copy side of that in more detail.

And don't let AI crowd out organic search. Shopify's own data says organic still sends more sessions than every tracked AI platform combined.

My opinion: for a furniture retailer with an ERP-fed catalog, this is a data-pipeline project more than a copywriting project. It touches ERP fields, sync rules, metafield definitions and theme rendering at the same time. A partner who has worked on both sides of that pipeline will usually get it right faster than a content sprint will.

FAQ

Does AI-referred traffic show up in Shopify analytics?

Partly. Clicks that carry a referrer or UTM tags can be attributed, but Kurt observed in #636 that some assistants omit UTM tags, so part of the traffic lands in direct. Shopify's Agentic area in the admin is the place to check what Shopify itself attributes to AI channels.

Do I need a separate product feed for ChatGPT?

Not necessarily. Shopify's help center says eligible products are discoverable by AI channels through Shopify Catalog by default, with Catalog Mapping available for stores that keep product data in custom fields. You can also remove Shopify Catalog access for ChatGPT or Microsoft Copilot if you need to.

Is this worth doing if AI is a tiny share of revenue?

Yes, if you treat it as product-data work rather than a separate channel bet. The same structured specs and clear copy help organic search, onsite filtering and the shoppers who never touch an AI tool.

How we know

This article summarizes episode #636 from its published transcript, cross-checked against episode #634 and two Shopify data posts linked below. Statistics are attributed to whoever stated or published them. We haven't verified Shopify's internal data independently. The Endertech examples come from our 2026 project work on furniture retailers' Shopify and STORIS programs, described without client names or results. The show is hosted by Kurt Elster of Ethercycle, and the hosts also sell a gift-with-purchase app, Promo Party Pro, which isn't a topic of this episode.

Last reviewed: October 21, 2026.

Limits

We haven't measured AI-referral conversion on any client store, and this article doesn't claim results from following the audit. Agentic channels, Shopify Catalog eligibility rules and analytics attribution are changing quickly, so check the current help docs before acting on any detail here.

Sources

Make the product page carry the sale

If AI shoppers are going to skip your homepage, your product data has to be good enough to land them on the right sofa and close the sale there. If your catalog starts in STORIS or another ERP and you want to see where the data gaps are, talk with Endertech about your furniture catalog.

Drag to pan. Use +/− or Ctrl/Cmd + scroll to zoom. Pinch to zoom on touch devices.