All posts
AI search

AI Shopping B2B Products: What Can Buyers See?

AI shopping can surface some B2B products, but discovery, account access and negotiated pricing are separate capabilities.

STSearchFIT team15 minutes read

AI shopping B2B products can appear when a shopping channel can access their product information and an eligible catalog includes them. But a public product listing does not mean an AI can see a wholesale buyer’s private price or apply their account terms. Before launch, check catalog eligibility, price requirements, customer authentication and the route from product selection to checkout. You can also use SearchFIT’s free tools to check public crawler access and structured data, although those checks do not configure B2B commerce permissions.

For ongoing monitoring and content workflows, see SearchFIT pricing.

What does it mean for an AI shopping agent to show a B2B product?

It means different things depending on whether you are asking about discovery, product details, pricing or purchase. Treat those as separate stages, not one yes-or-no capability.

An AI assistant might find a public product page and mention the product in an answer. A shopping channel might instead draw from a structured product catalogue, where the merchant supplies fields such as product name, price and availability. An account-aware integration may go further by identifying a signed-in buyer and applying relevant benefits. A purchase flow then needs to carry the right product and price into a merchant-controlled cart, checkout or approval process.

These stages can be summarised like this:

StageWhat the AI or channel can doMain B2B question
Public discoveryFind and describe information available on public pagesCan the page be reached without a login?
Catalogue discoveryMatch a product from submitted product dataIs the item eligible, and what price must the feed contain?
Account-aware shoppingUse an approved identity or account connectionCan it identify the right company, buyer and price list?
Purchase assistanceHelp build a cart or continue to checkoutAre permissions and terms preserved through the transaction?

A product can be discoverable while its contract price remains private. It can also be present on your website but missing from a particular shopping catalogue. Always ask which stage a platform supports before promising that a buyer can shop your wholesale range through it.

Can AI shopping show wholesale products?

Sometimes, but there is no universal rule that makes every wholesale product eligible for every AI shopping experience. The answer depends on the channel’s catalogue rules, the product’s public information and whether the channel supports account-specific access.

A wholesale product with a public product page may be found through ordinary web discovery. That does not mean a shopping channel will accept it into its structured catalogue. Nor does it mean the channel can show a price reserved for approved trade customers. A product that requires a login may be inaccessible to a crawler or excluded from a catalogue that expects publicly reachable product pages.

For example, Shopify says its agentic storefronts support direct-to-consumer sales only. Products identified as B2B-only, including products limited to B2B catalogues or requiring customer authentication, are excluded. For a product offered to both retail and wholesale customers, Shopify says the storefront uses the D2C price, not the B2B price. Those are specific rules for Shopify’s agentic storefronts, not a rule that applies to every AI platform. Shopify’s product discovery guidance explains the distinction.

So, begin with the channel, not a general assumption about what AI can do. Ask the platform or integration provider whether your product type is eligible, whether a public price is mandatory and whether the experience supports authenticated business accounts. If the documentation only describes retail shopping, do not assume that it supports wholesale terms.

Can ChatGPT show products that need a wholesale login?

A public product feed can help ChatGPT discover products, but it does not automatically unlock a wholesale login or buyer-specific pricing. OpenAI’s November 2026 announcement about businesses in ChatGPT describes product feeds with pricing and availability. Its product-feed schema requires a current price and availability, and product and image URLs must be publicly accessible. OpenAI’s business announcement and product-feed specification describe those requirements.

That means a feed is a way to supply product information, not a substitute for the rules in your commerce platform. If a price is negotiated separately for each account, submitting one of those private prices as if it were a universal public offer could mislead buyers or expose commercial information. If you cannot safely publish one accurate price, check whether the particular channel offers another supported route before adding the item.

OpenAI also documents Sign in with ChatGPT for selected commercial partners. The feature can help a merchant link a user to an existing merchant account for purposes such as discounts, order tracking or checkout. The merchant still verifies or links the account, and identity verification is not the same as purchase approval. It is a partner-gated capability, so a standard product feed should not be treated as proof that account-specific wholesale pricing is available. See OpenAI’s Sign in with ChatGPT integration guidance.

For Shopify merchants, the platform’s current agentic storefront guidance is more direct: B2B-only products are excluded, while shared products use their D2C price. If a wholesale product needs private access or negotiated terms, do not assume that a public ChatGPT product listing will reproduce its usual account experience.

Can Gemini or Google AI Mode show a buyer’s member or contract price?

Google documents an integration capability that can support member benefits, including member pricing, but that is not a blanket promise that every B2B contract price will appear. Google’s Universal Commerce Protocol documentation describes Identity Linking as an optional capability. It can let a shopper receive the same member or loyalty benefits on an integrated platform as on the retailer’s site. The protocol also describes catalogue capabilities for product details such as variants, inventory and pricing. Google’s UCP updates explain those capabilities.

Merchants still need to implement and qualify for an integration. Google’s UCP integration overview says merchants need to prepare a Merchant Center account and product feed, and Google approval is required before an integration can go live on AI Mode in Search and Gemini. Identity Linking is optional. A public feed alone does not establish that the assistant can identify an approved wholesale buyer or select the right account terms.

Google’s September 16, 2026 update described Minted More member pricing appearing for signed-in loyalty members searching for holiday cards. That is an example of an integrated member-pricing experience. It does not establish support for every wholesale catalogue, negotiated contract or company-location price. The same update named Tapestry, owner of Coach and Kate Spade, as a retailer using UCP-powered checkout on Google Search, including AI Mode, and the Gemini app. Google’s shopping update is useful evidence of retail integrations, not a general B2B compatibility guarantee.

For a B2B merchant, the practical test is whether the integration can connect the correct business identity to the correct catalogue and terms, then preserve those details through checkout. A platform’s support for loyalty pricing is a promising technical pattern, but it is not proof that your own account structure is supported.

What is different about emerging B2B agent workflows?

Some commerce platforms are developing workflows for business buyers, but an early-access product is not the same as broad availability of B2B products in AI shopping results. The distinctions matter when planning a launch or setting expectations with sales teams.

Commerce announced on November 16, 2026 that its B2B Agent was in early access. Its announcement cited AS Colour as a business using the product to automate purchase-order workflows, and described business-buyer agentic experiences as being developed for complex catalogues, negotiated pricing and account requirements. The same announcement described its Shopping Agent as focused on B2C retail. Commerce’s announcement is a platform-specific example of emerging B2B workflow support.

A purchase-order workflow may help a buyer create or submit an order. It does not, by itself, mean that a product is included in a public AI shopping feed, appears in general search results or can be purchased by an unauthenticated user. Confirm what the product actually does, who can access it, which commerce systems it connects to and whether its pricing logic matches your contracts.

This is a useful distinction for merchants with complex catalogues. You may have a working agent-assisted reorder process for approved accounts and still have no public product discovery for those items. Conversely, an AI may find a public product page without being able to place a valid business order. Evaluate each use case on its own terms.

What should you check before adding B2B products to an AI catalogue?

Check catalogue eligibility, public access and price rules before submitting product data. Then check how the channel handles buyer identity and the route to purchase.

Start by classifying every product you plan to expose. Useful categories include public retail products, products sold to both retail and wholesale customers, B2B-only products, login-gated products and quote-only products. This simple classification helps you see where one public feed could create a price or access mismatch.

Then answer these questions for each channel:

  • Is the product included in the channel’s structured catalogue, or only available on your website?
  • Can an unauthenticated visitor reach the product page and its images?
  • Does the channel require a numeric price and an availability status?
  • Can it accept B2B-only products, or does it exclude account-gated items?
  • If a product has retail and wholesale prices, which one will be shown?
  • Does the integration support sign-in or account linking for your kind of buyer?
  • Can it distinguish company accounts or purchasing locations when they have different terms?
  • Does the shopping experience send the buyer to your checkout, create a cart or support a quote request?

Do not treat an AI-generated description of a product as evidence that the channel has the right price. Discovery may use public text, while a product card may use a feed and an account-aware integration may use yet another source. The source of truth for each piece of information needs to be clear.

Document the answers alongside the product classification. For instance, a retail product might be approved for a public catalogue at its retail price; a wholesale-only item might remain behind an authenticated portal; and a quote-only product might have a public explanatory page but no catalogue offer. The right choice depends on the platform’s rules and your commercial policy.

What happens when a B2B product has no public price?

A product without a public price may still be described on a public webpage, but it may not meet the requirements of a product feed that requires a numeric price. OpenAI’s product-feed schema requires a current price and availability for each item, so a contact-for-pricing message is not a replacement for the required feed fields. See the OpenAI product-feed schema.

Do not invent a price simply to fill a required field. A starting price can also be misleading if the conditions that determine it are not obvious or if buyers cannot actually purchase at that price. If the platform accepts a public price, confirm that it is accurate for the audience and transaction represented by the feed. If not, ask whether quote-led discovery is supported or keep the item out of that catalogue.

Keep public explanations useful even when price is private. A product page can explain what the item does, who it is for, what configuration choices exist and how an approved business buyer can request a quote. Make clear whether pricing depends on volume, configuration, location or a commercial agreement, if that is how your own offer works. These details help a human buyer understand the next step and give public discovery systems accurate context, without publishing a confidential offer.

Also separate a public reference price from a negotiated price if your business uses both. The page and feed should not imply that the public figure applies to every account when it does not. Your sales, ecommerce and marketing teams should agree on the wording and data source before any product is submitted.

How can an AI shopping agent know which wholesale price applies?

It needs a supported way to identify the buyer and retrieve the right account context; a product feed with one price cannot infer private contract terms. Shopify’s B2B guidance says wholesale customers sign in to access B2B-specific information such as products and pricing, and that a company location can determine which catalogue applies. See Shopify’s guidance on B2B sign-in and customer accounts.

For an account-aware experience, test the complete chain rather than stopping at sign-in. The integration needs to authenticate the customer, link them to the correct merchant record, identify the relevant company and purchasing location, and return the right products and prices. It then needs to retain those permissions when the buyer makes a cart, requests a quote or goes to checkout.

OpenAI’s commerce plugin guidance describes structured product lookup that can return current price and availability for a requested customer context. Its sign-in guidance also makes clear that identity and purchase approval are separate. That distinction is important: recognising a customer does not necessarily authorise an order or mean the right person can accept the business’s purchasing terms. See OpenAI’s plugin-building guidance and its Sign in with ChatGPT documentation.

Use real test accounts where possible. Test an approved buyer, an unauthenticated visitor and accounts with different company or location permissions. Confirm not only the price that appears, but also which catalogue is returned, whether restricted products are hidden and what happens when a buyer attempts to continue without the required approval.

Can a product sold to retail and wholesale buyers show its wholesale price?

Not necessarily. In Shopify’s agentic storefronts, a product sold to both D2C and B2B customers uses the D2C price. That means a merchant should not expect the storefront to infer a particular buyer’s negotiated wholesale price from a shared product listing. Shopify documents this behaviour in its agentic storefront product guidance.

Mixed-channel products deserve special attention because the product itself may be public while its commercial terms are not. Check the catalogue mapping, price field and product eligibility for each channel. Make sure the public offer is the price you intend an unknown shopper to see, and that wholesale buyers are directed to the authenticated route that applies their terms.

Shopify also warns that custom themes or third-party apps that hide products or prices can make B2B products harder for Shopify to identify. A product could appear unexpectedly if the platform does not recognise the way the store implements its restrictions. This is a reason to test actual results after changes to theme code, access rules or commerce apps, rather than relying only on your intended configuration.

If showing the retail price is inappropriate for a product, do not assume a visual hide or custom template is enough to keep it out of a catalogue. Check the platform’s documented exclusion controls, inspect the submitted product data and verify what a logged-out visitor can access.

How do you keep wholesale-only products out of AI shopping results?

Use the channel’s documented catalogue controls and verify the result; hiding a product in a theme may not reliably exclude it. Also check what each exclusion does to ordinary web discovery.

Shopify says merchants can mark products Unlisted to hide them from AI discovery, but warns that this also hides them from sitemaps, search engines such as Google and online-store search. That broader impact matters if you want the product page to remain available to approved buyers or discoverable through other search routes. Review Shopify’s explanation of product discovery controls before choosing this approach.

For each product, decide which outcome you want:

  • Keep the product and its page public, but exclude it from a particular shopping catalogue if the platform supports that distinction.
  • Keep product information public while directing buyers to request a quote or sign in for account terms.
  • Restrict the product page itself when its existence or details should not be public.
  • Include a shared product at its appropriate public retail price, while handling wholesale pricing through a separate approved route.

Do not rely on one control to solve every discovery problem. Catalogue inclusion, page access, crawler access, search indexing and account permissions are different settings. An exclusion from a shopping feed may not remove a page from ordinary web discovery, and hiding a page more broadly may affect Google and other site search. Test the intended outcome in both the AI channel and conventional search.

How should you test AI shopping for B2B products before launch?

Run tests with different product types and buyer states, and follow each result through to the next step in the buying journey. A product appearing in a result is only one part of a successful B2B experience.

A practical pre-launch test can follow this sequence:

  1. Classify products as public retail, shared retail and wholesale, B2B-only, login-gated or quote-only.
  2. Review the AI channel’s catalogue and feed rules, including eligibility, price and availability requirements.
  3. Check the actual submitted catalogue for missing items, incorrect prices or products that should be private.
  4. Open product pages while logged out and as an approved buyer. Check images and important details as well as the page itself.
  5. Test different business accounts or company locations if they use different catalogues, prices or permissions.
  6. Add a product to a cart or follow the quote and checkout path. Confirm that the selected price and restrictions remain correct.
  7. Check how product descriptions and prices appear in the AI experience, then record the result and the account context used.
  8. Repeat the checks after meaningful changes to product data, themes, access rules or commerce integrations.

Keep a simple record with the product, channel, account state, intended result and observed result. If a product should not appear to an unauthenticated buyer, note whether it is absent from the catalogue and inaccessible on the public page. If a shared item should appear at a retail price, check that the displayed price matches the intended public offer. This gives ecommerce and sales teams a common way to spot gaps.

Monitor referrals and customer questions as well. If an AI result sends a buyer to a public product page but the buyer expects wholesale pricing, the page should make the account-specific next step easy to find. If buyers arrive with an incorrect expectation, review the product description and the data supplied to the channel before changing access controls.

Which checks can help with public discovery and structured data?

Crawler and structured-data checks can help you find public-page issues, but they cannot grant an AI agent permission to access a private catalogue. Use them to diagnose the discoverability layer, not to validate account-specific commerce logic.

SearchFIT’s free AI Crawler Checker and JSON-LD Validator can help assess crawler access and page structured data. Its AEO Grader can provide a baseline for how a brand appears in AI answers. These checks do not authenticate wholesale buyers, publish a private price or configure a commerce platform’s B2B catalogue.

A crawler check can be useful when a public product page should be available but you are unsure whether relevant crawlers can reach it. Structured data can help make public product information clearer to systems that process it. Neither one overrides a login, tells a channel which company catalogue to use or proves that a feed has been approved.

Keep technical checks alongside a commerce review. Confirm the product feed itself, inspect the channel’s catalogue rules, sign in with representative business accounts and verify the final cart or quote flow. For teams working across product pages and search visibility, SearchFIT’s ecommerce resources can also help connect site optimisation work with the broader customer journey. For a broader content review, see SearchFIT’s AEO content audit guide.

What should B2B merchants conclude about AI shopping?

AI shopping can show some B2B products, but public discovery, catalogue inclusion, buyer authentication and negotiated pricing are separate problems. A public product feed is most straightforward when you can safely supply one accurate price and availability state. When products or prices depend on an approved business account, look for a supported account-aware integration and test it against real buyer contexts.

The platform rules matter. Shopify says its current agentic storefronts are for D2C sales: B2B-only products are excluded, and shared products use the D2C price. Google’s UCP documents optional identity linking for integrated member benefits, but that is not a guarantee that every wholesale pricing model is supported. Commerce’s announced B2B Agent is an early-access, platform-specific example of agent workflows for business buyers, not evidence that all B2B products are broadly available in AI shopping.

The safest approach is to decide what each product is allowed to reveal, check the channel’s exact requirements, then test discovery and purchase separately. Do not send a private contract price as a universal public offer, and do not assume that hiding a page from one shopping catalogue will leave every other search surface unchanged.

For a practical next step, use the SearchFIT free tools to check public crawler access and structured data, then validate catalogue eligibility, account identity and checkout behaviour with your commerce platform. Treat those as complementary checks: one helps assess what public systems can reach, while the other determines what a real business buyer is allowed to see and buy.

Get SearchFIT Weekly

What we are learning about getting brands cited in AI search, in your inbox every week. Unsubscribe any time.