CELSIS CUSTOM WARRANTY SYSTEM

Celsis is a Lithuanian company well-known for selling heating, ventilation, air conditioning and bathroom equipment. It was established back in 1994 and has been around for more than two decades.

The company specializes both in retail and wholesale, leveraging the company’s well oiled chain of logistics, storage facilities and wide range of assortment, including everything from heating boilers and solar collectors to water mixers and bathroom furniture.

Celsis works directly with retailers, equipment installers and individual clients all around the country. Since a large part of the production is imported directly from the manufacturers, Celsis often takes care of the delivery, warranty and after-sales services.

To make the process of handling warranty and after-sales services more efficient and easier, the company decided to develop an internal system that all the repairmen and equipment installers could use. But Celsis needed development partners, that would have expertise and experience in developing custom web solutions. This is where Adeo Web comes into the picture.

Challenge

The system had to handle the warranty information and management for thousands of products: heating boilers, air conditioners, etc. When an independent contractor installs a boiler provided by Celsis, they’d need to enter the product information and documentation in the system. The system would be used to collect all the required documents and serial numbers for the products, monitor maintenance and support cycles, allow users to view and verify warranty information for the installed equipment.

Solution

The chosen framework for building the system was Symfony due to its wide application capabilities and customization potential. Since we would be creating the system from scratch, as usual, the process started out with a workshop to find out the exact needs of our client for MVP phase. After the workshop we’ve had the final list of required specifications for the system.

Then we could move on with creating the wireframe how the system would look. To ensure the system was developed exactly to the client’s needs, we had regular updates with Celsis.

The key functionalities for users and admins differed. Since the user (contractor, repairman) would be the one installing equipment provided by Celsis, he or she would need to have the ability to add information about the product to the system. The functionality was added that would allow not only to fill out the order info, but to also assign the equipment type (monoblock, internal or external), sign the documentation and warranty agreement, attach pictures of the product and add specific notes about the installation. The users can also search the system for a serial number of the equipment to verify whether it is already set up. In addition, the system allows for repairman/contractor to add warranty notes and separate installation/repair history for each order.

The system administrators need to ensure that all the documentation is correct and verified, also to make sure that all the maintenance is done on time. To enable that, we have created an extensive filtering system that allows Celsis administrators to categorize all data based on client information, object information, equipment type and serial number, installation data and status, maintenance intervals and so on.

The admins can also search for a serial number to find the equipment and verify the documentation. In some cases the documentation that reaches Celsis is not signed by the contractor, so we have developed functionality that would allow administrators to sign the documentation in the system.

The admin panel also allows administrators to manage user access and roles (equipment installer, admin), terms of the warranty, maintenance cycles and control system attributes (i.e. make certain fields in documentation forms mandatory or optional).

Over the course of the project there were quite a few additional functionalities that the client needed – assigning mandatory and optional fields in the documentation of the products, file import rules, data management for the system administrators, etc. Finally, the system was adapted to be responsive on different types of devices.

Result

After completing the development of all the required functionality for the MVP version, the project moved to the testing phase. As usual, the first round of testing was done by our internal QA engineers and project managers and only then the project testing was passed on to the client.

Finally, after 6 months of intense work the system was launched. It’s already being used by a part of the administrators and contractors. Of course, no system is ever truly “done”, as there is always room for improvement.

The project development will continue after receiving the feedback from independent contractors, but it’s already clear that the system could use some additional enhancements: connecting other products, Improved Administration Dashboard, additional language integrations and more.

 

Team

1 Project manager
1 QA engineer
1 Frontend developer
1 Backend developer