Skip to content

[DTC Charter]: B2B Procurement #947

Open

Description

@byteprincipal

Problem Statement

B2B procurement depends on fragmented integrations between procurement Platforms and supplier Businesses. Each integration independently models business identity, buyer eligibility, organization policy, business pricing, requisitions, approvals, purchase orders, post-purchase events, and reconciliation. This fragmentation increases implementation effort, slows onboarding, and produces inconsistent experiences as organizations adopt agentic procurement.

A shared B2B procurement protocol creates value for every participant:

  • Buying Organizations and their users: Procurement experiences preserve business policy, approval authority, pricing eligibility, cost allocation, and auditability across participating Platforms and Businesses.
  • Businesses: A common capability model replaces repeated point-to-point integrations for products, offers, order workflows, and post-purchase interactions.
  • Platforms: A consistent framework supports supplier capability discovery, governed requisitions, purchase orders, and lifecycle events without requiring a different interface for every Business.

UCP Strategic Fit

UCP provides a modular capability model, business profiles, shared commerce types, extension mechanisms, multiple bindings, and open governance. Procurement reuses product, price, address, identity, message, and order concepts while defining domain semantics that consumer shopping does not express. These semantics include requisitions, organization policy, approval boundaries, purchase orders, cost coding, post-purchase events, and reconciliation.

A dedicated B2B Procurement Tech Council gives Platforms and Businesses a shared venue to define these capabilities without creating point-to-point integrations. The council will reuse existing UCP primitives where their semantics hold, generalize cross-domain concepts when that benefits UCP, and define procurement-specific capabilities only where the domain requires them. Participants implement one shared model, reach multiple counterparties, and contribute to an open roadmap.

Use Case Roadmap

  • Phase 1: Procurement-Aware Discovery and Requisition Handoff
    • Buying organization aware catalog search and product lookup.
    • Machine-readable buyer eligibility, organization policy, business pricing, quantity, and delivery signals.
    • Separation of supplier-side cart or offer state from buyer-owned requisition and approval state.
    • Standard handoff from supplier results and cart candidates into a procurement Platform’s requisition workflow.
  • Phase 2: Requisition Through Purchase-Order Acknowledgment
    • Requisition lifecycle, business context, and cost coding.
    • Approval status and authorization challenges while approval authority remains with authorized humans and enterprise systems.
    • Purchase-order issuance, supplier acknowledgment, rejection, change requests, and order status.
    • Buyer and supplier identity, account linking, policies, and business-context propagation.
  • Phase 3 : Post-Purchase and Reconciliation
    • Fulfillment, shipment, receipt, returns, and substitutions.
    • Invoice submission, correction, and lifecycle events.
    • Purchase-order, receipt, and invoice reconciliation, including exception triage.
    • Buyer-initiated and supplier-initiated exception workflows.

Platforms

  • SAP
  • Zip
  • Lio
  • Vroozi
  • Procurify
  • ORO Labs

Businesses

  • Amazon

Commitment

  • By submitting this charter, the named platforms and businesses formally commit to a long-term collaboration focused on developing and actively promoting the industry-wide adoption of the primitives proposed by this Domain Tech Council (DTC).

Activity

  1. gsmith85 commented on Oct 16, 2026

    @gsmith85
    Contributor

    LGTM, this would be an exciting addition to the protocol.

    Some quick thoughts:

    1. B2B procurement has different payment modalities than B2C, so please work with the Payments Tech Council to make sure these new modes are well represented.
    2. To the extent possible, prefer extending existing Shopping capabilities. This avoids forcing businesses that participate in both B2B and B2C to build and maintain parallel stacks. For example, B2B catalog discovery could reuse dev.ucp.shopping.catalog while adding extensions for sub-org or cost-center scoping in identity and bracket-pricing tables.
    3. You have assembled an impressive industry group on the platform side, and bringing in a few additional suppliers could help lift adoption of the standard across the ecosystem.
  2. tc-steven-frechette commented on Oct 17, 2026

    @tc-steven-frechette

    TradeCentric supports this charter and would like to participate.

    We operate integration infrastructure between supplier businesses and procurement and ERP platforms, connecting suppliers to over 200 buy-side systems over cXML, OCI and EDI. We serve enterprise and mid-market manufacturers and distributors across a variety of industries.

    Two suggestions as the scope is finalized:

    1. Broader supplier-side representation. Today Amazon is the only named Business. Other suppliers, mid-market and enterprise alike, have materially different requirements: contract pricing across many buyer accounts, ERP-backed catalogs, and (especially in the mid-market) limited engineering capacity. We can help represent them and bring supplier customers' requirements into the discussion.

    2. An explicit interoperability scope item. Procurement platforms and suppliers will run UCP alongside cXML, OCI and EDI for years. Defining how Phase 1 to 3 primitives map to existing PunchOut, order and invoice messages, and where meaning would be lost in that mapping, would speed adoption and reduce risk for both sides.

    We'd welcome the chance to help with that mapping. Please let us know how organizations can be added as named participants.

    Steve Frechette, CPTO, TradeCentric

  3. amithanda commented on Oct 18, 2026

    @amithanda
    Contributor

    Thanks @byteprincipal for submitting the charter. UCP Governing Council (GC) is reviewing this charter and will reach out to follow up on this proposal.

  4. amithanda commented on Oct 18, 2026

    @amithanda
    Contributor

    4. TradeCentric supports this charter and would like to participate.
    We operate integration infrastructure between supplier businesses and procurement and ERP platforms, connecting suppliers to over 200 buy-side systems over cXML, OCI and EDI. We serve enterprise and mid-market manufacturers and distributors across a variety of industries.
    Two suggestions as the scope is finalized:
    1. Broader supplier-side representation. Today Amazon is the only named Business. Other suppliers, mid-market and enterprise alike, have materially different requirements: contract pricing across many buyer accounts, ERP-backed catalogs, and (especially in the mid-market) limited engineering capacity. We can help represent them and bring supplier customers' requirements into the discussion.
    2. An explicit interoperability scope item. Procurement platforms and suppliers will run UCP alongside cXML, OCI and EDI for years. Defining how Phase 1 to 3 primitives map to existing PunchOut, order and invoice messages, and where meaning would be lost in that mapping, would speed adoption and reduce risk for both sides.
    We'd welcome the chance to help with that mapping. Please let us know how organizations can be added as named participants.
    Steve Frechette, CPTO, TradeCentric

    @tc-steven-frechette - The nomination process that will be followed for new Domain Tech Council's (DTC) is defined here. You can also take a look at some of our recent DTC nominations as reference to get a better idea - Food and Lodging

  5. raj-zinzuvadia commented on Oct 19, 2026

    @raj-zinzuvadia

    Wholesale distribution is a big part of B2B buying that this charter should cover, and it looks different from the procurement suite flow in Phase 1. We're WayloAI. We work with wholesale distributors across the US and the businesses that buy from them, and we're building a business agent to business agent layer for their ordering. Their buyers are independent businesses ordering on account from a few distributors, mostly by rep, phone, text and EDI today, and their agents will want to read prices and order through UCP.

    That's the supplier side @tc-steven-frechette asked for more of, and we agree with his point on mapping to EDI. Where we can, we build on the existing catalog, checkout and order capabilities rather than new primitives, as @gsmith85 suggested.

    The charter already names eligibility, business pricing, PO acknowledgment and invoicing. The identity linking spec's B2B wholesaler example leaves eligibility, pricing and terms to each merchant at runtime, so an agent buying from several distributors has no standard way to read them. Here's what wholesale orders need that UCP doesn't carry yet. We're prototyping these as vendor extensions and would be glad to share schemas and what we learn.

    1. Buyer business identity: legal entity, ship-to locations, resale certificate, and the state licenses some products require, with expiry. Distributors often may only sell those products to licensed buyers.
    2. Credit on account: credit limit, available credit, overdue balance and hold status. dev.ucp.common.payment.terms covers when payment is due, not whether the account can buy. A hold should surface as requires_escalation, not a failed checkout. This is where B2B payment differs most, so it's a good item to take up with the Payments Tech Council as @gsmith85 suggested.
    3. Customer price lists: the buyer's price list or tier, and the bracket pricing that comes with it. The catalog :read scopes allow per account prices, but nothing names the list.
    4. Packs: each, inner pack and case with a GTIN per level, plus order multiples and minimums. quantity_unit.increment covers part of this.
    5. Backorder and substitution preference per line, and line changes at acknowledgment.
    6. PO number on checkout and order, with acknowledgment, ship notice and invoice objects that round trip to X12 850, 855, 856 and 810. Many buyers already run on EDI.
    7. Excise and other product taxes per line, as a type distinct from sales tax. Distributors pass them through on the invoice even when the buyer purchases for resale and pays no sales tax.
    8. Orders that didn't come from a UCP checkout. Most wholesale orders are placed by reps or EDI, and a linked buyer's agent should be able to read them. Today the order schema requires a checkout_id.

    Quotes (#929), price on request (#877) and handing an accepted quote into checkout (#845) all apply here too. We'd like to take part through the nomination process once the charter is approved.

  6. tc-steven-frechette commented on Oct 19, 2026

    @tc-steven-frechette
    1. TradeCentric supports this charter and would like to participate.
      > We operate integration infrastructure between supplier businesses and procurement and ERP platforms, connecting suppliers to over 200 buy-side systems over cXML, OCI and EDI. We serve enterprise and mid-market manufacturers and distributors across a variety of industries.
      > Two suggestions as the scope is finalized:
      > 1. Broader supplier-side representation. Today Amazon is the only named Business. Other suppliers, mid-market and enterprise alike, have materially different requirements: contract pricing across many buyer accounts, ERP-backed catalogs, and (especially in the mid-market) limited engineering capacity. We can help represent them and bring supplier customers' requirements into the discussion.
      > 2. An explicit interoperability scope item. Procurement platforms and suppliers will run UCP alongside cXML, OCI and EDI for years. Defining how Phase 1 to 3 primitives map to existing PunchOut, order and invoice messages, and where meaning would be lost in that mapping, would speed adoption and reduce risk for both sides.
      > We'd welcome the chance to help with that mapping. Please let us know how organizations can be added as named participants.
      > Steve Frechette, CPTO, TradeCentric

    @tc-steven-frechette](https://github.com/tc-steven-frechette) - The nomination process that will be followed for new Domain Tech Council's (DTC) is defined here. You can also take a look at some of our recent DTC nominations as reference to get a better idea - Food and Lodging

    Thanks @amithanda, that’s helpful. We’ll follow the nomination process once it opens, and in the meantime we’ll contribute to the B2B discussions where we can add value. Separately, is the participant list on this charter still open to additions before the Governance Council review, if supported by existing named participants?

  7. byteprincipal commented on Oct 20, 2026

    @byteprincipal
    Author

    Thank you @gsmith85, @tc-steven-frechette, @raj-zinzuvadia and @amithanda!

    @gsmith85, agreed on all three points. We'll work with the Payments Tech Council early, since payment terms, purchasing cards, credit on account and invoice-based payment cut across Phase 2 and Phase 3. On reuse, the charter commits the council to reuse existing UCP primitives where their semantics hold, so extending Shopping capabilities rather than building a parallel stack is the default we expect. We'd also welcome more suppliers through nominations.

    @tc-steven-frechette, thank you for the support. Contract pricing across many buyer accounts, ERP-backed catalogs and limited supplier engineering capacity are exactly the requirements the council needs to hear, and mapping the Phase 1 to 3 primitives to existing cXML, OCI and EDI messages is a natural topic for it to take up.

    @raj-zinzuvadia, thank you. Businesses buying on account from distributors are part of B2B buying, and several of your points line up with what the charter already names: buyer eligibility, business pricing, PO acknowledgment and invoicing. Credit on account also fits @gsmith85's point about working with the Payments Tech Council. We'd welcome your schemas and prototype findings in the council's discussions once it's seated.

  8. damaz91 commented on Oct 28, 2026

    @damaz91
    Contributor

    📋 Discussed in UCP Shopping Tech Council (STC) Meeting - 2026-10-16

    This issue was referenced under the following agenda topic(s):

    See the full meeting minutes for discussion notes and action items.

  9. damaz91 commented on Oct 29, 2026

    @damaz91
    Contributor

    📋 Discussed in UCP Shopping Tech Council (STC) Meeting - 2026-10-23

    This issue was referenced under the following agenda topic(s):

    • Direct-to-Consumer Proposals and Food Domain Feedback (view section)

    See the full meeting minutes for discussion notes and action items.

  10. evoleinik commented on Nov 3, 2026

    @evoleinik

    AirShelf supports this charter.

    We run the Business side of UCP for two B2B sellers. Neither seller publishes prices. Both have a live catalog and ask (dev.ucp.common.ask, merged after the 2026-08-25 release). One also has identity linking and a quote flow over MCP and chat, outside Cart and Checkout. No real buyers have used any of this yet. Three notes from this work apply to Phase 1.

    1. Unpriced catalog items. Some supplier catalogs, including both of these, list products whose price depends on the buyer, a contract, or a quote, or is shared only under NDA. Today, the catalog requires a price on every item. Our catalog omits the price and sends a disclosure message instead, which fails schema validation. We raised this in [Feat]: Catalog items with no public price ("price on request") #877, and @arjun2075 turned it into proposal [Proposal]: Caller-dependent catalog pricing states for price-on-request #969, which is still open.
    2. Buyer eligibility. For one seller, our deployment returns a price only after a buyer completes identity linking and accepts the seller's NDA. Before sign-in, a platform cannot tell what a seller requires. Here, the seller requires a work email and an NDA. Other sellers may require other steps, such as approval of each buyer by a person at the seller, or the buyer licenses raised earlier in this thread. We found no machine-readable state in the spec for a signed-in buyer who is still waiting for seller approval. Should a standard code for that state come through this council? Details and example responses are in Implementer notes: buyer eligibility for NDA-only B2B prices through identity linking #1028.
    3. Quotes as supplier-side offer state. On [Proposal]: Quote extension — Business-authoritative quotation binding on Cart and Checkout #929, we mapped our quote states to the proposal, using test data only. [Proposal]: Quote extension — Business-authoritative quotation binding on Cart and Checkout #929 allows expired only from quoted, so an unanswered pending request has no defined end. A request made in conversation also has no cart expires_at to limit polling.

    On @gsmith85's reuse point, our eligibility flow builds on identity linking with no new scopes or schema fields. Where UCP defines no message code, we used our own, listed in #1028. Our quote flow still runs outside Cart and Checkout, which is where #929 would attach it.

    AirShelf plans to apply for a seat when the public nomination round opens. Our corporate CLA is signed, and our first PR, #1044, passed the CLA check.

  11. amithanda commented on Nov 5, 2026

    @amithanda
    Contributor

    Hi @byteprincipal,

    GC has reviewed and approved this charter. As per the TC Election process, the next step here is for the GC to open up the nomination process for this DTC. I will update this charter when that is done and keep us posted on the nomination process.

  12. added
    gov:approvedTriggers the final code ownership checks
    and removed
    gov:needs-gc-reviewRequires review and approval from the Governance Council
    on Nov 5, 2026
  13. evoleinik commented on Nov 5, 2026

    @evoleinik

    For Phase 1's "machine-readable buyer eligibility" item, I filed #1047 as input. It adds a small extension with two account-status codes, account_pending and account_ineligible, and a hosted-step Action for signed-in buyers whose terms the business has not applied yet. It comes from an NDA-gated B2B seller we run (#1028), which already uses it. I'm glad for the council to take it over or reshape it.

  14. damaz91 commented on Nov 6, 2026

    @damaz91
    Contributor

    📋 Discussed in UCP Governing Council (GC) Meeting 2026-10-30

    This issue was referenced under the following agenda topic(s):

    See the full meeting minutes for discussion notes and action items.

  15. uzay-eth commented on Nov 7, 2026

    @uzay-eth

    Orkhon supports this charter. We build Usta, software for independent restaurant operators, and our team runs restaurants in Reno, Nevada, that order from broadline and local food distributors several times a week.

    Foodservice is a large part of B2B buying, and so far no one on this charter or in this thread represents it. @raj-zinzuvadia's list already covers credit on account, packs, PO round trips to X12 and per-line substitution preferences, and we agree with all of it. Foodservice adds a few needs that general wholesale and the procurement-suite flow don't carry:

    1. Cutoff and route. A restaurant's next delivery depends on the supplier's order cutoff and the route days for that ship-to location, and minimums or delivery fees often differ by route. Before checkout, an agent needs to read "confirmed by 4 pm Tuesday, delivers Wednesday 6-9 am" for the buyer's account. The charter lists delivery signals in Phase 1; cutoff and route belong there.
    2. Catch weight, estimated to actual. feat!: define sale-basis steps for quantities #653 handles goods sold by measured amount. Foodservice also sells by the case and bills by the pound: the buyer orders 2 cases of chicken at about 40 lb each, and the final line total is known only after the warehouse weighs the pick. That needs an estimated line total with a tolerance at checkout and an actual-weight adjustment on acknowledgment, ship notice and invoice. [Proposal]: Schema Extension for Variable-Yield/Catch-Weight Fulfillment and Programmable Authorization Holds #489 covers the payment-hold side of the same problem.
    3. Market-price items. Seafood and some produce are priced "market" and the price is fixed at acknowledgment, not at checkout. This is close to [Feat]: Catalog items with no public price ("price on request") #877 and [Proposal]: Caller-dependent catalog pricing states for price-on-request #969, with one difference: the item has a price, just not yet.
    4. Exceptions at the door. Shorts, damaged cases and temperature rejects are recorded at receiving, often with the driver present, and each one should open a credit request linked to the invoice line. In Phase 3 terms, receipt exceptions need to feed reconciliation directly.
    5. Order guides. Most restaurant orders start from the account's order guide (the supplier's list of items, pack sizes and prices for that buyer), not from catalog search. A readable order-guide resource would make Phase 1 discovery match how restaurants actually buy.
    6. The buyer is often one person. Phase 1 assumes a procurement Platform that holds requisition and approval state. Most independent restaurants have no procurement suite: the owner approves on a phone. The handoff should work when the buyer's agent is the Platform and approval comes from a single authorized human.

    We'd like to work these into concrete schema proposals that build on #653, #877/#969, #929 and dev.ucp.common.payment.terms, with examples from real restaurant orders, and to take part when the council's nomination round opens.

  16. uzay-eth commented on Nov 8, 2026

    @uzay-eth

    We filed #1060 as a first concrete input for Phase 1: pack content and net/drained weight on catalog items.

  17. damaz91 commented on Nov 10, 2026

    @damaz91
    Contributor

    📋 Discussed in UCP Shopping Tech Council (STC) Meeting - 2026-11-06

    This issue was referenced under the following agenda topic(s):

    • Approval of B2B and Services Domain Tech Council Charters (view section)

    See the full meeting minutes for discussion notes and action items.

  18. amithanda commented on Nov 14, 2026

    @amithanda
    Contributor

    Update: Nominations for the founding UCP B2B Procurement Tech Council cohort are now open through Nov 27, 2026! Please see the full announcement and application form here: #1094

    cc @byteprincipal

  19. damaz91 commented on Nov 16, 2026

    @damaz91
    Contributor

    📋 Discussed in UCP Governing Council (GC) Meeting 2026-11-13

    This issue was referenced under the following agenda topic(s):

    • B2B Procurement Domain Tech Council (DTC) Nominations (view section)

    See the full meeting minutes for discussion notes and action items.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

gov:approvedTriggers the final code ownership checks

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions