Lot Tracking and FEFO Management in the Food Industry

Publication Date: February 2026
Reading Time: 12 min read

---

1. Introduction: The Importance of Food Safety and Traceability

The Turkish food sector carries real weight in the national economy — it accounts for roughly 20% of GDP. In 2026 the sector is expected to move onto a more resilient and sustainable footing. That growth, though, only holds up as long as food safety and traceability standards are actually met.
One of the biggest risks in the food chain is not being able to pin down the source, or the affected batch, fast enough when a product recall becomes necessary. Food crises over the past few years have cost companies millions, and in some cases pushed them all the way to closure.
Turkish food legislation requires businesses to run a traceability system at every stage of production, processing, and distribution. Meeting that obligation without a modern ERP (Enterprise Resource Planning) system gets harder every year — it has stopped being optional.
This article walks through how lot tracking and FEFO management actually get put in place in a food operation, what ERP systems bring to the table, and what Turkish regulation expects of you.

---

2. What is Lot Tracking? Why is it Critical?

2.1 Definition and Basic Concept

Lot (batch) tracking comes down to this: you group together the products made in a given window or under the same conditions, then follow that group every step of the way from the production line to the point of consumption. The whole point is that no lot ever drops out of sight along the chain.
In the food sector, lot tracking exists to:

• Act quickly and accurately during a recall
• Catch the situations that call for precautionary measures
• Keep food safety risks to a minimum
• Report to the regulator (Ministry of Food, Agriculture, and Forestry) without gaps

2.2 The Critical Importance of Lot Tracking

Why lot tracking is critical for the food sector:

---

3. FEFO (First Expired, First Out) Management

3.1 What is FEFO?

FEFO (First Expired, First Out) is simple in principle: whatever is closest to its expiration date ships first. In food, letting a date lapse is both a legal and an ethical problem.
FEFO management matters most when it comes to:

• Perishable products, where it is critical
• Warehouse management, where it clears out inefficiency
• Cutting product loss (spoilage), where its effect is direct

3.2 Reducing Spoilage with FEFO

Spoilage runs about 2-5% of manufacturing cost in the food sector. The main culprits break down like this:

┌─────────────────────────────────────┐
│       SOURCES OF SPOILAGE           │
├─────────────────────────────────────┤
│ • Exceeded expiration date (40%)    │
│ • Inadequate warehouse management (25%)│
│ • Incorrect transportation (15%)    │
│ • Product damage/deterioration (20%)│
└─────────────────────────────────────┘

With FEFO in place:

• Product rotation runs automatically
• Expired stock drops to nearly zero
• Warehouse space efficiency rises by 15-30%
• Spoilage falls by 30-50%

3.3 FEFO Implementation Example

Scenario: 500 tons of milk powder in a warehouse
Without FEFO, LOT-001 may ship while LOT-003 sits idle and expires.

---

4. Turkish Food Legislation Requirements

4.1 Legal Framework

Lot tracking and traceability under Turkish food legislation:
#### 4.1.1 Food Codex Requirements

• Under the Regulation on Food Labeling and Consumer Information, the lot number is mandatory on product labels
• Each product must be documented with the raw materials and suppliers it came from
• Which customers received the product has to be on record

#### 4.1.2 FSMS (Food Safety Management System) Requirements

• The ISO 22000 Standard makes a traceability system mandatory
• It must be integrated with the HACCP (Hazard Analysis and Critical Control Points) system
• Products must be tracked within the framework of GHP (Good Hygiene Practices)

#### 4.1.3 Traceability Test Duration

• Under BRCGS Food and IFS Food standards: traceability must be completed within 4 hours
• Under GFSI-approved standards: testing is mandatory at least once a year
• Test more often if the system changes or a customer asks for it

4.2 Ministry of Agriculture and Forestry Inspection Criteria

What inspectors actually check during a Ministry visit:

• ✓ Ability to fully identify the source of the product (supplier, raw material delivery date)
• ✓ Recording of all parameters in the production process
• ✓ Suitability of warehouse and distribution conditions
• ✓ Completeness and accuracy of expiration date information
• ✓ Complete recording of customer information
• ✓ Integration with the rapid alert system

---

5. Food Traceability Modules with ERP

5.1 Raw Material Lot Tracking

The core of any modern food ERP is supplier-centric lot management.
Functions:

• Automatic recording of the lot number for each raw material received from the supplier
• Keeping expiration date information inside the system
• Storing certificate (hygiene, quality, analysis) information
• Supplier performance analysis
• Automatic supplier alerts

System Flow:

Supplier Delivery
        ↓
Lot Number Scan (QR/Barcode)
        ↓
Preparation Checkpoint
        ↓
Quality Control Tests
        ↓
Expiration Date and Storage Information Entry into ERP
        ↓
Becomes available for Production Planning

5.2 Production Batch Number

This is the unique identifier a manufacturer assigns to its own finished product.
Characteristics of a Production Batch Number:

5.3 Expiration Date (SKT) Management

Expiration-date management is arguably the most financially consequential function a food ERP has.
ERP Expiration Date Functions:

Automatic Expiration Date Calculation

– Raw material expiration date + Shelf life = Finished product expiration date
– Automatic adjustment based on storage conditions

Alerts for Products Approaching Expiration

– 30-day prior alert (discount/promotion)
– 7-day prior alert (urgent shipment)
– 0 days (expiration today) – automatic block

Warehouse Management Optimization

– Automatic application of the FEFO system
– Automatic generation of picking lists
– Maximizing warehouse empty space

5.4 Recall Scenarios

A recall is one of the toughest situations a food business can face, and modern ERP takes the manual grind out of it.
Recall Management Process:

PROBLEM IDENTIFICATION
    ↓
Identify the lot number of the raw material causing the problem
    ↓
Determine which finished product batches this lot entered in the ERP
    ↓
Find out which warehouses and customers have these product batches
    ↓
Send automatic notifications to affected customers
    ↓
Tracking of recalled products and disposal processes
    ↓
Reporting to the Ministry

Example Recall Scenario:
Say an E. coli contamination turns up in LOT-456 of raw material XYZ.
Without a system, these steps routinely stretch past 30 days.

5.5 QR Code / Barcode Integration

Modern food ERP systems tie into QR code and barcode technology built on GS1 standards.
Integration Points:

• Supplier Entry: QR code scan → automatic raw material entry
• Production Line: production batch code printed automatically → all lot information in the barcode
• Warehouse Management: shelf location scanned → FEFO order automatic
• Shipment: final product barcode scanned → documents created automatically
• Customer: the consumer reaches production information by scanning the QR code

In-Software Flow:

QR/Barcode → Scanner → ERP Database → Automatic Processes

---

6. Spoilage Reduction Strategies

For a food business, cutting spoilage feeds straight into the bottom line. The core strategies a food business can lean on:

6.1 Warehouse Management Optimization

Strategies:

6.2 Demand Planning Integration

The ERP’s Demand Forecasting module plays a decisive role in cutting spoilage.

• Analysis of past sales data → automatic discount recommendations for products nearing expiration
• Seasonal trends → avoiding overstock during fruit/vegetable seasons
• Customer order forecasts → optimized in production planning

6.3 Inter-Producer Collaboration

Through B2B portals, modern food ERP systems let you:

• Offer near-expiration products to other manufacturers or distributors
• Automate product swap transactions
• Turn leftover stock into a quick sale

---

7. Audit Preparation and Reporting

7.1 Preparation for Ministry Audits

Food businesses face an audit once or twice per calendar year. An ERP makes those audits far less painful.
Pre-Audit ERP Checklist:

• [ ] Are lot tracking details complete for all raw materials?
• [ ] Are production batch numbers recorded in the system?
• [ ] Are expiration date details accurate and up-to-date?
• [ ] Is the traceability test executable within 4 hours?
• [ ] Can a recall scenario be quickly run in the software?
• [ ] Can audit reports be generated automatically?

7.2 Automatic Reporting

An ERP can generate the following reports on its own:
Routine Reports:

• Daily warehouse inventory (by expiration date order)
• Weekly spoilage report (with causes)
• Monthly traceability test results

Reports for the Ministry:

• Recall incident reports
• Rapid alert system reports
• Production records (batch, expiration date, supplier)

Management Reports:

• Raw material supplier performance
• Warehouse efficiency (rotation speed)
• Spoilage analysis (cause, time, location)

---

8. ERP Selection Criteria for the Food Sector

What a food business should weigh when choosing an ERP:

Comparison Table

Selection Process

REQUIREMENT ANALYSIS
   ├─ Raw material diversity
   ├─ Production structure (batch/continuous)
   ├─ Warehouse size and number of locations
   └─ Customer profile (B2B/B2C)
SOFTWARE EVALUATION
   ├─ Demo/Trial operation
   ├─ Ability to migrate existing data
   └─ Integration capacity
CONSULTING AND IMPLEMENTATION
   ├─ Project planning (6-12 months)
   ├─ Data migration
   ├─ Training program
   └─ Go-live and support
PREVIEW
   ├─ 3rd month check
   ├─ 6th month optimization
   └─ 12th month evaluation

---

9. Frequently Asked Questions (FAQ)

Q1: Is it mandatory for a small food business to purchase an ERP?

Answer: Legally, no — but establishing a traceability system is mandatory. A small business can run one by hand, though going manual means:

• You avoid the ERP cost (~₺100K-500K to start)
• Audit risk climbs by 400%
• Spoilage runs 50%+ higher
• A recall scenario carries the risk of closure

Whatever the size, a compliant system is not optional.

Q2: What is the setup time for a FEFO system?

Answer: For a business that already runs an ERP, the FEFO module typically takes:

• Setup: 4-8 weeks
• Warehouse staff training: 2-4 weeks
• Full optimization: 3-6 months

The hardest part is getting warehouse operations used to the QR/barcode workflow and standardizing how the floor runs.

Q3: Is it really possible to perform a recall scenario in 4 hours?

Answer: Yes, but only if it has been tested in the software beforehand.

• First-time system use: 8-12 hours
• After initial software use: 2-4 hours
• Best practices (automated): 30 minutes

BRCGS and IFS standards have formalized the