Recently, our team has implemented distripark.com – an online shop from the chemical industry. During this project, we learned a lot about B2B implementations in Magento2. Below we have gathered the conclusions of the team.
Paweł, Leader of the backend team
Magento 2 is still a new product and is still buggy, at this stage. We can not wait for ready-made solutions from the M2 authors – the list of bug reports is very long, so it will take a long time. Usually, you have to take matters into your own hands.
In addition, distripark.com is a large B2B project, which means that it requires a large number of dedicated solutions. Many of them result directly from the specific nature of the business. That’s why the standard Magento is not enough here – you have to overwrite and expand the existing code in many places.
Agata, Backend team
With such complex projects, team communication is extremely important. It is crucial that all tasks are thoroughly discussed and written down. It is also important to estimate the time of each task appropriately – creating Magento 2 modules takes longer than on M1.
Maciej, Backend team
A B2B project requires more developer hours than B2C. Greater implementation also means more communication, which is extremely important. It is crucial to have a smooth flow of information about what has been implemented, and how – so that each team member has full knowledge of the project.
In addition, while creating M2 modules, you must be prepared to change the client’s decision on its operation – modules must be very flexible.
Marcin, Frontend team
Magento 2, as a new platform, with many changes to previous versions, has little current documentation. The bugs encountered may not yet have a solution from Magento, and you have to prepare the client for it, as well as the programmers.
As the previous speakers have emphasized, constant communication between team members is extremely important. Without this, errors in the assumptions of the code are born quickly.
You also need to set up a larger time buffer for tasks than for M1.
Wojtek, Testing team
A B2B project, compared to a regular B2C store, is certainly a bigger challenge because of its enhanced functionality.
It is good when the tester is more involved in the project at the very beginning when the analysis is still underway; it helps to better understand what the customers need, which then results in more accurate testing.
In such a large and complex project, automated testing is also very important.
Wojtek, Project Manager
The biggest challenge of this project was probably to create a platform dedicated to both B2B and B2C. In addition, the specificity of the chemical industry creates additional challenges for creating the necessary packing mechanisms for transport (safety).
In cases where we are working on a new technology – and this is the case with Magento 2 – we should always set up time buffers for implementation, especially in the initial stage of project implementation. The time for subsequent tasks was already easier to estimate due to the team’s mix and the optimal division of tasks.
For such large projects, all important functions / modules should be carefully analyzed and specified before development.
Read also: Open Source eCommerce Platforms 2017
Published June 6, 2017