he implementation budget for a mid-sized or large B2B platform typically ranges from PLN 150,000 to PLN 1.5 million for the project itself, with licensing accounting for a smaller share than most companies expect. The largest and most frequently underestimated cost is neither the platform nor the storefront, but integration with internal systems and the work required to organise product data.
Why most estimates are too low
Three reasons recur in every project.
First: estimating features rather than processes. Estimates are based on a list of features from the vendor's website rather than on how customers actually buy. An order involving unit-of-measure conversions, multiple delivery locations and managerial approval may be a single item on the feature list, but in reality it represents several weeks of work.
Second: treating integration as a lump-sum item. In many proposals, ERP integration appears as a single line with a round figure. In practice, it involves five to eight separate data flows, each with its own error-handling logic, data freshness requirements and retry mechanisms. It is usually the most expensive part of the project.
Third: assuming the data is ready. The budget is drawn up on the assumption that the product catalogue will simply be migrated. It then turns out that attributes are embedded in descriptions, units of measure are inconsistent and some data exists only at supplier level. Organising the data becomes a separate project that nobody planned for.
Five cost components
These percentages are indicative and based on our projects. The product data component varies the most and is often what determines whether the project stays within budget.
Component 1: licensing — what vendors actually publish
There are more misconceptions surrounding this component than any other, so it is worth separating facts from estimates.
Shopware: published pricing
Shopware states that pricing depends on GMV and individual factors, so 'from EUR 2,400' is an entry-level price, not the final amount. The actual licence cost for a B2B company with turnover in the tens of millions of Polish zlotys will be higher.
Shopify: published pricing
There are also costs that are easy to overlook: additional Plus stores at USD 300 per month beyond the primary store and nine included expansion stores, and a 0.20% transaction surcharge when using a payment gateway other than Shopify Payments. At higher volumes, Shopify switches to a variable, revenue-based platform fee, the amount of which it does not publish. For large B2B businesses, this means that USD 2,500 is not the final figure and the fee is subject to negotiation.
Adobe Commerce: unpublished pricing
Adobe does not publish any licence prices. The ranges quoted in agency materials, typically around USD 22,000–125,000 per year for the on-premises version and USD 40,000–190,000 for the cloud version, depending on GMV, are third-party estimates. We provide them as an indication of the order of magnitude for initial planning and recommend confirming them with Adobe. It is also important to remember that the B2B module is available exclusively under an Adobe Commerce licence, never in Magento Open Source, and access is governed by contractual entitlement.
Licences that are often overlooked
Operation-based iPaaS pricing requires particular attention because costs do not scale well when stock and order synchronisation generates high traffic. It is worth calculating this against actual volumes rather than averages.
Component 2: implementation
The complexity of the sales process matters more here than the number of pages. The following factors have had the greatest impact on implementation effort in our projects.
- Pricing complexity. A base price list with group discounts is one level of effort. Customer-specific contract prices, volume discounts, contractual terms and prices for selected items are an entirely different undertaking, often requiring a dedicated price server.
- Product configurability. Configurable products or products priced according to parameters can be the largest single component of the project.
- Unit-of-measure conversions. Kilograms to pallets, metres to packs, individual items to cases. This requires consistency across the entire chain: catalogue, basket, documents and ERP.
- Customer hierarchies and approvals. Headquarters, branches, purchasing groups, budgets and approval thresholds.
- Sales representative portal. Almost always necessary if the company has a sales team, and usually estimated separately.
- Multiple languages and markets. Each market requires more than translation: taxes, documents, payment methods and delivery options also need to be addressed.
Component 3: integrations — the most frequently underestimated cost
Integration is not a single budget item. It is a collection of data flows, each with its own cost.
Two factors increase this cost disproportionately.
First: the absence of a ready-made connector. As of 24 August 2026, the official Shopware Store has no connector for Comarch, enova365, Symfonia or Streamsoft. Shopify runs a partner programme with certified ERP connectors, but it does not cover Polish systems. Adobe provides an Integration Starter Kit, which is an integration framework rather than a connector. Integration with Polish ERP systems always requires custom work, which needs to be included in the budget rather than assuming a plug-in will suffice.
Second: the architecture of the ERP itself. An extreme example is Comarch ERP XL, whose API is a native, thread-bound Windows library. Its documentation explicitly advises against asynchronous patterns, and it requires an agent running on a machine with the ERP installed. It cannot be queried directly from a cloud platform, so a middleware layer must be included in the budget. Other systems have similar constraints: Dynamics 365 Business Central limits a single user to five concurrent OData requests and 6,000 requests per five-minute window, which becomes a hard throughput ceiling when using one service account.
Component 4: product data
This is the most variable item in the entire budget, ranging from a few per cent to one fifth of the project.
Signs that this will be expensive:
- Product attributes are embedded in marketing descriptions rather than stored in fields with a defined set of values.
- There is no single source of truth for product information; data is scattered across the ERP, spreadsheets and supplier files.
- Units of measure are inconsistent across systems.
- Some data, for example information on the origin of materials, exists only with suppliers and in PDF files.
- The catalogue contains more than several thousand items across multiple channels and languages.
Three or more of these issues usually indicate the need to implement a PIM system as part of the project or immediately before it. This investment pays off beyond e-commerce because the same data structure underpins multichannel sales, international expansion, Digital Product Passport requirements and product visibility in AI-powered channels.
Component 5: post-launch maintenance
As a rule of thumb, annual maintenance costs amount to 15–25% of implementation costs. For B2B, the figure is closer to the upper end because integrations require continuous attention.
This component covers the SLA and monitoring, platform and extension updates, integration maintenance as the ERP changes, ongoing feature development, hosting and infrastructure. It is also worth allocating a separate compliance budget, as 2026 and 2027 bring additional digital accessibility requirements and, for some industries, the need to prepare data for the Digital Product Passport.
Three budget scenarios
The indicative ranges below are based on our projects. They are estimates, not a price list, and are intended to establish whether the expected budget is in the right order of magnitude.
Scenario A: first B2B platform, simple business model
One company, one market, group-based pricing without contract prices, a catalogue of up to 1,000 items and an ERP with an HTTP API.
Implementation time: 4–7 months.
Scenario B: distributor or manufacturer, complex B2B model
Customer-specific contract prices, a sales representative portal, credit limits, several delivery locations, a catalogue of several thousand items and a Polish ERP system without a ready-made connector.
Implementation time: 8–14 months.
Scenario C: multiple markets and companies
Several markets and languages, multiple companies, configurable products, unit-of-measure conversions, budget approvals and EDI for large customers.
Implementation time: 12–24 months, usually in phases with a market-by-market rollout.
Where not to cut costs
Budget pressure is natural, but some cuts end up costing significantly more later.
- Workshops before estimation. The least expensive part of the project and the only one that genuinely reduces the risk of exceeding the budget.
- A sales representative portal if you have a sales team. Cutting costs here results in a platform with low adoption, effectively wasting the entire investment.
- A price server for complex pricing models. Without one, response times for large baskets make the platform unusable, and fixing the problem later is more expensive than building it correctly from the outset.
- Idempotency and error handling in integrations. Shopify explicitly does not guarantee exactly-once webhook delivery and retries up to eight times over four hours. Without safeguards on the receiving side, duplicate orders will occur.
- Organised product data. Postponing this work usually means a second project of similar value.
The cost of poor decisions: items that never appear in estimates
Three examples from real situations that are worth factoring into the risk assessment.
Overselling caused by overwriting stock levels. In Adobe Commerce, salable quantity is calculated from stock quantities at inventory sources, adjusted for reservations created when orders are placed. An integration that writes inventory levels directly to the sources bypasses the reservation lifecycle and generates orders for goods that have already been reserved. The cost goes beyond corrections: it also includes lost trust among B2B customers whose production may be disrupted by inaccurate availability information.
Overnight synchronisation as a source of inaccurate stock levels. Microsoft's documentation provides a precise example: with ten units in stock and two open orders, synchronisation on Tuesday publishes nine units and on Friday seven. The quantity displayed in the online store depends on when the task was run rather than on the physical stock level.
Choosing a platform without checking its limits. If the model relies on customer-specific contract prices and Shopify is selected on a plan below Plus, prices can only be assigned through Markets, with a maximum of three active catalogues. Correcting this means either upgrading to Plus, with a substantial increase in licence costs, or restructuring the pricing model.
How to build a budget that stands up to scrutiny
- Map the sales process, including activities that currently take place outside the system. Email and telephone orders are part of the scope, not exceptions.
- Estimate each integration flow separately. Define the direction, required data freshness and behaviour in case of failure for each one. Without this, integration becomes a lump-sum estimate and a likely source of budget overruns.
- Audit product data before requesting an estimate. This takes two to four weeks and can change the budget by several hundred thousand Polish zlotys.
- Check platform limits against your actual requirements, not against a feature list. Consider pricing tiers, the number of catalogues, units of measure and approvals.
- Plan a phased rollout. Launching in one market or for one customer group provides real data before the entire budget is spent.
- Allow a contingency for ERP changes. The ERP can also change during the project, and in Poland mandatory invoicing through KSeF has introduced an additional requirement.
- How we approach budgeting at Strix
Strix is an e-commerce agency operating since 2009, with offices in Kraków, Utrecht and Frankfurt am Main. We prepare estimates after workshops, not before them, and break down the budget into the five components described above to make the areas of risk visible.
Our publicly available reference figures are hourly rates of USD 150–199 and project values of USD 40,000–400,000, according to our Clutch profile, with typical implementation times of 6–18 months depending on scope. Accelerators such as B2B Box and the Headless PWA Frontend Accelerator reduce time to market.
The B2B projects behind these estimates include Lynka, Orno, 3W Group, EMM International, Agrorami, Dr. Hauschka, Tuindeco and Reifen1+, as well as B2B consulting for Decathlon.
Frequently asked questions
How much does it cost to implement a B2B platform? In the mid-sized and large business segment, the project budget typically ranges from PLN 150,000 to PLN 1.5 million, depending on pricing complexity, the number of integrations and the condition of product data. Licensing alone typically accounts for 10–25% of the first-year budget.
What is the largest cost component in a B2B platform budget? Implementation and integrations, together accounting for 55–85% of the first-year budget. ERP and internal system integrations are the most frequently underestimated item because many proposals present them as a single lump sum, whereas in practice they involve five to eight separate data flows.
How much does a Shopware licence with B2B features cost? B2B Components are available from the Evolve plan, starting at EUR 2,400 per month excluding VAT. Community Edition and Rise do not include them. Shopware states that pricing also depends on GMV and individual factors.
How much does Shopify Plus cost? USD 2,500 per month with a one-year contract or USD 2,300 with a three-year contract. Additional stores beyond the ten included cost USD 300 per month each, and a 0.20% transaction surcharge applies when using a gateway other than Shopify Payments. At high volumes, Shopify switches to an unpublished variable fee based on revenue.
How much does an Adobe Commerce licence cost? Adobe does not publish prices. Third-party estimates suggest around USD 22,000–125,000 per year for the on-premises version and USD 40,000–190,000 for the cloud version, depending on GMV. These are estimates, not vendor figures, and must be confirmed with Adobe.
How much does it cost to maintain a B2B platform after implementation? Approximately 15–25% of implementation costs per year, with B2B generally closer to the upper end because of integrations. This includes the SLA and monitoring, updates, integration maintenance when the ERP changes, feature development and infrastructure.
Why is integration with Polish ERP systems more expensive? Because there are no ready-made connectors for them. The official Shopware Store has no extensions for Comarch, enova365, Symfonia or Streamsoft, and the Shopify partner programme and Adobe Integration Starter Kit do not cover Polish systems. Some Polish ERP architectures also require middleware: for example, the Comarch ERP XL API operates as a synchronous Windows library requiring an agent on the machine running the ERP.
Can a B2B platform be implemented in phases to spread the cost? Yes, and we usually recommend this approach. Sensible reductions in scope include starting with one market, one customer group or one sales region. It makes little sense to remove the sales representative portal when there is an existing sales team, the price server when pricing is complex, or product data organisation, because each of these cuts reduces the value of the entire investment.
How long does it take to implement a B2B platform? Four to seven months for a simple model, eight to fourteen months for a complex B2B model with contract prices and a sales representative portal, and twelve to twenty-four months for multiple markets and companies. Accelerators can reduce time to market, but they do not shorten the analysis or integration work.
Next step
A reliable budget can only be prepared after mapping the sales process and auditing product data. Together, these activities usually take three to six weeks and are the best investment you can make in the entire project.
Strix, an e-commerce agency operating since 2009. Offices in Kraków, Utrecht and Frankfurt am Main.