Signal
ACP feed and checkout readiness
Whether a store targeting ChatGPT checkout ships the ACP feed with correct eligibility flags and the return fields checkout-eligible items require.
Per-platform status
Where a platform documents relevant behavior, its status and source are shown. Undocumented platforms show "unknown" - honest unknowns, never invented.
| Platform | Status | Notes | Source |
|---|---|---|---|
| ChatGPT | Supported | The feed spec defines the eligibility flags (is_eligible_search, default true; is_eligible_checkout, opt-in) and the return fields a checkout-eligible item needs. | Source (opens in new tab) · verified 2026-09-18 |
| Gemini / Google AI Mode | Unknown | Not documented by this platform. | - |
| Perplexity | Unknown | Not documented by this platform. | - |
| Copilot | Unknown | Not documented by this platform. | - |
| Claude | Unknown | Not documented by this platform. | - |
Evidence and sources
This signal is typed spec-fact (Very high confidence).
- ACP product feed specification (opens in new tab) · 2026-07-08
How to act on this
If you target ChatGPT checkout, enroll in OpenAI's merchant program, set is_eligible_search on products you want surfaced, and set is_eligible_checkout only on rows that also carry return_policy and return_deadline_in_days. The older enable_search, enable_checkout and return_window names are still accepted as aliases, so a feed written against the launch spec keeps working, but the current names are the ones to write.
Related checklist items
Handbook chapters