Deutsch Deutsch English English

Best Before Dates and Batches

Best-before date and batch management is a central control instrument for quality, food safety, and profitability in fulfillment for food and fresh products. Sloppy work here risks not only write-offs and complaints, but also legal problems and reputational damage. At the same time, robust batch logic ensures that goods receipts and issues remain transparent, First-Expire-First-Out works reliably, and affected stock can be quickly isolated in an emergency.

This guide shows in practical terms how best-before dates and batches are structured in day-to-day operations: from data capture in goods receipt through storage zones and picking rules to traceability and KPI management.

Why Best Before Dates and Batches Are Critical in Fulfillment

For food items, not only stock levels but above all remaining shelf life determines whether an item is sellable. Without batch reference, this information is hardly usable in a reliable way in warehouse operations.

Typical Risks Without Structured Batch Management

  • Incorrectly picked goods with too short remaining shelf life
  • Mixing of different batches without documentation
  • Incomplete traceability for complaints
  • Increased write-offs due to overstocking
  • High manual effort for blocks and recalls

Basics: Best Before Date, Batch, and Remaining Shelf Life

Understanding Best Before Dates Correctly

The best-before date is not a blanket disposal date, but a quality promise from the manufacturer when stored correctly. In the fulfillment context, it becomes an operational control value: not just "still fit for consumption," but "still suitable for the sales channel and delivery route."

Batch as a Traceability Anchor

A batch groups production quantities with shared characteristics (e.g., production period, raw material batch, line). For fulfillment, this means:

  1. Every warehouse-relevant unit must be assignable to a batch.
  2. Every outbound movement must be documented at batch level.
  3. Traceability must be possible in both directions (from goods receipt to customer delivery and vice versa).

Remaining Shelf Life as a Control Metric

A date alone is not sufficient for operations. What matters is the remaining shelf life in days at the time of goods receipt, picking, and shipping.

Best Before Date Control in Day-to-Day Operations

Six steps from goods receipt to KPI monitoring – critical checkpoints in steps 2 and 5:

1
Record goods receipt
2
Validate best before date and batch – Checkpoint
3
Assign storage zone
4
Control FEFO picking
5
Release for shipping based on remaining shelf life – Checkpoint
6
KPI monitoring and follow-up control

Operational Process Chain for Best Before Dates and Batches

1) Goods Receipt With Mandatory Inspection

Quality and data inspection must be mandatory in goods receipt. A traffic-light model is useful:

  • Green: Remaining shelf life above target value
  • Yellow: Borderline range, only for defined channels
  • Red: Blocked stock or clarification case

Goods Receipt Checklist (Mandatory):

  • Capture item, batch, and best before date per delivery line
  • Automatically calculate remaining shelf life in days
  • Document temperature record for chilled items
  • Link deviations with photo and delivery note
  • Set block status immediately at threshold values

2) Storage According to FEFO Logic

FEFO (First Expire, First Out) should be standard for best-before-date-managed items. This prioritizes the shortest remaining shelf life, not the oldest inbound date.

Especially important:

  • Physical separation of batches in clearly defined storage locations
  • Visible labeling at location and handling level
  • Block and quarantine areas for disputed goods

3) Picking With Remaining Shelf Life Rules

Picking logic should be channel-dependent. Example: B2B wholesale customers require longer remaining shelf life than B2C promotional goods.

Sales Channel
Recommended Minimum Remaining Shelf Life at Shipping
Practical Note
B2C Standard Shop
At least 30 days
Suitable for fast-moving assortments with clear consumer communication
B2B Retail
At least 60 to 120 days
Depending on contract, shelf placement, and promotional windows
Marketplace Promotions
At least 21 to 45 days
Only with explicit approval and increased returns monitoring
Donation or Clearance Channel
Below standard threshold, but legally safe
Documentation requirement and clear separation from regular sales

4) Shipping and Documentation

Every outbound movement should allow the shipped batch to be stored in the order. This significantly speeds up complaint handling and recall processes.

Recommended minimum data in the shipping record:

  1. Order number
  2. SKU
  3. Shipped quantity
  4. Batch
  5. Best before date of the shipped unit
  6. Shipping date and carrier

Traceability and Crisis Resilience

In an emergency, time counts. A robust batch system reduces the search space from "all deliveries of an item" to "all deliveries of a batch in period X."

Scenario
Without Clean Batch Management
With Clean Batch Management
Product complaint due to taste
Broad manual analysis, many open cases
Targeted inspection of affected batch, rapid isolation
Supplier deviation in goods receipt
Vague evidence, time-consuming clarification
Reliable documentation per batch and goods receipt
Recall action
Possible over-blocking of large stock quantities
Precise blocking and customer notification per batch

Batch Recall: Process Flow

Five steps from notification to completion documentation – steps 3 and 4 are particularly critical:

1
Notification received
2
Identify batch
3
Block stock – Critical
4
Generate affected shipments and customer lists – Critical
5
Communication and completion documentation

Typical Errors and How to Avoid Them

Error 1: Best Before Date Only at Item Level Instead of Batch Level

If the system only tracks a blanket shelf life per SKU, incorrect outbound movements occur. Solution: always track best before dates per batch and stock unit.

Error 2: No Channel-Specific Remaining Shelf Life Thresholds

Uniform thresholds for all channels lead to conflicts with B2B customers or marketplace requirements. Solution: define rule sets per channel and customer group.

Error 3: Manual Lists Instead of Systematic Block Logic

Excel or paper solutions are error-prone. Solution: block indicators directly in the operational system and mandatory checks during picking.

Error 4: Lack of Training in the Warehouse Team

Even good processes fail without a shared understanding. Solution: clear work instructions with regular short training sessions.

Maturity Level of Best Before Date and Batch Management

  • Batch and best before date are always captured in goods receipt
  • FEFO is active in the system
  • Remaining shelf life limits are defined per sales channel
  • Blocked stock is logically and physically separated
  • Shipping booking stores batch and best before date
  • Traceability in both directions is possible in under 30 minutes
  • KPI reporting on write-offs and best-before-date losses is established
  • Team training and audit routine run regularly

KPI Set for Best Before Date and Batch Control

Measurable metrics help permanently secure operational quality:

  • Share of outbound lines with remaining shelf life below target value
  • Write-off rate due to best-before-date expiry
  • Number of block cases per 1,000 goods receipts
  • Processing time for batch research in complaints
  • FEFO compliance rate in picking

Target Values in the Monthly Report

FEFO Compliance

> 98 percent

Write-off Rate

< 1.5 percent

Batch Research

< 30 minutes

Block Errors

= 0

Complaint Rate With Batch Reference

< 0.3 percent

Implementation in 30 Days: A Pragmatic Roadmap

Week 1: Define Data Standard

  1. Define mandatory fields for goods receipt
  2. Classify item groups with best-before-date relevance
  3. Document remaining shelf life limits per channel

Week 2: Adjust Process and Warehouse Layout

  1. Anchor FEFO rules in operations
  2. Clearly mark block and quarantine areas
  3. Tighten pick and shipping checks on remaining shelf life

Week 3: Team and Monitoring

  1. Train warehouse team on new rules
  2. Practice standard workflows for deviations
  3. Start KPI reporting on a weekly cycle

Week 4: Stress Test and Fine-Tuning

  1. Simulate test recall with a sample batch
  2. Measure lead times and correct bottlenecks
  3. Finalize documentation and fix responsibilities

Introducing Best Before Date and Batch Process

Four milestones from data standardization to stabilization:

Week 1
Data Standard – Mandatory fields and channel limits defined
Week 2
Process Restructuring – FEFO, block areas, and pick rules live
Week 3
Team and KPIs – Training and weekly reporting established
Week 4
Recall Simulation and Stabilization – Stress test and fine-tuning completed

Conclusion

Best-before date and batch management is not an isolated compliance topic, but a central lever for stable food fulfillment processes. Those who think of remaining shelf life, FEFO, block logic, and traceability as an interconnected system reduce losses, increase delivery quality, and remain capable of action in critical situations. The most important success factor is the combination of clean data capture, clear process rules, and consistent operational discipline.

Related Topics

Last updated: July 7, 2026

Frequently Asked Questions about Best Before Dates and Batches in Fulfillment

Question
Answer
Why are best-before dates and batches critical in food fulfillment?
For food and fresh products, sellability depends less on stock quantity alone and more on remaining shelf life. Without a batch reference, that information cannot be used reliably in warehouse operations. Weak batch logic increases write-offs, complaints, legal risk, and reputational damage, while robust processes keep goods receipt and outbound transparent, make First-Expire-First-Out workable, and allow affected stock to be isolated quickly in an emergency.
Is the best-before date the same as a disposal date?
No. The best-before date is a quality promise from the manufacturer when goods are stored correctly, not a blanket disposal date. In fulfillment it becomes an operational control value: the question is not only whether the product is still fit for consumption, but whether it is still suitable for the intended sales channel and delivery route. What matters day to day is remaining shelf life in days at goods receipt, picking, and shipping.
What does FEFO mean and how does it differ from FIFO?
FEFO stands for First Expire, First Out and should be the standard for best-before-date-managed items. It prioritizes the shortest remaining shelf life rather than the oldest inbound date. To make FEFO work in practice, batches must be physically separated in clearly defined storage locations, labeled visibly at location and handling level, and supported by block and quarantine areas for disputed goods.
How should remaining shelf life thresholds differ by sales channel?
Picking rules should be channel-dependent because customers have different shelf-life expectations. For a B2C standard shop, at least about 30 days remaining shelf life at shipping is a practical guide for fast-moving assortments. B2B retail often needs 60 to 120 days depending on contract, shelf placement, and promotional windows. Marketplace promotions may use 21 to 45 days only with explicit approval and stronger returns monitoring, while donation or clearance channels can go below the standard threshold if they remain legally safe and clearly documented separately from regular sales.
What must be checked and captured at goods receipt?
Quality and data inspection at goods receipt must be mandatory. A traffic-light model helps: green when remaining shelf life is above the target, yellow for borderline stock limited to defined channels, and red for blocked stock or clarification cases. The mandatory checklist includes capturing item, batch, and best-before date per delivery line, calculating remaining shelf life in days automatically, documenting temperature records for chilled items, linking deviations with photo and delivery note, and setting a block status immediately when thresholds are breached.
How does clean batch management improve recalls and complaint handling?
In an emergency, time counts. A robust batch system narrows the search from all deliveries of an item to all deliveries of a specific batch in a defined period. That enables targeted inspection and rapid isolation for taste complaints, reliable documentation for supplier deviations, and precise blocking plus customer notification in a recall instead of over-blocking large stock quantities. The recall flow runs from notification and batch identification through stock blocking and generation of affected shipment and customer lists to communication and completion documentation, with stock blocking and customer-list generation as the most critical steps.
Which KPIs and target values should control best-before date and batch quality?
Useful metrics include the share of outbound lines below target remaining shelf life, write-off rate due to best-before-date expiry, block cases per 1,000 goods receipts, processing time for batch research in complaints, and FEFO compliance in picking. Monthly targets cited in the guide are FEFO compliance above 98 percent, write-off rate below 1.5 percent, batch research under 30 minutes, zero block errors, and a complaint rate with batch reference below 0.3 percent. A mature setup also captures batch and best-before date at every goods receipt, stores them in the shipping booking, and keeps bidirectional traceability possible in under 30 minutes.