Skip to main content

New farm bill 2020: Who is protesting & why

On Sunday, Rajya Sabha passed two of the three farm reforms Bills that have seen widespread protests in recent weeks, particularly in Haryana and Punjab, where the ruling BJP has lost its ally Shiromani Akali Dal. Prime Minister Narendra Modi has reiterated that farmers will benefit from the changes, first mentioned as part of the Atmanirbhar Bharat Abhiyan package. The Bills replaced three ordinances promulgated earlier.

What do the Bills do?

The first thing to do is to simplify the names of these ordinances as agriculture economist Sudha Narayanan (of the IGIDR) has done.


So, think of “The Farmers Produce Trade and Commerce (Promotion and Facilitation) Ordinance, 2020” as the APMC Bypass Ordinance. Treat “The Essential Commodities (Amendment) Ordinance, 2020” as “The Freedom of Food Stocking by Agribusinesses Ordinance”, and “The Farmers (Empowerment and Protection) Agreement on Price Assurance and Farm Services Ordinance, 2020” as the Contract Farming Ordinance.

On paper, what the first one attempts to do is allow farmers to sell their produce at places other than the APMC-regulated mandis. It is crucial to note that the idea is not to shut down APMCs but to expand a farmer’s choices. So, if a farmer believes a better deal is possible with some other private buyer then he can take that option instead of selling in the APMC mandi.

The second Bill proposes to allow economic agents to stock food articles freely without the fear of being prosecuted for hoarding.

The third Bill provides a framework for farmers to enter into contract farming — that is signing a written contract with a company to produce what the company wants in return of a healthy remuneration.

The idea with all three Bills is to liberalise the farm markets in the hope that doing so will make the system more efficient and allow for better price realisations for all concerned, especially the farmers. The central concern, presumably, is to make Indian farming a more remunerative enterprise than it is right now.

How have they been received?


There are two diametrically opposite ways to look at these changes.

One is to believe that the plan on paper will operationalise perfectly in real life. This would mean farmers will get out of the clutches of the monopoly of APMC mandis and evade the rent-seeking behaviour of the traditional intermediaries (called arhatiyas). A farmer would be able to pick and choose who to sell to, and at what price, after making an informed decision. And that, most crucially, when he does this, more often than not, he will end up earning more than what he typically did in the past when he sold his produce through the “exploitative” arhatiyas in the APMC mandis.

The polar opposite viewpoint, from the protesters, is that this move towards greater play of free markets is a ploy by the government to get away from its traditional role of being the guarantor of minimum support prices (MSPs). To be sure, MSPs work in the formally regulated APMC mandis, and not in private deals.

Farmers, especially in Punjab and Haryana where MSPs are more prominently employed, are suspicious of what the markets will offer and how the “big companies” will treat them. Farmers can influence the most powerful governments through the electoral process but vis-a-vis big companies, they are exposed as minor players, incapable of bargaining effectively.

Which view is correct?


There are no easy answers apart from saying that while both have some valid points, neither view is fully correct.
For instance, the new laws are not shutting down APMC mandis, nor are they implying that MSPs will not be functional. Moreover, it is true that — across several sectors of the economy — liberalisation has expanded the size of the pie and improved wellbeing across the board.

Why should a farmer not have more choices? If the private deal is not distinctly better, a farmer can carry on as before. If corporate farming does manage to weaken the APMC mandi system, it would only be because hordes of farmers chose corporate farming or selling outside existing mandis. Could it be the case that the arhatiyas and existing elites are the ones who are threatened by this reform?

Moreover, there is an unwarranted fascination with MSPs in India. The last Agriculture Census (2015-16) showed that 86% of all land holdings were small and marginal (less than 2 hectares); see Chart. These are such small plots that most farmers dependent on them are net buyers of food. As such, when MSPs are raised they tend to hurt the farmers the most.



This is notwithstanding the data that shows more and more farm produce is being sold to private players — instead of the government via MSPs — already.

On the other hand, one can understand why farmers are so sceptical about markets. A good example is what happened when the government enforced a ban on onion exports. In doing so, the government prioritised the interests of the consumers over the interest of the farmers (the producers).

This is not the first time. There are innumerable past examples when the government’s decision to protect the consumers from higher prices have resulted in farmers being robbed of the higher prices a free market could have provided them. In fact, the MSP, it can be argued, is the embodiment of this distrust.

Another underlying structural problem is the lack of information with farmers, which inhibits their ability to make the best decision for themselves. For instance, how will an average farmer figure out the right price for his or her produce?

Similarly, in the absence of adequate infrastructure to store their produce, farmers may not have the capacity to bargain effectively even if they knew the right price.

Where is all this heading to?


In the end, what will determine the results of this latest set of reforms will be their implementation.

If farmers feel robbed and exploited when they participate more fully in the market, they will blame the political masters. But, if they taste success via better returns on a sustained basis — higher profits that allow them to afford better standards of living — then several long-standing doubts and misgivings about markets and these reforms will melt.

Comments

Popular posts from this blog

Spring Security with JWT for REST API

Spring is considered a trusted framework in the Java ecosystem and is widely used. It’s no longer valid to refer to Spring as a framework, as it’s more of an umbrella term that covers various frameworks. One of these frameworks is Spring Security , which is a powerful and customizable authentication and authorization framework. It is considered the de facto standard for securing Spring-based applications. Despite its popularity, I must admit that when it comes to single-page applications , it’s not simple and straightforward to configure. I suspect the reason is that it started more as an MVC application -oriented framework, where webpage rendering happens on the server-side and communication is session-based. If the back end is based on Java and Spring, it makes sense to use Spring Security for authentication/authorization and configure it for stateless communication. While there are a lot of articles explaining how this is done, for me, it was still frustrating to set it up for the f...

Java Functional Interfaces

  The term   Java functional interface   was introduced in Java 8. A   functional interface   in Java is an interface that contains only a single abstract (unimplemented) method. A functional interface can contain default and static methods which do have an implementation, in addition to the single unimplemented method. Here is a Java functional interface example: public interface MyFunctionalInterface { public void execute(); } The above counts as a functional interface in Java because it only contains a single method, and that method has no implementation. Normally a Java interface does not contain implementations of the methods it declares, but it can contain implementations in default methods, or in static methods. Below is another example of a Java functional interface, with implementations of some of the methods: public interface MyFunctionalInterface2{ public void execute(); public default void print(String text) { System.out.println(t...

Java Logger

In Java, logging is an important feature that helps developers to trace out the errors. Java is the programming language that comes with the logging approach. It provides a Logging API that was introduced in Java 1.4 version. It provides the ability to capture the log file. In this section, we are going to deep dive into the Java Logger API. Also, we will cover logging level, components, Logging handlers or appenders, logging formatters or layouts, Java Logger class, What is logging in Java? In Java, Logging is an API that provides the ability to trace out the errors of the applications. When an application generates the logging call, the Logger records the event in the LogRecord. After that, it sends to the corresponding handlers or appenders. Before sending it to the console or file, the appenders format that log record by using the formatter or layouts. Need for Logging It provides the complete tracing information of the application. It records the critical failure if any occur in ...