Why does the nearest pallet always ship? FIFO needs hard blocks, not wall posters

The forklift driver chose 'the visible pallet'.

When a rush order is sent to the PDA, the system recommends the earliest batch in the back; but at the passageway, new racks that were just shelved are piled up. The driver scanned the code nearby, the system beeped and let it go again—because the strategy stops at 'recommend' and doesn’t block it. The FIFO poster on the wall is still there, and the outbound ledger records 'what was actually shipped,' not 'what should have been shipped.'

The reasons for changing rules on-site are always sufficient: the route is short, it's easy to handle, the customer is pressing, the forklift is busy. When there is no enforcement, all these reasons are valid. The goal of governance is not to eliminate exceptions, but to make exceptions costly, auditable, and controllable; to make the correct batch the option with the least resistance on the default path.

The fields are there, but control is not necessarily there.

Many warehouses have already 'been added to the batch list': receiving can be empty, picking can be changed, and checking only involves counting—having the field does not mean the control exists. True compliance is judged by the number of interceptions and the closure of exceptions, not by whether there is a batch number in the master data.

Level 3 force, don’t lock everything right away

FEFO and FIFO distribution: Items with an expiration date/reinspection period follow FEFO; items without a valid period but requiring batch order follow FIFO. For serial number materials, the batch to which the SN belongs should also be verified during outbound, to avoid 'correct batch but mixed-up serial numbers.' Treating 'can deliberate wrong batch scanning be blocked' as a spot check question is more effective than watching a demonstration video.

Minimum fields of the exception form

An exception without a field is equivalent to having no system:

• Applicant and Authorizer (Separation of Duties)
• Reason codes (urgent orders, re-ship damaged items, inventory discrepancies, customer-specified batches, etc.)
• Associate outbound order or work order
• Post-review deadline and reviewer
• Additional confirmation of expiration risk (if applicable)

Exception rates should be discussed in the warehouse management weekly meeting: a continuous increase indicates that the enforcement level does not match the storage location/replenishment design, rather than a simple 'workers are not cooperating' explanation. Granting all staff exception privileges, aligning system batches by 'picking first then correcting', and disabling validations to 'maintain efficiency' — all of these will make the execution rate report misleading.

Inventory Management and Prohibition of Mixed Batches: Prerequisites for Enforcement

No matter how correct the allocation algorithm is, if the earliest batch is buried deep and the picking location only has new batches, the site will continue to request exceptions. Shelving and replenishment must align with FIFO/FEFO:

One tray containing multiple batches is a cancer for verification: scanning a tray code cannot correspond to a unique batch. The historical process for managing mixed batches is: isolate → break down the tray or separate it into scannable units → then perform verification. Locking the entire warehouse before completing the breakdown will only create a scanning war, after which there will be demands to 'release everything'—once released at once, the force of enforcement becomes zero.

The near-expiry warning should be linked with the outbound strategy: after entering the alert pool, it should be prioritized for allocation or trigger disposal; if an alert is issued but the items are still shipped according to the 'easy-to-grab new batch' rule, it indicates that the system has data but the business lacks a closed loop. Key dates for shelf life (production, expiration, and re-inspection) should be fully recorded at the time of receipt, and products missing key dates should not enter the available inventory. Outbound verification should randomly check whether the batch matches the allocation, not just the quantity.

If the three tracking questions are not answered, do not expand the mandatory categories for now.

The management value of FIFO/FEFO ultimately comes down to two things: the controllability of expiration risk, and the ability to narrow the scope when problems occur. At the very least, it can answer:

1. When will this batch of goods be received, which storage locations currently contain them, and which orders/work orders have they been shipped to?
2. When a customer returns a certain SN/batch, can the associated outbound range be listed quickly?
3. For the batches that were released as exceptions, is it possible to list them separately for quality follow-up?

When you can't answer, first supplement the collection of received goods, container codes, and outbound binding, then expand the mandatory measures for more categories — otherwise, the enforcement only creates scanning pain without bringing traceability benefits, and the project will be rejected on site.

JEDP-WMS emphasizes consistency between accounts and actual inventory, first-in-first-out (FIFO), and full-chain traceability of SN/batch/SKU/container codes; inbound and outbound operations cover shelving, wave picking, and outbound verification. FIFO must be implemented in allocation and verification: collecting batch/expiration date during receipt and prohibiting batch-less storage (for controlled categories); inventory is recommended or locked for outbound batches and locations according to strategy; picking scans verify and block incorrect batches; high-risk outbound requires a second check; exceptions go through an authorization workflow and reporting.

Pilot sequence: first be able to block, then be able to expand

Pragmatic sequence: Start with verification level for expiry dates and high-value/safety items → clean mixed batches → organize inventory to make the earliest batches accessible → then expand to general traceable materials (remind to raise verification) → for regulatory sensitive items, use locked level and dual-person review. When batch master data is largely missing, first supplement receiving collection and inventory cleaning, without blanket warehouse locking. When locations do not differentiate picking locations from storage locations, first organize the structure, otherwise FIFO disputes and efficiency disputes will be intertwined. When network instability causes frequent scan failures, first address availability, otherwise interception will be bypassed as a fault. Low-value auxiliary materials do not need to forcibly demonstrate FIFO; when multiple projects are stocked together without owner segregation, first segregate, then discuss batch rules.

Useful observations: FIFO/FEFO compliance rate by row, the number of wrong batch interceptions and exception release rate, the number of mixed batch inventory entries, near-expiry inventory and dead stock, and the time that recall drills can be located. Batches are only labeled on cartons and not entered into the system; drills are bound to fail.

Three 'Legitimate Appearances' That Are Recommended to Be Bypassed

When bypassing FIFO on-site, people rarely directly say 'I don't care about the rules.' More commonly, there are three actions that seem reasonable: first, 'ship out the ones that look good,' leaving the shelf-life risk for the next shift; second, 'ship out the ones that are already opened,' which is convenient but disrupts batch accounting; third, 'the customer specifically requested this batch number,' verbally specified but not processed through an exception form. The first two are managed through FEFO/FIFO verification and proper inventory handling; the third requires going through an authorized exception—the customer request is allowed, but it cannot leave no trace.

Production returns to the warehouse, non-conforming isolation, and pending inspection release will all rewrite the allocatable set. If returned materials are by default made available and batch tracking is not used, the FIFO link will break at the point of re-entry into inventory; if frozen batches still appear in the allocation candidate list, exception channels will also dismantle the quality checkpoint. Batch strategies and inspection status need to take effect simultaneously: frozen batches cannot be released from the warehouse just for 'first-expire, first-out,' nor can pending inspection be skipped just for 'ease of handling.'

If the wave engine allows batches to be opened in reverse for the shortest path, all previous checks will be diluted the moment the task is generated. After batches are assigned and locked, wave optimization can only reorder paths within a compliant set. If the picking accuracy project only verifies quantities and not batches, there will be the awkward situation of 'high accuracy but large recall'—the quantities matching does not equal batches matching.

In scenarios with multiple consignors or consignment, FIFO also needs consignor segregation: getting 'whose goods go out first' wrong is more serious than getting 'which batch goes out first' wrong. When the rules are not clearly defined, prioritize segregating by consignor/inventory attributes first, then discuss batch sequence to avoid scanning triggering two sets of compliance at once.

Choose a sensitive category and test one week of misbatch interception

First, select products based on expiration date or customer complaint-sensitive categories, turn on the wrong batch interception for one week, and only look at what the exception report says. If more than half of the exception reasons are 'the picking location does not have the batch to be issued,' the problem lies in replenishment and warehouse management, not attitude. The report can only be considered a valid exception control if it can find authorization release records in a short time; otherwise, first supplement the fields and permissions before discussing full warehouse implementation. If at the end of the week the interception count is zero but there are still customer complaint batch issues, prioritize checking whether there were universal skips or after-the-fact batch changes.

• WMS Warehouse Solution: Batch / SN Traceability and Operations
• Wave Picking and Error Classification
• Cycle Counting
• Traceability from batch to workstation