‘Horsegate’ should prompt debate on labelling

‘Horsegate’ should prompt debate on labelling

Clearer labelling on meat products to aid consumer choice and demonstrate greater transparency is needed to safeguard long-term consumer confidence in beef and lamb products.

That’s the view of Nick Allen, EBLEX sector director, in the wake of the “horsegate” scandal that has gripped the UK this week.

Nick welcomed the NFU view that retailers need to re-examine sourcing and labelling policies and said there was a high level of frustration among farmers who adhere to strict guidelines on production, only to potentially be let down further up the supply chain.

“Co-mingling of meats of different country of origin has been repeatedly raised by consumers as a concern in recent years,” he said.

“We would support calls for clear, simple labelling and welcome a debate on the issue. Origin is important to people. They want to know provenance and exactly what is in the product they are buying. While it is accepted that lower value meat products are unlikely to contain as high a proportion of beef than at the quality end of the market, the contents still need to be clearly labelled on the packet.

“We would encourage consumers to look for the assurance marks on packs, like the Red Tractor logo or the Quality Standard Mark (QSM) for beef or lamb, which give a level of reassurance on where a product is from and that it has been produced to clearly defined standards.

“Our own QSM scheme is independently audited and remains robust. However, in the light of this incident coming to light, we are looking at introducing random DNA testing to beef and lamb produced under our scheme as an additional failsafe.

“We await with interest the outcome of the investigation into how the horsemeat found its way into value beef burgers. We can then look at making sure it cannot happen again.”

Previous / Next posts...

Warning: Undefined variable $nextthumbnail in /home/yandellpublishin/meatmanagement.com/wp-content/themes/meatmanagement-two/single.php on line 73

Submit a Comment

Your email address will not be published. Required fields are marked *