We support and implement online stores and B2B ecommerces on Magento. With us, your store will be fast (over 80 points for mobile and 90 for desktop on Google PageSpeed), safe, with low maintenance costs, and will convert exceptionally well.
Adopting a technology that only a few developers use can be problematic since you can’t easily switch your software house or ecommerce agency in case of poor collaboration. There are approximately 110.000 Magento developers and hundreds of companies with Magento expertise. Consequently, the development of your business isn’t dependent on a single company, as it can be easily replaced.
Ecommerce licensing fees can substantially increase implementation and maintenance costs, decreasing the profitability of the entire business. Magento is open-source software without licensing fees, effectively reducing your implementation and maintenance costs.
Managers of rapidly growing ecommerces often complain that when the number of products, orders, and users increases, the store begins to malfunction, preventing customers from placing orders correctly and leading to a loss of revenue. That’s why Magento is designed to function flawlessly, even with several hundred thousand monthly orders and millions of products in the database.
Companies are increasingly entering foreign markets. They are looking for ecommerce technology that will work correctly on the scale of dozens of countries and allow the customization of prices, payment forms, delivery, product offerings, and the store’s appearance for each market. That’s why we use Magento, which allows for such configuration. We use one admin panel and one back-end, which reduces your implementation and maintenance costs.
Incomplete integrations are a significant problem in growing ecommerces and B2B companies. Some work is done manually, which is time-consuming and error-prone. That’s why Magento has an extensive API, allowing you to integrate Magento with any ERP, CRM, or payment system.
Ecommerce directors and owners complain about the increasing costs of acquiring users. Magento, utilizing Hyva, is very fast. This will result in your site receiving more free organic traffic and increasing your business’s profitability.
Magento is excellently prepared for SEO optimization. As a result, you will gain higher positions in search results, leading to more free traffic from organic searches.
The ecommerce market is becoming increasingly competitive. To stand out, one must implement new and unconventional functionalities. With Magento, you can build any solution. You are not confined to the rigid framework of a SaaS platform.
Are you a brand, manufacturer or distributor selling directly to consumers in a B2C model?
If so, we will help you create a fast store (with Google PageSpeed ratings over 80 for mobile and 90 for desktop) that sells well. Whether your company is 100% focused on online or your ecommerce is intended to support the omnichannel strategy.
Are you a company that operates in a B2B model?
If so, we will assist you in creating a B2B ecommerce on Magento that will enhance your sales department’s efficiency and fit into your company’s digital transformation. Your clients will be satisfied with real-time access to financial and accounting data, and that trade conditions in ecommerce will be the same as those offered by your sales representative.
Contact us. We’ll discuss your business situation and determine together if Magento is a good choice.
We build modern and top-selling online stores. It doesn’t matter if you have experience in ecommerce and want to move from PrestaShop or WooCommerce, or if investing in Magento is your company’s first and decisive step in ecommerce. With years of experience, we know how to tailor Magento 2 to your business requirements and your customers’ needs.
Are you in the process of implementing a new online shop or B2B ecommerce, but the project is over budget, behind schedule, and the code written is full of bugs? We assist companies in such situations. We start with an audit of the project’s current state (evaluation of code quality, integrations, graphic design, and system architecture), verifying the pre-deployment analysis. Next, we develop a plan to fix errors and complete the project.
Are you tired of your current agency that lacks initiative, merely completing assigned tasks and leaving much to be desired? Join our clientele for whom we are an inseparable business partner. We analyze their data, involve a strategist, and build a development backlog, which we efficiently implement while maintaining the highest quality standards.
We also have expertise in:
Designing user experience for Magento stores
Migrating online shops and B2B ecommerce from other engines to Magento
Omnichannel implementations based on Magento
Audits and optimization of code quality, performance, and speed
Advanced integrations with PIM, ERP, CRM, payment systems, and courier services
Creating ecommerce with headless PWA technology
Migrations from Magento 1 to the latest Magento 2
PIM implementations (Akeneo)
Coding Magento frontends based on Hyva technology
We conduct workshops with your team to understand your business, its competitive advantages, systems, and strategy. We prepare UX sketches and a custom graphic design. We plan the system architecture. An Ecommerce Consultant coordinates this stage. A solid pre-implementation analysis reduces the total cost of implementation and provides financial security and predictability.
At this stage, we code the backend and frontend and perform integrations. We work with Agile methodology. Every two weeks, you receive newly completed components of your ecommerce. Before any new functionality reaches you, it is thoroughly tested by a Tester. This saves you time from reporting bugs and prevents you from feeling like an external tester of the ecommerce agency you work with.
Product data are transferred to PIM, and order data and registered user information are transferred to Magento. During this stage, we also carry out SEO migration.
At this stage, you finally check whether the service is functioning correctly. This should go smoothly because, throughout the implementation phase, a Tester verified all features, and every two weeks, subsequent parts of the service were delivered.
As soon as we get the signal from you that the service is in order, we set a date for your new store (or B2B ecommerce) to be made available to your customers. We meticulously go through each point on the checklist during the launch. This increases security.
After the store launch, we will continue to develop new functionalities, install modules updates, and ensure security. We aim to be a long-term partner that helps grow your business, make strategic decisions, and provide support after implementation. We achieve this through the involvement of an Ecommerce Consultant with at least 10 years of experience and a Project Coordinator with experience in ecommerce.
What sets us apart is our focus on the revenues and efficiency of our Clients. We create fast online shops that sell exceptionally well and B2B ecommerces that increase the efficiency of sales departments.
How do we achieve this? For each project, we implement our 16 technological solutions that increase sales, and we also provide an ecommerce consultant with at least 10 years of experience in the online industry.
Ecommerce directors and owners want as many visitors as possible to purchase in their stores. In our projects, we achieved an average of 41% increase in conversion rates. We manage this because we always implement 16 proprietary technological solutions for free, increasing the conversion rate. In addition, before we design your store, we learn about its users, how they navigate the site, and what prevents them from making purchases. This ensures that the stores we create achieve excellent sales.
Clients who have experience working with a Software House often complain that it is not a partner for business discussions. That’s why we assign an ecommerce consultant with at least 10 years of experience in the industry to each project. As a result, our Clients receive support when making development decisions.
A big problem is the rising cost of acquiring users in ecommerce. This reduces the profitability of the entire business. Therefore, we have created a set of 4 free modules for Magento, which increases organic traffic. This reduces the cost of customer acquisition and improves the profitability of the entire organization.
Magento allows for handling several hundred thousand transactions per month and can quickly work with a multi-million product database. However, its downside is the maintenance and development costs. In Magento, we use Hyva—the maintenance and development costs are 50% less than PWA and about 20% less than traditional Magento front-ends based on Luma. If the business has several different stores, we use only one back-end. This reduces the implementation costs and later maintenance and development.
When choosing a software house to implement Magento, it is very difficult to assess and compare the competencies of the development team. That’s why we are an Adobe-certified partner and ensure each team member has a certificate confirming their knowledge of Magento. This means that your choice is safer because you know that an external company has verified our competencies and processes.
We have noticed that the most difficult stage in Magento deployment is integration. Therefore, we have built a team capable of integrating Magento with the most popular systems in Poland. We have carried out Magento integration with ERPs (Subiekt GT, Wf-Mag, Enova, Streamsoft, Comarch XL, SAP), PIMs (Akeneo, Pimcore, ETIM Mapper) and OMS (Baselinker, Apilo, Selly)). As a result, the total cost of integration in your project will be lower and completed on time.
A huge problem for ecommerce owners and directors is that the actual implementation budget is often much higher than the initial estimates from the valuation stage. That’s why we conduct a detailed business analysis coordinated by an Ecommerce Consultant. The acceptance criteria, graphic design, and system architecture are created during this process. As a result, the scope is accurately described and can be detailed estimated by developers. This means that the budget estimation matches the actual cost and is predictable.
We noticed that a significant problem when working with ecommerce agencies is that they only make the store clickable at the end of the implementation. Therefore, the Coordinator on your side must give up all other tasks and spend a few weeks checking the entire store. They become a bottleneck in the process of launching a new store. All parties put pressure on and rush to finish the checking stage as quickly as possible. That’s why we provide a clickable version just 2 weeks after starting coding. Every 2 weeks, it grows with the coded functionalities. Your Coordinator can calmly and regularly check new elements of the store. And you control the direction in which the project is going.
We have prepared straightforward and specific answers to the most common questions we get from people considering Magento.
Magento 2 is an ecommerce that comes in two versions: the free Community Edition and the paid Adobe Commerce. It’s open-source software, meaning it’s publicly available and customizable to individual needs. In short, you have access to every line of code, and can freely modify such an ecommerce or B2B ecommerce.
Compared to other open-source ecommerce engines, Magento is easy to expand beyond the standard and continues to function correctly even when heavily modified. Secondly, it easily withstands large-scale traffic, products, currencies, and languages. Therefore, it’s an excellent choice for growing online stores (especially if they plan to operate in many different geographic markets) and for B2B ecommerces. In B2B sales, every company has a unique sales strategy and it’s essential to tailor the ecommerce to the sales strategy, not the other way around.
Magento 2 hit the market in 2015. Since then, it has evolved significantly, and today it is a stable and continuously developing ecommerce engine with new functionalities.
Selecting a business partner for Magento implementation and subsequent development is challenging. If you want to choose an ecommerce agency so that the Magento implementation is professional, it’s worth paying attention to a few points.
Agency Certification—Adobe, which owns Magento, certifies its partners. This ensures that the agency’s processes and team have been checked by an external company.
Project Coordinator Doesn’t Perform All Roles—If an ecommerce agency claims that they have a Renaissance man who performs the role of Project Coordinator, Business Analyst, Ecommerce Business Consultant, and Tester, then it’s unlikely that the agency can be a proactive business partner. It is best to choose a software house where these roles are performed by different individuals.
Experienced Ecommerce Consultant—If the ecommerce agency states that an ecommerce consultant will be part of the project team, it’s worth investigating their experience. Ideally, this person would have worked as an Ecommerce Director.
Composition of the Project Team—Professional Magento implementations are carried out by professional teams. That’s how it is. Before the start of development work, ask the agency to present the exact personnel composition of the project team. Then check the experience of the members, at least on LinkedIn. If the proposed team consists only of juniors, it is not the best solution.
If you pay attention to these points when selecting an ecommerce agency, you will increase the likelihood of choosing a proactive Magento agency.
Once you have an Adobe Commerce license, you get access to their repository and can tap into their modules.
In the free version of Magento (Community Edition), you probably have several to dozens of extra modules.
When connecting to this repository, you might face conflicts due to module incompatibility. In such a case, simply disable the conflicting modules from the Adobe Commerce paid version.
The migration process is fairly straightforward. You just need to sort out conflicts between modules. Then, start removing modules from the free version of Magento (Community Edition) while enabling modules from Adobe Commerce.
The whole process is not costly and doesn’t take long. Everything depends on:
whether you remove all the conflicting modules at once,
or whether you upgrade Magento to the latest version before switching to the paid version, i.e., Adobe Commerce.
The cost of implementing Magento usually ranges between 84.000 EUR/USD and 98.000 EUR/USD, and this applies to B2C stores.
This cost mainly arises from calculating the hourly rate of developers multiplied by the number of hours needed to create an online store.
The number of hours required to code Magento depends on the scope of implementation.
The amount of 84.000 – 98.000 EUR/USD includes all stages of implementation, including business analysis, graphic design, coding, integrations,
testing, project management, and production launch. In total, it is about 1300-1500 hours of work by the software house.
Within this budget, a fast, integrated ecommerce with a custom graphic design will be developed, poised to generate a high conversion rate.
It’s worth remembering that if you include a multitude of functionalities and integrations within the implementation scope, the budget could exceed 280.000 EUR/USD.
B2B ecommerces costs more than B2C stores. This is because B2B ecommerce requires more functionalities from the very beginning. The cost of implementing a
B2B ecommerce on Magento ranges from 116.200 EUR/USD to 145.600 EUR/USD.
As with B2C stores, within this budget:
all stages of implementation are included
the ecommerce will be fully integrated
an ecommerce will be created with a custom graphic design and with several functionalities characteristic of B2B ecommerces (such as the transfer of pricing policies or the creation of a lead generation mechanism for new business)
Magento implementation usually takes about 7-9 months (until the coding is complete).
The analysis, design, and coding phase lasts from 7 to 9 months. Meanwhile, the testing and production rollout phase takes about a month.
The following factors primarily influence the Magento implementation timeline:
the size of the implementation (meaning the number of functionalities and integrations)
the number of different companies working on the project
how well-thought-out the project scope is
the number of developers assigned to the project by the agency you’ll be collaborating with
the quality of coding by the software house
Implementing Magento is not just the work of a software house but also your own. The amount of time your team or you personally will need to commit primarily depends on how extensive the implementation is and whether the agency you are working with carries out the testing process.
To greatly simplify, the implementation can be divided into four stages: business analysis, coding phase, UAT (User Acceptance Testing), and production launch.
The business analysis stage (pre-implementation, also known as the discovery phase) will require about 15 to 20 hours per week from your team.
The implementation phase will require approximately 11 to 31 hours per week.
UATs are the stage where you thoroughly check the store before its final acceptance, to make sure that everything is in order. This will take about 40 to even 100 hours.
As for the production launch, the involvement of your team is reduced to a minimum. It will probably be just one hour.
Magento MVP version is Magento with all the basic functionalities and integrations that ensure the proper operation of an online store. At Growcode, we recommend this approach because, with a faster store launch, it begins to generate revenue earlier and you will freeze less cash in the project itself.
Magento MVP implementation will include:
a custom graphic design (Hyva used on the front-end)
improved pricing communication
simplified checkout
integrations with ERP, PIM, and OMS
improved navigation and filtering
The time required to implement Magento MVP version is at least 1,300 hours. This translates into a budget of about 91.000 EUR/USD. Such a store will have a high conversion rate, be SEO optimized, be integrated, and achieve high scores in Google PageSpeed (over 80 on mobile and over 90 on desktop).
When implementing Magento, there are additional costs that most are not aware of. In total, during the Magento deployment, you have to consider 7
additional costs:
The work of your own team.
Services of a company integrating ERP with Magento.
Additional templates (Hyva license) and modules.
Server configuration.
Collaboration with an SEO agency.
Support from a web analytics company.
The production launch of the Magento store.
Several key points can help lower the costs of implementing Magento.
Changing frontend technology: You can save on implementation costs by choosing the right frontend technology. Opting for technology compatible with PWA (Progressive Web App) can significantly increase costs. It is worthwhile to consider whether another, simpler frontend would suffice for your project (for example, Hyva).
Limiting functionality: Not all functionalities need to be available right away. Using the MoSCoW method can help prioritize and understand which features are critical to start and which ones can be introduced later.
Simplifying design projects: The online store design should be thoughtful, but creating complicated designs is not always necessary, especially if the designer lacks experience with Magento.
Focus on business analysis: It’s worth spending more time on business analysis. It can help avoid unexpected costs during coding, and the budget will be more predictable.
Simplification of integrations: It’s not always necessary to create complex integrations. Sometimes existing solutions can be used, which can save time and money.
Considering other ecommerces: Magento is not always the best choice. It is worth considering other ecommerces, such as Shopify, which may be more suitable for small projects.
Price negotiations: Negotiating a lower hourly rate with the supplier can also help reduce project costs.
There are several reasons why it’s worth limiting the costs of the initial implementation of Magento. Firstly, a smaller project means a shorter period of cash freeze. Secondly, a smaller project is usually less complicated and carries a lower project risk.
Business analysis is a project stage where the target system’s design, functionality, and appearance are precisely defined. The results of this analysis
should include creating the system architecture, formulating business requirements in the form of stories and acceptance criteria, and preparing
graphic designs.
We can approach this topic in two ways.
Smaller-scale business analysis: This approach assumes it is sufficient to define the general assumptions at the beginning of the project and start the development work,
leaving the elaboration of details for later. This is typical for startup and innovative projects, where the rapid market entry and user testing of the product are essential.
Larger-scale business analysis: This approach suggests that it is worthwhile to accurately define the project details from the outset, including
graphic designs. This avoids wasting time. In the case of ecommerce projects, especially in the current uncertain economic environment, it provides greater
financial security, and budget control, and shortens the implementation timeframe.
The maintenance and development of Magento is a subject that is rarely discussed in our market. It is always important to remember that running an online store requires a budget for its upkeep.
For an ecommerce that has:
3000 transactions
150.000 monthly users
10.000 SKUs
3 environments (test, stage, and production)
the costs of maintenance and development over the next 5 years range from approximately 350.000 EUR/USD to 840.000 EUR/USD.
This amount will vary depending on the quality of support and hosting, as well as the level of development. The better the quality and the more intensive the development, the greater the costs you will incur. The first value corresponds to maintenance and very little development. The second value assumes intensive development activities.
If you’re wondering whether it’s possible to reduce costs upon seeing amounts from 350.000 EUR/USD to 840.000 EUR/USD – the answer is yes! There are several ways to do this.
Limit the number of hours allocated for development.
Ask the agency for an experienced Magento Project Coordinator to configure the panel independently.
Remove unused modules.
Try to negotiate a lower hourly rate.
Implement the Page Builder.
Obtain the Adobe Commerce Business Practitioner certification and perform part of the configuration work yourself.
Develop a standard for reporting bugs with the software hous.
Develop a standard for proposing new features with the software house.
Automate certain types of tests that were previously conducted manually.
It’s important to remember that everything depends on the software house you are working with and their hourly rates. Nonetheless, by applying these methods, you could save approximately 40-60 hours a month, which means about 33.600 – 50.400 EUR/USD annually if the rate is roughly 70 EUR/USD. If you are looking to save even more, you’ll need to reduce the number of hours designated for development.
One of the maintenance tasks for Magento is upgrading it to a higher version. When it comes to Magento updates, we have two options:
1. Minor upgrade – performing it is recommended twice a year.
These concern the last digit in the Magento version. For instance, a minor upgrade would be updating from version 2.4.3 to 2.4.4.
2. Major upgrade – usually occurs once every 3-4 years, and that’s when an update needs to be done.
A major upgrade relates to the middle digit in the version name. If the current Magento version is 2.4.3 and perhaps someday version 2.5.1 may be released, then
the update from version 2.4 to 2.5 will be considered a major upgrade.
Taking into account the combined work of a programmer, project coordinator, and tester, a minor Magento upgrade takes about 40-45 hours, while a major
Magento upgrade takes around 160 hours.
The number of hours needed to update Magento is influenced mainly by the quantity and quality of additional modules, the frontend used, and the level of
project customization. The fewer the modules and the higher their quality, the less time it will take to upgrade Magento to a higher version.
To speed up Magento with a front-end based on a modified Luma or a template built on Luma, you can implement two solutions. The first one is the implementation of a Magento front-end based on Hyva, and the second is the optimization of Luma.
Regarding the implementation of Hyva, it will take about 780 to 1070 hours. It is a significant investment; however, you can then achieve results on Google PageSpeed of around 80 on mobile and 90 on desktop.
As for improving the speed of Magento based on Luma, there are several things you can do:
Slimming down Magento by removing unnecessary PHP packages that unnecessarily burden the entire system.
Implementing a module for blocking and optimizing JavaScript files.
Implementing modules for handling images in WebP format.
Configuring lazy loading, i.e., TclPath, JavaScript deferring, and minification of HTML, JS, and CSS.
Thanks to this, you can expect results around 85 on desktop and about 45-47 on mobile.
Magento is not a good solution for managing a large product base. If you need to change a technical parameter on several hundred or thousands of products at once, it is very inefficient. There are, exceptions where it is possible to effectively manage products in Magento, but this applies solely to situations where you have about 10 products, you only sell in one geographic market, and you have one language version.
All product data in Magento should be divided into two categories.
Rapidly changing product data, which are related to availability, stock levels, and product pricing, should be managed in an ERP (Enterprise Resource Planning).
Slowly changing product data, related to product photos, descriptions, attributes, technical parameters, files, attachments, and technical specifications, are best managed in a PIM (Product Information Management).
If you’ve decided on Magento, you’ve certainly wondered how to migrate data to it. There are three categories of data. These are product data, order data, and customer data.
To Magento, it is worth transferring only the data of registered users. Above all, these are user ID, email address, and contact information.
As for the data concerning orders, it is again worth migrating elements such as the order ID, order status, or the order amount.
When it comes to product data, there are fast-changing and slow-changing data, which have been discussed earlier. Fast-changing data should remain in the ERP – then, this system needs to be integrated with Magento. Slow-changing data should not be migrated to Magento but to a PIM – for example, it can be Akeneo or Pimcore.
In certain situations, Magento 2 may not be the best solution. Scenarios where you should not decide on Magento 2:
you expect that you can implement this solution for less than 84.000 EUR/USD
you expect low maintenance costs, below 70.000 EUR/USD annually
you expect to implement ecommerce in less than seven months
you assume that implementing Magento with a PWA-based frontend will eliminate the need to create native applications
you plan to make changes to the code by yourself
you expect that the engine will function as a PIM, ERP, or WMS
In each of these situations, you should reconsider your choice. It’s possible that another ecommerce engine would be much better for you.
There are situations when Magento may not be the optimal choice, but also times when Magento could be the only solution capable of supporting a given
business.
Primarily when your business is scaling up. The premises that justify using Magento are:
Product count exceeding 100.000
Over 4.000 transactions per day
More than 5 overlapping and concurrently running price promotions
Access to over 10 international markets
More than 5 different frontends connected to a single backend
Another scenario is when the number of custom solutions is on the rise. Then you should also consider Magento, because the further you deviate from the standard of a simpler engine, the more your technological debt grows. Moreover, the engine’s performance slows down while maintenance costs escalate. Magento is written in such a way that even if you significantly deviate from the standard, this engine operates efficiently.
Conversion rate optimization on this ecommerce is not a particularly challenging task. Magento is a flexible engine, so there is no problem with implementing custom solutions such as configurators or modified filtering methods.
In most cases (about 98%), Hyva is the best choice. Only occasionally will PWA be more suitable—in the case of a very specific business model or project scale.
4 key factors should be considered when choosing a frontend for Magento:
Security
ROI (Return on Investment)
Revenue Generation
Investment Costs (TCO)
The implementation and maintenance costs of PWA are higher than those of Hyva, therefore it’s worth considering whether the anticipated revenue justifies this investment.
Therefore, for most Magento projects, Hyva is the best choice. PWA is more suited to unusual business models, while Luma and third-party templates are now obsolete and non-progressive technologies.
In the case of PWA, it is worth deciding on PWA Studio or Vue Storefront.
Magento is suitable for expansion into foreign markets and offers many customization options for different business requirements, currencies, languages, payment methods, delivery forms, and frontends.
A huge advantage of Magento is that you can maintain everything on a single backend. This means that one backend can be connected to several different frontends (you can even have a completely different graphic design for each country).
The costs associated with expansion into foreign markets using Magento vary depending on specific requirements. If the expansion involves only adjusting the language version, the costs can be around 2.100 EUR/USD. If it requires adjusting currency, payment methods, delivery, and changing the frontend, the costs can even reach 9.800 EUR/USD.
It is worth considering the inclusion of foreign markets at an early stage of the Magento project to optimize the structure and adjustments for international expansion. It can help minimize costs and facilitate the management of the international operations.
At the outset, check if your project exhibits symptoms of a failed implementation:
Errors appear that once fixed, return.
The appearance of the store differs from the original vision despite having prepared graphic designs.
Fixing one error leads to other issues arising in different parts of the store.
Mechanisms such as validation are not functioning as expected.
Integrations with other systems, such as ERP, are not working correctly.
Both the project’s deadline and budget have been exceeded.
To fix a failed Magento implementation, it is best to start by conducting an audit with an external company specializing in Magento and developing a recovery plan. You will receive a list of unfinished functionalities and errors. Ultimately, you must decide whether the project should be completed by the current Software House or another agency.
In the end, remember the most common causes of failed Magento implementations:
Inaccurate business analysis.
Too many external modules.
Use of PWA technology.
Too broad a project scope.
Contact us. We’ll discuss your business situation and determine together if Magento is a good choice.
Czy przenieść Cię na polską
wersję tej podstrony?