Shopfloor Matters

The biggest barriers to MES success in food manufacturing

MES success in food depends on the people as much as the technology. The team, the scope, the master data and the platform choice are where projects succeed or stumble.

Illustration: MES barriers in food manufacturing

Food and beverage manufacturers face pressures most other industries don't. Strict food safety regulation. Perishable raw materials. Allergens. Traceability that has to work in minutes, not days, when a recall lands. And margins that often live or die on yield.

MES/MOM should be the answer to a lot of that. When it's implemented well, it is.

But too many food projects stumble. The technology matters, and choosing the right platform is one of the biggest decisions you'll make. The people matter just as much, and they're the part that's most often underestimated. These are the four barriers I see most often, and what to do about each.

1. People need as much attention as the technology

Most project plans are built around the technology: the platform, the integrations, the configuration. That work is essential. But the team you build, and how you bring the shopfloor with you, has just as big an impact on your success. Without the right people in the right roles, and a sponsor who'll clear the way, even the best system will struggle to deliver.

I speak to many food manufacturers who underestimate the change management. Operators have run the same process for years, sometimes decades. Ask them to adopt a new digital system without involving them in the design, or explaining why, and you'll get resistance. Sometimes quiet, sometimes not.

Get operators involved early. They know the process better than anyone, including the workarounds that never made it into the SOP. Their input makes the system better. Their buy-in makes adoption faster.

2. Starting too big, too fast

The second mistake is trying to do everything at once. Production, quality, inventory, maintenance and traceability, across every line and every site, on day one.

It's doable. But it multiplies the risk, and food is not an industry that forgives a bad week on the line.

Phase the delivery, and get early wins on the board, but make the decision as a company.

The manufacturers who succeed think big and start pragmatically. They know the end state. They just don't try to get there in one leap.

3. Underestimating the data foundation

Food manufacturers often want the headline capabilities straight away: real-time OEE, automated batch traceability, SPC on critical quality parameters, digital allergen control. All the right things to want.

But they sit on top of the unglamorous basics. Master data. Recipes and bills of materials. Routings. Equipment hierarchies. Specifications and inspection plans.

Food adds its own layer of complexity here. Recipes with substitutions, variable yields from natural raw materials, units that change from kilograms in to cases out, shelf-life rules that differ by product. If that isn't defined properly, nothing downstream works properly either.

I'd urge anyone starting an MES/MOM project to invest properly in this phase. Rushing through data preparation to reach the exciting functionality is one of the most common causes of delay and rework I see. Get the data right first. The rest follows.

4. Choosing the wrong platform

Be wary of a cheaper solution chosen as a stop-gap.

Too many food manufacturers fill one gap with one small tool. A checklist app for hygiene sign-offs. A standalone OEE dashboard. A separate quality app for line checks. Each solves today's problem. Few of them share data, and none of them can grow into what you'll need next year.

Food is the industry where that hurts most, because the questions that matter cut across every department at once. Which batches of finished goods contain this lot of raw material? Did it pass goods-in inspection? Which line ran it, after which clean-down, with which allergen changeover? Answer that from four disconnected systems and your two-minute recall becomes a two-day investigation.

Pick a mature, configurable MOM platform from the start. One that puts production, quality, inventory and maintenance on the same data, and handles food's specific requirements natively rather than through customisation:

  • Batch and lot traceability, forwards and backwards
  • Recipe and formulation control, including substitutions
  • Shelf-life, expiry (FEFO) and FIFO enforcement
  • Allergen management and changeover validation
  • Yield and give-away tracking at the line

Yield is often the single biggest profit lever in food. A system that shows you give-away by line, by shift and by product in real time can pay for itself on that alone.

Practical advice for anyone starting the journey

Assemble the team before you touch the technology. You need an experienced project manager, operational subject matter experts, IT support, and an executive sponsor who will clear roadblocks. If you lack MES/MOM expertise internally, bring in an experienced partner, ideally one who has delivered MES/MOM in food before. A good consultant or systems integrator shortens the learning curve enormously.

Define success early, and make it specific. What does good look like after phase one? Scrap down by a set percentage? Batch release in hours rather than days? Digital traceability for every finished pallet? Allergen changeovers signed off digitally? Measure it, and use the system to capture the data that proves it. That evidence is what funds phase two.

Don't underestimate quick wins. When an operator sees their own downtime data for the first time, or a quality manager traces a batch in seconds rather than hours, adoption accelerates. Those moments build momentum. And momentum is what carries a project from a pilot line to an enterprise standard.

If you're in food and beverage and partway through a project, which of these barriers is giving you the most trouble right now?

Written by Matt Barber · Last updated August 2026

Matt Barber
Written by

Matt Barber

VP & General Manager for the shopfloor at Infor. Started as an MES developer, then ran projects, solution design and product. Writes about the smart factory, shopfloor AI and the MES/MOM foundations underneath them.

Keep reading

The newsletter

Get the next one in your inbox

New articles on shopfloor AI, smart factory strategy and the MES/MOM lessons I wish someone had told me before my first implementation.

  • Vendor-neutral, practical guidance
  • Written from real implementations, not brochures
  • Shopfloor AI, smart manufacturing and MES/MOM
  • No hype, no buzzword bingo