UCP & ACP Readiness — Partner Brief
Google and OpenAI
are building the rails
for AI commerce.
They define how product data, pricing, availability, and purchase flows need to be structured for AI systems to discover products and complete transactions on a buyer’s behalf. Most merchants are nowhere near ready. That’s your practice opportunity.
The SIs who understand UCP and ACP first — and can walk clients through readiness — will own the next wave of digital commerce strategy engagements. That window is open now. It won’t stay open long.
Google Universal Commerce Protocol
UCPDefines how merchants must structure product data, pricing, availability, and transactional workflows so Google’s AI systems can surface, represent, and transact on products inside conversational and AI-native surfaces.
developers.google.com/merchant/ucp →OpenAI Commerce APIs
ACPEnable ChatGPT and other OpenAI surfaces to surface products, present structured offers, and initiate direct purchase flows inside conversational interfaces — when merchant data meets the API requirements.
developers.openai.com/commerce →What UCP and ACP are
Plain-language explanations for your client conversations.
You don’t need to be a protocol engineer to lead these conversations. You need to understand what each framework requires and what it means for your clients’ visibility in AI-driven discovery and purchase surfaces.
Google
Universal Commerce Protocol (UCP)
UCP is Google’s framework for structuring commerce data so AI systems can act on it. Think of it as the next evolution of Google Shopping — but instead of just surfacing product listings in search, UCP enables Google’s AI to discover, compare, and facilitate purchases inside conversational and AI-native surfaces like Gemini, AI Overviews, and future Google commerce interfaces.
Structured product data: titles, descriptions, attributes, images in machine-readable format
Real-time pricing and availability signals the AI can trust and act on
Transactional workflow data enabling direct checkout initiation from AI surfaces
Behavioral signals that help the AI rank and personalize product recommendations
Merchant identity and trust signals for authorized representation in AI interfaces
OpenAI
Commerce APIs (ACP)
OpenAI’s Commerce APIs define how merchants expose their product catalog, pricing, and purchase flows to ChatGPT and other OpenAI surfaces. When a shopper asks ChatGPT to recommend or purchase a product, ACP is the mechanism that determines which merchants are visible, how their products are represented, and whether the transaction can be completed inside the conversation.
Catalog exposure: structured product listings ChatGPT can index and retrieve
Offer presentation: pricing, availability, and variant data in a format AIs can display
Direct purchase flows: checkout initiation from inside the ChatGPT conversation
Order management integration: status, returns, and support handled in-conversation
First-party behavioral data signals for personalized AI recommendations
UCP and ACP are separate frameworks maintained by separate companies — but they share the same underlying requirement: merchants need structured, synchronized, first-party data captured at the infrastructure layer. A merchant who achieves UCP readiness is largely ready for ACP as well. Your consulting practice addresses both in a single engagement.
The merchant risk
What happens without readiness.
This isn’t a future problem. AI-driven product discovery is active today. The merchants without structured data are already being disadvantaged in AI surfaces — they just don’t know it yet.
Reduced AI visibility
When a shopper asks Gemini or ChatGPT for product recommendations, merchants with unstructured data either don’t appear or appear far down a ranked list. Visibility in AI surfaces depends directly on data structure quality — not brand recognition or spend.
Inaccurate product representation
AI systems working from unstructured page content generate descriptions, prices, and availability based on best-guess interpretation. Inaccurate AI representation erodes trust, drives returns, and creates liability — with no easy path to correction without addressing the underlying data structure.
Missed direct-purchase opportunities
UCP and ACP enable AI surfaces to complete purchases on behalf of shoppers without them ever visiting the storefront. Merchants without the right data structure are excluded from this channel entirely — they’re invisible at the moment a shopper is ready to buy.
The question for any client: “If a shopper tried to buy one of your products inside ChatGPT or Gemini today, could they? Would your product appear, would the price be accurate, and could they complete the transaction?” For most merchants today, the answer is no to all three. That’s the scope of the readiness problem — and your engagement.
The four readiness requirements
What UCP and ACP both require. What Webscale provides.
Both protocols share four underlying requirements. Your audit assesses each. Webscale’s architecture satisfies each without replatforming. No new infrastructure. No rip-and-replace.
01
Structured first-party behavioral data
UCP and ACP both require behavioral signals — browse patterns, purchase history, session behavior — in a structured format AI systems can act on. Most merchants have this data scattered across analytics tools in forms that aren’t machine-actionable.
How Webscale satisfies this
The CDP captures first-party behavioral data at the infrastructure layer in real time — structured into clean shopper profiles the moment it happens. No pipeline to build. No export to maintain.
02
Clean, synchronized product catalog data
AI surfaces require product data that is complete, consistently structured, and synchronized with live pricing and availability. Catalog data that’s incomplete, inconsistently formatted, or delayed makes accurate AI representation impossible.
How Webscale satisfies this
The AI Shopping Assistant runs on live catalog data and maintains synchronized product, pricing, and availability signals the AI can trust. BI dashboards surface catalog health and completeness scores immediately.
03
Infrastructure-layer data capture
Both protocols are designed for data that is complete and unsampled — not data collected via script tags, filtered through third-party aggregation, or delayed by batch export. Infrastructure-layer capture is the only way to meet this requirement reliably.
How Webscale satisfies this
Webscale sits between the internet and the application — every request flows through it. Data is captured at the source, before the application processes it, with no sampling and no delay. This is what infrastructure-layer capture means in practice.
04
API-driven transactional readiness
Direct-to-checkout conversational flows require merchants to expose purchase, order, and return workflows via API in a format AI systems can invoke. Most merchant stacks have no API layer built for this purpose, and retrofitting it is a significant technical project.
How Webscale satisfies this
The AI Shopping Assistant already handles conversational discovery, comparison, and order support — including order status and returns. Its architecture is designed for the API-driven transactional flows that UCP and ACP require.
Your consulting practice
A four-stage UCP/ACP engagement model.
Each stage is independently scoped and billable. The ongoing alignment retainer is defensible because both UCP and ACP are evolving frameworks — compliance today doesn’t guarantee compliance in six months.
Stage 01
Readiness Audit
Project-based engagement
Assess the merchant’s current data posture against the four readiness requirements. Evaluate product catalog structure, behavioral data availability, infrastructure capture capability, and API transactional readiness. Score each dimension and deliver a prioritized gap analysis.
Four-dimension readiness scorecard against UCP and ACP requirements
Catalog completeness and structure audit
Behavioral data availability and format assessment
API transactional readiness evaluation
Stage 02
Gap Analysis and Roadmap
Project-based engagement
Translate the audit findings into a sequenced remediation roadmap. Prioritize gaps by impact on AI visibility and implementation complexity. Scope Webscale CDP and AI Shopping Assistant deployment as part of the infrastructure remediation work.
Prioritized remediation roadmap with effort and impact estimates
Webscale CDP and AI Shopping Assistant deployment scope
Catalog content enrichment and schema implementation plan
API integration scope for transactional readiness
Stage 03
Remediation and Implementation
Project-based engagement
Execute against the roadmap. Deploy Webscale CDP to establish the behavioral data foundation. Structure and enrich product catalog data to meet UCP and ACP specifications. Configure the AI Shopping Assistant for API-driven transactional readiness. Validate against both protocol requirements.
Webscale CDP deployment and behavioral data pipeline activation
Catalog data restructuring and content enrichment for UCP and ACP compliance
AI Shopping Assistant configuration and API transactional readiness validation
UCP and ACP compliance validation and sign-off documentation
Stage 04
Ongoing Alignment
Monthly retainer
Monitor compliance as UCP and ACP requirements evolve. Track AI visibility metrics via BI dashboards. Refresh catalog data structure and behavioral signal accuracy. Update API integrations as protocols expand. This is not optional maintenance — both frameworks are actively developed and requirements change.
Monthly compliance review against evolving UCP and ACP specifications
AI visibility monitoring and performance reporting via BI dashboards
Catalog and behavioral data refresh as product lines and pricing change
Protocol update response: schema and API adjustments as UCP and ACP evolve
What your practice earns
Strategic advisor. Durable engagement.
UCP/ACP readiness is a multi-phase, technically complex, ongoing engagement. It positions your practice as the strategic partner who navigated clients into AI-native commerce — not the agency that got there second.
01
A genuinely new consulting category
Four stages. Multi-month scope. Ongoing retainer. This is not a one-time audit — it’s a practice with recurring revenue justified by evolving protocol requirements and continuous compliance monitoring.
02
Strategic advisor positioning
The SI that leads the UCP/ACP conversation becomes the client’s primary technology advisor for AI-native commerce. That positioning opens every future conversation about infrastructure, AI, and platform strategy — from a position of demonstrated expertise.
03
Natural expansion into full Webscale stack
UCP/ACP readiness work naturally expands into AI Segmentation deployment, AI Shopping Assistant optimization, and full Agentic Commerce OS activation. The data infrastructure you establish in Stage 03 is the foundation every other Webscale product builds on.