magento-plugin

Magento 2 plugins (interceptors) modify core or third-party method behavior without touching vendor code. You create before, after, or around plugins and register them via di.xml configuration to safely intercept public methods.

Magento 2 before plugins change input arguments, after plugins modify return values, and around plugins wrap the original method entirely. Choosing the least invasive plugin type minimizes conflicts and preserves core functionality.

You configure a Magento 2 plugin in di.xml by defining a type node, adding a plugin child node with a name, class, and sortOrder. Proper scope placement in etc/frontend/di.xml or etc/adminhtml/di.xml minimizes conflicts.

Yes, Magento 2 plugins can intercept public methods on product classes like getName or save flows. This enables you to implement custom business rules in both frontend and admin contexts without modifying vendor code.

Use around plugins in Magento 2 only when you need to wrap the original method entirely to change both input and output. Before and after plugins are less invasive and preferred when you only need to modify arguments or return values.

Magento 2 interceptors only work on public methods and require proper di.xml configuration. You must manage sortOrder spacing carefully to avoid conflicts and ensure safe integration across frontend and admin scopes.