Docs

Feed Specs, Submission & Formatting for UCP and ACP

How to prepare, format, and submit product feeds and catalog data for Universal Commerce Protocol (UCP) and Agentic Commerce Protocol (ACP). Asva AI guide.

Last updated: February 19, 2026

Evidence & References

This content is based on official sources and ecosystem developments:

Get implementation help

Why feed quality matters for AEO/GEO

Answer Engine Optimization (AEO) and Generative Engine Optimization (GEO) depend on structured, complete product data. Feeds that meet UCP/ACP specs are also optimized for how AI systems and answer engines discover and cite your products. Use the Readiness Score and Entity & Citation tools on asvaai.com to audit feed and entity readiness.

Feed formats and structure

Common formats

JSON — Preferred for UCP/ACP programmatic consumption. Use the schema required by the platform (Google Merchant Center, Shopify, or custom endpoints).

XML — Often used for sitemaps, RSS-style product feeds, and legacy integrations. Ensure required fields are present and namespaced correctly.

Structured data (JSON-LD) — On-page Product, Offer, and Organization schema. Required for discovery and citation; see AEO + GEO.

Required fields (typical)

Product: id, title, description, link, image, availability, price, priceCurrency

Offers: Clear price and availability; variant info when applicable

Organization/brand: Name, URL, and (where required) legal entity

Exact requirements vary by platform. See UCP getting started and ACP getting started for platform-specific feed specs.

Submission paths

UCP (Google, Shopify, etc.)

Google Merchant Center: Submit product feed via Content API or scheduled feed upload. Ensure feed matches Google's product data spec and that your domain has a valid UCP manifest at /.well-known/ucp.

Shopify: UCP is enabled via Checkout Kit and store configuration. Product data is exposed through Shopify's APIs; see Shopify UCP guide.

Custom / headless: Host a feed URL and reference it from your UCP manifest. Use the Manifest Generator on Asva AI to generate a compliant manifest.

ACP (ChatGPT, Instant Checkout)

Product and offer data are consumed by ACP-compatible agents via your declared endpoints and any catalog/feed URLs you expose. Ensure endpoints and feeds match the ACP spec and use the ACP Validator to test.

Formatting best practices

IDs: Use stable, unique identifiers for products and variants (no session or timestamp-only IDs).

Prices: Include currency and numeric value; avoid "from" or range-only unless the spec allows.

Availability: Use a consistent enum (e.g. in_stock, out_of_stock, preorder).

Images: Absolute URLs, sufficient resolution; prefer same aspect ratio across products.

Validation: Run the Readiness Score on your domain to catch missing or malformed feed signals.

Checklist before submission

Feed URL is reachable and returns valid JSON or XML.

Required fields are present and non-empty.

UCP manifest is live at /.well-known/ucp (or equivalent) and points to your feed/capabilities.

For ACP, checkout and order-status endpoints are implemented and validated with the ACP Validator.

On-page Product/Offer schema is present for key pages (AEO/GEO); see Entity & Citation.

Evidence & References

Evidence & References

Feed Specs, Submission & Formatting

Why feed quality matters for AEO/GEO

Feed formats and structure

Common formats

Required fields (typical)

Submission paths

UCP (Google, Shopify, etc.)

ACP (ChatGPT, Instant Checkout)

Formatting best practices

Checklist before submission

Related