'%20clip-path='url(%23canvas-clip)'/%3e%3cg%20clip-path='url(%23canvas-clip)'%3e%3cg%20transform='rotate(0,%20256,%20256)'%3e%3cg%20transform='translate(87%2087)%20scale(14.083333333333334%2014.083333333333334)%20translate(0%200)'%3e%3cpath%20fill='none'%20stroke='%23FFFFFF'%20stroke-linecap='round'%20stroke-linejoin='round'%20stroke-width='2'%20d='m18.064%2010.877l-4.89-7.26c-.42-.625-1.287-.803-1.936-.397a1.4%201.4%200%200%200-.41.397l-4.893%207.26C4.24%2013.715%204.9%2017.318%207.502%2019.423a7.13%207.13%200%200%200%204.168%201.572M15%2018a3%203%200%201%200%206%200a3%203%200%201%200-6%200m5.2%202.2L22%2022'/%3e%3c/g%3e%3c/g%3e%3c/g%3e%3c/svg%3e)
Shopify B2B Search Eligibility: Markets, Catalogues, Customer Context, and Price Truth
A product existing in Shopify does not mean it is eligible for every B2B buyer. Eligibility is the hard boundary before matching and ranking: market, publication, company location, catalogue, price, inventory, and customer context must all agree. Only then can search answer which eligible item best satisfies the request.
This guide traces that boundary from source record to cart. It is the companion to the parts and compatibility guide, which proves whether an item fits. Here the question is different: may this buyer see and act on it under the current commercial context?
Decision rule: treat eligibility as a separate proof. Never use a broader match, a cached price, or a public product record to bypass the active buyer's market and catalogue.
Chapter 1 · The eligibility ladder
Trace access before you judge relevance
The ladder below is a diagnostic order, not a claim that every store implements the same service layers. Start with the source and move towards the action. At each step, record the context and the evidence. If a hard step fails, the result is ineligible even when the words match perfectly.
Source record
Ask: Does the product or variant exist with the required identity, price, and operational fields?
Failure boundary: The search cannot repair missing or conflicting source data.
Publication and searchability
Ask: Is the item published to the relevant channel and allowed to appear on the active search surface?
Failure boundary: A product can be page-visible yet absent from storefront search, or unlisted by design.
Market and locale
Ask: Does the buyer's region, language, currency, and market context include the item?
Failure boundary: A result from another market can carry the wrong price, stock, or availability promise.
Buyer and company location
Ask: Is the buyer associated with the company location whose terms are being evaluated?
Failure boundary: A logged-in customer without the expected B2B context can receive a different experience.
Catalogue assignment
Ask: Does the relevant catalogue make the item available to this company location and define its price?
Failure boundary: The product exists globally but is not part of the buyer's assigned assortment or terms.
Inventory and action
Ask: Can the buyer act on this exact variant now, under the active selling-when-out-of-stock policy?
Failure boundary: Visibility is confused with availability, or a stale result survives into the cart.
Bridge · From diagnostic path to platform vocabulary
The ladder only helps when each rung has a real owner
The ladder gives us an order for investigation, but it does not yet tell an operator where to look. If a product exists in admin but disappears from a buyer's search, “search relevance” is the wrong first diagnosis. The cause may belong to publication, a market condition, a customer association, a catalogue assignment, or inventory policy.
Chapter 2 now names those platform concepts because the distinction changes the repair. You are not learning Shopify terminology for its own sake. You are mapping each eligibility question to the source of truth that can confirm or reject it, before search ranking gets involved.
Chapter 2 · Shopify's documented model
Catalogue, market, and customer context answer different questions
Shopify's B2B documentation describes catalogues as controls for the products and pricing available to B2B customers. Catalogues can be assigned to companies or company locations, and those locations can have their own commercial context. Shopify's Markets documentation describes market conditions and customisations that can change available products and prices by region or other conditions.
That gives you a useful vocabulary for diagnosis, not a shortcut around the data contract. The request still needs to carry enough context to distinguish an anonymous visitor, a customer at location A, and a customer at location B. The ecommerce market-context guide shows the broader source-to-cart trace; this article applies it to B2B catalogue eligibility.
The buyer context is not established by a generic login. Shopify's B2B requirements say the order must have a B2B customer associated with a company location when it is placed; without that association, D2C rates apply. Treat that company-location association as an action-boundary value, not a guess from an email address or a logged-in state.
Catalogue
Which products and commercial terms are assigned to the B2B context?
Market
Which regional conditions, currency, and product availability apply?
Customer
Who is the buyer, and which company location and permissions are active?
Chapter 3 · Worked context
The same part can be searchable and still ineligible
Consider an illustrative example: the same compatible part is present in the source catalogue, but it is assigned to one B2B company location and not another. A visitor in Canada, a buyer at location A, and a buyer at location B can all type the same part number. The correct answer may be a public result, a location-specific price, or no eligible result. None of those outcomes can be inferred from the product title alone.
| Context | Possible result | Price context | Decision |
|---|---|---|---|
| Anonymous visitor | Can discover only what the public market and search surface expose. | Public or fallback context only | Do not imply a B2B price or account-specific entitlement. |
| B2B buyer at location A | Can receive the products and pricing assigned to that company location. | Location and catalogue context | Verify the customer association before presenting an eligible action. |
| B2B buyer at location B | May receive a different assortment, price, quantity rule, or payment context. | Do not inherit location A | Keep the location in the test fixture and never fall back silently. |
| Unpublished or unlisted item | The source item may exist while the active storefront search cannot return it. | Not an actionable search result | Repair publication or state the boundary. Do not broaden matching to expose it. |
Context must be explicit. If changing the buyer changes the eligible assortment or price, that context belongs in the query, response, test fixture, and final handoff.
Chapter 4 · Diagnostic recovery
Fix the failing boundary before changing ranking
When an eligible result is missing, changing synonyms or broadening semantic matching can hide the real issue. Use the symptom to choose the first boundary to inspect, then repair the source or context and re-run the same query.
| Symptom | First check | Avoid |
|---|---|---|
| Product exists in admin but search returns nothing | Publication, unlisted state, channel, market, and active search surface. | Adding synonyms or semantic matching before proving eligibility. |
| Product appears but price is wrong | Buyer, company location, catalogue, market, currency, and price list context. | Caching a formatted price from an anonymous or different-market response. |
| B2B buyer sees D2C assortment | Customer account and company-location association at the time of the request. | Treating login alone as proof of the correct B2B context. |
| Search result was valid but cart cannot add it | Variant identity, publication, inventory, selling policy, and handoff freshness. | Substituting a neighbouring variant or treating an old result as a current offer. |
The Agent Search Contract guide gives the machine-readable match states that keep ineligible, partial, and exact outcomes distinct.
Chapter 5 · The action boundary
Revalidate context when the buyer is about to act
Eligibility can change between search and cart. Inventory can move, catalogue assignment can change, a session can lose its company location, or a price can be recalculated for a different market. A search result is evidence at a time and in a context, not a permanent entitlement.
Carry the exact product and variant identity, buyer context, market, price, currency, availability state, and a checked time into the handoff. If any hard value changes, surface the change and ask for a new decision. Never silently substitute a public price or a neighbouring variant.
Important current boundary: Shopify's B2B requirements documentation currently lists agentic storefronts as incompatible with B2B. Treat any agentic B2B flow as a vendor-neutral design and testing problem unless the relevant platform documentation says otherwise.
Chapter 6 · Reader-run acceptance test
Make eligibility observable, not assumed
Run these tests with the same product, the same query, and deliberately different contexts. The expected difference is part of the acceptance set.
Create a public fixture, a B2B location A fixture, and a B2B location B fixture for the same product family.
For each fixture, record the expected catalogue, market, currency, price, quantity rule, availability, and search state before testing.
Check an item excluded from the assigned catalogue. Expect it to remain ineligible even if its title is an exact textual match.
Check a product that is visible on a product page but excluded from search. Record the publication or searchability reason rather than calling it a relevance failure.
Change only the buyer or company location and repeat the query. Any change in eligible products or price must be explainable by that context change.
Open the exact variant and carry it to cart. Revalidate price, currency, availability, and buyer context at the action boundary.
Pass condition: every eligible result is explainable by the active context, and every ineligible result stays out even when its words match exactly.
Run the pass condition on desktop and mobile while authenticated as the same company location. Verify the visible price and currency, selected variant, focus or touch path, back navigation, and cart line at the moment of action. A correct search result that silently becomes a retail or ineligible line at the handoff is still a failed B2B test.
Research basis
Eligibility claims need a current source
This guide uses Shopify's current B2B, Markets, searchability, and inventory documentation for platform boundaries. It does not infer a store's configuration from those docs. Confirm the actual catalogue assignment, customer relationship, market, publication state, and cart result in the store under test.
Sources checked August 19, 2026
- Shopify B2B catalog documentation: Catalogues control which products and pricing a B2B buyer can access and are assigned to companies or company locations.
- Shopify B2B companies and customers: Reference for company, company location, customer, and buyer relationships that shape B2B context.
- Shopify Markets overview: Markets can change available products, pricing, currency, and the customer experience by region and context.
- Shopify managing searchability: A product can be visible in one way and excluded from storefront search through its searchability state.
- Shopify inventory documentation: Reference for inventory quantity, tracking, and the source state that must be checked before calling a result actionable.
- Inventory-aware ecommerce search guide: The visibility, availability, freshness, and cart-handoff distinctions used in the action checks.
- Shopify B2B requirements and considerations: Current Shopify boundary check for B2B requirements, including the documented incompatibility of agentic storefronts with B2B.
Final judgement
Search quality starts with the right buyer context
A B2B search answer is trustworthy when it names not only what matched, but for whom, where, under which catalogue, at what price, and with what action state. If those facts are unavailable, the honest answer is a bounded result or a request for context, not a confident product card.