B2B ecommerce search: the complete guide for distributors

Retail search helps a shopper discover something they might like. B2B search helps a buyer find the exact item they already intend to order, at the price their account pays, in the quantity that is actually in stock. The two tasks look similar and are built differently.

Four differences drive everything else:

• Query type. A retail shopper types "blue running shoes". A distributor's customer types "123-57-ABC", "57-AB" or scans a barcode. In B2B catalogs a large share of queries contain a code rather than a word. A measured share across Shopsense storefronts will be added when that figure exists.
• Catalog size and churn. A wholesale catalog often runs to tens of thousands of SKUs, with products added, discontinued and restocked weekly. Search must index that churn without manual work.
• Account-specific truth. The same product has a different price for every customer tier, and may be restricted to licensed accounts. Search results that ignore the account are wrong for every buyer.
• Cost of a wrong result. A retail shopper who sees a stale stock level is mildly annoyed. A retailer who orders fifty cases that do not exist has a shelf gap, a cancelled line and a reason to try another supplier.

A distributor's storefront search needs seven capabilities. Core relevance is table stakes. The last four are where most retail-first tools fall short.

1. Code search. Exact, partial, unformatted and mistyped SKUs, manufacturer part numbers and barcodes must all resolve. See the guide to SKU and part number search.
2. Semantic and attribute search. "Menthol 5% pod" should match on flavour and strength attributes, not just on words in the title.
3. Autocomplete. Product, brand and category suggestions as the buyer types, so a three-character code shows candidates before Enter.
4. Live stock in results. Quantity, low-stock and backorder state on every result, from the system of record, not from a synced copy. See real-time inventory and pricing in search.
5. Customer-specific pricing in results. Each signed-in account sees its own tier or contract price in the result list, not only on the product page.
6. Account restrictions. Products that an account is not licensed or entitled to buy are never shown to it.
7. Search analytics. Zero-result queries, popular queries and conversion by query, so purchasing and catalog teams can act on demand signals. See site search analytics for distributors.

In B2B the quality of search depends less on the ranking model and more on where the index gets its stock and price data. Most search tools index a copy of the catalog exported from the ecommerce platform, which in turn is synced from the ERP on a schedule. Every hop adds delay and a place for the two systems to disagree.

An ERP-native approach builds the index directly from the ERP's item, inventory and price list tables. There is no intermediate copy, so stock and prices in search are the ERP's current values. The guide to ERP-integrated ecommerce search covers the two architectures in detail. Shopsense is a B2B ecommerce search engine for distributors and wholesalers that connects directly to ERP systems.

Evaluate a B2B search tool on data source, pricing model and B2B features before you evaluate relevance. Relevance is similar across modern tools. The other three vary widely and are harder to change later.

The guide to ecommerce search pricing explains the four pricing models and how to compare them.

A B2B search rollout succeeds or fails on data mapping, not on code. Work through these steps before go-live.

1. Map every code field: internal SKU, manufacturer part number, UPC, EAN, superseded codes, aliases.
2. Confirm which price list applies to each customer group and how promotions override it.
3. Define stock states and thresholds: in stock, low stock, backorder, discontinued.
4. List account restrictions: licensed products, regional limits, customer-group catalogs.
5. Collect the top 200 queries from the current search log, including the ones that returned nothing.
6. Build a synonym list from how buyers actually speak: "dispo", "5k puff", "1 1/4 cones".
7. Decide guest visibility: list price, no price, or sign-in prompt.
8. Agree a latency target from ERP change to visible result and a method to measure it.

• SKU. Stock keeping unit. A seller's internal code for one sellable item or variant.
• MPN. Manufacturer part number. The maker's own code, often different from the seller's SKU.
• Zero-result search. A query that returned no products. The most useful signal in the search log.
• Price list. A named set of prices in the ERP assigned to one or more customers or tiers.
• Sync layer. Any scheduled process that copies data from one system to another. The main source of stale stock in storefront search.
• ERP-native search. Search whose index is built directly from the ERP's tables rather than from a copy.