ERP for Food & FMCG

An ERP for food and FMCG has to master one thing above all without gaps: the traceability of every batch from goods receipt to delivery - including best-before date, FEFO picking, cold chain evidence and correct allergen declaration. Unlike in classic retail, this is not an add-on feature but a legal obligation (EU Regulation 178/2002) and, in the event of a recall, vital for survival. On top of that comes the high turnover speed of perishable goods, which quickly turns manual processes into a bottleneck. In this article we show you, vendor-neutrally, which requirements a food ERP absolutely has to cover, what to watch for when choosing, and which systems are worth considering in the DACH region.

Why the food industry places special demands on ERP

Food and FMCG (fast moving consumer goods) differ from other trade goods in three factors: limited shelf life, statutory documentation duties and extremely high throughput volumes. Every item ages, every batch has to stay traceable, and the flow of goods runs in days rather than months.

A standard retail system that only knows quantity and item number fails here. You need batch management that carries not just the quantity but also batch, best-before date and origin - across the entire process from goods receipt to goods issue. If this foundation is missing, it can hardly be retrofitted cleanly later.

Batches and traceability: the foundation

The core of every food ERP is seamless traceability. The EU General Food Law 178/2002 requires the principle of "one step back, one step forward": for every batch you must be able to prove which supplier the raw material came from and which customer the product went to.

Batch tracking from goods receipt to delivery

Batch management assigns or takes over a batch or lot number at goods receipt and records it on every posting. In processing operations, the input batch is linked to the output batch, so that from a finished product all the raw material batches it contains can be reconstructed. When choosing, check whether the system forms this batch-to-batch relationship automatically - not every retail ERP can do this.

For products requiring individual tracking (such as high-value or approval-bound items), serial number management complements the batch logic. In classic food trade, however, the batch dominates.

Recall in minutes instead of days

The real purpose shows in an emergency: if a recall becomes necessary, you have to know within minutes which customers received which batch. A cleanly managed system delivers this list at the push of a button - manual research through paper documents costs days in case of doubt, and with them reputation. An audit-proof audit trail additionally documents who made which posting and when.

Best-before date, FEFO and cold chain: managing shelf life

The second domain is dealing with the limited lifespan of the goods. This is where it is decided whether your system minimises spoilage or produces write-offs.

Best-before date tracking and FEFO picking

Every batch carries a best-before date (BBD) or a use-by date. The decisive factor is the picking strategy: in the food sector FEFO applies (First Expired, First Out) - the batch with the earliest expiry date is picked first, not necessarily the one stored first. This is what distinguishes FEFO from the classic FIFO principle: FIFO controls by storage order, FEFO by expiry date. A pure FIFO system can let goods expire even though they are physically available.

The ERP has to map FEFO in the picking proposal and monitor remaining shelf life: batches with a tight best-before date are prioritised, and are automatically blocked for lock periods (e.g. minimum remaining shelf life at the customer). Blocked and quality-inspection stock for locked or to-be-checked batches belongs here too.

Cold chain and temperature control

For chilled or frozen goods, the cold chain is part of compliance. A food ERP should map temperature zones in the warehouse, distinguish chilled and frozen storage locations and, ideally, document temperature evidence (e.g. from sensors or goods receipt inspection) on the batch. That way, in the event of a complaint, you can prove that the chain was not interrupted.

Declaration, allergens and product data

Food is subject to strict labelling obligations under the EU Food Information Regulation (FIC, Regulation 1169/2011). Ingredients, nutritional values, the 14 allergens subject to declaration and origin information must be correct and up to date on the product.

The ERP - often in interplay with a PIM - keeps this declaration data structured in the item master. Versioning is important: if a supplier changes the recipe, the new allergen and ingredient information must take effect traceably. For exporting this data into online shops and to trading partners, structured standards such as eCl@ss have become established. Incorrect or outdated declaration is not only a compliance risk but can trigger warnings and recalls.

High turnover: speed and inventory accuracy

FMCG thrives on pace. Inventory management has to be right in real time, because with perishable goods every shortfall directly means lost revenue or a write-off. A high inventory turnover - the frequency with which the stock is completely turned over in a year - is both a goal and a key figure in the food sector: the faster the goods turn, the less spoilage and tied-up capital.

This gives rise to concrete system requirements:

• Automatic replenishment with order proposals that take remaining best-before shelf life and sales velocity into account instead of just a reorder point.
• Barcode/scanner-supported processes in goods receipt and picking, to capture batches quickly and without errors.
• Permanent inventory accuracy via perpetual inventory instead of just an annual cut-off count.
• GTIN/EAN tracking for clean item identification in retail.

If automation is missing here, the manual effort becomes a bottleneck at several thousand movements per day.

Compliance in the DACH region: what is mandatory in 2026

In addition to food law requirements, the general accounting and tax obligations apply. Two points are non-negotiable.

First, the system must work GoBD-compliant: archiving documents and postings in an unalterable, complete and traceable way. For traceability this is a double benefit, because the same principles apply.

Second, the e-invoice. In the DACH region a clear staggering applies. In Germany, the obligation to receive structured B2B e-invoices has existed since 1 January 2025. The obligation to issue comes in stages: in principle from 1 January 2027 for companies with more than 800,000 euros in prior-year revenue, then from 1 January 2028 for all remaining companies. The format must comply with the European norm EN 16931 (such as XRechnung or ZUGFeRD). Food businesses in particular, with a high document volume and EDI connection to food retail, should anchor these deadlines in the system early - when in doubt, coordinated with the tax advisor.

The following overview summarises the must-have criteria by area:

Fitting systems for food and FMCG

There is no single best food ERP - the choice depends on assortment, depth of processing, channels and volume. For orientation, a vendor-neutral overview; the details are in the respective profiles in the ERP directory.

• Trade and D2C food without own production: cloud systems such as weclapp, xentral or reybex cover batches, best-before dates and inventory management and can be rolled out comparatively quickly. Limits show up with deep recipe and production planning.
• Operations with production and individual process needs: Odoo offers recipe, batch and manufacturing logic via modules, but in return demands more configuration and integration effort.
• Upper mid-market with production and retail connection: suites such as Dynamics 365 Business Central, Oracle NetSuite or SAP S/4HANA Cloud bring extensive batch, quality and multi-company functions - at higher complexity and higher cost.

Important: this classification is a starting point, not a winner ranking. Use the system comparison to mirror candidates against your concrete requirements. Because the batch, FEFO and cold chain logic experience shows takes the most effort in implementation, it pays off early to get neutral ERP consulting that checks your processes against the system landscape before you move into implementation.

Conclusion

An ERP for food and FMCG stands or falls with seamless batch traceability, clean best-before and FEFO control, documented cold chain and correct allergen declaration - all at high turnover speed. Standard retail systems most often map these functions only half-heartedly, so check them first. Draw up a prioritised requirements list, match it against concrete systems, and plan for GoBD as well as the e-invoicing deadlines of 2025/2027/2028 from the start. Anyone who takes the perishability and the documentation duties of the food industry seriously early on avoids the most expensive mistakes in system selection - and is able to act in the event of a recall.