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 is critical to the national economy, accounting for approximately 20% of GDP. In 2026, the sector is expected to move towards a more resilient and sustainable direction. However, this growth can only be achieved by adhering to food safety and traceability standards.
One of the biggest risks in the food chain is the inability to precisely identify the source or quickly determine the affected product batch during product recall scenarios. Food crises in recent years have caused companies to suffer millions of dollars in losses, and even led to their closure.
Under Turkish food legislation, food businesses are mandated to establish a traceability system at every stage of production, processing, and distribution. To fulfill this obligation, modern ERP (Enterprise Resource Planning) solutions are no longer an option but a necessity.
In this article, we will examine in detail how to successfully implement lot tracking and FEFO management in the food sector, the capabilities offered by ERP systems, and Turkish regulatory requirements.

---

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

2.1 Definition and Basic Concept

Lot (Batch) Tracking is the process of identifying and continuously monitoring a group of products manufactured within a specific period or under specific conditions during the food production process. Each lot must be traceable and trackable at every stage from production to the point of consumption.
The primary goal of lot tracking in the food sector is to:

• Act quickly and accurately during recall operations
• Identify situations requiring voluntary measures
• Minimize risks to food safety
• Submit reports to regulatory authorities (Ministry of Food, Agriculture, and Forestry)

2.2 The Critical Importance of Lot Tracking

Reasons 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 the principle of shipping products with the nearest expiration date first. In the food sector, exceeding the expiration date is both a legal and ethical issue.
FEFO management is particularly critical for:

• Perishable products
• Warehouse management to eliminate inefficiencies
• Directly effective in reducing product loss (spoilage)

3.2 Reducing Spoilage with FEFO

Product loss (spoilage) in the food sector accounts for 2-5% of manufacturing costs. The main causes of these losses are:

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

With the FEFO system:

• Automatic product rotation is ensured
• Exceeding expiration dates is virtually eliminated
• Warehouse space efficiency increases by 15-30%
• Spoilage rate decreases by 30-50%

3.3 FEFO Implementation Example

Scenario: 500 tons of milk powder in a warehouse
Without a FEFO system, LOT-001 might be shipped, while LOT-003 remains idle and expires.

---

4. Turkish Food Legislation Requirements

4.1 Legal Framework

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

• According to 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
• It must be recorded which customers received the product

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

• A traceability system is mandatory according to the ISO 22000 Standard
• 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

• According to BRCGS Food and IFS Food standards: Traceability must be completed within 4 hours
• According to GFSI-approved standards: Testing is mandatory at least once a year
• Testing should be more frequent if there is a system change or upon customer request

4.2 Ministry of Agriculture and Forestry Inspection Criteria

Points checked during Ministry inspections:

• ✓ 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 module of modern food ERP systems is supplier-centric lot management.
Functions:

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

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 identification number assigned by the food manufacturer to its own product.
Characteristics of a Production Batch Number:

5.3 Expiration Date (SKT) Management

Expiration date management is the most crucial financial function of a food ERP.
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 operation is one of the most serious situations that can occur in the food sector. Modern ERP automates this process.
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:
An E. Coli contamination was detected in LOT-456 of XYZ raw material.
Without a system, these processes can typically take 30+ days.

5.5 QR Code / Barcode Integration

Modern food ERP systems work in integration with QR code and barcode technologies compliant with GS1 standards.
Integration Points:

• Supplier Entry: QR code scan → Automatic raw material entry
• Production Line: Production batch code automatic printing → All lot information in barcode
• Warehouse Management: Shelf location scanned → FEFO order automatic
• Shipment: Final product barcode scanned → Automatic document creation
• Customer: Consumer accesses production information by scanning QR code

In-Software Flow:

QR/Barcode → Scanner → ERP Database → Automatic Processes

---

6. Spoilage Reduction Strategies

Reducing spoilage is a matter that directly translates to increased profit for food businesses. Key spoilage reduction strategies for a food business include:

6.1 Warehouse Management Optimization

Strategies:

6.2 Demand Planning Integration

The ERP’s Demand Forecasting module plays a critical role in reducing spoilage.

• Analysis of past sales data → Automatic discount recommendations for products nearing expiration
• Seasonal trends → Avoiding overstocking during fruit/vegetable seasons
• Customer order forecasts → Optimized in production planning

6.3 Inter-Producer Collaboration

Modern food ERP systems, through B2B portals:

• Offer near-expiration products to other manufacturers or distributors
• Automate product swap transactions
• Facilitate the quick sale of found products

---

7. Audit Preparation and Reporting

7.1 Preparation for Ministry Audits

Food businesses undergo audits 1-2 times per calendar year. An ERP system simplifies these audits.
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

ERP systems can automatically generate the following reports:
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

Criteria food businesses should consider when selecting 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: It is not mandatory from a legal perspective, but establishing a traceability system is mandatory. Small businesses can set up manual systems, but:

• ERP costs (~₺100K-500K initial) decrease
• Audit risk increases by 400%
• Spoilage is 50%+ higher
• Risk of closure arises in recall scenarios

Regardless of size, they must establish systems for regulatory compliance.

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

Answer: For a business with an ERP already in place, the FEFO module:

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

The most critical part is for warehouse operations to adapt to the QR/barcode system and for operations to be standardized.

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

Answer: Yes, but it must have 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