Build vs Buy

Pre-built B2B portal or custom build: how manufacturers should choose

Pre-built B2B platforms win on time and cost when how you sell matches what the platform assumes. A custom build wins when your contract logic, account structure, or configuration rules are too specific for a package to honour. For most mid-market manufacturers the honest answer is a package plus selective custom work on the parts that are genuinely unusual.

The buy-or-build conversation usually starts with a feature comparison and ends in a stalemate, because at that level every platform can do everything. The question that actually separates them is narrower: can this platform express the commercial rules that make your business awkward, without custom code? Contract pricing per account, a parent company with fifteen ship-to locations and one approver, a product that has to be validated before it can be quoted. Those are where packages either fit or don't.

What a pre-built platform gives you

Packaged B2B platforms have improved considerably, and for standard selling they're the right default. You get hosting, security patching, payment compliance, and a roadmap you don't fund. You also get a support path that isn't your own developers.

The caution is that B2B capability tends to live in the upper tiers, and the published pricing makes that plain. Shopify's B2B company-level catalogues and pricing require Plus, which starts at $2,300 per month. On BigCommerce, price lists and advanced promotions, which is to say the B2B feature set, sit in the Performance tier starting at $1,499 per month billed annually tier, while B2B Edition itself is quote-only. Adobe Commerce and Sana publish no figures at all.

It's also worth reading the fine print on capabilities you'd assume are standard. BigCommerce's own documentation notes that its B2B credit amount only caps an order's value and doesn't track usage against it, so real credit management still needs the ERP. Shopify has no native buyer-initiated request for quote, and its B2B account structure doesn't model parent and child companies. Adobe is the strongest of the group on hierarchy and purchase-order approval rules, but its B2B capability is a separate extension installed on top, which changes the upgrade conversation.

What a custom build gives you, and what it costs

A custom or decoupled build is the answer when the buying experience has to follow your business rather than the reverse. Product configuration with validation, pricing that no standard data model represents, a blended direct and dealer experience on one system of record. You get exact fit and you own the result.

The cost that gets underestimated isn't the build, it's the upkeep. Master B2B's practitioner framework puts implementation at five to fifteen times the software license cost and a world-class B2B experience at 12 to 18 months to deliver. That's a consulting estimate rather than survey data, so treat it as a planning heuristic, but the direction is right.

Platform vendors are unusually candid about the maintenance trade-off, which makes their documentation the best evidence available. Sana states that custom projects cannot be automatically updated to a newer version, because customizations are made in Sana's core code, and that a customized solution won't receive its biweekly product updates. Adobe ships an Upgrade Compatibility Tool whose entire job is finding what your customizations will break on the next version. That's the real bill for customization: not the first release, the fifth.

Payment compliance belongs in the same column. PCI DSS 4.0.1 brought 64 new requirements into force on 31 March 2025, and the standards council's own guidance notes they've been challenging for many stakeholders, especially smaller merchants, to implement. A merchant satisfies the ecommerce payment-page requirements either by implementing the controls themselves or by relying on a compliant third-party provider's embedded payment form. That's a genuine argument for a package unless you have a reason to own it.

The test that settles it

Write down the five commercial rules that make your business hard to serve. Then check each against the platform, in the platform's own documentation rather than a sales call. Three outcomes, and they map cleanly to a decision.

1. The platform expresses all five natively – Buy the package. Don't build past it. This is more common than manufacturers expect, particularly for distributors selling standard goods on standard terms.
2. It expresses three or four – Buy the package and build the exceptions deliberately, keeping custom work at the edges rather than in the core. This is where most mid-market manufacturers land.
3. It expresses one or two – Look at a decoupled build with the ERP as system of record. If you're customizing the platform's core to survive, you've bought a maintenance liability rather than a platform.

One prerequisite sits above all three. If pricing or inventory isn't modelled correctly in the ERP, no platform choice rescues it, and the integration will be blamed for a data problem. Settle where each answer comes from first.

Be realistic about integration capacity

The strongest argument against an ambitious composed stack isn't philosophical, it's operational. Distribution Strategy Group's 2026 survey of 233 North American distribution executives found that 55% had invested in ERP, CRM, ecommerce, and analytics but had not integrated them. High-maturity distributors run around 28 integrated technologies; low-maturity ones average five.

If more than half of the market can't integrate four systems, composing fifteen isn't a mid-market strategy. Master B2B's 2026 research points the same way: data hygiene has been the top growth barrier two years running, and its recommended sequence is to clean the data, build the product content foundation, and layer anything clever on top of that.

Whichever way the decision goes, what a portal needs to include covers the capability list worth scoping, and the rollout piece covers the launch. If you want help scoring your own requirements, talk to us.

Frequently Asked Questions

Next Step

Get the foundation right before you build.

For readers scoping a platform decision or wanting a full architecture recommendation.