FIFO Inventory Management System 2026: Thailand Guide

A FIFO inventory management system is more than placing older stock at the front of a rack. It is an operating foundation that records item, lot, expiry, location and quantity consistently at receipt, storage, issue, return, transfer and count, then tells the operator which stock to take next. This guide turns FIFO and FEFO into practical WMS and production-management requirements for factories and warehouses in Thailand.

Conclusion first: FIFO must connect inventory events, not merely sort receipt dates

FIFO, or First In, First Out, normally issues the stock received first. FEFO, or First Expiry, First Out, issues the stock that expires first. If a newly received lot expires before stock already on hand, their issue sequences differ. FEFO may therefore be appropriate for food, pharmaceuticals, medical products, adhesives, coatings and other expiry-controlled materials.

The system should do five things:

1. Define FIFO, FEFO, specific-lot and blocked-issue rules by item.
2. Capture lot, expiry, location and stock status at receipt, not only receipt time.
3. Present the recommended issue stock and record a reason and approval for an alternative lot.
4. Record transfer, split, merge, return, hold and count discrepancy as immediate inventory events.
5. Design physical issue rotation separately from financial inventory valuation.

FIFO performance depends on knowing when, where and how much of each lot moved. Paper or spreadsheets may work in a small operation, but multiple warehouses, shifts, outside storage and returns quickly create delayed records and unmanaged exceptions.

FIFO versus FEFO: do not issue expiry-controlled stock by receipt sequence alone

The WHO warehouse manual applies FEFO to items with an expiry date and FIFO to items without one. It also warns that newly received supplies may expire before older receipts. WHO TRS 1025 Annex 7, published on 17 June 2020 and still listed in WHO’s current distribution-guideline index when checked on 28 August 2026, calls for appropriate stock rotation and FEFO for medical products. We use it as an international operating reference, not as a substitute for Thai law.

An “FIFO item” checkbox is not enough. Define whether an expiry exists, its precision, whether it may be calculated from production date, the customer’s minimum remaining shelf life, opened-container life, retest date and quality status. Artificial dates for non-expiring stock obscure meaning; receipt-only sorting for expiry stock strands short-dated lots.

Physical FIFO and financial FIFO are different requirements

Warehouse picking and accounting valuation must be designed separately. A WMS may recommend the oldest receipt while the ERP values inventory at moving average or standard cost. Conversely, an ERP FIFO costing model does not automatically prevent an operator from issuing another physical lot.

The current Microsoft Dynamics 365 inventory costing FAQ describes FIFO as a periodic costing model involving inventory close and settlement. An RFP should therefore test physical allocation, pick instruction, actual lot, financial valuation and period close separately instead of accepting a generic “supports FIFO” statement.

Twelve illustrative data fields for a FIFO inventory management system

Current quantity is insufficient; the decision needs event history. The GS1 Global Traceability Standard, checked as current on 28 August 2026, identifies event time and time zone, instance or batch/lot identifier, location, business step and disposition, and where appropriate the responsible party as core traceability data.

The following 12 fields are an implementation example for making an RFP and acceptance test concrete. They are not a universal GS1 or Thai-law minimum; add or remove fields for the products, customer rules and current systems, then link the selected fields to each inventory event.

Define what “receipt time” means: truck arrival, unloading, inspection start, quality release and inventory posting are distinct events. Some items use physical receipt as the FIFO key; others may use release time. Without a policy, interface timing or operator habits change the pick order.

Warehouse location management: manage stock that can actually be picked

In warehouse location management, physical presence and pick eligibility are different. Receiving, inspection, hold, regular storage, forward pick, returns and disposal areas may contain the same item and lot with different status. If they are simply aggregated, an inspection lot may be recommended or the system may point to an inaccessible pallet.

The location master should cover warehouse, zone, aisle, level, bin, storage condition, capacity, pick sequence, mixing permission and fixed versus dynamic use. Excessive detail, however, encourages unrecorded moves. A handheld workflow that scans “from location → inventory ID → to location” should complete a transfer in seconds.

A practical allocation sequence is:

1. Include only stock in an available status.
2. Filter by customer, production order, quality and storage constraints.
3. Sort FEFO items by expiry and FIFO items by receipt sequence.
4. Break ties by pick path, opened stock, partial quantity or handling efficiency.
5. Block or require approval for stock below the minimum remaining shelf life.

Oracle WMS Cloud 26A documentation explicitly distinguishes FIFO by inventory or LPN creation timestamp from FEFO by Priority Date. Regardless of product choice, it is a useful example of specifying the priority key and tie-break rules.

Real-time inventory management requires event-time confirmation

Real-time inventory management is not merely a self-refreshing screen. The critical measure is the delay between physical movement and system confirmation. If operators post work later in the office, the next allocation uses stale stock. Receipt, put-away, replenishment, issue, production consumption and return should be confirmed at their work points.

Offline design matters. If devices can operate without a network, retain device event time, replay sequence, an idempotency ID and a conflict queue. When two operators might take the same unit, combine allocation, work reservation and scan-time validation. “100 on hand” does not mean 100 available if 90 is already reserved.

One illustrative workflow uses five operational states: created, reserved, in progress, confirmed and cancelled. This is not a universal standard; combine or add states to fit the process. Decide whether provisional work affects available stock or only confirmed work does. Define the responsibility handoff, such as material consumption at physical use and shipment at loading or dispatch confirmation.

Handheld devices should add evidence without adding typing

Express the work through scan order, not manual data entry. For issue, validate “instruction → location → inventory ID → quantity.” If an operator scans a non-recommended lot, show the reason, a safe alternative and the approval route. A hard stop without an exception path often drives urgent work outside the system.

See our handheld terminal implementation guide for Thailand factories for device rollout. Test concise Thai or agreed-language screens, gloves, lighting, label quality, wireless dead spots, charging and spare units.

Standard FIFO/FEFO flow from receiving to issue

1. Match expected receipt with physical goods

Compare the purchase order, ASN or delivery note with physical item, quantity, supplier lot, manufacture date and expiry. When Buddhist Era labels, Gregorian dates or different day-month formats may appear, separate the input and display formats. Never assign an unknown expiry a convenient distant date; quarantine it as “expiry unverified.”

The WHO FEFO standard operating procedure recommends capturing batch/lot number, expiry and shelf/rack location at receipt. Although written for medical supply chains, it is useful for identifying receiving requirements for expiry-controlled goods.

2. Apply quality status before put-away

Decide by item whether stock becomes available at receipt or only after inspection. Inspection stock may be visible but must remain outside the pick candidates. At release, record a status-change event and decide whether the original receipt or release time remains the FIFO key.

3. Record replenishment and movement

Keep the inventory ID when moving reserve stock to the forward pick face. When splitting into smaller containers, record parent ID, child IDs and quantities. Limit mixed-lot containers because they weaken traceability.

4. Separate allocation from actual issue

The system recommends stock according to policy; an operator scan confirms the actual lot. Retaining the planned-versus-actual difference reveals whether location, labels, holds or instructions caused the deviation. Customer lot, trial material and equipment compatibility are legitimate exceptions when controlled by reason codes.

5. Return residual material to its history

Registering unused production material or cancelled shipment stock as a new receipt destroys its sequence. Verify the original lot, expiry, opened status, storage excursion and remaining quantity. Reuse only after status review. If the original ID cannot be retained, issue a child ID and keep the relationship.

Inventory discrepancy causes and countermeasures: do not close with a quantity adjustment

For inventory discrepancy causes and countermeasures, identify the missing event before changing the balance. Frequent adjustments may align total quantity while leaving FIFO receipt order, lot, expiry and location history unreliable.

Cycle counting need not close the whole warehouse. Select high-velocity, high-discrepancy, near-expiry items and empty locations according to risk. Design blind counts, recount approval and transaction control before final adjustment. Oracle’s current Cycle Count documentation also covers location-based inventory counting.

Do not rely on one discrepancy rate. Track non-recommended pick rate, missing expiry, ageing hold stock, incomplete transfers, recounts and short-dated disposal by cause. This article intentionally claims no universal improvement percentage. Measure results with the same definition and comparable scope before and after rollout.

Exception management: expose FIFO deviations without stopping the factory

Absolute enforcement can stop work when stock is held, customer-designated, inaccessible or needed to recover a line. Unlimited warning overrides make the rule meaningless. In this design example, classify each exception as prohibited, supervisor approval, reason required or automatically allowed, then adjust the four levels to the quality rules and authority model.

For example, unavailable status may be prohibited; shipment below remaining-life requirements may need quality approval; another location within the same expiry may need a reason; and another container in the same lot may be automatically allowed. Assign approvers by role with delegation and after-the-fact review for emergencies.

The dashboard should show recommended stock, actual stock, reason, approver and process. Repeated exceptions may indicate poor location design, late replenishment, a master-data error, customer constraints or slow system response—not simply operator misconduct.

Responsibilities across WMS, production management and ERP

WMS typically manages locations, inventory units, allocation, picking, movement and cycle count. Production management or MES links production orders, work-in-process, consumption, output and production lots. ERP often owns purchasing, sales, finance, enterprise item data and valuation, but actual ownership must fit the existing architecture.

Interfaces should include item, UOM, warehouse, lot, expiry, stock status, document and cancellation. Daily stock synchronization cannot support real-time allocation; specify which events are immediate and which are aggregated. Put duplicates, out-of-order events, network failures and unknown master values into a visible exception queue rather than discarding them.

Budget for labels, handhelds, wireless coverage, printers, master-data preparation, integration, training and local support—not only licenses. Our WMS cost guide for Thailand factories provides a procurement framework.

RFP and acceptance-test checklist

A product demo usually proves normal receipt and issue; real operations fail at exceptions. Specify data, rules, actions, evidence and recovery rather than a feature name.

Master data and policy

• Configure FIFO, FEFO or specific-lot rules by item.
• Explain the receipt-sequence key and tie-break policy.
• Combine expiry, minimum remaining life, quality status and customer conditions.
• Retain split, merge, repack and UOM-conversion history.
• Preserve request, approval, effective date and history for master changes.

Shop-floor operation

• Present concise instructions in Thai or the agreed operating language.
• Handle unreadable barcodes, quantity differences, alternative lots and offline work.
• Prevent duplicate posting through pause, cancel and resume.
• Transfer unfinished work safely when replacing a device.
• Control exception approval and adjustment by role.

Audit and recovery

• Search before/after values, operator, time, device and reason.
• Navigate from balance to event history and original document.
• Detect ERP integration failures and replay without duplication.
• Reconcile stock and pending events after backup restoration.
• Export definitions and code values with the data.

Illustrative acceptance set: ten scenarios

These ten scenarios are not a universal certification checklist. Add or change them for the approved scope and risks.

1. Create an older and a newer receipt and verify the FIFO candidate.
2. Give the later receipt an earlier expiry and verify the FEFO candidate.
3. Hold the top-priority lot and verify selection of the next eligible lot.
4. Exclude stock that fails a customer’s minimum remaining shelf life.
5. Split a pallet and reconcile parent-child quantities and expiry.
6. Scan a non-recommended lot and record warning, reason and approval.
7. Work offline and verify replay order and deduplication after reconnecting.
8. Link a return to its source lot and reuse only after status review.
9. Recount a discrepancy and verify history before and after adjustment.
10. Force one ERP interface failure and verify that replay does not double stock.

Use non-confidential test data that includes Thai and English names, similar item codes, different UOMs, month-end, year-end, equal timestamps and non-expiring items. Acceptance should reconcile screen, event history, API, report and on-hand balance.

A phased 90-day implementation example

Ninety days is an illustrative implementation window, not a legal period or universal standard. Phase 1 defines master data and current flow for one warehouse and item family. Phase 2 tests handhelds, labels, allocation, exceptions and integration. Phase 3 runs night shift, offline, count, recovery and month-end reconciliation before a production decision.

Start with expiry-controlled, lot-tracked or high-velocity items rather than every SKU. Include returns, holds, splits, UOM conversion and emergency issue so the pilot is not limited to an easy normal flow.

FAQ

What does a FIFO inventory management system manage?

It manages item, lot, expiry, quantity, location and status plus receipt, transfer, issue, return and adjustment history. It recommends stock under policy and records why and by whom another lot was approved.

Should we choose FIFO or FEFO?

FIFO is a common starting point for non-expiring items. FEFO may suit food, medicines and other expiry-controlled materials. Decide from product quality, customer remaining-life conditions, storage, contracts and applicable local requirements. Do not configure the terms as synonyms.

Fixed or dynamic warehouse locations—which is better?

Neither is universally better. Fixed bins are easy to find but can waste space; dynamic locations are flexible but depend on scan discipline. Many sites combine fixed forward-pick faces with dynamic reserve storage.

Does real-time inventory require permanent connectivity?

Continuous connectivity is desirable, but outages remain possible. Offline operation needs event IDs, event time, replay order, conflict detection, deduplication and reconciliation. Screen refresh speed alone does not prove real-time control.

Where should inventory discrepancy analysis begin?

Before adjusting quantity, find the last reliable event and the missing transfer, issue, return or adjustment. Separate quantity, lot, expiry and location differences, then record cause, action, owner and due date.

Does installing WMS automatically enforce FIFO?

No. Master data, labels, rack layout, scanning, exception approval, training and ERP/production integration must work together. Acceptance testing should include real exceptions, not only the product demo’s normal flow.

Summary

Reliable stock rotation distinguishes FIFO from FEFO by item, captures receipt, expiry, lot, location and status at receiving, and confirms movement and issue where work occurs. Physical picking and financial costing are separate. A suitable system exposes alternative picks, returns, holds, offline events and count discrepancies, and it proves integration and recovery through scenarios—not a checkbox labelled “FIFO.”

If you are defining FIFO/FEFO, warehouse locations, handheld workflows or ERP and production-management integration for a Thailand factory, you can contact TOMAS TECH even before the requirements are final. We can review the current flow and identify a practical starting scope.

References

• WHO TRS 1025 Annex 7 (published 17 June 2020; current WHO distribution index checked 28 August 2026)
• WHO Guidelines: Distribution (current index checked 28 August 2026)
• WHO eManual: Warehouse and Stock Management (checked 28 August 2026)
• WHO FEFO standard operating procedure (checked 28 August 2026)
• GS1 Global Traceability Standard (current-standard page checked 28 August 2026)
• Oracle WMS Cloud 26A: Allocation Method (checked 28 August 2026)
• Oracle WMS Cloud 25D: Expiration Dates (checked 28 August 2026)
• Microsoft Learn: Inventory costing FAQ (checked 28 August 2026)