B2B eCommerce is not B2C with a discount

Somewhere in your company there is a spreadsheet that moves more revenue than your website does.

It belongs to Edward, a sales rep who stopped trusting the site months ago. A key account asked for their contracted price, the site showed list price, so the deal moved to email. Payment delay got agreed on a phone call. The quote for 400 units went out as a PDF, version seven, saved as final-FINAL.xlsx. The site still takes orders, but everything that actually closes a deal, the pricing and the trust behind it, lives in WhatsApp threads and Eddie's laptop.

That store is a Potemkin village. A clean facade, with the real business happening out of sight.

It is the most common failure we see in B2B eCommerce, and it usually gets misdiagnosed. Merchants assume they bought the wrong plugin or the wrong platform, and that a different one will fix it.

It won't, because the problem was never the storefront. B2B buying only looks like retail from the outside; underneath it works differently, and running it as a B2C store with a few plugins bolted on doesn't close that gap. The work just moves into spreadsheets and chat apps, where it quietly eats your margin.

Your customer is not a person

In B2C eCommerce, you design the user flow for one ‘persona’ on a thin, well-lit path. They land, they buy, and the craft is removing friction between wanting something and paying for it.

A B2B customer is a committee with a logo. Behind one login sits a procurement officer who builds the cart, a department head who needs the goods, a CFO who signs off on the spend, and a warehouse manager fitting the delivery into next week. Each shows up with different permissions and a different reason for being there.

The purchase doesn't happen in one sitting either. A consumer buys a kettle in ninety seconds; a distributor placing a recurring five-figure order moves through evaluation, internal sign-off, and a budget cycle that can run for weeks. So the system isn't hosting a checkout, it's holding a relationship that has to stay consistent across many people and many days.

Therefore we keep telling clients that B2B commerce is a design problem before it is technical. Not ‘design’ as in colours and buttons, but mapping how a company actually buys: who sees what, who approves what, in what order, and what each role needs on screen to do its part. If that mapping is wrong, no platform or plugin will rescue it.

The real difference between platforms is how far they let you change them. Shopify and Squarespace let you restyle the storefront but not rework the logic underneath. Others, like WooCommerce and BigCommerce, are built to be extended, so a competent team can take the native checkout apart and rebuild it around real ERP data instead of bending the business to the platform's defaults. That flexibility is what B2B actually needs, and it only pays off when the documentation and code quality are good enough to keep the work maintainable.

Four questions that tell you the system is shallow

If you want to know whether your store is doing the B2B job or only impersonating one, run these four checks. Each tests the same thing: whether the storefront reflects what the ERP actually knows.

1. The price. When a tier-2 distributor logs in, do they see their exact contracted, volume-adjusted price, or the same list price everyone else gets next to a "call for pricing" banner? That banner admits the site can't do the one thing this buyer came for, and it sends them back to the salesperson.

2. The terms. Can that buyer check out on a purchase order with Net 60 credit, the way their finance department actually works, or does the system insist on a company credit card for a €20,000 order?

3. The workflow. Can a junior procurement officer assemble a cart and route it to their CFO for approval inside the store, or does approval drop into a forwarded email and a chase three days later? Real organisations buy through approval chains, and a store that can't represent the chain isn't really part of the purchase.

4. The inventory. When the store says "in stock", does that mean the goods are allocated to this customer in the ERP, or only that they haven't sold out on the B2C side? This one fails after the sale, when the buyer schedules a delivery against stock that was never really theirs.

The part nobody copies from a tutorial

This part doesn't come with any template, because it's a judgement call about your own catalogue: how much should someone see before they have an account?

Miscalculate it in either direction and it costs you. Hide everything behind a login and you're invisible to search engines and to the buyers doing prior research, which today is most of them. Open everything up and a competitor can read your full spec sheet. Neither extreme is right.

Take a build we did for Plastribution, the UK's leading distributor of plastics raw materials, with a catalogue of over 5,000 grades running off NetSuite. The public site carries the product range and the marketing information, so it does its job for search and for a buyer comparing grades at 11pm. The documents that actually close a technical sale sit behind a login: datasheets, material safety data sheets, REACH statements, certificates of analysis. A browsing stranger sees enough to get interested. A registered customer sees plenty to specify and commit.

The moment you gate content, you have designed a workflow, whether or not you meant to. How does a buyer request access, who reviews the request and on what criteria, how long does it take, and how much of the back office's day does it cost? Get that wrong and you have built a bottleneck your own team routes around, which puts you right back in the shadow operation.

This reframes content management in B2B. The job is governing who has the right to see which commercial and technical assets, and proving you can show your capability to the market without handing your intellectual property to the competition. That is a real merchant fear, and a well-designed access model is the answer to it.

Now lay all of this onto the systems that actually run businesses in this region, and the difficulty turns specific. Western commerce writing quietly assumes a clean, modern, well-documented API into NetSuite or SAP. Across Central and Eastern Europe, the back office is more often a heavily customised local ERP like Pantheon or Wand, a localised Microsoft Dynamics NAV or an in-house database that predates the current IT team. Many were never built to be connected to a website, and the modern REST API you were counting on may simply not exist.

This is why the out of the box plugin approach breaks here, and why a Western playbook does not transfer. Customer-specific pricing and a gated content workflow are hard enough against a modern API. Against a legacy ERP with no clean way in, they become an architecture problem you have to solve deliberately. Doing that takes a team that has already done it against these exact systems, and that experience is the part a competitor cannot copy quickly.

What it costs to leave it shallow

None of this is an IT footnote. It shows up in the numbers that decide what the company is worth. Sales rep Edward spends more time fixing orders than closing them, and the cost is measurable. Manual quoting runs an error rate around 8 to 12%. On €50M of annual quotes, that is up to €5M priced wrong every year. Manual data entry costs roughly $28,500 per employee.

Each of those is margin leaking quietly out of the business, and margin is what an acquirer multiplies at exit. A company scaling on a B2C store and a stack of spreadsheets carries a ceiling it has not hit yet, and the first serious investor to run diligence will find it before the founder does.

We have watched capable teams keep buying plugins to patch a problem that a few days of honest design work would have framed properly. Reaching for the next add-on is understandable, and sometimes a shortcut is the right call; plenty of businesses run fine on a lightly customised store.

B2B eCommerce just isn't one of those cases. The store is the easy 10%. The other 90% is pricing logic, approval chains, payment terms, and ERP integration. Get that right and the spreadsheet quietly running your business disappears, because the website is finally doing its job. Get it wrong and you keep paying for it, one workaround at a time.