Case study
Food distributor ERP: FEFO expiry control and cold-chain traceability
A food and beverage distributor deployed ERPNext with FEFO expiry controls and lot-level cold-chain traceability, ending near-expiry write-offs after go-live.
Results
- 28%Reduction in Inventory Write-offsTo confirm · Internal measure
- 100%Lot Traceability from Supplier to CustomerTo confirm · Internal measure
- 30 minFood Safety Audit Prep (was 2 days)To confirm · Internal measure
- 0Near-expiry Write-offs in Month 1 Post Go-liveTo confirm · Internal measure
Near-expiry stock discovered at month-end. Too late to move. Half written off.
Every product had a shelf life. Most had strict cold-chain documentation requirements from their supplier contracts. Several were subject to food safety regulations requiring traceability from supplier batch to end customer delivery.
Expiry dates were recorded on paper lot cards when goods arrived in the warehouse. Picking was done by warehouse staff based on physical proximity to the picking area, not by expiry date. FEFO (First Expiry, First Out) was a policy on paper but not enforced in any system. No one knew which batches were approaching expiry until a physical count was done at month-end.
Near-expiry goods were regularly discovered during monthly counts too late to redistribute or discount effectively. Between 4 and 6 pallets were written off every month. In one quarter, a supplier issued a recall and the team spent three days manually tracing which customers had received the affected batch.
Food safety audits required the compliance team to manually compile chain-of-custody documentation from paper lot cards, delivery notes, and supplier certificates. A single audit preparation took two full working days. The business was growing its institutional food service accounts, which had stricter traceability requirements than existing customers. The current system could not scale to meet them.
What Was Causing Losses and Risk
- FEFO not enforced at the system level pickers chose stock by proximity rather than expiry date, consistently shipping newer goods first and leaving older stock to expire
- No near-expiry alerts approaching expiry dates were invisible until the monthly physical count, by which point clearance was often impossible
- Lot traceability existed only on paper, requiring 3-day manual cross-referencing to respond to a supplier recall or customer complaint
- No supplier lot documentation linked to outbound deliveries, so chain-of-custody for institutional clients had to be reconstructed manually
- Chilled and frozen stock handled the same way as ambient no temperature zone separation in the stock records or picking logic
FEFO-Driven Picking with Full Lot Traceability
- Batch & Expiry Management (FEFO). System-enforced FEFO picking across all product categories, with automatic near-expiry alerts at 30, 14, and 7 days before expiry
- Lot Traceability End-to-End. Full supplier lot linked to every customer delivery — one-click traceability report from receipt to dispatch, covering every movement in between
- Stock & Warehouse Management. Temperature zone separation (ambient, chilled, frozen) with zone-specific putaway rules and picking sequences built into the warehouse layout
- Purchase & Supplier Management. Supplier certificates and lot documentation captured at goods receipt, linked to batch records and available for audit in one click
- Quality & Compliance Reporting. Food safety audit reports generated directly from ERPNext in under 30 minutes, replacing two days of manual document preparation
How it was delivered
- Full Physical Count & Batch Data Capture (Weeks 1–2). A full physical count was conducted across all stock, capturing lot numbers and expiry dates for every item in the warehouse. This created the clean opening batch data that FEFO enforcement depended on.
- ERPNext Configuration & Warehouse Zoning (Weeks 3–6). Warehouse zones were configured in ERPNext for ambient, chilled, and frozen categories. FEFO picking rules, near-expiry alert thresholds, and supplier lot capture templates were set up and validated with the warehouse manager.
- Warehouse Team Training & FEFO Drill (Weeks 7–8). All warehouse staff trained on FEFO picking procedures, lot receipt entry, and the near-expiry alert dashboard. A two-day live-order drill confirmed the team could execute FEFO correctly under real picking pressure before go-live.
- Full Go-live & Hyper-care (Weeks 9–10). ERPNext went live as the sole system of record. Paper lot cards were retired. All new receipts entered the FEFO queue automatically. A 30-day hyper-care period followed, with daily check-ins for the first two weeks to catch any edge cases in the FEFO logic.
Related service
ERPNextRelated
Related case studies and services
More case studies, and the case studies hub.
- ResourceCase studiesCase studies of ERP, AI and custom software projects delivered by TCB Infotech: the problem…
- Case studyImport-export trading ERPHow a regional import-export trading company replaced 14 spreadsheets with ERPNext in 10 weeks…
- Case studyAI Finance AgentA finance AI agent reads supplier invoices, matches them to orders and prepares entries for approval…
- Case studyElectronics Wholesale PortalAn electronics wholesale business launched a B2B customer portal on Odoo…
- Case studyERPNext Distribution Case StudyA regional distributor ran four branches on one ERPNext stock and sales system…
- Case studyFMCG Wholesale DistributorAn FMCG distributor connected three warehouses and six sales channels on Odoo…
- Case studyLead-Gen ChatbotA lead-generation chatbot qualified visitors, captured details into the CRM and booked demos after hours…
- Case studySupport ChatbotA support AI chatbot grounded in the help centre and orders now answers about 70% of routine questions instantly…
- Case studyAuto Parts Order CyclesAn automotive parts manufacturer connected sales…
- Case studyB2B Ordering AppA self-service B2B ordering web app let trade customers of a distributor order online around the clock…
- Case studyContractor Project CostingA building contractor put BOQ, procurement, billing and cost on one ERPNext system across eight projects…
- Case studyInfrastructure ProjectsAn infrastructure EPC firm ran packages, subcontractors and multi-stage billing on SAP S/4HANA…