B2B Ecommerce Portal Development: Build or Buy at Your Pricing Complexity
One question decides this, and it is not revenue. Is a trade price a field you could export nightly, or the output of a calculation involving the customer, the contract, quantity breaks, the branch, a promotion and sometimes what is already in the cart?
On this page
One question decides this, and it is not revenue. Is a trade price a field you could export nightly, or the output of a calculation involving the customer, the contract, quantity breaks, the branch, a promotion and sometimes what is already in the cart? If it is a field, buy a platform and be trading this quarter. If it is a calculation, you are building a live pricing integration with a reconciliation job behind it, and that usually starts to make sense above roughly $30 million in business to business revenue or 500 active accounts. Most distributors under $20 million with tiered pricing should buy, and we have told them so.
When is off the shelf genuinely the right call for trade commerce?
Whenever a price is a field rather than a calculation. If your trade pricing is a handful of published tiers or a straightforward percentage off list, your accounts are single site, and no customer has mandated procurement integration, a platform will have you trading this quarter and you should take that deal.
Sana Commerce is the specific product to look at first, because it is designed around live enterprise resource planning (ERP) pricing and removes most of the hardest problem in this category if you run a system it supports natively. BigCommerce B2B Edition is a fair answer for a smaller operation that wants to be selling within a quarter rather than next year. OroCommerce deserves a serious look if you want an open platform and have the internal capability to extend it. Adobe Commerce B2B handles company accounts, price lists and approval workflows competently and is a reasonable choice where your organisation already runs on that stack.
None of those is a compromise at the right shape of business. At roughly $12 million in trade sales with tiered pricing and single site customers we have told operators not to build, and we would say it again on a call. The flexibility you would pay a build premium for is flexibility you will not use, and the residual manual work at that size is one person's Monday morning rather than a role.
Buy as well when the honest blocker is product data rather than software. A trade catalogue with tens of thousands of parts and no attributes, images or unit of measure discipline cannot be browsed on any platform, and writing your own code will not change that. Enrichment is a workstream with its own owner and its own budget of $20,000 to $80,000, and it is the most common reason a launch date slips whichever route you pick.
When does a custom build actually pay off?
When your price is the output of a calculation that no list can represent. Ask your commercial director how a specific customer's price for a specific item is derived. If the answer runs five minutes and involves a base list, a contract that overrides some items by percentage off and others by fixed price, quantity breaks that may be per line or per order or per rolling annual volume, a branch adjustment, a promotion that beats the contract this month but must not next month, and a customer specific part number mapping to a kit you assemble, that is not going to survive a nightly export.
Build when two or more of these are true. First, your pricing rules cannot be expressed as a price list without being wrong. Second, your customers' organisational and approval structures are specific enough that configuring them in a platform means fighting it, typically because approval keys off product category or project code rather than a value threshold. Third, you have punchout or electronic data interchange (EDI) mandates from accounts that matter and the platform connector does not cover the trading partner in question. Fourth, availability across branches with a real delivery promise is a competitive weapon in your category. Fifth, you have already attempted a platform project and abandoned it, which happens more often than vendors admit and usually means your rules genuinely did not fit.
The revenue threshold most people quote is a symptom rather than a cause. What actually changes above roughly $30 million in trade revenue is that contract pricing stops fitting inside a list, and the phone order desk starts capping how much your branches can physically handle.
How do they compare on the things that matter to a distributor?
Where the price comes from. A platform stores a price and refreshes it. A build calls your ERP pricing engine at display and again at submission, with the full context of customer, ship to, item, quantity and cart, caching at session level for speed and never at catalogue level. Whichever you choose, insist on a reconciliation job that samples customer and item combinations daily and proves your number matches what a representative would quote. A price nobody can verify gets undermined by the sales team inside six weeks.
The shape of the buyer. Adobe Commerce B2B and OroCommerce both model company hierarchies, budgets and approval flows properly, and for a great many businesses that is enough. They strain when approval is not a value threshold, and when a credit hold has to block one member company without blocking its siblings. Nothing destroys trade confidence faster than a portal that accepts an order finance will cancel.
Order intake paths. Your largest accounts may never log in at all. They buy through Ariba, Coupa or Jaggaer and expect you to appear inside their procurement system over cXML or OCI, then send the order as EDI. Ask any platform which named trading partners its connector actually covers, not which categories.
Availability. A contractor wants to know whether he can collect from the branch two miles away in an hour. That is a promise engine with transfer times, carrier cut offs per location and freight against parcel handling, not a stock number on a page.
Portability and economics at scale. Check for a transaction or revenue share component in your contract, because that line grows with your success rather than with your seat count.
What does total cost of ownership look like at your volume?
Build figures first, from Digital Heroes delivery experience. A self service core covering live ERP pricing at display and submission, the customer organisation tree with credit position and approval rules, catalogue and search, and reorder from history with saved lists runs $70,000 to $150,000 over 14 to 20 weeks. A full trade portal adding punchout for named partners, EDI order and invoice flows, multi branch availability with a delivery promise, quote to order, customer specific part number mapping and a representative ordering console runs $200,000 to $500,000 phased over 8 to 14 months. Punchout is priced per partner at $18,000 to $30,000, and each partner takes several weeks of calendar time regardless of engineering effort, because their procurement team controls certification.
An older ERP with no documented pricing service adds $30,000 to $70,000 on identical functional scope, because the rules have to be reimplemented outside the system with a daily reconciliation behind them.
Running costs are where the honest comparison lives. Support and enhancement runs 15 to 20 percent of build cost annually. Product data stewardship is $25,000 to $60,000 a year and it is a person rather than a licence, because new parts arrive weekly without attributes or images. Punchout partner maintenance is $4,000 to $12,000 per partner per year. Search and hosting is $9,000 to $30,000 a year, scaling with catalogue size rather than order volume.
Set that against your current renewal, and be honest that a build will not beat a subscription on cost alone in the first two years. What a build changes is the ceiling, not the run rate.
What does the hybrid look like, and when is it the honest answer?
Buy the platform, build the thin layer you actually need. For a lot of distributors this is the right answer and it is treated far too rarely as a serious option.
The pattern that works: keep Sana Commerce, Adobe Commerce B2B or OroCommerce for catalogue, search, checkout, content and the customer facing shell, all of which are solved and unrewarding to rebuild. Then build the three pieces those products hand back to you. A pricing service that calls your ERP with full context and a nightly reconciliation job that proves the numbers. An order intake adapter that accepts punchout and EDI into the same order object as the web store, so a national account is not a separate system. And a representative console where a rep places orders inside the customer's own context at the customer's prices, sees quotes convert with one customer click, and gets their accounts' abandoned carts above a value threshold as a call list.
That combination typically lands between the two bands above, and it keeps you out of the two worst outcomes: a platform you fight every quarter, and a rebuild of a catalogue you did not need to own.
Fix the commission plan before any of it. Portals fail on representative resistance far more often than on technology, and crediting portal orders from their accounts to the rep who owns them costs nothing.
Which should you choose, by operator size and stage?
Under about $15 million in trade sales, tiered pricing, single site accounts. Buy. BigCommerce B2B Edition or Sana Commerce, live this quarter. Spend the difference on product data and on getting your top 2,000 parts properly enriched, which will do more for conversion than anything you could build.
$15 million to $40 million, contract pricing, no procurement mandates yet. Buy the platform and build the pricing service and reconciliation on top. That is the cheapest correct answer for this shape and it keeps your options open when the first punchout demand arrives, as it usually does.
$40 million and up, multi branch, contract pricing, punchout mandated by at least one account. Build the trade portal properly, and sequence it. Self service core first at $70,000 to $150,000, then one punchout partner, then the delivery promise engine once you have three months of real order data to base promises on.
Anyone who has abandoned a platform project. Treat the sunk cost as evidence rather than as an argument. It usually means your rules did not fit the product, which is the strongest single signal in favour of building, and it also means you now know exactly which rules broke it.
Anyone whose catalogue is not enriched. Neither. Fix the data first with its own owner and its own budget, then revisit this decision in two quarters with a catalogue that can actually be browsed.
When you are ready to turn this into a specification, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. You can take that specification to any other firm on your shortlist.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- The average documented online shopping cart abandonment rate is 70.22% (based on 50 studies), and large ecommerce sites can achieve a 35.26% increase in conversion rate through better checkout design. Source: Baymard Institute (2024) →
- Retailers improving Core Web Vitals saw measurable gains: Vodafone improved LCP by 31% for 8% more sales, Lazada saw a 16.9% mobile conversion increase, and Cdiscount saw a 6% Black Friday revenue uplift. Source: web.dev (Google Chrome team) (2021) →
- This World Bank report argues that digital technology adoption raises SME competitiveness, productivity and resilience, while documenting that smaller firms consistently lag larger ones in digital adoption - a gap that constrains their growth and market reach. Source: World Bank (2022) →
- The global point-of-sale terminal market is projected to reach approximately $181.47 billion by 2030, growing at an 8.1% CAGR from 2025 to 2030, driven by digital payment adoption and demand across retail, restaurant, and hospitality sectors. Source: Grand View Research (2025) →
Frequently asked questions
Is Sana Commerce enough, or do we need to build?
Sana Commerce is built around live enterprise resource planning pricing and it removes the hardest problem in this category if you run a system it supports natively and your rules fit its model. For a lot of distributors it is a strong buy and we would say so.
Building becomes the better answer when approval rules key off product category or project code rather than value thresholds, when customer specific part numbers are many to many and sometimes map to kits you assemble, or when a platform project has already been attempted and abandoned.
How long does a B2B portal take to launch?
Fourteen to 20 weeks for a credible self service release with pricing, accounts, catalogue and reordering, then 8 to 14 months in total for the full portal with punchout, electronic data interchange and a delivery promise.
The usual cause of overrun is not development, it is product data. Treat catalogue enrichment as a parallel workstream with its own owner, and onboard accounts in waves of twenty then a hundred rather than announcing a launch to everyone at once.
What does it cost to move off our current commerce platform?
The licence exit is the small part. The real cost is your customer organisation data, your price list configuration, your content and your order history, plus recertification of any punchout partners, which runs to their procurement calendar rather than yours.
Assume a parallel period. Run the new store with twenty friendly accounts for four weeks before you move anyone else, because that first wave finds the customer specific part numbers nobody documented and the ship to addresses that are wrong in the master data.
What happens if our platform vendor changes its pricing or revenue share?
Check your contract for a transaction or revenue share component before you answer that, because that line grows with your success rather than with your seat count and it is the one that moves a build into range.
Your bargaining power comes from portability. If your customer hierarchy, pricing configuration and order history can be exported into a documented format, a renewal is a negotiation. If your punchout partners are certified against the vendor rather than against you, it is closer to an invoice.
Do we really need punchout, and what does it add?
You need it when a large account mandates it, which is common in national and public sector buying, and without it you are simply not on the vendor list. A single national account that mandates punchout is often worth more than the entire self service channel at launch.
Budget $18,000 to $30,000 per partner and several weeks of calendar per partner regardless of engineering effort, plus $4,000 to $12,000 a year each in maintenance. Start the conversation while the self service core is being built so the certification window runs in parallel.
Can we do this on an older ERP with no modern interface?
Usually yes, through a read replica or integration layer that mirrors pricing inputs, customer hierarchy, stock and open orders, with orders written back through whatever interface the system does expose. Expect $30,000 to $70,000 of extra work on identical functional scope.
The trade is that pricing rules get reimplemented outside the system, which is only acceptable if you also build the daily reconciliation that samples customer and item combinations and proves both engines agree.
How do we stop the sales team from killing the portal?
Fix the commission plan first so portal orders from a representative's accounts credit to them. It costs nothing and it matters more than any feature, because adoption stalls when reps believe the channel competes with their number.
Then give them something the portal makes better: a console where they order inside the customer's context at the customer's prices, quotes that convert with one customer click, and visibility of their accounts' abandoned carts above a value threshold, which is a better call list than most systems give them.
We do $12 million in trade sales with simple pricing. Should we build?
No. At that size with tiered pricing and single site customers, BigCommerce B2B Edition or Sana Commerce will have you trading within a quarter for a fraction of a build, and the flexibility you would be paying for is flexibility you will not use.
Revisit when contract pricing stops fitting a price list, when a major account mandates punchout, or when the phone order desk is genuinely capping how much your branches can handle.
How many SaaS seats do we need before building custom becomes cheaper?
The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.
Is Wix good enough for my business, or will I regret starting there?
Wix is genuinely fine for a clean 5 to 10 page presence, with published plans from $17 to $159 a month. You will regret it when you need features beyond its App Market, server-side logic, or full SEO and performance control, and especially when you want to leave: Wix has no site export, so moving means rebuilding from scratch. If your website is a brochure, Wix works; if it is a revenue channel with custom workflows, it becomes the bottleneck.
Can I start on Wix or Squarespace now and move to a custom website later?
Yes, and for a pre-revenue business that is often the right call, but budget for a rebuild later, not a migration. Wix offers no export at all and Squarespace exports only a partial WordPress file, so your text and images move by hand while design, structure, and functionality start over. Two protections now make the eventual move cheaper: register the domain in your own account, and keep a list of your page URLs so every one can be 301 redirected at switchover.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
Should I hire a freelancer or an agency to build my website?
A strong freelancer is the better buy for a small, well-defined site, typically 30 to 50 percent below agency pricing for the same scope in the quotes Digital Heroes gets compared against. An agency earns its premium when the project needs design, development, SEO, and project management at once, and when you want someone reachable in year two; solo builders regularly disappear into full-time jobs. A workable rule: below about $5,000 of scope a freelancer is fine, above it one person doing four jobs starts costing you schedule.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
How many people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
Can a custom website connect to the tools I already use, like my CRM and booking software?
Yes, and this is the strongest single argument for going custom: anything with an API can be integrated, including HubSpot, Salesforce, Calendly, Stripe, and Xero. Wix and Squarespace limit you to their app marketplaces, and the moment two tools need to talk to each other in a way no marketplace app anticipates, you hit the wall. List your must-have integrations in the brief; in Digital Heroes builds a standard integration adds roughly two to four days of development each.
What are the real limitations of Squarespace for a growing business?
You cannot run custom server-side code, database logic, or logged-in customer experiences beyond what Squarespace ships, and its templates constrain layout once your needs outgrow them. Migration is the hidden cost: Squarespace's export produces a partial WordPress file that skips product pages, styling, and several content block types, so leaving later means a substantial rebuild. It is excellent value for portfolios and simple sites from around $16 a month, but it is a ceiling rather than a foundation once your site needs to do things instead of just say things.
Can we migrate years of data out of our current system into new custom software?
Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.
What are the biggest mistakes first-time software buyers make?
Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.
Does it matter which tech stack the agency wants to use?
Yes, but not in the way most buyers expect: the goal is boring, popular technology such as React, Node.js or Python, and PostgreSQL, because any future team can maintain it and hiring a replacement developer takes days, not months. The red flag is an agency-proprietary framework or an unusual language, which welds you to that one vendor no matter what your contract says about code ownership. A useful test: could you find three freelancers fluent in this stack within a week? If not, push back.
Who can build a custom website system?
Digital Heroes builds custom website systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other website companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
Published · Last updated .
