Gsyfuy

In my Magento project I have to receive pricing and inventory information on our products. Right now I have created my own method within the product model to make a SOAP request in the getPrice() function.

Here's what that looks like:

../app/code/core/Mage/Catalog/Model/Product.php

/**

 * Get product price throught type instance

 *

 * @return unknown

 */

public function getPrice()

{

    if ($this->getData('is_api')){

        $this->getAPIData();

    }

    if ($this->_calculatePrice || !$this->getData('price')) {

        return $this->getPriceModel()->getPrice($this);

    } else {

        return $this->getData('price');

    }

}



/**

 * Get time since last update

 *

 * @return  int

 */

public function getTimeSinceLastUpdate() {

    return time() - strtotime($this->getUpdatedAt());

}



/**

 * Get product data from API

 *

 * @return  price

 */

public function getAPIData(){

    if ($this->getTimeSinceLastUpdate() > 5){

        $parts = new SoapClient("XXXX");

        $res = $parts->PartLookup([

            'userName' => 'XXXX',

            'password' => 'XXXX',

            'partnumber' => 'XXXX',

            'make' => ''

        ]);

        $this->updateAPIProduct($res);

        return $res;

    }

}



/**

 * Update API Product

 *

 * @return   unknown

 */

public function updateAPIProduct($data){

    $this->setPrice($data->PartLookupResult->PartInformation_v2[0]->Price);

    Mage::app()->setCurrentStore(Mage_Core_Model_App::ADMIN_STORE_ID);

    $this->save();

    Mage::app()->setCurrentStore(1);

}

However, this seems like the wrong way to do this. To me, it would make more sense to test whether or not it's an api product during product object creation. At that point I would update pricing AND inventory information.

I've also run into a bug where when I update the pricing while on the frontend the new price is grey and has a strike through it and the old price next to it.

The only problem is that I have no idea where to go to update that information at that point.

Not a real answer, but too long for a comment:

I think to set the information when the object is created is the correct approach. With your solution now, one product could technically have a different price in different sections of the site, because the price could have been updated in the "source" in the meantime.

I would also try to do it in an observer and not in a class rewrite, as the latter can lead to problems with other extensions (only one rewrite of a certain class can be active at a time in Magento).

So, I would suggest to try something like this (not sure about the exact event name):

<!-- config.xml  -->

<global>

    <events>

        <catalog_product_load_after>

            <observers>

                <my_module_observer_name>

                    <class>mymodel/observer</class>

                    <method>setRealValues</method>

                </my_module_observer_name>

            </observers>

        </catalog_product_load_after>

    </events>

</global>

...and the PHP file:

<?php // Observer.php



    class Namespace_Mymodel_Model_Observer {

        public function setRealValues($observer) {

            $product = $observer->getEvent()->getProduct();

            $attributes = ['price', 'name', 'something']

            /*

             * Either get all values you need with one request, or 

             * do a foreach() loop over $attributes

             */

        }

    }

You would also have to do this for cataloginventory_stockitem_load_after, because technically, this holds the stock data.

There is another problem with product lists: Magento uses a collection object for this. I think if the API only allows single request - have fun requesting the data for 20+ products in a time that is acceptable for the customer :) cURL can do some kind of asynchronous stuff that might help you here. The event to listen for would be catalog_product_resource_collection _load_after, I guess (not sure again).

Maybe that this does not get all the possibilities where the price is displayed, but I think it's a place to start.

Update after comment:

I think saving the products at night would be a good start; keep in mind that the most expensive action will be loading the collection (600k SKUs means you should probably do it in chunks) and saving the product with a save() method. The latter can be avoided if you first check if the data has actually changed, and if you use $product->getResource()->saveAttribute($product, 'price', 10.00) (not sure about exact method name) instead of saving the whole model.

You might also want to make separate functions for updating the product and the stock item, as the stock item does not operate with such big objects and can maybe run more often.