Pool & Spa is being reranked by AI. Is your catalog readable?

A pool builder or service tech replacing a burned-out single-speed motor this summer doesn't start on a distributor's website — he asks ChatGPT or Perplexity whether the pump he's about to order meets the DOE's dedicated-purpose pool pump standard, which pushed single-speed motors above 1.15 THP off the market for residential replacements in September 2025. If your product data can't answer that, it moves to whichever distributor's data can, and that distributor gets the order. Pool & Spa is a category where every pump replacement is now also a compliance check, exactly the kind of question AI answer engines are least forgiving of thin data on.

Buying research has already moved into the chat window

This shift isn't specific to pool and spa, but distributors in the category are as exposed to it as anyone selling a considered equipment purchase. Forrester's 2026 Buyers' Journey Survey, covering nearly 18,000 global business buyers, found AI tool usage in the purchase process grew from 89% in 2025 to 94% in 2026, with more buyers naming generative AI as their most meaningful research source than any other channel — ahead of vendor websites, product experts, and sales reps (Machine Relations, B2B Buyers Now Research Vendors in AI Engines Before Visiting Any Website). The same research ties that shift to website traffic declines of 10 to 40% a year as research moves into chat windows.

For a pool builder, retailer, or service company sourcing pumps, heaters, salt chlorinators, or safety covers, that means the shortlist of distributors worth calling is increasingly assembled before anyone lands on a website. An answer engine synthesizes its response from a handful of parseable sources, not a full page of results — so being left out isn't a lower ranking, it's no visibility at all.

Why a full catalog can still look empty to a model

Most pool and spa ERP exports were built to move product through a warehouse, not to answer a spec question. A typical pump listing looks like this:

Raw ERP feed description (as-is):

PMP VS 1.5THP 230V UPRT TEFC 2IN

That string is fine if you already speak your own ERP's abbreviations. It tells a model almost nothing reliable — total horsepower, voltage, motor enclosure, and plumbing size are compressed into one token with no labels, and there's no explicit statement of whether the pump actually meets the DOE standard that now determines whether it's even legal to sell as a residential replacement.

Enriched, the same SKU looks like this:

Once THP, DOE compliance status, and plumbing size are explicit, labeled fields instead of a compressed string, a model can match "variable-speed pump that meets the new DOE pool pump standard for a 20,000-gallon pool with 2-inch plumbing" to the actual SKU instead of guessing at what UPRT or TEFC mean.

Ask an answer engine: what this looks like in practice

Here's a query a pool owner, builder, or service tech could plausibly run today:

"My single-speed pool pump just failed and I heard single-speed pumps over 1.15 horsepower aren't legal to sell as replacements anymore. What variable-speed pump meets the new DOE standard for a 20,000-gallon pool with 2-inch plumbing, and which distributors have one in stock this week?"

The engine is parsing that for THP threshold, DOE compliance, pool volume, plumbing size, and availability. Whether that data lives in schema.org Product and additionalProperty markup, in visible, labeled attributes on the page, or in a feed a retrieval layer can parse, matters less than whether it exists as a discrete fact anywhere at all. Structured markup isn't a guarantee of citation — one widely cited analysis found no consistent correlation between schema coverage and citation rates across a large sample of ChatGPT answers — but it does measurably improve how accurately a model extracts a fact once it's looking at the page, and "is this legal to sell" is exactly the kind of question where that accuracy matters (Search Engine Land, How schema markup fits into AI search — without the hype).

What machine-readable actually requires

None of this is exotic for pool and spa distributors — it's the data cleanup most already know they're behind on, with a sharper reason it matters now:

• Split compressed spec strings into discrete, labeled fields — THP, voltage, motor enclosure, plumbing size, flow rate.
• State DOE and energy-compliance status on the product record itself, not buried in a linked spec sheet, since compliance is now a purchasable fact.
• Standardize abbreviations and units across manufacturer lines (Pentair, Hayward, Jandy, and others) so THP and flow rate aren't lost in inconsistent shorthand.
• Keep values current ahead of the second compliance phase-in for smaller pumps in September 2027, so an engine isn't recommending a model that's about to age out.

Done by hand, this runs somewhere in the 30-45 minute per SKU range — pulling the spec sheet, confirming DOE listing status, normalizing units, filling the gap. Across a catalog spanning pumps, heaters, filters, salt systems, covers, and chemicals from a dozen manufacturer lines, that's not a project a data team clears before the next update makes it stale again. The values still have to come from somewhere real — extracted from supplier documentation and quality-scored, not invented — because a wrong THP or compliance claim here isn't just an inconvenience, it's a return or a compliance problem.

Where this fits for distributors

Your ERP or PIM stays the system of record — Anglera doesn't replace it and has nothing to do with your CRM. It plugs into whatever you already run (Akeneo, Salsify, inriver, Stibo, Syndigo, Pimcore, Informatica, or nothing formal — a flat export is enough to start) and continuously extracts, scores, and gap-fills the attributes that turn a compressed ERP string into something an answer engine can match against a real question. Most distributors can get a meaningful slice of a pool and spa catalog there within 30 days, not a multi-year systems project. Getting there first isn't about chasing a better ranking — it's making sure your SKU is the one an AI answer engine confidently recommends the next time a buyer asks whether a pump is even legal to sell.