Implementing an event observer in Magento

Implementing an event observer in Magento

July 20, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Implementing an event observer in Magento

Implementing an Event Observer in Magento

As you begin to explore the powerful event system in Magento, you may find yourself looking for specific events to trigger your custom module functionality. In your case, you want to automatically deduct inventory quantities from child SKUs whenever a parent product is purchased.

To achieve this, we’ll use Magento’s observer pattern and specifically target the sales_order_place_after event. This event is dispatched by Magento after an order has been successfully placed and can be used to perform post-purchase actions such as updating inventory levels for related products.

Understanding the Event Observer Structure

An event observer in Magento consists of three main components:

  1. Event: The specific action that triggers the observer (in this case, sales_order_place_after).

  2. Observer class: A PHP class responsible for handling the dispatched event and performing any necessary actions.

  3. Configuration file: An XML file that maps the event to the observer class in your module’s etc/event directory.

Creating Your Observer Class

Let’s create a new Magento plugin to handle this functionality:

use Magento\Framework\Event\Observer;
use Magento\Framework\Event\ObserverInterface;

class UpdateChildSkusObserver implements ObserverInterface
{
    protected $productRepository;
    protected $resource;

    public function __construct(
        ProductRepositoryInterface $productRepository,
        ResourceModel $resource
    ) {
        $this->productRepository = $productRepository;
        $this->resource = $resource;
    }

    public function execute(Observer $observer)
    {
        $order = $observer->getEvent()->getOrder();
        foreach ($order->getAllItems() as $item) {
            if (isset($item->getProductOption('child_skus')) && is_array($item->getProductOption('child_skus'))) {
                foreach ($item->getProductOption('child_skus') as $childSku) {
                    try {
                        $product = $this->productRepository->get($childSku);
                        $product->setQty($product->getQty() - 1);
                        $this->resource->saveAttribute($product, 'qty');
                    } catch (\Exception $e) {
                        // Log or handle exception
                    }
                }
            }
        }
    }
}

In this observer class:

  • We use the sales_order_place_after event to trigger our functionality after an order is placed.
  • We iterate through all items in the order and check if the parent product has a child_skus attribute with valid SKU values.
  • For each child SKU, we retrieve the corresponding Magento product object using the ProductRepositoryInterface.
  • We then decrement the quantity ($product->setQty($product->getQty() - 1)) and save it back to the database.

Configuring Your Event Observer

To map this observer class to the sales_order_place_after event, you need to create an XML configuration file (e.g., etc/event.xml) in your module:

<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:module:Magento_Event:etc/event.xsd">
    <event name="sales_order_place_after">
        <observer name="update_child_skus_observer" instance="Vendor_Module\Observer\UpdateChildSkusObserver"/>
    </event>
</config>

In this XML file:

  • We define the event we want to observe (sales_order_place_after).
  • We create a new observer called update_child_skus_observer.
  • We specify the fully qualified class name of our observer (Vendor_Module\Observer\UpdateChildSkusObserver).

Conclusion

By following this guide, you now have a solid understanding of how to implement an event observer in Magento to handle post-purchase actions like updating inventory levels for related products.

Remember that proper exception handling and logging are crucial when working with Magento’s event system. In the provided example, we’ve added basic exception catching to ensure the functionality doesn’t break if a product cannot be found or any other errors occur during the process.

For more information on Magento’s event observer pattern and best practices for developing custom extensions, I recommend exploring the official documentation and resources available at Laravel Company.

Catalog Security Extensions Configuration

Our network