KP Snacks seeks permission for warehouse at Billingham crisp factory
Summarised from 2 outlets · Updated 11 Nov, 09:01 · Archive
KP Snacks has applied for planning permission to build a warehouse housing a heat exchanger at its Billingham factory.
KP Snacks has applied for planning permission to build a warehouse at its Billingham crisp factory on Cowpen Lane Industrial Estate. The factory, the company's largest manufacturing site, employs about 800 people.
The proposed warehouse would house a heat exchanger to warm the cooking oil used in the crisp-frying process, supporting production of approximately two tonnes of finished product per hour. The building on Macklin Avenue would cover about 176 square metres with two 14-metre-high ventilation stacks. The company plans to demolish two small disused outbuildings to make way for it.
In planning documents, KP Snacks described the project as a replacement and modernisation of essential production infrastructure rather than an expansion of manufacturing capacity. The firm said the new equipment would provide a reliable and controlled source of heat, help maintain production efficiency, improve process control and support the long-term reliability of the manufacturing operation. The company presented the investment as protecting existing manufacturing capacity and ensuring business continuity at the Teesside site.

How it is being reported
- Crisp factory plan for two-tonne per hour productionKP Snacks wants to upgrade equipment at its factory, which employs about 800 workers.BBC Tees · 11 Nov, 08:42
- Crunch time for KP's warehouse plan to help make 'two tonnes of crisps per hour' in BillinghamKP Snacks has applied for planning permission to build the unit at the crisp factory on Cowpen Lane Industrial EstateTeessideLive · 11 Nov, 00:01
In this story: KP Snacks · Billingham · Stockton Council · Cowpen Lane Industrial Estate · Macklin Avenue · Teesside
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem · Corrections log
Comments (0)