Sponsored placement / ranking provenance on catalog search results — in scope?

[archerII]

I'm evaluating UCP for a buyer-side agent that shops on behalf of a user with an explicit ranking preference (e.g., "camera quality matters more than brand").

Before asking, I checked docs/specification/catalog/search.md and the search request/response scaffolds: the only ranking-related language I found is that filter-only queries return products "without text-relevance ranking," and I couldn't find any field marking a result as sponsored, boosted, or otherwise commercially incentivized. Apologies if I missed it in another schema.

Three concrete questions:

1. Is there a field (current or planned) exposing sponsored/paid placement or ranking provenance on catalog search results?
2. If such metadata exists or gets added, would it be normative (MUST when applicable), or optional — i.e., could a conformant business omit it while returning commercially influenced ordering?
3. Is there any mechanism for the buyer-side agent to request a neutral ordering (or to learn what the ordering criterion was), or is result ordering entirely business-defined and opaque by design?

Context for why I'm asking: an agent that picks the top-ranked result satisfying its hard constraints will systematically absorb the business's ranking preferences into what looks like a neutral choice. If ranking incentives aren't machine-readable, the agent can violate its user's stated preference order without any protocol violation on either side. I'd like to understand whether that is considered in scope for UCP's catalog capability, or intentionally left to marketplace regulation / implementer policy. Either answer helps.

[yhay81]

Reading the current published specification literally, the answers are:

1. No standardized field today. The Catalog Search response contains products, pagination, and optional messages; the standard Product fields do not include sponsored placement, boost reason, rank score, or ranking provenance. A business could place private data in product.metadata, but that is explicitly business-defined and is not an interoperable disclosure signal.
2. No current conformance requirement to disclose commercial influence. Because the base schema has no such field or condition, a business can return commercially influenced ordering and still conform to the current Catalog Search capability.
3. No neutral-ordering or sort criterion request today. The standardized request inputs are query, context, signals, attribution, filters, and pagination. There is no sort, ranking_policy, or neutral input, and no response field identifying the criterion used.

The sentence about filter-only browse requests being returned ‘without text-relevance ranking’ does not imply a neutral order. It only says that there was no text query from which to compute text relevance; the business still chooses the order. The catalog overview also says that ordered arrays put the most relevant item first and that, for search, the best match is based on query and context—without specifying or exposing the scoring function.

Relevant current sections:

• Catalog Search request/response and Search Inputs
• Product fields and ordered-array semantics
• Published roadmap (which currently does not list ranking transparency or sponsored placement)

I cannot answer whether the working group plans this beyond the published roadmap, but I do not see evidence that it is intentionally guaranteed to remain opaque either. Today it is simply unspecified by the base capability.

The protocol already has a clean way to add it: a negotiated Catalog Search extension. For example, an extension could add:

{
  "ranking": {
    "requested_objective": "user_preference",
    "preferences": ["camera_quality", "brand"]
  }
}

and a per-result disclosure such as:

{
  "placement": {
    "kind": "sponsored",
    "sponsor": "seller-or-campaign-id"
  },
  "ranking": {
    "criterion": "business_relevance",
    "organic_position": 4
  }
}

For this to solve the trust problem you describe, the extension would need a normative rule such as MUST disclose when payment or another commercial incentive changed inclusion or order. Making the fields optional would not let a buyer agent distinguish ‘organic’ from ‘undisclosed.’ The request side should also distinguish ‘apply these user preferences’ from ‘return a business-neutral order’; the latter may be impossible for some implementations, so the response needs an explicit supported/applied value rather than silent fallback.

Until such an extension is negotiated, a buyer agent should treat result order as business-selected—not as evidence of neutral quality—and re-rank returned candidates itself using product attributes. That still cannot recover products displaced from the returned page, which is why disclosure/request semantics belong at the protocol level rather than only in agent policy.