Observer for Checkout Start

Observer for Checkout Start

July 11, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Observer for Checkout Start

Detecting Checkout Process Start: Observers vs. Controllers

The checkout process is a critical step in an e-commerce platform. Detecting when it begins can be useful for various purposes—saving data to sessions, triggering third-party services, or logging user activity. However, doing this without overriding controllers presents a challenge.

Understanding Magento’s Event-Driven Architecture

Magento is built on an event-driven architecture, which means you can tap into its system by listening for specific events. An observer allows you to listen for these events and execute custom logic when they occur.

For the checkout process start, we are interested in two key events:

  • controller_action_predispatch_checkout_onepage_savePayment
  • controller_action_predispatch_checkout_onestepcheckout_index

The predispatch event triggers just before a controller action is executed. This means our observer will fire right before the checkout process begins.

Creating an Observer

Let’s create an observer for these events:

// app/code/Vendor/Module/etc/events.xml

<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:framework:Event/etc/events.xsd">
    <event name="controller_action_predispatch_checkout_onepage_savePayment">
        <observer name="vendor_module_observe_checkout_start" instance="Vendor\Module\Observer\CheckoutStartObserver" />
    </event>
    <event name="controller_action_predispatch_checkout_onestepcheckout_index">
        <observer name="vendor_module_observe_checkout_start" instance="Vendor\Module\Observer\CheckoutStartObserver" />
    </event>
</config>

In the above XML configuration, we are mapping our CheckoutStartObserver to both checkout events.

Implementing the Observer

Now let’s implement the observer:

// app/code/Vendor/Module/Observer/CheckoutStartObserver.php

namespace Vendor\Module\Observer;

use Magento\Framework\Event\ObserverInterface;
use Psr\Log\LoggerInterface;
use Magento\Framework\Controller\ResultFactory;
use Magento\Framework\App\Request\Http;
use Magento\Framework\DataObject;

class CheckoutStartObserver implements ObserverInterface
{
    protected $logger;

    public function __construct(LoggerInterface $logger)
    {
        $this->logger = $logger;
    }

    public function execute(\Magento\Framework\Event\Observer $observer)
    {
        $request = $observer->getRequest();
        if ($request->getFullActionName() == 'checkout_onepage_savePayment' || $request->getFullActionName() == 'onestepcheckout_index') {
            // Your custom logic here
            $this->logger->info('Checkout process started.');
        }
    }
}

In the execute method, we check if the current action is either saving a payment or entering one-step checkout. If it is, you can execute your custom logic.

Conclusion: A Cleaner Approach

Using observers to track the start of the checkout process provides several advantages:

  1. It’s a cleaner way than overriding controllers.
  2. It allows for more organized and maintainable code.
  3. It doesn’t require touching any core Magento files.

Remember, you can extend this pattern to other parts of the checkout flow as well, such as when an order is placed or a payment fails.

For more information on Magento’s event system and how to leverage it effectively in your extensions, consider checking out Laravel Company’s guide on Magento 2 events.

The key takeaway here is that with the right approach, you can achieve a lot without resorting to controller overrides. It’s all about understanding and utilizing Magento’s built-in capabilities.

Checkout Cache Security API

Our network