# The CommerceClarity blog

> The CommerceClarity blog covers what changes when AI agents own the product data pipeline: product attributes and taxonomy, channel and marketplace rules, catalog compliance, on-site search, SEO and generative engine optimization, and agentic commerce. Articles are written by the people who run the agents on enterprise catalogs, and each one carries its own Q&A.

From the CommerceClarity blog: what changes when agents own the product data pipeline.

## Get the latest from CommerceClarity

New explainers, regulation updates, and research, straight to your inbox.

[Book a demo](/book-a-demo)

## Articles

- [ChatGPT product feed: nine required fields, and the optional ones that decide what gets surfaced](/blog/chatgpt-product-feed-required-fields) · 2026-09-18 · A ChatGPT product feed needs nine required fields. Optional attributes give OpenAI the data to filter, compare and surface the right products.
- [Your ecommerce has an AI agent score.](/blog/llms-txt-webmcp-ecommerce) · 2026-09-14 · We ran Lighthouse’s experimental Agentic Browsing checks on our own site and read what they measure. What a retailer should do with the result, what to try with WebMCP and llms.txt, and where the real preparation for agentic commerce happens: the catalog.
- [Claude Commerce Agents: the agent got easy to build. The catalog decides what it can enforce.](/blog/claude-commerce-agents-catalog-constraint) · 2026-09-03 · Anthropic and Shopify made the shopping agent easy to build. We read the code to show what it asks of the catalog underneath, and why creating the field is only the start.
- [Meet the Retail Engineer](/blog/meet-the-retail-engineer) · 2026-09-01 · One person owns an AI agent deployment in retail, from the first business question to the live catalog. This is what a Retail Engineer does, and where the forward deployed engineer fits.

## Questions

### What does the CommerceClarity blog cover?

Retail catalog operations and the agents that run them: product attributes and taxonomy, channel and marketplace rules, catalog compliance, on-site search, SEO and generative engine optimization, and agentic commerce.

### Who writes it?

The people who do the work: Retail Engineers, product and go-to-market at CommerceClarity. Every article carries a named author with their own page, so you can see what else they wrote.

### Are the claims sourced?

Yes. Every claim carries a source, and customer numbers appear only with the customer’s sign-off. Where something is not yet proven, the article says so rather than rounding it up.

### Can we quote or republish an article?

Quote it with a link back. For a full republication or a syndication, write to press@commerceclarity.com and we will sort out the terms.

## Entities

- [Google](https://www.google.com) · Organization, mentions
- [OpenAI](https://openai.com) · Organization, mentions
- [GS1](https://www.gs1.org) · Organization, mentions

## Sources

- [Creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) · Google Search Central
- [Product structured data](https://developers.google.com/search/docs/appearance/structured-data/product) · Google Search Central
- [Commerce documentation](https://developers.openai.com/commerce/) · OpenAI
- [GTIN, the GS1 global trade item number](https://www.gs1.org/standards/id-keys/gtin) · GS1

---
Canonical: https://commerceclarity.com/blog
Every page of this site is available as markdown: append `.md` to its path. Index: /llms.txt