B2B & wholesale

Each buyer sees their catalogue, their prices, their history.

B2B buyers know exactly what they want and type article numbers. AACSearch matches codes exactly, enforces customer-specific assortments with document-level access, and puts repeat orders one search away.

Queries plain keyword search gets wrong

6ES7214-1AG40-0XB0manufacturer articleкабель ввгнг 3х2.5spec in a codeкак в прошлом заказеreorder intentаналог schneidercross-brand

Where search loses customers today

Customer-specific assortments

Contract catalogues differ per buyer. Showing a product the buyer can't order — or another customer's prices — is a serious error.

Long technical codes

Article numbers and spec codes must match exactly; generic search turns them into noise.

Repeat orders

Buyers reorder the same lines every month and search for them from scratch every time.

Technical documentation

Datasheets and certificates live in PDFs that search can't read.

How AACSearch solves it, layer by layer

Each card names the capability behind it. Items marked “in development” are designed and scheduled, not live yet.

Finds the right item from the first letters — typos, synonyms, filters, meaning.

Document-level access

ACL on every document: the buyer's organisation and groups filter results before they are counted — totals and facets never leak.

Exact codes

Article numbers match exactly and rank first.

Connectors

Sync from 1C-Bitrix, CSV and JSON feeds, or push via API.

Widens the basket: similar, frequently together, personal.

Reorder first

Each buyer's purchase history drives ranking, so regular lines are on top.

Analogues

Equivalent products from other brands when a line is unavailable.

Answers questions a filter can't, citing your own catalogue and docs.

Datasheet answers

Answers technical questions from datasheets and certificates, with citations — restricted to documents the buyer may see.

Learns how items, queries and topics connect — and leads the visitor to the goal.

Assemblies

Will link components that are ordered together into assemblies and suggest the missing parts of a typical order.

One visitor, from first query to goal

What the visitor does on the left, what AACSearch does on the right.

  1. 1

    Log in

    A buyer from a contract customer opens the portal.

    Search is scoped to the customer's assortment by ACL.

    Document-level access
  2. 2

    Reorder

    Types the first letters of a regular product.

    Last month's lines appear first.

    Personalization
  3. 3

    Check spec

    Asks about the operating temperature range.

    Answers from the datasheet the buyer is allowed to see, with a link.

    AI answers with citations

Your first two weeks

A typical rollout for this industry. Most teams are live on day one and spend the rest of the time measuring and tuning.

  1. Day 1

    Import the catalogue with article numbers; add `acl` lists per contract customer.

  2. Day 2

    Test search as two different buyers to confirm assortments differ.

  3. Week 1

    Index datasheets for the assistant, with the same access lists.

  4. Week 2

    Measure time from login to submitted order.

What to measure

The numbers to judge a rollout by. Compare them with an A/B split or a before/after window on the same traffic.

Time to order
From login to submitted order — the B2B equivalent of conversion.
Orders via search
Share of order lines found through search.
Access violations
Must be zero; covered by ACL tests.

Connects to

  • 1C-Bitrix
  • CSV / JSON
  • REST API
  • SDK (TypeScript, Python)

Capabilities used

Coming next

Questions

Search for B2B & wholesale, live this week

Connect a feed or a site, embed one script, and measure the difference on your own traffic.