When a True Citation Produces a Bad Buying Decision

Hallucinations are easy to recognize because something was invented. The subtler failure is harder to spot: the evidence is real, the citation is accurate, and the buying conclusion is still unsupported.

VendorAgent · September 13, 2026

Consider the kind of information a B2B software company publishes every day. There may be an uptime commitment, a support-response target, a compliance capability, a European region, several retention periods, and a pricing table. Each statement can be correct while belonging to a different plan, service, data type, contract, support tier, or customer state.

Once those conditions are stripped away, the buyer is no longer using the same fact the seller published. It is using a broader version of that fact that the evidence never established.

The citation can survive while the meaning drifts.

A familiar example: one acronym, two promises

Suppose the lower-priced plan includes a support SLA, while Enterprise carries the contractual 99.99% uptime commitment. A buyer asks whether the lower plan satisfies a contractual 99.99% availability requirement. The model finds both pages, notices “SLA” in each place, and combines the cheaper plan with the stronger promise.

Nothing had to be fabricated. The error came from treating two scoped commitments as though they were one vendor-wide entitlement.

What a safer representation preserves

Rather than storing the percentage alone, a procurement system may need the surrounding state:

availability_sla = 99.99%
plan = enterprise
service = covered_services
contract_state = applicable_agreement
effective_date = current

The first line is the memorable part, but the remaining lines keep that number from becoming a promise the seller never made.

Compliance creates the same problem in a different form

A vendor may genuinely support regulated workloads and still require a specific plan, executed agreement, add-on, deployment, or customer configuration before a particular workload qualifies. If a buying system turns “capability available” into “this account is ready,” it has promoted one true statement into a stronger statement without evidence.

Geography and retention are especially easy to overgeneralize

Broad regional labels can hide narrower jurisdiction questions, and a retention figure may describe archives while searchable logs follow a different clock. Platform-level claims create similar trouble when only certain services or components are actually covered. Human readers often recover these distinctions from the surrounding page; automated buyers need them carried forward explicitly.

Pricing errors can look mathematically flawless

The buyer might calculate self-serve usage perfectly and then attach Enterprise support, a negotiated SLA, or a custom entitlement to that result. Every number in the spreadsheet can be correct while the assembled commercial state is impossible. In cases like this, arithmetic quality tells you almost nothing about decision quality.

The category is moving beyond demos

BCG's 2026 procurement research describes enterprises moving agentic AI from pilots toward production and identifies data quality, integration, process redesign, capability building, and governance as scaling constraints. Oracle's 26C Supplier Qualification Workspace uses AI to summarize supplier qualification, flag missing or adverse qualifications, and recommend actions, while explicitly telling users to review those recommendations before applying them.

Research is also exploring multi-agent vendor evaluation. A 2026 Scientific Reports paper describes a multi-agent LLM framework spanning financial, risk, sentiment, and benchmarking analysis. At the payment layer, Visa, Mastercard, and Ant International announced work on identifying and verifying purchasing agents, while Reuters reported that India's NPCI is developing a registry for AI agents that transact through UPI.

Authentication solves a different problem

Knowing who the agent represents can establish that the buyer authorized it to act. The seller still has to determine which facts govern the request and what may safely be promised in response. Scope, provenance, freshness, policy, and seller-side authority remain necessary even after identity is settled.

Some questions should end in clarification

Not every procurement request contains enough information to produce a deterministic answer. The plan may be missing, two authoritative sources may conflict, the customer's contract state may be unknown, or a requested concession may sit outside delegated seller authority. In those situations, clarification or escalation is not a failure of automation; it is the more accurate outcome.

A simple test for your own public surface

Choose one product and ask ten realistic questions that combine pricing, plan boundaries, uptime, support, compliance, geography, retention, and custom terms. Then ignore how impressive the citations look for a moment. Did every material condition attached to the cited fact make it into the final conclusion?

If the answer can change while every cited sentence remains true, you have found a scope problem.

Test one product

VendorAgent's $250 AI Buyer Failure Scan runs 10 public-information buying scenarios against one B2B SaaS/API product and reports the strongest scope failures the evidence can support.

Request a Failure Scan

Sources