Magento Extend Mage_Sales_Model_Order with a new function

Magento Extend Mage_Sales_Model_Order with a new function

October 9, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Magento Extend Mage_Sales_Model_Order with a new function

Extending Magento Sales Model for Custom Order ID Display

As an experienced e-commerce developer working with Magento, I often encounter requests like yours to extend core models for custom functionality. In this case, you’re trying to add a new function to Mage_Sales_Model_Order and display it in your frontend templates.

Let’s break down the problem step by step and provide a comprehensive solution.

Identifying the Issue with Your Current XML

Your current XML configuration is almost correct, but there are two common pitfalls that might be causing issues:

  1. Model Name Format: In Magento, model names follow a specific naming convention that includes the module name and the model class name separated by an underscore (_). You’ve used MY_MODEL_Sales_Model_Order, which isn’t compatible with this format.

  2. Code Pool Configuration: While you’ve set the code pool to local, it’s important to ensure that the file is actually located in your local pool directory. This usually looks like: app/code/local/MY/Model/Sales/Model/Order.php.

Correct XML Configuration

First, let’s correct your XML configuration with the appropriate format:

<config>
    <modules>
        <My_Model>
            <active>true</active>
            <codePool>local</codePool>
        </My_Model>
    </modules>
    <global>
      <models>
        <sales>
          <rewrite>
            <Mage_Sales_Model_Order>My_Model_Sales_Model_Order</Mage_Sales_Model_Order>
          </rewrite>
        </sales>
      </models>
    </global>
</config>

Notice the change in the model name format (My_Model_Sales_Model_Order).

Creating Your Custom Model

Now, let’s create the actual Order.php file in your local pool directory. Here’s a basic structure:

<?php

class My_Model_Sales_Model_Order extends Mage_Sales_Model_Order {

    public function getNewCustomAttribute() {
        // Add your custom logic here to calculate or set the new attribute
        return 'Your Custom Value';
    }

}

In this example, I’ve added a getNewCustomAttribute method. You can replace the default return value with your own logic based on the order data.

Accessing the New Function in Your Templates

To access this function in your frontend templates like info.phtml, you’ll need to create an object of your custom model and call the method:

<?php $_customModel = Mage::getModel('sales/order') ?>
<p>Custom Attribute: <?php echo $_customModel->getNewCustomAttribute() ?></p>

Conclusion

Extending Magento core models is a powerful way to add custom functionality without modifying the core code. However, it requires a good understanding of the model hierarchy and naming conventions.

Remember that any changes to your local pool will be overwritten if you upgrade or reinstall Magento, so make sure to version control your files appropriately.

For more advanced techniques like event observers or plugin systems, I recommend checking out the official Magento Development documentation and our guide on Extending Magento Core Functionality.

Extensions Themes Configuration Orders

Our network