I'm updating a bunch of product prices at once, I plan on doing this using a shell script that loads a SKU and the price to update. I also need to make sure this only applies to a specific store. So here is how I planned to go about it:

  • Load my list of products into an array
  • Include Mage.php
  • Load the store scope
  • Load each product in my list by SKU
  • Change the price using setPrice
  • Save the product attribute without having to save the entire product (I have a lot of SKUs to update)
  • Iterate through each product using the same process

My question is, can this be done with core attributes? Or does it need a full product save? I've seen several posts and scripts of people using saveAttribute with custom attributes under the default store, but the last time I attempted this it had huge reprocussions. I've tried a CSV using the import and it won't work right, and magmi is failing due to some strange errors, so I'm forced to take matters into my own hands.

2 Answers 2


Let's assume you have an array like this with the sku and prices.

$prices = array(
    'sku1' => '12.99',
    'sku2' => '15.00',

and you only need to change the price for store view 2.

Here is a fast way to do it.

Since the price can be global or has the website scope, you will also need to change the price for all the store views in the same website as the store view with id 2. The next script will do that for you, just make sure that prior to running it, you set the price scope to 'website'.

$storeId = 2;
$idsByPrice = array();

foreach ($prices as $sku=>$price) {
    $id = Mage::getSingleton('catalog/product')->getIdBySku($sku);
    if ($id) { //if the product exists
        if (!isset($idsByPrice[$price])) {
            $idsByPrice[$price] = array();
        //group all skus by price so you will have less updates.
        $idsByPrice[$price][] = $id; 

//now you have an array of product ids grouped by price
//$idsByPrice = array(
//    '12.99' => array(2,3,7,12),
//    '15.00' => array(9,44,22),...

foreach ($idsByPrice as $price=>$ids) {
        $ids,  //ids to update
        array('price'=>$price), //attributes to update
        $storeId //store view to update the attribtues

Include Mage.php at the top of the script and run it. back up your db first, just in case. And your indexes may need rebuilding when you are done.

  • Hmm, this also updated prices on other store views. How would I set the price scope to website?
    – DWils
    May 6, 2014 at 17:30
  • I just found the option in config under Configuration > Catalog > Catalog > Price
    – DWils
    May 6, 2014 at 17:32
  • Here's the gist for anyone interested: gist.github.com/uabassguy/e61f474d5e9749df5475 , this will parse a csv with sku and price columns
    – DWils
    May 6, 2014 at 21:04

I'd go the following route:

$collection = Mage::getModel('catalog/product')->getCollection();
$connection_write = Mage::getSingleton('core/resource')->getConnection('core_write');
foreach ($collection as $product){
    $sql = 'UPDATE `catalog_product_entity_decimal` SET `value` = ? WHERE `entity_id` = ? AND `attribute_id` = ?';
    $connection_write->query($sql, array($your_desired_price, $product->getId(), $price_attribute_id);

This uses direct SQL to update the database pricing directly, which will run exceptionally quickly and save resources.

The $price_attribute_id can be identified by:

Catalog → Attributes → Manage Attributes

Filter by 'price' and click onto it. Then look at the URL to identify the attribute ID:


The /attribute_id/60/ in this instance indicates to me that 60 is the attribute id for price, yours may probably be similar.

Let me know if you run into any problems.

  • 1
    This is a fast way of doing it (probably the fastest) but instead of UPDATE I think you should use INSERT..ON DUPLICATE KEY UPDATE... since there might be products that don't have a price set for a specific store view and use the default values. In this case UPDATE won't do anything. Also if you change the price for a store view, you have to change it for all store views within the same website to keep a consistency for the price scope. If you can manage to do that with direct insert/update statements then for sure is the fastest approach.
    – Marius
    May 6, 2014 at 7:13
  • The answer is much appreciated, but I avoid direct database writes unless absolutely necessary. Direct writes don't allow any other dispatch observers to do their jobs.
    – DWils
    May 6, 2014 at 17:57
  • This is not a good solution. It's almost certainly a bad idea to suggest writing bespoke SQL queries in an MVC application. Think abstraction!!
    – scrowler
    Oct 20, 2014 at 22:40

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.