Name calling: FPCCI wants Basmati issue resolved

Asks ministry to register name as India plans its move.


Our Correspondent June 03, 2015
Traded: $2.1b is the amount Pakistan fetched through rice exports in 2014, which is the second highest export item after textiles. STOCK IMAGE

KARACHI: Federation of Pakistan Chambers of Commerce and Industry Senior Vice President Abdul Rahim Janoo has urged Commerce Minister Khurram Dastgir to immediately take up the registration issue for Basmati rice to protect the country’s global trade situation.

In his letter to the commerce ministry, he warned against India’s move in registering the rice under the name Basmati, which would consequently not allow Pakistan to export it under the same name, causing a tremendous loss.

“It is high time for the ministry to pre-empt the Indian move because in case India succeeds, Pakistan will not be able to export its Basmati rice in the name, style and title of Basmati,” he said. He said that the ministry of commerce should take steps to thwart the move to get its Basmati rice registered to secure its trade in the international market.

He further added that it would have far-reaching negative impact on the country’s economy as rice holds an extremely important position.

He elaborated that Pakistan had earned $2.1 billion foreign exchange through rice exports in 2014, which is the second highest export item from Pakistan after textiles.

“Pakistan is the world’s fourth largest producer of rice after China, India and Indonesia and millions of farmers rely on rice cultivation as a major source of employment,” he informed.  He underscored the need for taking necessary measures to safeguard the interest of indigenous Basmati rice farmers and exporters in the said matter.

Published in The Express Tribune, June 3rd, 2015.

Like Business on Facebook, follow @TribuneBiz on Twitter to stay informed and join in the conversation.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ