Site for B2B: catalog, conditions, calculation request

Our recommendation is not to install at the first launch. The basket is justified where the price is fixed, and the range is repeated: a regular buyer types the order himself and does not wait for the manager. If each shipment is accompanied by an agreement on the volume, term and payment, the cart creates the illusion that the order will still go through the conversation, and you will pay for the checkout, statuses and end-to-end scenario testing. That's why we start with a miscalculation request, put an event on it in analytics, and after a few months we see what proportion of applications repeats the previous one. If it is large, we add a basket in the second stage, already knowing what it is for.

There are three options, and two of them are cheap. Showing a single price and agreeing on a discount in a conversation is the easiest way, but also the most frequent. Showing volume levels visible to everyone is a little more work, but you can see why they are getting a better price. Personal conditions for each contract require authorization, roles and sources of these prices from the outside: this is already a closed office, a separate project and a separate estimate. In debriefing, we name the difference in labor intensity between the three so that the decision is made with the number, not blindly.

It is possible, if there is somewhere to get them. An error in availability in B2B costs more than in retail: the counterparty plans its schedule for your shipment, and the disruption hits its production. Therefore, we either pull up the balances from the account according to the schedule, or show the status in a range - "in stock", "on order", "in the manufacturer's warehouse". There is only one fair limit here: the exchange does not correct the account. If the system resorts and unrepresented write-offs, the site will show the inaccuracy quickly and accurately. And there is always a window between exports, in which a position can be booked twice.

This is the most common failure in B2B catalogs, and it is done by hand. The standard search of most systems looks for a substring in the name: the counterparty enters "1234 5", and the database contains "A-1234/5" - there is no match, the issue is empty, the person leaves. We start a separate field of the normalized article: hyphens, slashes, spaces and a case are removed from it, and it receives its own index. The search query undergoes the same normalization before comparison. At the import stage, we will run real codes with separators - exactly the ones that your managers use. The limitation of this mechanism is simple: it helps someone who already knows the code. Those who are still choosing need categories and characteristics.

Yes, this is a work area. The parts catalog we measured holds 1,848 cards and 138 categories, has a first response time of 388.1 ms at 120.2 KB of HTML, and has 1,992 addresses in the sitemap without a single duplicate. Volume is almost never the problem here—data quality is. If the characteristics are glued together in one text field, the filter will not be collected from them either on two thousand items or on two hundred. That's why we don't look at how many lines you have, but what columns they have.

To call with the article number. The site in B2B saves not the manager, but the first five minutes of the conversation: the person comes, already knowing the position, volume and terms of payment. The second effect is more noticeable at a distance — new counterparties find you by the code of the part or the name of the equipment, and not by the name of the company, which they do not yet know. And immediately honestly about the measurement: the meter itself does not improve anything, it only lets you see. The data still needs to be read, and GA4 shows a trend, not an accounting truth — blockers and consent mode eat up some of the events.

25-50 working days from approved TOR, seven stages: disassembly and TOR 3-5 days, structure and prototype 4-6, design 5-9, assembly 7-13, price import 3-8, integrations and analytics 2-5, testing and transfer 1-4. It is not the layout that takes the longest, but bringing the price to a look suitable for import — and it is this stage that almost everyone underestimates at the start. The second thing that pushes the deadline: agreeing on the terms of cooperation within the company, when it turns out that for three old customers there are rules that are not in any document.

Depends on who you are selling to. Both B2B directories we measured have two language versions, and in one of them the hreflang is set correctly — uk-ua, ru-ua and x-default. Technically, it is not difficult, but honesty is needed here: the translation of the interface is not an entry into a new market. The new market also requires local payment, local delivery, local support and local prices — the site closes only the first layer. If a second language is needed for the domestic market, that is one job; if for export, count it as part of a much larger project.