UCP B2B Procurement Council Approved: What Happens Next for Business Buying

Business buying now has a council on the way. On 5 November 2026, Amit Handa wrote on the B2B Procurement charter that the UCP Governing Council "has reviewed and approved this charter". The next step is for the Governing Council to open nominations for the council's members.

That makes B2B Procurement the fourth industry council approved, after Food, Lodging and, a day earlier, Local Services. There is still no B2B spec of its own. Here is what was approved, how it got here, and what happens next.

#What was approved?

The Governing Council approved a charter for a B2B Procurement Domain Tech Council: a standing council that will own how organisations buy from suppliers through agents. The charter was filed on 14 October 2026 as issue #947, and the Shopping Tech Council's minutes describe it as sponsored by Amazon. It names six procurement platforms (SAP, Zip, Lio, Vroozi, Procurify and ORO Labs) and one business, Amazon.

The scope is the work consumer shopping doesn't express: buyer eligibility and organisation policy, business pricing, requisitions, approvals, purchase orders, cost coding, post-purchase events and reconciliation. The charter commits the council to "reuse existing UCP primitives where their semantics hold" and to define procurement-specific capabilities only where the domain requires them. We went through the charter in our post on what it proposes.

#How it got here

Three points were settled along the way.

Extend shopping, don't fork it. Greg Smith's review asked the council to "prefer extending existing Shopping capabilities", so that businesses selling to both consumers and businesses don't have to build and maintain parallel stacks. His example: B2B catalog discovery could reuse dev.ucp.shopping.catalog, with extensions for cost-centre scoping and bracket pricing. The charter owners agreed that extending shopping "is the default we expect".

Payments come in early. B2B pays differently: payment terms, purchasing cards, credit on account and invoices. The review asked the council to work with the Payments Tech Council, and the owners said they would do so early, since those modes run through the charter's second and third phases.

More suppliers, and people who know UCP. The review noted a strong platform side and only one named business, and suggested bringing in more suppliers. The owners pointed to nominations. Separately, the Governing Council recommended including members with UCP experience on all new councils, "as has been followed for all new DTCs such as Food and Lodging."

Four companies posted support or input on the issue while it was under review: TradeCentric (integrations between suppliers and procurement systems over cXML, OCI and EDI), WayloAI (wholesale distributors and the businesses that buy from them), AirShelf (two B2B sellers already on UCP) and Orkhon (restaurants ordering from food distributors). Two filed first inputs for the council's first phase: account status for signed-in buyers (#1047) and pack content and weights on catalog items (#1060).

#What happens next

The Tech Council election process sets the order. The Governing Council sets a date and shares a nomination form on the UCP announcement board, and organisations apply by the deadline. The criteria include commitment to an open, vendor-neutral ecosystem, contributions to the protocol through issues and PRs, representing a large established ecosystem in the domain, and bringing the expertise the council needs. Members sign UCP's contributor licence agreement before the first meeting. As of 11 November, the nomination call hasn't been posted.

Once seated, the council starts on the charter's first phase: procurement-aware discovery and the handoff into a requisition. That means catalog search and lookup aware of the buying organisation; machine-readable eligibility, policy, pricing, quantity and delivery signals; supplier-side cart or offer state kept apart from the buyer's requisition and approvals; and a standard handoff from a supplier's results into a procurement platform's workflow. Requisitions through purchase-order acknowledgment come second, and receipts, invoices and reconciliation third.

#What it means for suppliers, procurement platforms and agent builders

For procurement platforms and suppliers: this is the window to take part. The nomination form decides who writes the spec, and the review asked for more suppliers on it.

For businesses selling to other businesses today: a fair amount already works on the released spec. Identity linking lets a signed-in business account see its own prices, and payment terms (dev.ucp.common.payment.terms) can carry Net 30 against an invoice. We walked through both on a test wholesale store in UCP for B2B: an agent buys on net 30 terms. Requisitions, approvals and purchase orders wait for the council.

For agent builders: keep the line between the released spec and proposals. Quotes (#930), price on request (#969), invoice payment (#957) and account status (#1047) are open proposals, not part of any release.

#What we'll watch

• The nomination call on the UCP announcement board, and who is seated, including how many suppliers.
• How the council works with the Payments Tech Council on terms, purchasing cards and invoices.
• The first B2B capability filed as a PR, and whether it extends shopping's catalog and checkout as the review asked.

Our UCP for B2B page tracks it as it moves.

#FAQ

Is there a UCP B2B council? It has been approved, not yet seated. The Governing Council approved the B2B Procurement charter on 5 November 2026. Nominations for its members come next.

Who is behind the B2B Procurement charter? The Shopping Tech Council's minutes describe it as sponsored by Amazon. It names SAP, Zip, Lio, Vroozi, Procurify and ORO Labs as platforms, and Amazon as the business.

Does UCP support B2B buying yet? Partly, through the released spec: identity linking for account pricing, and payment terms for Net 30. Requisitions, approvals, purchase orders and invoicing aren't in the spec; they are the council's work.

Will B2B be a separate protocol from shopping? The review asked for the opposite: extend shopping capabilities where possible, so businesses selling to consumers and to businesses keep one stack. The charter commits to reusing UCP primitives where their semantics hold.

How do companies join the council? Through the Tech Council nomination process: the Governing Council posts a nomination form on the UCP announcement board, and organisations apply by the deadline it sets.

What does the council work on first? Procurement-aware discovery and the handoff into a requisition: catalogs that know who is buying, eligibility and pricing signals, and a standard way to pass a supplier's results into a procurement platform.

#About UCP Checker

UCP Checker is the independent validation and observability layer for the Universal Commerce Protocol. We crawl, validate and grade every public UCP manifest we can find, run the merchant directory, the UCP Score, live adoption stats, the vertical guides and the authority-bound vendor map, and track the spec as it evolves so you don't have to — measured from two vantages (what a business declares, and what actually happens when an agent transacts), the same way for everyone, without picking winners.

#Sources

• Issue #947: [DTC Charter]: B2B Procurement, UCP GitHub, filed 14 October 2026; approval comment, 5 November 2026.
• Shopping Tech Council meeting, 16 October 2026. UCP meeting minutes.
• Governing Council meeting, 30 October 2026. UCP meeting minutes.
• Shopping Tech Council meeting, 6 November 2026. UCP meeting minutes.
• Tech Council election process. UCP governance.
• Issue #1047: account status for signed-in buyers. Open proposal.
• Issue #1060: pack content and net/drained weight for catalog items. Open proposal.

Related coverage: UCP for B2B: a procurement council charter, quotes and price on request · UCP for B2B: an agent buys on net 30 terms · UCP Local Services council approved