B2B e-commerce: when a standard platform is no longer enough

For distributors, wholesalers and manufacturers, B2B e-commerce is not an online store with different prices. Every customer has their own price lists, discounts and payment terms, orders by the pack and wants to know what is really in stock. As these rules grow, the platform has to follow the sales model, not the other way around.

That doesn't mean you always need a custom build: for simple catalogs a standard platform works very well. The point is to recognize when the limit is close and choose a path that holds up over time.

01What makes B2B e-commerce different

In B2C the price is the same for everyone and the buyer is one person. In B2B almost every part of the order comes with an extra rule.

• Per-customer price lists and discounts: dedicated prices and negotiated discounts.
• Payment terms: due dates, credit limits and different methods for each company.
• Minimum quantities and packs: minimum orders, multiples of a case or a pallet.
• Quick reorder: repeat a past order or upload a list of product codes.
• Several buyers per company: roles, spending limits and approvals before the order goes out.
• Quotes: requests for quotation that become orders when the customer accepts.
• Large catalogs: many product codes and variants in size, color or pack.
• Real availability: stock and delivery times read from the ERP or the warehouse.
• Documents and invoices: order history, delivery notes and invoices in the private area.

A platform designed for consumers covers some of these with extensions. The difficulty begins when you need all of them together, aligned with your ERP.

02When a standard platform is enough

If the catalog is contained, prices are the same for everyone or split into a few groups, and orders reach your ERP through a ready-made connector, a standard platform is the right choice: you get started sooner and the common features are already there. We say so to companies that ask us for custom e-commerce, too.

03Signs your platform has hit its limit

The limit usually doesn't arrive overnight: it shows in signs that add up.

• A plugin for every feature: price lists, minimums, quotes and approvals from different extensions; every update risks breaking one of them.
• Manual work: orders re-entered into the ERP, price lists uploaded by hand, spreadsheets for the exceptions.
• Misaligned data: stock, prices and order status differ between the site and the ERP.
• A slow site: pages and search slow down as the catalog grows, and you lose orders, especially on mobile.
• Logic you can't express: a pricing rule, an approval flow or a commercial condition the platform doesn't provide for.

When every new feature needs another plugin, the whole setup keeps getting more fragile.

04Three paths, with pros and cons

When the signs add up, there are three paths. None is right in absolute terms: it depends on how specific your sales rules are and how deep the integrations need to go.

Stay standard and integrate better

You keep the platform and improve its connections with the ERP and the warehouse to remove manual work. It is the least invasive path: no migration. The limit: logic the platform doesn't provide for stays out, and the plugins stay in.

Headless commerce

The front end, meaning what the customer sees, becomes independent and connects to the commerce engine through APIs. You gain freedom over the buying experience and performance. The limit: you now maintain two systems, and pricing and ordering rules remain whatever the engine can handle.

A custom platform

The platform is built around your sales model: price lists, terms, roles and integrations designed from the start. When you need per-customer price lists, B2B rules, deep integrations or high performance, it tends to perform better and cost less to maintain. The limit: a higher initial investment and an analysis that has to be done properly.

05Integration with ERP, warehouse and logistics

In B2B the website is only one part of the process: prices, terms and stock originate in the ERP, and orders, shipments and invoices have to flow back without being retyped.

With a well-built integration, orders, stock, prices and master data stay aligned automatically, and the site also talks to carriers, payments and e-invoicing. Every flow should be monitored, so you know right away if a sync stops.

You don't need to replace systems that work, but to make them work together: we covered this in how to connect different systems without stopping operations.

06Migrating without losing customers or rankings

Changing platforms carries two risks: customers who can't find their data and pages that disappear from search engines. A planned migration covers four elements.

1. 01Catalog: product codes, variants, descriptions and images, checked before the switch.
2. 02Customers: companies, users, price lists and terms, so everyone finds their own prices.
3. 03Orders: the history, so quick reorder and issued documents are not lost.
4. 04Redirects: every old address leads to the matching new page.

Together with the page structure, redirects are what preserve your visibility in search engines. Integrations come in step by step, running alongside current flows until they are verified.

07Where to start

You don't have to rebuild everything at once. There are two sensible starting points.

• The B2B portal: a private area for business customers, with dedicated price lists and terms, reorders and documents. The public storefront can stay as it is or share the same platform with B2B.
• A single process: the connection that costs the most manual work today, for example orders and stock between the site and the ERP. You solve that one, check the result, then decide the next step.

Either way, you begin by writing down your current sales rules and data flows: from there you can see which path holds up. Explore our custom e-commerce service and our system integration service.