<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
    xmlns:admin="http://webns.net/mvcb/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
    
    <title>Knowledge Base</title>
    <link>http://www.magentocommerce.com/knowledge-base/</link>
    <description></description>
    <dc:language>en-us</dc:language>
    <dc:creator>adi@varien.com</dc:creator>
    <dc:rights>Copyright 2008</dc:rights>
    <dc:date>2008-06-26 T;21:48:00-08:00</dc:date>
    <admin:generatorAgent rdf:resource="http://expressionengine.com/" />


<item>
    <title>What are Catalog Price Rules and how do I use them?</title>
    <link>http://www.magentocommerce.com/knowledge-base/entry/what-are-catalog-price-rules-and-how-do-i-use-them</link>
    <description><![CDATA[<p>There are 2 types of price rules in Magento, <b>Catalog</b> and <b>Shopping Cart Price Rules</b>. Catalog Rules are enacted on products before they are added to the cart, while Shopping Cart Price Rules are applied in the shopping cart. Here we will look at how to set up Catalog Price Rules.
</p>
<p>
To create a Catalog Price Rule go to <b>Promotions</b> -> <b>Catalog Price Rules</b> and select <b>Add New Rule</b>. 
</p>
<p>
<img src="http://www.magentocommerce.com/images/uploads/admin_catalogpricerule_information.jpg" style="border: 0;" alt="image"  />
</p>
<p>
The first thing to do is enter a Name and Description for the catalog price rule. Once that is set up we will Enable it by selecting Active from the Status dropdown.
</p>
<p>
You then select which Websites to apply the rule to. In this case we will enact the rule for all Websites.
</p>
<p>
You are then able to select which Customer Groups you want the rule to apply to. The first option is Not Logged In, those customers who are not signed in to any account, and therefore not assigned to a customer group. In this case we will also offer the discount to the General and Retailer customer groups.
</p>
<p>
We are also setting a date range for the Rule to take effect. If you leave the date range empty the rule will be enabled as soon as it is created.
</p>
<p>
You will also set the priority on this page. The priority is there in case a product has two separate Catalog Price Rules. Whichever has the priority (1 being the most priority) will take effect. We will discuss priority after creating another rule.
</p>
<p>
Once you have set up the information for the product you create the conditions for the Rule. In this case we are going to discount every Sony product which is $100 or more by 15%.
</p>
<p>
<b>Now here is how we do it:</b>
</p>
<p>
If you are going to create a rule which requires 2 conditions (as we are doing here, the product must be in apparel and the price must be over $50) select &#8216;If All these Conditions are True&#8217;. If we wanted the discount to take effect if the product was a Sony product OR if the product was over $50 we would select &#8216;Any&#8217;.
</p>
<p>
Select Product Attribute from the dropdown (we will get to conditions combination in a bit) and select the Default Category from the list of attributes. We then want the middle rule to be is and we then enter the name of the manufacturer in the field, giving us this:
</p>
<p>
<img src="http://www.magentocommerce.com/images/uploads/catprice_1.jpg" style="border: 0;" alt="image"/>
</p>
<p>
So the rule will now apply to all products whose manufacturer is Sony; but we want to further limit this to only those products which are $100 and over. Open a new Condition and select Product Attribute. From the attribute list select Price, and then select &#8216;equals or greater than&#8217; from the condition dropdown. We then enter the value, 100.00, and we have our second condition created.
</p>
<p>
<img src="http://www.magentocommerce.com/images/uploads/catprice_3.jpg" style="border: 0;" alt="image"/>
</p>
<p>
Now that we have the Conditions set we need to create the Actions.
</p>
<p>
<img src="http://www.magentocommerce.com/images/uploads/admin_catalogpricerule_action.jpg" style="border: 0;" alt="image"  />
</p>
<p>
The Apply dropdown allows you to decide whether the discount is a percentage or a fixed amount, and whether the discount amount will be subtracted from the original price (By) or whether the discount amount will be the actual final price (To). For this case select select <b>By Percentage of the original price</b> and we then enter our value, 15. This will give a final price that is a 15% reduction of the original price. To select <b>To Percentage of the original price</b> would give a final price that is equal to 15% of the original price (an 85% reduction). The last thing to do is decide whether we want to stop other rules from taking effect on the products we have selected. In this case we will select Yes. Now, remember the priority we entered on the last page? This is what decides which rules are applied first.
</p>
<p>
In this case we entered the priority as 1. Say we had another rule, $5 off all products, which had a priority of 2. If we had selected No on the Stop Further Rules Processing dropdown that $5 discount would take effect on the already 15% discounted price. Since we select yes the $5 discount will still apply to other products, but not Sony products equal or great than $100.
</p>
<p>
Now we select Save Rule and the rule is created. What&#8217;s that Save Rule and Apply button you ask? Well, I&#8217;m glad you did.
</p>
<p>
You may also notice that there is a Apply Rules button on the list of Catalog Price Rules. For the rule to change the price of the items selected you will either need to select Save Rule and Apply, or the Apply Rules button on the list of Catalog Price Rules. The reasoning behind this is that as you add new rules, the system must recalculate the prices and the priorities of the rules. The rules are applied each night automatically, but if you do want to immediately apply a new rule you must select one of the Apply buttons. Now the Sony Products equal or greater than $100 are discounted by 15%.
</p>
<p>
Now on to some increased functionality. I promised I would talk about Condition Combinations and I will do so here.
</p>
<p>
Let&#8217;s switch examples to discounting apparel. White is the new color and you have an overstock of all your Red and Black clothing. You want to discount it, but don&#8217;t want to go through and create 2 different rules. Here is where Condition Combinations shine.
</p>
<p>
We start our first line with All the Conditions being True.
</p>
<p>
Now when we go to set up our first condition we select Conditions Combination from the dropdown. We then need to set up the conditions below as being Any, since we are going to discount products which are <i>either </i>Black or Red.
</p>
<p>
At this point the Conditions look like this:
</p>
<p>
<img src="http://www.magentocommerce.com/images/uploads/catprice_condition1.jpg" style="border: 0;" alt="image" />
</p>
<p>
Now we set up the other option, if the Color is Red and we have this:
</p>
<p>
<img src="http://www.magentocommerce.com/images/uploads/catprice_condition2.jpg" style="border: 0;" alt="image" />
</p>
<p>
Now that we have set up our Condition for the colors we move back to the first level of conditions and select the price as being equal to or greater than $20.00 and we see this:
</p>
<p>
<img src="http://www.magentocommerce.com/images/uploads/catprice_condition3.jpg" style="border: 0;" alt="image" />
</p>
<p>
Now we need all the conditions to be true. The price must be equal to or greater than $20 and the color must be either Black or Red.&nbsp; Apply your actions as described above, Save and Apply the Rule and that overstock will be moving out of the warehouse in no time.
</p>]]></description>
    <dc:language>en-us</dc:language>
    <dc:creator>chris@varien.com</dc:creator>
    <dc:rights>Copyright 2007</dc:rights>
    <dc:date>2007-08-29 T;19:41:00-08:00</dc:date>
</item>
<!--
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
         xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"
         xmlns:dc="http://purl.org/dc/elements/1.1/">
<rdf:Description
    rdf:about="http://www.magentocommerce.com/knowledge-base/what-are-catalog-price-rules-and-how-do-i-use-them/"
    trackback:ping="http://www.magentocommerce.com/trackback/197/"
    dc:title="What are Catalog Price Rules and how do I use them?"
    dc:identifier="http://www.magentocommerce.com/knowledge-base/197/"
    dc:subject="Promotions"
    dc:description=""
    dc:creator="varienchris"
    dc:date="2007-08-29 07:41:00 PM GMT" />
</rdf:RDF>
--> 


    <item>
      <title>Comment by poacherDave</title>
      <link>{url_as_link}</link>
      <description><![CDATA[<p>Thanks for the reply Daniel. Judging by  the forums this affects alot of people who are currently using fudges and workarounds (dual stores) for this. I&#8217;m not sure that anyone in the forums, myself included has adequately described to problem to Roy, Moshe et.al. 
</p>
<p>
Be nice to get it in the maintained core code (probably a lot less code than a module). Have you considered submitting/contributing your code for possible inclusion in future releases?
</p>
<p>
If you are happy to share your current solution pls post a diff which may do a better job of describing the issue than all this guff.
</p>]]></description>
      <content:encoded><![CDATA[<p>Thanks for the reply Daniel. Judging by  the forums this affects alot of people who are currently using fudges and workarounds (dual stores) for this. I&#8217;m not sure that anyone in the forums, myself included has adequately described to problem to Roy, Moshe et.al. 
</p>
<p>
Be nice to get it in the maintained core code (probably a lot less code than a module). Have you considered submitting/contributing your code for possible inclusion in future releases?
</p>
<p>
If you are happy to share your current solution pls post a diff which may do a better job of describing the issue than all this guff.
</p>]]></content:encoded>
    <dc:date>2008-06-26 T;21:48:00-08:00</dc:date>
    </item>

    <item>
      <title>Comment by danieln</title>
      <link>{url_as_link}</link>
      <description><![CDATA[<p>We were facing the same task. We&#8217;ve done it buy adding just a few lines of code. I would not recommend doing this because you will lose any upgradabily. I did not have an idea how to solve this as a module. Maybe a article on how to manipulate price with a custom module would be great!
</p>]]></description>
      <content:encoded><![CDATA[<p>We were facing the same task. We&#8217;ve done it buy adding just a few lines of code. I would not recommend doing this because you will lose any upgradabily. I did not have an idea how to solve this as a module. Maybe a article on how to manipulate price with a custom module would be great!
</p>]]></content:encoded>
    <dc:date>2008-06-26 T;21:48:00-08:00</dc:date>
    </item>

    <item>
      <title>Comment by poacherDave</title>
      <link>{url_as_link}</link>
      <description><![CDATA[<p>Moshe
</p>
<p>
Happy new year - apologies about any confusion above - i&#8217;d like to be able to edit/clarify some of those
</p>
<p>
i may have missed the answer to this question. There seems to be alot of it throughout the community pages eg <a href="http://www.magentocommerce.com/boards/viewthread/335/">http://www.magentocommerce.com/boards/viewthread/335/</a> 
</p>
<p>
I added a wholesale_price to attribs but the menu/wizardesque thingy at promotions/catalogue price rules/conditions and actions lets me browse attribs in the first column but forces me to set a price in the second (i&#8217;d need a rule for every product)
</p>
<p>
i want my wholesale customers to be presented with their buy price in the catalogue - magento goes some of  the way with this but the % model doesn&#8217;t suit everyone
</p>
<p>
so i think i&#8217;d like to be able to say price=wholesale_price (browse the attribs in the second column) for my wholesale customers 
</p>
<p>
hope this makes my problem a bit clearer &amp; if there is an existing way to do this pls let me know
</p>]]></description>
      <content:encoded><![CDATA[<p>Moshe
</p>
<p>
Happy new year - apologies about any confusion above - i&#8217;d like to be able to edit/clarify some of those
</p>
<p>
i may have missed the answer to this question. There seems to be alot of it throughout the community pages eg <a href="http://www.magentocommerce.com/boards/viewthread/335/">http://www.magentocommerce.com/boards/viewthread/335/</a> 
</p>
<p>
I added a wholesale_price to attribs but the menu/wizardesque thingy at promotions/catalogue price rules/conditions and actions lets me browse attribs in the first column but forces me to set a price in the second (i&#8217;d need a rule for every product)
</p>
<p>
i want my wholesale customers to be presented with their buy price in the catalogue - magento goes some of  the way with this but the % model doesn&#8217;t suit everyone
</p>
<p>
so i think i&#8217;d like to be able to say price=wholesale_price (browse the attribs in the second column) for my wholesale customers 
</p>
<p>
hope this makes my problem a bit clearer &amp; if there is an existing way to do this pls let me know
</p>]]></content:encoded>
    <dc:date>2008-06-26 T;21:48:00-08:00</dc:date>
    </item>

    <item>
      <title>Comment by Moshe</title>
      <link>{url_as_link}</link>
      <description><![CDATA[<p>@poacherDave: correct me if i misunderstand the question, but it is possible to specify applicable customer groups in:
<br />
* tier prices in product edit,
<br />
* catalog price rules (as shown on the picture in this blog post),
<br />
* shopping cart price rules.
</p>]]></description>
      <content:encoded><![CDATA[<p>@poacherDave: correct me if i misunderstand the question, but it is possible to specify applicable customer groups in:
<br />
* tier prices in product edit,
<br />
* catalog price rules (as shown on the picture in this blog post),
<br />
* shopping cart price rules.
</p>]]></content:encoded>
    <dc:date>2008-06-26 T;21:48:00-08:00</dc:date>
    </item>

    <item>
      <title>Comment by poacherDave</title>
      <link>{url_as_link}</link>
      <description><![CDATA[<p>Thanks Roy
</p>
<p>
Point taken with the OS hackability. Mods by me are on the cards after I prove to myself I am not reinventing the wheel. I would like to take this opportunity to tell you how horribly lost I so far in your php OO labyrinth. I&#8217;m picking it to bits but V slowly with grep. By the time I navigate my way to a solution you guys will have implemented it in 3 lines of code.
</p>]]></description>
      <content:encoded><![CDATA[<p>Thanks Roy
</p>
<p>
Point taken with the OS hackability. Mods by me are on the cards after I prove to myself I am not reinventing the wheel. I would like to take this opportunity to tell you how horribly lost I so far in your php OO labyrinth. I&#8217;m picking it to bits but V slowly with grep. By the time I navigate my way to a solution you guys will have implemented it in 3 lines of code.
</p>]]></content:encoded>
    <dc:date>2008-06-26 T;21:48:00-08:00</dc:date>
    </item>

    <item>
      <title>Comment by poacherDave</title>
      <link>{url_as_link}</link>
      <description><![CDATA[<p>I lied. the catalog price rules can distinguish wholesale customers but I can only apply a product update on a per product basis. That is I cannot point back at a more generic wholsale price attrib which would be V handy
</p>
<p>
Hoping you guys think this needs doing or are going to tell me the more obvious sensible way to do this?
</p>]]></description>
      <content:encoded><![CDATA[<p>I lied. the catalog price rules can distinguish wholesale customers but I can only apply a product update on a per product basis. That is I cannot point back at a more generic wholsale price attrib which would be V handy
</p>
<p>
Hoping you guys think this needs doing or are going to tell me the more obvious sensible way to do this?
</p>]]></content:encoded>
    <dc:date>2008-06-26 T;21:48:00-08:00</dc:date>
    </item>

    <item>
      <title>Comment by RoyRubin</title>
      <link>{url_as_link}</link>
      <description><![CDATA[<p>@poacherDave - I don&#8217;t believe such functionality exists out of the box. Given the product is open source (and you have access to the code), you can certainly custom develop this feature for your needs. 
</p>
<p>
Also, try posting this issue in the forums and see what other community members suggest in terms of a workaround for this issue.
</p>]]></description>
      <content:encoded><![CDATA[<p>@poacherDave - I don&#8217;t believe such functionality exists out of the box. Given the product is open source (and you have access to the code), you can certainly custom develop this feature for your needs. 
</p>
<p>
Also, try posting this issue in the forums and see what other community members suggest in terms of a workaround for this issue.
</p>]]></content:encoded>
    <dc:date>2008-06-26 T;21:48:00-08:00</dc:date>
    </item>

    <item>
      <title>Comment by poacherDave</title>
      <link>{url_as_link}</link>
      <description><![CDATA[<p>magento has everything (a very pleasant piece of SW all round) except in one little showstopper (for me) instance where it seems to be skirting all around the functionality I want. I have the wholesale/retail problem and would love to be able to add a wholesale price attribute that is ONLY displayed to logged in customers that I have deemed to be wholesale. Whether I can do this or not (or get the same functionality some other way) is still not apparent to me. I have been searching /reading /testing since August. I don&#8217;t believe the % rule is going to work in my case and the promotions rules seem to only look at product attribs, not customer group. any clues V welcome.
</p>]]></description>
      <content:encoded><![CDATA[<p>magento has everything (a very pleasant piece of SW all round) except in one little showstopper (for me) instance where it seems to be skirting all around the functionality I want. I have the wholesale/retail problem and would love to be able to add a wholesale price attribute that is ONLY displayed to logged in customers that I have deemed to be wholesale. Whether I can do this or not (or get the same functionality some other way) is still not apparent to me. I have been searching /reading /testing since August. I don&#8217;t believe the % rule is going to work in my case and the promotions rules seem to only look at product attribs, not customer group. any clues V welcome.
</p>]]></content:encoded>
    <dc:date>2008-06-26 T;21:48:00-08:00</dc:date>
    </item>

    <item>
      <title>Comment by danieln</title>
      <link>{url_as_link}</link>
      <description><![CDATA[<p>lol&#8230; good think the pictures fit to the text <img src="http://www.magentocommerce.com/images/smileys/wink.gif" width="19" height="19" alt="wink" style="border:0;padding:0;" />
</p>]]></description>
      <content:encoded><![CDATA[<p>lol&#8230; good think the pictures fit to the text <img src="http://www.magentocommerce.com/images/smileys/wink.gif" width="19" height="19" alt="wink" style="border:0;padding:0;" />
</p>]]></content:encoded>
    <dc:date>2008-06-26 T;21:48:00-08:00</dc:date>
    </item>

    <item>
      <title>Comment by Ængel</title>
      <link>{url_as_link}</link>
      <description><![CDATA[<p>yes thanks !
</p>]]></description>
      <content:encoded><![CDATA[<p>yes thanks !
</p>]]></content:encoded>
    <dc:date>2008-06-26 T;21:48:00-08:00</dc:date>
    </item>

    <item>
      <title>Comment by adimagento</title>
      <link>{url_as_link}</link>
      <description><![CDATA[<p>All images should be up now.
</p>]]></description>
      <content:encoded><![CDATA[<p>All images should be up now.
</p>]]></content:encoded>
    <dc:date>2008-06-26 T;21:48:00-08:00</dc:date>
    </item>

    <item>
      <title>Comment by Ængel</title>
      <link>{url_as_link}</link>
      <description><![CDATA[<p>hi,
</p>
<p>
is it me or there is some missing pictures at the end of the post?
</p>]]></description>
      <content:encoded><![CDATA[<p>hi,
</p>
<p>
is it me or there is some missing pictures at the end of the post?
</p>]]></content:encoded>
    <dc:date>2008-06-26 T;21:48:00-08:00</dc:date>
    </item>


</channel>
</rss>