The Better Supply Path May Suddenly Look Longer.
A programmatic supply path may become longer on paper because it became more honest.
That is the operational tension inside IAB Tech Lab’s proposed SupplyChain 1.1 update. The specification expands the familiar schain object beyond the parties paid in a transaction to include certain companies that take technical custody of a bid request.
Buyers may see more nodes, not because more intermediaries appeared, but because infrastructure that already handled the request is finally being named. (IAB Tech Lab announcement, June 23, 2026)
This is a decision memo for media buyers, publishers, agencies, and ad-tech teams. The decision: stop using chain length as a proxy for supply quality before the transparency upgrade makes that shortcut actively misleading.
Decision: Retire the Shortest-Chain Reflex
Supply-path optimization has often treated fewer hops as cleaner economics. That can be sensible when extra nodes represent redundant reselling, hidden fees, or duplicate access to the same impression.
SupplyChain 1.1 complicates the picture by disclosing technical custody as well as payment flow.
The proposal uses hp=1 for a node in the direct payment chain and hp=0 for a custody-taking entity outside that chain—for example, some wrappers, ad servers, SSAI platforms, SDKs, or mediation layers.
The implementation guidance says all third parties that take control of a bid request must be listed, whether their code operates client-side or server-side. Systems that only provide data or recommendations without controlling the request remain outside scope.
A buyer that penalizes every additional node equally will therefore punish disclosure. The scoring model must distinguish paid intermediation from technical custody before it decides whether a longer path is wasteful.
What Changed: Custody Joins Commerce
SupplyChain 1.0 primarily described the commercial route. Version 1.1 preserves those nodes and adds the systems able to initiate or route a bid request. The order of hp=0 nodes follows the outbound request sequence, which may differ from the payment sequence.
Consecutive unpaid nodes operated by the same company are collapsed; paid and unpaid roles held by the same company remain separately represented. (IAB implementation rules)
The validation burden also changes. The proposal does not require an ads.txt authorization record for hp=0 nodes, while strongly recommending corresponding sellers.json entries.
A new version marker and expanded completeness language allow systems to distinguish chains that include paid and unpaid custody nodes. The public-comment record says the comment period closes August 21, 2026. (Public-comment record)
What changed is not the auction itself. The record traveling with the request became more expressive.
What Did Not Change: Disclosure Is Not a Verdict
A complete custody map does not establish that every disclosed partner adds value. It does not measure latency, auction quality, fee efficiency, duplication, fraud, or campaign performance. It identifies who could control or route the request; it does not decide whether that control was necessary.
Nor does a longer v1.1 chain automatically signal a worse path.
IAB Tech Lab’s own rollout announcement warns that chains may lengthen as transparency improves and recommends staged testing, parsing validation, bid-health monitoring, and progressive scaling between SSPs and DSPs. (Official rollout guidance)
Analysis: the new object improves the evidence available to supply-path decisions, but it cannot replace those decisions. Node purpose, performance, economics, and duplication still require interpretation.
The Leverage Moves to Better Questions
Buyers gain a way to separate “who was paid?” from “who controlled the request?”
Publishers gain a stronger record of the infrastructure through which their inventory travels. Infrastructure providers gain visibility—but also scrutiny—because technical participation that previously disappeared behind a paid seller can become legible.
The risk moves toward three groups: platforms whose parsers assume every node needs ads.txt validation; buying systems that reject longer chains without reading hp; and commercial teams whose contracts name sellers but ignore custody-taking technology.
A transparent path could lose demand simply because an old filter mistakes new disclosure for new complexity.
For OrionPilot, the relevant discipline is upstream of execution: keep the campaign’s media assumptions beside its audience, evidence, constraints, and measurement plan, then treat a supply-path rule as a declared buying policy—not an invisible platform default.
That makes a future change in accepted custody, duplication, or verification standards a decision the strategy can absorb rather than a silent rewrite of the campaign.
The Urgent Decision Is a Parser Test
Before the public-comment window closes, ask every DSP, SSP, measurement partner, and programmatic operations owner four questions.
Can the system ingest version 1.1 without dropping or misclassifying hp=0 nodes?
Does supply-path scoring separate payment from custody?
What happens when a chain becomes longer but more complete?
Which partner owns the investigation when two visible paths appear duplicative?
Then replay historical buying rules against representative v1.1 examples.
The IAB implementation repository includes web, mobile, and CTV paths precisely because custody behaves differently across wrappers, SDKs, ad servers, and SSAI systems. (Official example set)
Analysis: the immediate commercial danger is not that an unseen intermediary will suddenly appear. It is that a newly seen intermediary will be judged by a rule written for something else.
Transparency has changed the shape of the evidence. The buying policy now has to prove it can read.
Comments