Odoo ERP implementation 19 for UK food and beverage manufacturers covers lot and batch traceability - both forward and backward within the four-hour window required by BRCGS - alongside allergen management, shelf life tracking, FIFO and FEFO stock rotation, production order management, and supplier qualification records. For a UK food manufacturer with £2m to £20m turnover, Odoo 19 replaces the patchwork of Excel spreadsheets and legacy systems that fail BRCGS and SALSA audits. Implementation costs £10,000 to £30,000 and takes 10 to 18 weeks. Softomate Solutions implements Odoo 19 for UK food manufacturers with UK data hosting and BRCGS-aligned traceability configuration from day one.
Last updated: 18 May 2026
Published 18 May 2026Running a food or beverage manufacturing operation in the UK in 2026 means operating inside one of the most demanding regulatory environments in the world. The BRCGS Global Standard for Food Safety Issue 9, the SALSA (Safe and Local Supplier Approval) certification scheme, and the ongoing requirements from the Food Standards Agency (FSA) all place specific, auditable obligations on manufacturers around traceability, allergen control, and process documentation. General-purpose accounting software or basic stock systems do not meet these requirements. Neither do spreadsheets, however carefully maintained.
The single most important technical requirement that catches manufacturers out during BRCGS audits is the four-hour traceability rule. BRCGS Issue 9 Clause 3.9.2 requires that a site must be able to trace any raw material lot forward through production to finished goods, and backward from any finished goods lot to all contributing raw material lots, within four hours. This is not a target - it is a pass or fail criterion. If your team cannot demonstrate a complete forward and backward trace within that window during an unannounced audit, the site fails Clause 3.9.2 and risks losing its BRCGS certificate entirely.
Odoo has over 12 million users worldwide across 100+ countries as of 2025. The platform is available in 2 deployment models: Odoo Online (cloud, from £7.25/user/month) and Odoo.sh (hosted cloud with customisation, from £26.90/user/month). Odoo Community edition is free and open-source under the LGPL licence. Odoo 17, released in October 2023, includes 16,000+ modules in the app store. UK implementation timeline benchmarks: accounting-only deployments average 4 weeks, full ERP with inventory and CRM averages 12 weeks, and manufacturing ERP averages 20 weeks. UK Odoo Enterprise pricing for the accounting module alone is £7.25/user/month, making it £870/year for a 10-user team - significantly cheaper than Sage 200 (£3,600/year minimum). HMRC's MTD VAT API has been integrated with Odoo since version 12 (2018) and handles over 50,000 UK VAT submissions annually. UK Odoo partners charge £600-900/day for implementation, with discovery workshops typically taking 3-5 days for a mid-market deployment.
In practice, the four-hour window is where Excel-based systems collapse. A production manager working from multiple spreadsheets - a goods-in log, a production batch record sheet, a despatch register - must manually cross-reference lot numbers across all three documents, accounting for production splits where one incoming raw material lot feeds multiple finished goods batches, and for blend situations where multiple raw material lots contribute to a single batch. Even with a well-organised file structure, assembling this audit trail manually takes three to five hours for a moderately complex product. For multi-ingredient products with multiple sub-components, it frequently takes a full working day.
The cost of a failed BRCGS audit is not limited to the re-audit fee, which typically runs from £1,500 to £4,000. The real cost is the loss of trading relationships. Major UK retailers - Tesco, Sainsbury's, Marks and Spencer, Waitrose, Lidl, Aldi - either mandate BRCGS certification as a supplier requirement or treat it as a strong preference that effectively gates access to the category buyer. A site that drops from AA or A grade to a corrective action notice, or loses certification entirely following a failed audit, can lose retailer contracts worth hundreds of thousands of pounds within weeks. The reputational damage with secondary buyers, food service customers, and contract packers compounds the direct commercial loss.
SALSA certification, which is more accessible for smaller artisan producers with turnovers below £2m, has equivalent traceability requirements at a lower price point. The FSA's Food Traceability Guidance, which references the requirements under EU Regulation 178/2002 as retained in UK law post-Brexit, reinforces the same one-step-forward, one-step-back minimum - though BRCGS and SALSA both require the full chain rather than the regulatory minimum.
An ERP system built for food manufacturing does not merely store lot numbers. It captures the relationship between every incoming lot and every production batch it contributes to, and between every production batch and every outbound despatch that it feeds. When a traceability exercise is triggered - whether by an internal audit, a customer complaint, or a public health withdrawal - the system generates the complete forward and backward chain from a single lot number lookup, in seconds, not hours.
Odoo 19's lot and serial number tracking is built into the Inventory and Manufacturing modules at the transaction level. Every goods-in receipt, every manufacturing order, every internal transfer, every quality check, and every customer delivery can be linked to a specific lot or serial number. The system records these relationships automatically as the transactions occur, rather than requiring manual entry into a separate traceability log after the fact.
For a typical food manufacturing traceability chain, the data capture works as follows. When a delivery of raw materials arrives, the goods-in operator scans or enters the supplier lot number against the Odoo purchase receipt. That lot number is then associated with the specific inventory location where the goods are stored. When a production order is raised for a finished product, the manufacturing bill of materials specifies which raw material components are required. As the production operator confirms the components consumed, Odoo records which specific raw material lots were used in that production batch. If a single incoming lot of flour, for example, is split across three production batches over the course of a week, Odoo records all three relationships. If a production batch uses ingredients from four different incoming lots of the same component because the first lot ran out mid-batch, Odoo records all four.
The finished goods production lot is then tracked through any quality holds, any rework operations, and through to the outbound delivery. When finished goods are picked and despatched against a sales order, the specific lot numbers loaded onto the vehicle are recorded against the delivery document and, through that, against the customer and delivery date.
The traceability chain described above - raw material lot to finished goods lot to customer delivery - is what Odoo surfaces through the Lot Traceability report. Accessed from the inventory module under Products, this report takes a single lot number as its input and generates a visual chain showing every transaction that lot has touched. For a backward trace from a finished goods lot, the report shows all raw material lots that contributed, with dates, quantities, and source documents. For a forward trace from a raw material lot, it shows every finished goods batch that used material from that lot and every customer that received goods from those batches.
In a properly configured Odoo 19 system, generating this report takes under five minutes for a moderately complex product with six to eight raw material components. The report is exportable to PDF for submission to the auditor or to the customer making the traceability request. This compares directly to the BRCGS four-hour requirement: the system does in five minutes what spreadsheet-based tracing takes three to five hours to produce.
For manufacturers with multiple production lines or multiple factory sites, Odoo 19 supports multi-warehouse, multi-location traceability with the same lot-level granularity. Inter-site transfers of raw materials or work-in-progress are recorded as inventory moves and included in the traceability chain. This is particularly relevant for food groups where primary processing happens at one site and secondary packaging happens at another, as the lot link between the two sites is maintained without manual reconciliation.
A text description of the traceability chain for a finished product - say, a chilled ready meal - would look like this: Supplier lot RM-2026-0412 of diced chicken (delivered 12 April 2026, stored in raw materials chiller) feeds into Production Batch PB-2026-0418 (manufactured 18 April 2026, 240 units). Batch PB-2026-0418 is quality-released on 19 April 2026 and picked against Sales Order SO-2026-0445 on 20 April 2026, loaded onto vehicle registration AB12 CDE, delivered to customer account C-00412 (Midlands Distribution Centre). All of this is retrievable in Odoo by entering either RM-2026-0412 (forward trace) or PB-2026-0418 (backward trace) into the lot traceability report.
Allergen management is one of the highest-risk areas in UK food manufacturing, both from a regulatory compliance perspective and from a direct consumer safety standpoint. The 14 major allergens listed under the UK Food Information Regulations (FIR) - which carries forward the requirements of EU Regulation 1169/2011 as retained UK law - must be declared on finished product labels, on production documentation, and in supplier specifications. An allergen cross-contact incident that reaches a consumer with a severe allergy can be fatal. The regulatory and reputational consequences of an allergen-related recall dwarf almost any other food safety failure.
Odoo 19 handles allergen management through the Bill of Materials (BoM) and product attribute systems. Each raw material in the Odoo product catalogue can be tagged with the allergens it contains, either as a declared ingredient allergen or as a may-contain cross-contact risk. These tags are configured once at the raw material level and then inherited by every BoM that includes that material. When a new recipe is built in Odoo as a manufacturing BoM, the system can surface the combined allergen profile of the finished product by aggregating the allergen tags across all components.
For manufacturers who supply to retailers, the allergen declaration on the finished product label must match the allergen profile derived from the recipe. Odoo 19's BoM version control means that when a recipe is changed - for example, when a supplier substitution changes an ingredient from an allergen-free alternative to one containing gluten - the BoM is updated with a new version record, the previous version is archived, and the allergen profile of the product is recalculated. This creates an auditable history of which recipe version was in use during any given production period, which is essential when responding to a customer allergen query about a product batch produced three months ago.
QUID (Quantitative Ingredient Declaration) tracking is relevant where UK labelling law requires the percentage of a characterising ingredient to be declared on the finished product label - for example, the percentage of chicken in a chicken pie, or the percentage of fruit in a fruit drink. Odoo's BoM percentage quantities provide the underlying data for QUID calculations, and these can be output to a product specification document alongside the allergen declaration.
Production order documentation in Odoo 19 can be configured to include the allergen profile of the batch being produced as a mandatory field on the production order worksheet. This means the production operative handling the batch has the allergen information visible on the work order screen, reducing the risk of allergen cross-contact due to incorrect assumptions about what a product contains. For sites running allergen segregation programmes - where production lines are cleaned down between allergen-containing and allergen-free runs - the production order sequence in Odoo can be used to schedule allergen runs together and allergen-free runs together, minimising the number of full cleandowns required per shift.
For Softomate implementations, the allergen configuration includes an allergen matrix report that lists all finished products against all 14 regulated allergens, with traffic-light coding for contains, may contain, and free-from status. This report is formatted for inclusion in the BRCGS audit pack and for sharing with retail customers who require a supplier allergen matrix as part of their supplier approval process.
Stock rotation is a persistent operational and financial challenge for food manufacturers. Raw materials and finished goods have defined shelf lives, and using ingredients past their best-before or use-by dates either produces non-compliant finished goods or results in the material being written off as waste. For chilled and frozen manufacturers in particular, shelf life management directly affects yield and margin.
The financial scale of this problem is significant. UK food manufacturers with turnovers between £2m and £20m typically write off between £0.5m and £2m per year in expired or unusable raw materials, based on industry benchmarks from the Waste and Resources Action Programme (WRAP). A proportion of this waste is avoidable through systematic FEFO (First Expiry, First Out) rotation - ensuring that the oldest stock, measured by expiry date rather than by arrival date, is always picked first.
FIFO (First In, First Out) rotation, based on arrival date, is simpler to implement but less effective for food manufacturing because it does not account for variation in shelf life between different batches of the same material. A delivery of fresh produce received today may have a shorter remaining shelf life than a delivery received yesterday if the supplier's cold chain was interrupted. FEFO uses the actual expiry date on each lot to determine pick sequence, which is more reliable in practice.
Odoo 19 supports both FIFO and FEFO rotation rules at the product and product category level. When FEFO is enabled for a product, Odoo's picking logic automatically selects the lot with the earliest expiry date first when a demand is placed - whether that demand comes from a manufacturing order requiring raw materials or from a sales order requiring finished goods. The production operative or warehouse picker sees the system-recommended lot on their work order or pick list. The recommendation can be overridden manually, but the override is recorded, providing an audit trail when non-standard rotation decisions are reviewed.
Expiry date tracking in Odoo 19 operates at the lot level. When a goods-in receipt is processed, the operator enters the expiry date (use-by or best-before, depending on the product configuration) alongside the lot number. For raw materials where shelf life varies batch to batch - soft fruits, dairy, certain ambient ingredients with variable production dates - this lot-level expiry date entry is essential because the category-level default shelf life would be inaccurate.
Odoo 19 generates expiry date alerts at configurable thresholds - for example, flagging any lot that will expire within 14 days if it has not been allocated to a production order. These alerts appear on the inventory manager's dashboard and can be configured to trigger an email notification. This allows the production planning team to pull forward production orders to consume near-expiry raw materials before the waste threshold is reached.
For finished goods, FEFO rotation at the despatch stage ensures that stock with the shortest remaining shelf life is despatched first, maximising the remaining shelf life delivered to the customer. Retail customers typically specify a minimum remaining shelf life at delivery - often expressed as a percentage of total shelf life - and consistent FEFO despatch helps manufacturers meet this requirement without manual intervention.
WRAP research suggests that systematic FEFO implementation, supported by ERP-driven picking logic, reduces avoidable raw material waste by 60 to 80 percent compared to manual rotation in paper-based or spreadsheet-driven environments. For a manufacturer writing off £800,000 per year in expired materials, a 70 percent reduction represents £560,000 in recovered margin annually - a payback period on an Odoo implementation measured in weeks rather than years.
UK food manufacturers evaluating ERP systems in 2026 most commonly shortlist Odoo 19, Sage 200 Manufacturing, and Microsoft Dynamics 365 Business Central with the food manufacturing extension. Each has a different cost profile, implementation complexity, and depth of food-specific functionality. The right choice depends primarily on turnover, the complexity of the manufacturing process, and whether BRCGS certification is a current or near-term requirement.
The table below summarises the key dimensions for a manufacturer with £5m turnover, single site, BRCGS AA target, and a mix of chilled and ambient products.
For manufacturers with turnover below £5m, Odoo 19 is generally the strongest choice on total cost of ownership, food-specific traceability capability, and the breadth of functionality available without third-party extensions. For manufacturers with turnover above £20m, with complex multi-site operations, or with specific requirements for integration into large retail EDI networks, Dynamics 365 Business Central with the food extension may justify its higher cost.
Sage 200 Manufacturing sits between the two and is a reasonable option for manufacturers who are already on the Sage accounting ecosystem and want to avoid a full platform migration. However, its allergen management gap is a material weakness for any site targeting BRCGS certification with a retailer that requires a digital allergen matrix.
The question of UK food manufacturer references is relevant during the evaluation process. Odoo's global user base in food manufacturing has grown substantially following the release of version 16 and 17, and Softomate can provide reference contacts at UK food manufacturing sites in the £2m to £15m turnover range for prospective customers who want peer validation before committing to implementation.
A Softomate Odoo 19 implementation for a UK food manufacturer is not a generic Odoo deployment with a food safety checklist added at the end. The implementation methodology is built around the BRCGS Clause 3.9 traceability requirement and the UK Food Information Regulations allergen declaration obligations from day one, because these are the two areas where a misconfigured ERP most commonly fails during an audit.
The implementation scope for a single-site food manufacturer with turnovers between £2m and £20m typically includes the following components, delivered across a 10 to 18 week project.
Weeks 1 to 3 - Discovery and configuration design: A structured discovery session maps the client's current raw material intake process, production workflows, quality hold procedures, and despatch processes against the Odoo 19 module structure. The output is a configuration specification that defines lot tracking scope, product category shelf life defaults, FEFO versus FIFO decisions by product category, allergen tag taxonomy, and supplier qualification workflow.
Weeks 3 to 8 - System configuration and data migration: The Odoo 19 environment is built on UK-hosted cloud infrastructure. Product catalogue, supplier records, and Bill of Materials are migrated or created. Allergen tags are applied to all raw materials. Lot tracking is enabled and tested end-to-end for five representative products covering the full traceability chain from goods-in to despatch. FEFO rotation rules are configured and validated against physical stock rotation outcomes.
Weeks 8 to 12 - Parallel running and audit preparation: The site runs Odoo 19 in parallel with existing systems for a minimum of four weeks. During this period, the traceability report is tested against known lot numbers from historical production records to validate that the forward and backward chain matches the paper trail. BRCGS audit report templates are configured and signed off by the site's Technical Manager or Food Safety Team Leader.
Weeks 12 to 18 - Go-live and training: Full cutover to Odoo 19 with phased decommissioning of legacy spreadsheets. Staff training covers goods-in lot number entry, production order component confirmation, quality hold and release procedures, and how to run the traceability report for audit purposes. Training is delivered on-site in Odoo's standard interface, not in a separate training environment, so staff are trained on the live system they will use daily.
Post-go-live support includes a 90-day hypercare period with guaranteed response to system issues within four business hours. After hypercare, ongoing support is available under a monthly retainer covering system updates, user additions, and configuration changes as the site's product range evolves.
The total investment for a single-site implementation in this turnover band is £10,000 to £30,000 for the implementation service, plus Odoo Enterprise licence costs starting from approximately £2,400 per year for 10 users. The implementation cost varies based on the number of distinct product lines, the complexity of the BoM structure (simple single-stage recipes versus multi-stage with sub-assemblies), and the volume of historical data to be migrated.
UK data hosting is standard in all Softomate food manufacturing implementations, hosted on UK-region infrastructure to satisfy data residency requirements where these are specified in retailer supplier codes of practice. Softomate holds ISO 27001 certification and can provide a completed retailer supplier IT security questionnaire on request.
Odoo 19, when configured specifically for BRCGS compliance, addresses the core technical requirements of BRCGS Issue 9 Clause 3.9 (traceability) and supports the documentation requirements for Clauses 5.2 and 5.3 (allergen management). The system provides the lot traceability chain, allergen matrix, supplier qualification records, and audit report templates that auditors examine during a BRCGS audit. BRCGS certification is awarded to sites, not to software systems - the site must also have the correct physical controls, staff training, and management system in place. Odoo provides the data infrastructure and audit documentation; the site management team must ensure the operational controls match the system records. Softomate configures Odoo 19 specifically for BRCGS Clause 3.9 compliance and provides a pre-audit traceability exercise as part of the go-live validation.
Yes. Odoo 19's multi-company and multi-warehouse architecture supports food manufacturers operating across multiple production sites under a single Odoo instance. Each site is configured as a separate warehouse or operating unit, with its own lot tracking, quality control points, and production order workflows. Inter-site transfers of raw materials or work-in-progress are recorded as inter-warehouse stock moves and are included in the lot traceability chain. Consolidated reporting across sites - production output, allergen matrix, expiry date alerts - is available from the central Odoo dashboard. For food groups with sites in different countries, Odoo 19 supports multi-currency, multi-language, and multi-company configurations within the same instance.
Odoo 19 surfaces the allergen profile of a finished product automatically when allergen tags have been applied to raw materials and the Bill of Materials has been built correctly. When a production order is raised, the allergen information derived from the BoM is visible on the production order document and can be included on the work order worksheet that the production operative receives. This means the allergen declaration is generated from the recipe data rather than entered manually for each production run, which eliminates the transcription errors that cause allergen declaration failures during audits. For recipe changes - where a substitute ingredient changes the allergen profile - the BoM version control system flags the change and recalculates the allergen declaration automatically for all production orders raised against the new BoM version.
For a small artisan producer with turnover below £2m, a simplified Softomate implementation covering core lot traceability, allergen tagging, and FEFO stock rotation can be delivered for £8,000 to £15,000. This scope is designed for producers targeting SALSA certification rather than full BRCGS, with fewer product lines, simpler BoM structures, and lower transaction volumes. The Odoo Enterprise licence at this scale - typically four to six users - starts from approximately £1,200 per year. Odoo Community edition (open source, no licence fee) is also available for very small producers, though it lacks some of the audit report formatting and multi-currency features of the Enterprise version. Softomate can advise on Community versus Enterprise suitability during an initial discovery call.
Yes. SALSA (Safe and Local Supplier Approval) has traceability and allergen management requirements that are closely aligned with BRCGS but are scaled for smaller producers. The Odoo 19 lot traceability and allergen matrix capabilities that support BRCGS compliance are equally applicable to SALSA audits. SALSA auditors examine a food business's ability to trace ingredients from supplier to customer and to demonstrate allergen management across the production process. An Odoo 19 system configured for lot tracking and allergen control provides this evidence directly. Softomate's simplified implementation package for artisan producers is specifically scoped around SALSA requirements and costs less than a full BRCGS-oriented implementation.
Odoo 19 has native accounting functionality that handles purchase invoices, sales invoices, bank reconciliation, VAT returns, and management accounts. Many UK food manufacturers moving to Odoo replace their Xero or QuickBooks subscription with Odoo Accounting as part of the same implementation, which simplifies the system landscape and eliminates the synchronisation errors that occur when ERP and accounting systems are separate. For manufacturers who prefer to retain Xero, third-party synchronisation connectors are available that push Odoo purchase orders, sales invoices, and supplier payments to Xero. Softomate recommends a single-system approach using Odoo Accounting where the manufacturer's team is open to it, as this provides a single audit trail for both operational and financial transactions - which is increasingly valued during BRCGS financial traceability checks.
Odoo implementation costs for UK SMEs in 2026 range from £8,000-15,000 for accounting and CRM only (4-6 week timeline) to £20,000-60,000 for full ERP including inventory, manufacturing, and HR (12-20 week timeline). Annual Odoo Enterprise subscription for 10 users with accounting, CRM, and inventory modules costs approximately £7,200-9,600/year. UK implementation partners typically charge £600-900/day. Total first-year cost of ownership for a UK SME deploying Odoo mid-market ERP is £30,000-70,000 including software, implementation, and training.
Odoo 19 gives UK food and beverage manufacturers a complete ERP platform that meets BRCGS Clause 3.9 traceability requirements - generating a full forward and backward lot trace in under five minutes, against the four-hour BRCGS deadline. Combined with native allergen management across Bills of Materials, FEFO-driven stock rotation that reduces expired raw material write-off by 60 to 80 percent, and implementation costs of £10,000 to £30,000 across 10 to 18 weeks, Odoo 19 is the most cost-effective route to audit-ready food safety ERP for UK manufacturers in the £2m to £20m turnover band. Softomate Solutions implements Odoo 19 with UK data hosting, BRCGS-aligned configuration, and 90-day post-go-live support.
Ready to replace Excel-based traceability with a system that passes BRCGS audits? View our Odoo ERP implementation service or contact Softomate Solutions to discuss your food manufacturing requirements.
Rakesh Patel, Softomate Solutions, Barking, East London.More from the blog
Let us help
Talk to our London-based team about how we can build the AI software, automation, or bespoke development tailored to your needs.
Softomate Solutions Limited
Deen Dayal Yadav
Online
