INDEPENDENT MERCHANT INTELLIGENCEPUBLIC BETA / SEPTEMBER 2026 BASELINE
readiness / Merchant field guide

B2B commerce merchant readiness

A practical review of product truth, public evidence and integration gaps for B2B commerce merchants.

Merchant answer / Evidence review pending

Account-specific prices, quotes and approval rules can make public evidence an incomplete picture. Separate the public catalog from contractual purchasing behavior. Map this role to your existing stack and confirm the exact version, access conditions and implementation scope before making a merchant decision.

What this establishes
A practical way to inspect evidence and make the next merchant decision.

What it cannot establish
An unresolved dependency remains. Treat affected claims as provisional. Live merchant deployment, private account eligibility, purchase completion or guaranteed AI selection.

Evidence dates and document versions remain attached to the ledger below. Editorial presentation reviewed 30 September 2026; this is not a new source verification.

Start with your deployed store

Account-specific prices, quotes and approval rules can make public evidence an incomplete picture. Separate the public catalog from contractual purchasing behavior.

Where the decision gets specific

An assistant may be able to discover a product without access to a negotiated offer. Do not expose confidential prices to improve a public scan result. Map who can view, request, approve and execute each action in the authorized environment.

Make the audit repeatable

Select a small sample that covers normal products, variants and an unavailable item. Record the exact page, market, time and expected values. Run the public check, then compare its findings with your own authoritative records. For each issue, identify whether the repair belongs in source data, a template, a mapping or an account setting. Preserve the report before making changes so that the next check measures a real difference.

What public evidence cannot establish

The L0 scanner cannot inspect private feed acceptance, authenticated account configuration, payment authority or completed orders. A blocked page is not proof of a missing capability. Confirm those questions through official merchant tools and scoped provider documentation. Treat any suggested candidate as a capability to investigate, not a ready-made endorsement.

Your next step

Evidence ledger

Go to the source.

Primary documentation records what is publicly stated. It does not independently prove outcomes or your account’s eligibility.

  • Agentic Payment Protocol v0.2

    AP2 project · official primary · Checked 2026-09-28

    Claim scope: Authorization mandates and receipts

    Payment authorization within a commerce protocol; catalog API details are out of scope.

    Source ID: ap2-spec · Published: Not stated

  • UCP overview, 2026-08-25

    UCP · official primary · Checked 2026-09-28

    Claim scope: Discovery profile and commerce capabilities

    Version-pinned profile discovery; declared capabilities do not prove successful transactions.

    Source ID: ucp-spec · Published: Not stated

  • Product vocabulary

    Schema.org · official primary · Checked 2026-09-28

    Claim scope: Product properties

    Vocabulary presence is not validation, eligibility or certification.

    Source ID: schema-product · Published: Not stated

Dispute a fact or suggest a source