Food & Beverage ERP Consultant, UK

What a UK food site asks of its ERP

A typical UK food or drink site runs on tight lead times. A supermarket's order for chilled lines may land through EDI in the evening, production runs overnight, and lorries leave for regional distribution centers before dawn. Ambient producers, breweries and distillers plan over longer horizons but face their own promotional peaks and seasonal ranges. The flow I map usually covers:

• Goods in: supplier batch, use-by or best-before date, temperature on arrival and any positive release check.
• Preparation and cooking: issue by batch, separation of raw and ready-to-eat areas, cook and chill records.
• Packing: labels printed from approved data, weights checked against declared quantity, packs coded with batch and date.
• Dispatch: picking against each depot's minimum life on receipt, delivery notes and electronic delivery notifications.

Two details deserve attention early. First, use-by and best-before dates behave differently, and the ERP should know which one each product carries. Second, packing to an average declared weight under UK weights and measures rules makes giveaway a real cost line, so checkweigher data is worth capturing against each batch. My general food and beverage ERP page explains the core modules; here I focus on what UK sites add.

Third-party audits, traceability tests and withdrawals

UK retailers and many foodservice customers expect suppliers to hold a recognized food safety certification, often an audit against a standard such as BRCGS, alongside their own technical visits. Those audits typically include a traceability test: take a raw material batch, find every finished product it went into and reconcile the quantities, then do the reverse from a finished pack. The exact expectations sit in the standard and with your auditor, so your technical manager decides what the system must prove; I make sure it can.

In practice that means designing for:

• Batch capture at goods in, at each issue to production and at packing, including rework and work in progress carried between shifts.
• Mass balance reports showing quantity in against quantity out for any batch.
• Hold and release status that blocks picking until QA approves.
• Links from customer complaints back to the original batch and supplier.
• Fast lists of affected customers and depots if a withdrawal or recall is needed, for notifying customers and, where required, the relevant food authority.

I build a full traceability test into user acceptance testing and repeat it shortly after go-live, so the first live audit is not the system's first real trial.

Allergens, labels and reformulation control

Allergen mistakes are a recurring cause of product withdrawals in the UK, and the rules for food prepacked for direct sale mean even small sites selling over their own counter need full ingredient lists with allergens emphasized. For manufacturers, the risk usually comes from data rather than intent: a supplier changes a specification, a recipe is reformulated, or a substitute ingredient is used when stock runs short.

The requirements I write here connect three things that often live apart:

• Ingredient specifications from suppliers, with allergen and may-contain information and a review date.
• Recipe versions in the ERP, approved by the technical team before production can use them.
• Label and artwork data, generated from the approved recipe or checked against it, so the pack matches its contents.

Substitution rules matter too. If production swaps one flour or oil supplier for another, the system should check whether the allergen profile changes and stop the batch if it does. Some businesses keep specifications in a dedicated technical system and pass approved data to the ERP; others hold everything in one place. Both can work, provided ownership is clear. I settle that during requirements gathering, with your technical manager in the room.

Supermarket EDI, promotions and VAT on food

Supplying UK grocery multiples means exchanging orders, delivery notifications and invoices electronically, usually through an EDI provider using retail message standards, while some customers run their own supplier portals instead. Forecasts arrive alongside orders, promotions change volumes sharply for a week or two, and late amendments are normal. The ERP has to absorb all of this without customer service retyping orders.

Points I include in the design:

• Order import with validation, so price or product mismatches are flagged before the production plan is fixed.
• Minimum life on delivery per customer and depot, enforced by FEFO picking, with an alert when stock cannot meet it.
• Promotional funding, retrospective discounts and line fees recorded against product and customer for true margin.
• Catch weight for meat, fish and cheese sold by actual weight.

VAT on food is less simple than it looks. Much basic food is zero-rated, while items such as confectionery, crisps, soft drinks and alcohol are generally standard-rated, and the boundary cases are detailed. Drinks producers may also manage alcohol duty and bonded stock. Tax codes should be set per item, confirmed with your accountant and reported under Making Tax Digital. For customs and EU export paperwork, see my UK manufacturing ERP page.

Sage, spreadsheets and remote delivery for UK food firms

Many UK food businesses I speak with keep accounts in Sage or Xero, run recipes and costings in Excel, and record batches on paper sheets filed after each shift. Others have an older food-specific system that still works on the floor but no longer connects well to customers or finance. Before any migration, I want three things settled: a single approved recipe per product, consistent units from kilogram to case to pallet, and a counted opening stock by batch, date and location, including anything held at a cold store or third-party warehouse.

Workshops run during the UK working day by video, arranged around production and hygiene shifts, with recorded sessions for night-shift supervisors who cannot join live. A site visit can be agreed if seeing the line would change the design, though remote sessions cover the great majority of the work. For broader ERP questions, read my ERP consulting for UK businesses page, and the UK hub explains how I support companies across England, Scotland, Wales and Northern Ireland.