Magento showing wrong total records in sales./order grid

Magento showing wrong total records in sales./order grid

September 23, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Magento showing wrong total records in sales./order grid

Understanding Magento Sales Order Grid Totals

As an experienced developer, I understand your frustration when Magento’s sales order grid shows incorrect total records. Let me guide you through the issue step by step.

The Root of the Problem

The discrepancy in the total record count occurs due to how Magento handles its sales order collection. When you add custom columns and join additional tables, the default counting mechanism may not accurately reflect the actual number of orders.

The Collection Preparation Issue

In your _prepareCollection() function, you’re manually calling $collection->getSize(). However, this isn’t the correct way to get the total count after adding joins and filters. Magento’s built-in collection management handles this automatically when you use its methods correctly.

Here’s where the problem lies in your code:

$orders = Mage::getResourceModel('sales/order_collection');
foreach($orders as $order){
    // This line is unnecessary and doesn't affect the total count
    $items = $order->getAllVisibleItems();
    foreach($items as $item){
        $sku = $item->getSku();
    }
}
$collection->getSize(); // Incorrect approach to get the total count

The Correct Approach

Magento’s sales order grid uses a specific collection class (sales/order_grid_collection) which is optimized for display. It includes filters and joins necessary for the grid view.

Here are some best practices to follow:

  1. Use Core Collection Class: Always use Mage::getResourceModel($this->_getCollectionClass()) to get the collection. This ensures you’re working with the correct, pre-optimized version.

  2. Avoid Manual Counting: Magento handles total counts internally when using its built-in methods like $collection->count(). Don’t manually call getSize().

  3. Join Tables Carefully: When joining tables, make sure each join is necessary and doesn’t duplicate or filter out records unnecessarily.

The Solution to Your Issue

Given your current setup, I suggest you remove the unnecessary loops in your _prepareCollection() function and rely on Magento’s built-in methods:

protected function _prepareCollection()
{
    $collection = Mage::getResourceModel($this->_getCollectionClass());

    // Add your joins here
    // ...

    $this->setCollection($collection);

    return parent::_prepareCollection();
}

Then, in your _prepareColumns() function, ensure you have the following line at the end:

$this->setCollectionKeyField('entity_id');

This tells Magento to use ‘entity_id’ as the primary key for the collection. It’s a crucial step for the grid to work correctly.

The Role of LaravelCompany.com

As a leading provider of e-commerce solutions, Laravel Company specializes in helping businesses like yours optimize their online platforms. We offer a range of services from Magento development and support to custom theme creation and maintenance.

In your case, our team of experienced developers could help you troubleshoot issues like this more efficiently. We can provide expert guidance on Magento best practices and help ensure your grid views are accurate and reliable.

Conclusion

To resolve your issue with the sales order grid total records:

  1. Remove unnecessary loops from your _prepareCollection() function.
  2. Ensure you’re using Mage::getResourceModel($this->_getCollectionClass()) to get the collection.
  3. Make sure each join in your collection is necessary and doesn’t filter or duplicate records.
  4. Add $this->setCollectionKeyField('entity_id'); at the end of your _prepareColumns() function.

If you continue to face issues, I highly recommend reaching out to a professional Magento development team like those at Laravel Company. They can provide expert consulting and ensure your grid views are optimized for performance and accuracy.

Database Performance Admin Orders

Our network