What an online shop project really costs
Magento costs vary enormously in practice, and there are reasons for it. This guide sorts the one-off and ongoing items, explains the drivers behind big price differences and calculates an example with our published rates openly.
Table of contents
- 1. Magento costs at a glance: why there is no flat rate
- 2. One-off Magento costs for the build
- 3. Ongoing Magento costs in operation
- 4. Cost drivers: why offers lie so far apart
- 5. A worked example with open rates
- 6. Checklist: planning Magento costs realistically
- 7. Cost traps, risks and common misconceptions
- 8. How we keep Magento costs transparent
- 9. Summary
- 10. FAQ
1. Magento costs at a glance: why there is no flat rate
Anyone asking about Magento costs rarely gets a single number. That is not obfuscation but a result of the fact that a shop consists of building blocks of very different sizes. A retailer with 200 products and standard payment methods has a completely different project from a manufacturer with thousands of variants, customer group prices and a connection to an ERP system.
It helps to split the costs into two groups: one-off items for the build and ongoing items for operation. The one-off items are easy to plan once the scope is fixed. The ongoing items are often forgotten in budget planning, although over the years they frequently add up to more than the build.
The software itself is not the big item. Magento Open Source can be used free of charge, Adobe Commerce is a licensed variant whose price Adobe sets individually. The money mainly flows into working time: concept, set-up, customisation, data transfer, tests and support.
2. One-off Magento costs for the build
The one-off items include concept and design, setting up the shop with theme and basic configuration, taking over products, customers and orders from a legacy system, connecting payment and shipping, and tests before go-live. The more individual the design and the more special functions, the more hours accrue.
A big lever is the frontend. A modern, lean theme such as Hyvä usually saves development effort on customisations compared with a classic set-up and delivers faster pages. Faster pages in turn influence bounce rates and rankings, which indirectly affects revenue.
Then come extensions. Some functions can be solved with ready-made modules, others need custom development. Ready-made modules mostly have a fixed purchase price, custom development is billed by effort. Have the offer state which function is implemented with which solution.
3. Ongoing Magento costs in operation
Operation includes hosting, maintenance, security updates, monitoring, backups and smaller changes to content and functions. Added to this are fees of payment providers and possibly running licences for extensions. Anyone who does not plan for these items gets an unpleasant surprise after the start.
Security and feature updates appear several times a year. They have to be applied and tested, especially if the shop uses extensions. Anyone who does not want to do this themselves should plan a maintenance package. With us these packages start at 89 euros per month and can be cancelled monthly.
Further development is also an ongoing item. No shop stays unchanged for years, and new payment methods, marketplaces or legal requirements demand adjustments. Plan an annual hours budget for this so that such changes do not trigger a fundamental decision every time.
4. Cost drivers: why offers lie so far apart
When offers for seemingly the same project differ strongly, it is almost always due to different assumptions. The following table shows the most common drivers and how they affect the cost.
| Cost driver | Effect on Magento costs | What you should clarify |
|---|---|---|
| Size of the range | More products and variants increase effort for data transfer and upkeep | Number, variants, attributes, image material |
| Design | Individual design costs more hours than an adapted standard theme | Own design or theme with customisation |
| Interfaces | Every connection to ERP, PIM or shipping needs development and tests | Which systems, which data flows |
| Data migration | Legacy data must be cleaned, mapped and checked | Source system, data quality, volume |
| Extensions | Ready-made modules save time, custom development is more flexible but costlier | Function list with priorities |
| Multilingual | Each language and country brings translation, taxes and legal texts | Markets, languages, currencies |
| Operation and support | Response times and support determine the ongoing items | Desired availability |
Another driver is the quality of preparation. If you bring requirements in writing, that saves queries and therefore hours. Unclear wishes, on the other hand, lead to changes in the middle of the project, and those are almost always costlier than good planning.
5. A worked example with open rates
The following figures are a worked example, not a price guarantee. They are meant to show how Magento costs add up. We calculate with our published hourly rate of 30 euros. Assume that for an extension we estimate 24 hours and for tests and coordination another 6 hours. That is 30 hours and therefore 900 euros net. Only after the first call can anyone seriously say how many hours your project actually needs.
For ongoing operation, our orientation is: a shop rental starts at 100 euros per month service rate plus about 50 euros server cost, so from about 150 euros per month, plus a one-off set-up from 490 euros. Anyone who hosts the shop themselves buys a maintenance package from 89 euros per month instead of the rental. All models and prices are openly listed on the pricing page.
For larger projects such as relaunch, migration or ERP connection there is a custom offer. There we calculate by effort at the known hourly rate, either as a fixed price when the scope is clear enough or as an hourly estimate with an upper limit.
6. Checklist: planning Magento costs realistically
How to plan your budget for Magento costs
- ✓Write down the scope: products, languages, payment methods, interfaces, wanted special functions
- ✓Calculate one-off build costs and ongoing operating costs separately
- ✓Reserve at least a third of the build budget for tests, corrections and the unforeseen
- ✓Plan hosting, maintenance and updates from the start instead of clarifying them after launch
- ✓Demand hourly rate, estimate and possible upper limit in writing from every provider
- ✓Have ready-made modules and custom development shown separately in the offer
- ✓Plan an annual hours budget for further development and legal adjustments
7. Cost traps, risks and common misconceptions
The most common cost trap is a fixed price without a clear scope of services. It sounds reassuring but often leads to change requests as soon as a function was not described unambiguously. Demand that every offer states in writing what is included and what is not.
Where budgets typically derail
Budgets are often exceeded by later change requests, underestimated data transfer and missing care after launch. Anyone who skips maintenance and updates saves in the short term and pays later for repairs after a security incident or a failed update. Include these items from the beginning.
Very low offers without justification are equally risky. If the price is clearly below the market, ask what is missing: tests, documentation, support or access to the source code. A cheap start that triggers expensive corrections later is no saving.
One misconception says Magento is free because the open-source version costs nothing. The software is a small part of the total cost, the biggest share is working time and operation. The opposite misconception says Magento is generally too expensive for small retailers. With a manageable scope and a fitting operating model, such as a rental, even a small shop can be run economically.
A third misconception is the expectation that the price is fixed after the first conversation. A price can only be stated seriously once systems, data and requirements are known. Anyone who names a fixed number beforehand either includes a large safety margin or plans later change requests.
8. How we keep Magento costs transparent
We are a web agency in which fixed freelancers work together, all remotely from a home office. We do not maintain office or reception rooms and therefore do not pay for them through your hourly rate. That is one reason we can state an open rate of 30 euros per hour. Collaboration runs by video call, Git and a ticket system.
Before the project starts you receive a written effort estimate, either as a fixed price or as an hourly estimate with an upper limit. Our services for Magento web shops are described and the prices are open. This article is general orientation, and the figures in the worked example are not binding offers.
9. Summary
Magento costs consist of a one-off build and ongoing operation. The software is the small part, working time, hosting and maintenance make up most of it.
Magento costs, the essentials at a glance
Two pots
Build is one-off, operation is ongoing, plan both separately
Know the drivers
Range, design, interfaces and data migration set the price
Calculate openly
Demand hourly rate, estimate and upper limit in writing
Plan operation
Include maintenance and updates in the budget from the start
Note: This article offers general information. The figures in the worked example are not binding offers.