UCP Cart and Order Capabilities
Understand how UCP advertises cart and order functionality and why capability declarations should match real endpoints.
Why it matters
UCP profiles advertise capability support alongside service bindings. Current shopping capability identifiers include cart and order, each versioned independently within the profile.
How it works
Cart operations and order retrieval or lifecycle events have different authorization and state-management concerns. A profile should advertise only capabilities that the implementation actually supports.
Practical takeaway
Static validation can detect missing versions, schemas and bindings, but live conformance still requires exercising the real service and its authentication, error and webhook behavior.
Use the tools, then verify against the protocol or platform you actually implement.Browse all tools