Spec versions
Which UCP releases are stores running? Across the web from our monthly market read, and across the stores we check.
The Universal Commerce Protocol uses date-based versions (YYYY-MM-DD). The protocol, capabilities and extensions version independently, so a store can run the latest checkout capability on an older protocol release. Stores can also declare supported_versions for backwards compatibility. Check your profile against any release with the UCP Validator.
98.6%of the 1.2 million valid UCP profiles across the web are on 2026-08-25 (November 2026)
1.4%of the 1.2 million valid UCP profiles across the web are on 2026-04-08 (November 2026)
2026-08-25
current
Also supports 2026-01-23, 2026-04-08, 2026-08-25
2026-04-08
Also supports 2026-04-08, 2026-01-23
2026-01-23
Also supports 2026-01-23, 2026-04-08, 2026-01-11
2026-01-11
How does UCP versioning work?
Releases are dated
YYYY-MM-DD. The protocol, individual capabilities and extensions can each version on their own. Adding optional fields or endpoints is backwards compatible; removing fields or changing types is a breaking change.Can a store support more than one release?
Yes. A store declares one primary version in its profile and can list
supported_versions for backwards compatibility, each with its own profile URL, so agents can choose which to use.What happens when a new release comes out?
Official
dev.ucp.* capabilities version with the protocol by default; vendor capabilities (com.{vendor}.*) version on their own. A store should update the version in its profile when it adopts a new release.