--- title: "What does a B2B web shop cost? Costs and duration | ECOPLAN" description: "An integrated B2B web shop with a customer portal typically costs €80,000 to €120,000 at ECOPLAN. Sample calculation, ongoing costs, project duration." url: "https://www.ecoplan.com/en/services/b2b-webshop-costs.php" --- # What does a B2B web shop cost? Costs and project duration at ECOPLAN Find out here what introducing an integrated B2B web shop with a customer portal costs, how the effort is made up, and how long a project takes. [Request a project](#contact) [Book a call directly](/en/contact/book-a-call.php) Complete solution, no MVP ERP integration included Transparent calculation ![Costs and project duration of a B2B web shop](/wAssets-ecoplan/img/agentur/kosten-hero-projektdauer-en.svg) Costs and project duration of a B2B web shop ## What does an integrated B2B web shop cost? Introducing a complete B2B web shop with an integrated customer portal, including integration of ERP, PIM, and CRM, typically costs 80,000 to 120,000 euros at ECOPLAN. This is not a minimum version (MVP), but the complete, fully integrated solution. ![Typical implementation costs compared: €80–120k versus the often-cited €250k and more](/wAssets-ecoplan/img/agentur/kosten-einfuehrung-vergleich-en.svg) Typical implementation costs compared: €80–120k versus the often-cited €250k and more €80,000–120,000 typical implementation costs, fully integrated, no MVP ca. 67 person-days in the sample calculation 98% of requirements covered with standard functions 1–3 person-days for major updates ## Sample calculation based on avanta ECOPLAN calculates based on avanta, a B2B commerce platform recognized as a Leader on OMR Reviews. It includes typical B2B functions as standard, such as customer-specific prices, roles and permissions, approvals, customer portal, PunchOut, and order automation. In our experience, this covers around 98% of requirements. Anything beyond that is evaluated as customizing in the workshops and calculated separately. > avanta covers 98% of our complex requirements with standard functions. Dr. Dominik Eberl, Head of eBusiness, profine GmbH - International Profile Group ![98 percent of requirements covered as standard](/wAssets-ecoplan/img/agentur/kosten-98-prozent-standard-en.svg) 98 percent of requirements covered as standard ## How the implementation costs are made up The ECOPLAN sample calculation for a B2B web shop with a customer portal at standard functional scope, including integration of ERP, PIM, and CRM: | Component | Content | Effort | Cost | | --- | --- | --- | --- | | Planning & workshops | Requirements and integration workshop, documentation, follow-up coordination, concept design | approx. 8 person-days | approx. 12,500 € | | Configuration | Setup of web shop and customer portal within the standard functional scope | approx. 20 person-days | approx. 29,600 € | | Coordination & alignment | Meetings and alignment with your team, internal coordination | approx. 14 person-days | approx. 20,700 € | | Integration | Data model, design and implementation of the interfaces to ERP, PIM, and CRM, testing and quality assurance | approx. 25 person-days | approx. 37,000 € | | Total | approx. 67 person-days | approx. 99,800 € | | ## Why this is less than often assumed For integrated B2B shops, 250,000 euros and more are often quoted. The reason: the shop is built in an elaborate way, with numerous extensions, apps, and custom developments. 100 to 150 person-days and more are quickly used up for this before the integration even begins. At ECOPLAN, the shop runs on standard functions with around 20 person-days. That is why the integration with ERP, PIM, and CRM, at around 25 person-days, is the largest component here. This is exactly where the real value of a B2B shop is created. ECOPLAN is not cheaper per day, but needs fewer days. ![Person-days compared: elaborate shop versus ECOPLAN](/wAssets-ecoplan/img/agentur/kosten-personentage-vergleich-en.svg) Person-days compared: elaborate shop versus ECOPLAN ## What to look for when comparing quotes Check how many days go into building the shop and how many into the integration. Some quotes allow only a few days for the integration or leave it out entirely, and the actual costs only become apparent during the project. At ECOPLAN, integration is a fixed part of the calculation. ![Comparing quotes: check effort for shop and integration separately](/wAssets-ecoplan/img/agentur/kosten-angebote-vergleichen-en.svg) Comparing quotes: check effort for shop and integration separately ## What is not included in the ECOPLAN sample calculation ![Icon for customizing](/wAssets-ecoplan/img/agentur/icons/sliders-horizontal.svg) Customizing ### Customizing if requirements actually go beyond the standard functions. This is more the exception, because ECOPLAN deliberately limits customizing to what is necessary. The effort is evaluated in the workshops and calculated separately. ![Icon for AI applications](/wAssets-ecoplan/img/agentur/icons/sparkles.svg) AI applications ### AI applications ECOPLAN quantifies the effort only after the requirements have been clarified, because it depends on the specific use case. ![Icon for rollout](/wAssets-ecoplan/img/agentur/icons/rocket.svg) Rollout ### Rollout to additional countries, languages, sales organizations, or brands. For this, ECOPLAN plans an additional services budget, as well as for training and support during go-live. For additional websites or organizational units, additional license and ongoing costs may need to be considered. ## Ongoing costs Monthly costs for usage, SLA and hosting of an ECOPLAN solution as SaaS start at approx. €2,000. System maintenance and updates add approx. €12,000 per year and up. There are no revenue shares or transaction fees. ![Ongoing costs for SaaS, hosting, and system maintenance](/wAssets-ecoplan/img/agentur/kosten-laufende-saas-hosting-en.svg) Ongoing costs for SaaS, hosting, and system maintenance ## Updates: the underestimated cost factor Prospects with heavily customized shops often report update costs between 30,000 and 50,000 euros, not infrequently twice a year. Updates alone thus add up to 60,000 to 100,000 euros per year. With ECOPLAN solutions, major updates are usually completed in one to three person-days, because as much as possible is covered with standard functions. ![Update effort per year compared](/wAssets-ecoplan/img/agentur/kosten-updates-aufwand-pro-jahr-en.svg) Update effort per year compared ## Project duration How long an ECOPLAN project takes depends mainly on how closely the requirements match the standard and how quickly data and contact persons are available on the customer side. Two examples in which ECOPLAN implemented the complete, integrated solution from the first workshop to go-live: ![Oest logo](/wAssets-ecoplan/img/referenzen/ohne-schutzraum-schwarz/oest.svg) Oest 4 months from workshop to go-live ### Oest B2B web shop with SAP integration in four months [View Oest case study](/en/references/oest.php) ![Prodinger logo](/wAssets-ecoplan/img/referenzen/ohne-schutzraum-schwarz/prodinger.svg) Prodinger 4 months from workshop to go-live ### Prodinger B2B web shop with Oracle integration in four months [View Prodinger case study](/en/references/prodinger.php) ECOPLAN usually starts AI applications with a pilot project that takes 4–6 weeks. Project inquiry ## Want to know what your B2B shop will cost? Tell us your requirements. **Simply fill out the form. We will get back to you within 2 business days.** If you would rather talk directly, book an appointment with us. Afterwards you will receive a transparent cost breakdown for your solution. 30 minutes by video conference, no obligation. [Book a call directly](/en/contact/book-a-call.php) ## FAQ – Frequently asked questions ### What does a B2B web shop with a customer portal and ERP integration cost? The cost of a B2B web shop with a customer portal depends mainly on the scope of the integration with ERP, PIM, and CRM and on the share of customizing. At ECOPLAN, most of the calculation goes to the integration, because the shop itself comes as standard. Customizing, AI applications, and the rollout to additional countries are not included. ### How long does it take to implement a B2B web shop? How long implementation takes depends on how closely the requirements fit the standard and how quickly data and contacts are available. The Oest shop went live four months after the first workshop, the Prodinger shop four months after project kickoff. AI applications start with a pilot of 4 to 6 weeks. ### What ongoing costs are there? Ongoing costs arise for usage, SLA, and hosting as well as for system maintenance and updates. Updates remain manageable at ECOPLAN because customizing is deliberately limited to what is necessary. ### What should I look for when comparing B2B shop offers? Check how many days are allocated to building the shop and how many to the integration. Some offers allocate only a few days to the integration or leave it out entirely, and the actual costs only become clear during the project. At ECOPLAN, the integration is a fixed part of the calculation. ### Why does a B2B shop at ECOPLAN require fewer effort days? The reason lies in the effort, not in the daily rate: ECOPLAN is not cheaper per day, but needs fewer days. The shop comes as standard because the platform already includes typical B2B functions, so the integration with ERP, PIM, and CRM is the largest component of the calculation. With heavily customized shops, by contrast, a lot of effort goes into extensions, apps, and custom development. ### Why do updates remain manageable with ECOPLAN solutions? ECOPLAN covers as much as possible with standard functions and deliberately limits customizing to what is necessary. As a result, major updates can usually be completed with little effort. With heavily customized shops, updates are often an underestimated cost factor.