Economic Lessons - Consumer Influence on Price

Have been reflecting on some economy principles and rules for a while and here's what still doesn't came through to me in regard to Supply and Demand equilibrium and price results:

How do consumers influence the price? Say when we come to the grocery store or a super market we don't bargain, right?
Also with big purchases like furniture, expensive electronics, cars or real-estate we don't do many of those frequently enough to influence the price. There is another part of economy - B2B where "consumer" or one side of the relationship sometimes can influence the price and sometimes can't. Very often in case of businesses the procurement decisions are not made by one person and not always fair or economically efficient. Or I am missing something here?

I just thought the Demand part of this system should "belong" to the consumer, hence the idea that the buyer should influence the equilibrium somehow. However, to me usually the consumer has only got an option to accept the already set price.

Would really appreciate any useful comment on that, because it has been something I thought about for a while now.

It appears that in different areas of economy customers have different levels of influence or no influence at all in some cases.
Here's one example Supply and Demand Pricing Rules for Property Market

Comments

Wine - 2011 Brown Brothers Crouchen Riesling

Very nice wine with fruity taste - peach and pear: Consumed with Hungarian salami. Tasting notes .

Scrum - Team Culture and Wall Manifesto

In the Scrum framework one of the key components is the wall and daily stand-up. In some organisations I worked with the whole concept of the wall is not accepted by many developers, because of the stand-up necessity and "time waste". Very often all that methodology is used for the sake of methodology and not to achieve what we actually do - adding or creating value to our customer (usually called "The Business"). I can understand frustration that is caused by the wall and stand-up process. From the software developer perspective it is really a waste of time for the following reasons: 1. In 95% of cases developers are head down working like hell delivering valuable outcomes that they are accountable for. Extra effort to go to the wall, staying there for 15-30 minutes and listening or not listening to what others were doing yesterday and will be doing tomorrow is annoying for them; 2. The mere fact of having to do something mandatory to do that looks like

Mastering The Multitasking

There is usually two distinct perspectives on multi-tasking: 1. Multitasking is counterproductive. We get distracted by multiple tasks that all get our way and fight for our scarce attention, time and resources. This leads to a common fallacy that if you do multiple activities “at a time” you are not doing good work in any of those. 2. Multitasking is a way of getting many things done in a short period of time or in a long run. Indeed it can be either a disaster or a great helper depending on how it is used and practiced. Most recent research shows that we don’t do multiple tasks purely in parallel or simultaneously. That means we don’t purely multi-task, but switch between tasks and execute them one at a time, but by spending very small timeframes on each task. A good example from the history is a story about Julius Caesar capabilities in that area. Plutarch writes, “Caesar disciplined himself so far as to be able to dictate letters from on horseback, and to give directi

Travels etc.

Search This Blog