What is a Plugin in Magento 2?

A Plugin (Interceptor) is one of the most powerful customization mechanisms available in Magento 2. It allows developers to modify the behavior of public methods without overriding the original class.

Plugins can execute custom logic before, after, or around a method call, making them a flexible and upgrade-safe way to extend Magento functionality.

Because Plugins avoid direct class overrides, Magento recommends them as the preferred customization approach for most development scenarios.

Where is a Plugin Defined?

Plugin Folder Structure

Vendor/
└── Module/
    ├── etc/
    │   └── di.xml
    └── Plugin/
        └── ProductPlugin.php

Plugin Example

<type name="Magento\Catalog\Model\Product">
    <plugin
        name="custom_product_plugin"
        type="Vendor\Module\Plugin\ProductPlugin" />
</type>

What is a Preference in Magento 2?

A Preference in Magento 2 allows developers to replace an existing Magento class with a custom implementation. When Magento requests the original class through Dependency Injection (DI), it automatically loads the preferred custom class instead.

Preferences are commonly used when a complete class override is required and Plugins cannot achieve the desired customization. Since a Preference replaces the entire class, it provides full control over methods and functionality.

Although Preferences are powerful, Magento recommends using them carefully because they can create conflicts when multiple modules attempt to override the same class.

Where is a Preference Defined?

Preference Folder Structure

Vendor/
└── Module/
    ├── etc/
    │   └── di.xml
    └── Model/
        └── Product.php

Preference Example

<preference
    for="Magento\Catalog\Model\Product"
    type="Vendor\Module\Model\Product" />

What is an Observer in Magento 2?

Observers are part of Magento 2's event-driven architecture. They allow developers to execute custom code whenever a specific Magento event is triggered within the application.

Magento dispatches hundreds of events during various processes such as customer login, order placement, product save, checkout completion, and many other actions. Observers can listen to these events and perform custom business logic automatically.

This approach helps developers extend Magento functionality without modifying core classes, making Observers a flexible and upgrade-safe customization method.

Where is an Observer Defined?

Observer Folder Structure

Vendor/
└── Module/
    ├── etc/
    │   └── events.xml
    └── Observer/
        └── CustomerLogin.php

Observer Example

<event name="customer_login">
    <observer
        name="customer_login_observer"
        instance="Vendor\Module\Observer\CustomerLogin" />
</event>

Plugin vs Preference vs Observer Comparison