Define AddOns with drawbacks?

Addons are a type of extension that allows for extending the functionality of an SAP Hybris Commerce Accelerator storefront. They are primarily intended for customization of the frontend logic in a target storefront and should be used whenever such customization is required, since they allow the changes to be made without modifying the storefront files directly. 

There are several benefits:

• Upgrading the Accelerator to a new version is easier, since the no customizations need to be merged from the old implementation.
• It is easier to toggle features when they are implemented as AddOns as they can be removed without the need to refactor the storefront. This is especially helpful for customers who will run multiple storefront on a single platform with different requirements. 
• Facilitates implementation of multiple features in parallel by using separate AddOns instead of working directly within the Accelerator.

The use of AddOns also have some potential drawbacks when compared to making direct modifications in the Accelerator extensions and these should be considered as well:

• Correctly implementing AddOns might be less straightforward since conflicts and name clashes can arise if AddOns are applied to the storefront inappropriately.
• The use of AddOns adds a level of indirection which might seem confusing to some developers.

Recommended practice:

• Minimize customizations to the Accelerator source code. Prefer making these customizations in AddOns and accompanying extensions.
• Place frontend customizations in an AddOn and place business logic in regular extensions on which the AddOn depends.
• Specify data model changes related to a specific feature in the related AddOn's or related extension's items.xml and beans.xml.