Commerce Checks

When commerce applies

Commerce is the only dimension AIScan turns off by default. It activates when the scanner detects an e-commerce platform (Shopify, BigCommerce, WooCommerce, Magento) or e-commerce structured data on the page. For everyone else, these checks return na and don't affect your score.

M1 — Product feed

Agents that shop on a user's behalf need a stable, machine-readable list of what you sell. AIScan looks for a Google Merchant Center XML feed, a JSON product catalog, or a CSV at common paths (/products.json, /feed.xml).

How to fix

• Shopify — /products.json ships by default; expose it explicitly.
• WooCommerce — add a feed plugin (Product Feed PRO, CTX Feed) that generates Google Merchant XML.
• Custom — emit a feed at build or via an endpoint with stable URLs, prices, SKUs, and availability.

M2 — Structured product data

On product pages, AIScan checks for schema.org/Product JSON-LD with the basics: name, image, offers.price, offers.priceCurrency, offers.availability. Most e-commerce themes include this; older themes don't.

How to fix

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Acme Widget",
  "image": "https://acme.com/widget.jpg",
  "sku": "WIDGET-1",
  "offers": {
    "@type": "Offer",
    "price": "29.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock"
  }
}
</script>

M3 — Agentic checkout

Emerging standards from Visa, Mastercard, OpenAI, Anthropic, and Shopify are converging on the idea of a machine-callable checkout endpoint. AIScan flags whether your store exposes one — informational for now, but worth tracking.

How to fix

Most platforms aren't there yet. Watch for Shopify's Agent Commerce rollout and equivalent on Stripe/Visa. If you build a custom checkout, expose an OpenAPI description and link it from your API catalog.