Another customization was made in this, magneto by default doesn’t manage dependencies. To manage its dependencies customization was made in the system. Attributes were added in the mainframe bike. For example, if a customer chooses a bike of 24 inches in the meantime its attributes are shown which type of battery, rims, engine, etc. suitable for a 24-inch bike. All these attributes were automatically handled by the system.

Built a custom module for the configurator. It required design change as well as backend code/logic. It manages products with its dependencies automatically so as customers couldn’t be able to select even the wrong product for his/her Powerbike. Product selection is a stepwise process and one can’t jump the steps other than the defined process like one has to choose the frame first, then brake system followed by rims, motors, etc. Every selected product is immediately shown in a mini cart on the same page in its respective section so customers could be aware of what he/she has selected so far.

The third customization which we made was, we had to show the customer’s cart to the customer as a single product. In magneto, these products were added as a single individual product but in the system, a bundle is created in runtime so that the visualization becomes the same.

Normally bundle products are pre-defined in the magneto backend but in this case, we had to create one on the fly which involved a custom module with a lot of complex logic to get this done so that customer could see invoice/emails and products in cart as a single unit and he/she consider it as Powerbike purchased with customized options, not the frame, motor, rims, brakes, etc. as individual products.