How to verify a Shopify UCP discovery profile
A discovery profile can advertise protocol compatibility and commerce capabilities to agents. It does not prove that every product is eligible, every capability works, or any platform will recommend the store. Test each layer separately.

01A profile check is not a commerce certification
A successful request to /.well-known/ucp establishes that a domain returned a document. It does not establish that your agent negotiated a usable operation, found the intended variant or completed a permitted checkout. Treat those as separate acceptance decisions with separate evidence.
For a merchant using a standard Shopify storefront, first determine whether there is an actual integration failure. You do not need to build a proxy or install another app merely to respond to a protocol announcement. For an agent developer or headless team, the useful task is narrower: identify the first failing boundary between your client, the public domain and the commerce service.
The September 4, 2026 Shopify announcement[1] added advertised compatibility with UCP 2026-08-25 without adding capabilities or requiring a storefront configuration change for that update. That is a dated platform fact, not permission to hard-code a version forever or claim that all storefront architectures work identically.
What the evidence does and does not prove
| Result | What it establishes | What it does not establish |
|---|---|---|
/.well-known/ucp returns 200 | The domain returned a document | That it is a valid profile, or that any operation works |
| The JSON parses | Syntax is valid | Capability relationships, versions or endpoint trust |
| Negotiation returns capabilities | The intersection of business and agent declarations | That the right product or variant will be found |
| Shopify's September 4, 2026 compatibility update | UCP 2026-08-25 is advertised, with no new capabilities or required changes | That every storefront architecture behaves the same |
02Separate the business profile from your agent profile
Shopify's negotiation documentation[2] distinguishes the business profile from the platform/agent profile. The business validates the agent's declared version and capabilities, computes the compatible intersection and removes extensions whose required parent is absent. Responses expose the negotiated metadata. An unsupported protocol version is different from a capability-version mismatch that leaves a smaller compatible set.
This is the first improvement to a superficial “JSON is valid” test: save what was advertised, what your client declared and what was actually negotiated. A tool missing from the result can be an expected consequence of the agent profile rather than a merchant outage. Do not advertise capabilities your client cannot safely implement simply to make the tool list longer.
Use your own reviewed profile for a production integration. Official example fixtures are useful in a controlled test, but copying a broad example does not prove your application supports its checkout, consent or payment behavior. Keep profile changes versioned so a later client release can be matched to the declaration it used.
03Make the first investigation read-only
- Identify the exact origin. Record the public store domain, any headless domain and the service owner. Do not assume a response on one hostname validates the others.
- Capture the response. Save status, content type, redirect chain, timestamp and a digest of the body. A branded HTML error with status 200 is not a profile. A redirect needs explanation and a destination-ownership check, not automatic acceptance.
- Check the declared contract. Parse the document and compare required fields and versioned semantics with the selected UCP specification[3]. A generic JSON parser does not check duplicate-key ambiguity, capability relationships or endpoint trust.
- Inspect your own profile's availability. The business needs to retrieve it. Check the intended public HTTPS URL without an editor login, and distinguish an inaccessible file from a semantically incompatible profile.
- Compare the negotiation result. Record the operation you intended to use and the compatible capabilities actually returned. Do not infer success from the storefront document alone.
Inspect declared URLs as data before using them. Do not automatically follow arbitrary service addresses into private networks, send credentials to a newly discovered host or weaken TLS validation to get a green test. A profile is an interoperability document, not blanket trust or buyer authorization.
04Match the failure to its owner
| Evidence | Likely investigation owner | Next discriminating check |
|---|---|---|
| HTML or a routing fallback at the profile path | Public-domain routing/CDN owner | Compare the approved origin and edge path; do not replace the platform profile with invented JSON |
| The agent profile cannot be fetched | Agent hosting owner | Public access, redirects and cache freshness for that exact profile URL |
| Version rejected | Agent protocol owner | Supported protocol version rather than an unrelated product or theme setting |
| Only some capabilities survive | Client integration owner | Capability versions and extension dependencies in both declarations |
| Negotiation works but the product is absent | Catalog/integration owner | Scope, query, market context and actual catalog response |
| Product is found but checkout fails | Commerce flow owner | Exact operation, selected variant and transaction state; discovery has already passed |
These are investigation directions, not diagnoses from a status code alone. A cached error and an origin error may look similar at the browser. Preserve the failing response before purging caches or changing routing. On hosted Shopify, do not assume merchants can access or alter origin-server configuration.
05Test one catalog path without confusing it with global discovery
Storefront Catalog MCP[4] is scoped to one merchant; cross-merchant discovery belongs to Global Catalog. Shopify documents that the storefront endpoint requires an agent-profile reference and that returned tools depend on advertised capabilities. Use the current live input schema rather than adapting an old copied payload by guesswork.
In an authorized test, select a product whose identity you already know. Compare its selected option, current price, currency, availability and destination URL with the storefront. Include a choice that should not be purchasable so that a permissive fallback cannot masquerade as success. Record the buyer context supplied; a response for another market is not a valid comparison.
Illustrative example: the profile loads, negotiation succeeds, and the catalog returns a product. Its default choice differs from the buyer's requested size. The discovery layer has passed, but selection has not. Repair that mapping rather than modifying the profile's version string or adding SEO text to the page.
06Cart and checkout tests need their own authorization
Catalog reads and cart or checkout creation are not the same kind of action. Prefer a test store and approved test data. Before any write, agree what can be created, who can inspect it and whether payment is prohibited. Stop before a real purchase unless that transaction is explicitly authorized.
Capture the selected item and quantity, the returned state, any required buyer interaction and the final handoff destination. An accepted request can still require further action. If a request times out, check the operation's documented state and retry semantics before sending another write; do not guess whether the first request succeeded.
Never put payment credentials, customer addresses, private checkout links or authorization headers into public screenshots or article evidence. The UCP specification separates protocol capabilities from transaction integrity and security obligations; a discovery-page audit cannot certify a payment integration.
07Copy this uCP boundary test record and fill in the brackets
UCP boundary test record
Public domain tested: [domain] Headless/other host: [domain or none] Owner: [name] /.well-known/ucp: status [n], content-type [x], redirects [chain], body digest [sha256], fetched [date time] Business profile version: [yyyy-mm-dd] Agent profile URL: [URL], version [..], publicly fetchable [yes/no] Negotiated capabilities: [list] Expected operation: [name], present [yes/no] Catalog test (known product): selected option [..], price [..], currency [..], destination URL [..] → matches storefront [yes/no] Should-not-be-purchasable case: [result] Cart/checkout: not exercised / exercised in test store [ID] with approval from [name], stopped at [state] Not tested: [list]
08Report exactly which boundary passed
A useful handoff names the tested domain, profile version/digest, client profile version, negotiated capabilities and sample outcome. It also states what was not tested. “Discovery and catalog lookup passed; checkout not exercised” is actionable. “AI-ready” without those boundaries is not.
Recheck after a relevant client, routing or platform change. A profile diff can signal a review, but an added compatible capability is not automatically an outage. Keep discovery failures, product mismatches and transaction failures separate so each reaches the correct owner.
Reviewed October 9, 2026. This is a source-based verification guide, not a test of a merchant or a protocol certification. No cart, checkout or payment was created for it. UCP does not replace accurate product markup, Merchant Center data or publisher discovery files, and this article makes no ranking or recommendation guarantee.
09Questions
Do Shopify merchants need to do anything for UCP?
For a standard Shopify storefront, Shopify's September 2026 update required no storefront configuration change. Investigate only if an actual integration fails.
What is the difference between the business profile and the agent profile?
The business profile is what the store advertises. The agent profile is what your client declares. Negotiation keeps only what both support.
Is a UCP profile an SEO ranking factor?
Nothing in the documentation reviewed suggests so. It is an interoperability document, not a substitute for accurate product pages or Merchant Center data.
Sources and what still needs a direct check
- Shopify developer documentation, September 4, 2026 Shopify announcement. Checked October 9, 2026.
- Shopify developer documentation, Shopify's negotiation documentation. Checked October 9, 2026.
- UCP specification, UCP specification. Checked October 9, 2026.
- Shopify developer documentation, Storefront Catalog MCP. Checked October 9, 2026.
Still to check yourself
- The live input schema of the catalog endpoint you call. Don't reuse an old payload.
- Who owns routing for the profile path on headless or proxied domains.
- Written approval before any cart, checkout or payment test.