Put away before QC? Hold-and-release must beat verbal “QC said OK”

That pile on the night shift platform

The urgent material truck was delayed by two hours, and the production line was already flooding the shortage message group. The unloader pushed the pallets onto the shelf marked 'Inspection Pending Area,' and the warehouse staff clicked the receipt confirmation in the system— the next moment, the wave algorithm locked this batch of materials into the material picking task for tomorrow morning. The quality inspector only discovered the next morning: this batch hadn’t been unpacked yet.

The controversy has never been about 'whether to test,' but ratherDoes the system regard 'Not Tested' as unavailable?The shelf label says 'Pending Inspection,' but the inventory status is 'Available,' and no matter how many times the password is entered, it can't stop the wrong dispatch.

"Why can't the 'Pending Inspection Area' prevent mis-shipments?"

Many warehouses understand quality inspection as a spatial issue: freeing up some space, putting up a sign. Space is certainly useful, but it cannot solve three things:

1. Whether the wave and allocation read the quality status—Don't read it, the batch will be locked to the warehouse anyway.
2. Where do conclusions come from, and who sees the failures?——The quality has been judged as qualified, yet it is still frozen in the warehouse; or the quality has not been judged, but it is verbally released in the warehouse.
3. Where do the goods go after failing?——The rejected items are still piled next to the qualified goods aisle, and during the busy weekend, they were swept into the pickable area again.

Must be pending inspectionInventory status that cannot be picked or shipped; Shelf placement guidelines, wave allocation, and outbound review all need to recognize this status. Storage locations are just the execution carrier, not the strategy itself.

First write strategies by product category, then discuss 'all pending inspection'

One-size-fits-all 'full inspection' will clog both the platform and the inspection station during peak periods, forcing verbal clearance; 'full exemption' buries the risk into the production line. The pragmatic approach is a goods category strategy table:

Exemption from inspection does not mean ignoring it: the basis must be clearly stated (supplier grade, material risk), the sampling ratio, and how the strategy will tighten if the sampling fails. Scheduling for peak receiving periods, waiting inspections will occupy the platform and storage capacity—the strategy table must be viewed together with the schedule, otherwise 'inspection backlog' will once again force verbal release.

Conclusions recognize only one source

The main responsibility on the warehousing side is to trigger IQC (and PQC/OQC as needed) tasks after receiving goods, and to place the inventory in pending inspection/frozen/available status. Inspection standards, sampling, and reporting should primarily follow the quality side when integrating the quality system, and the warehouse side should not maintain a second set of "pass/fail" conclusions.

A closed loop can be compressed into a chain:

Receipt confirmation → Pending inspection according to strategy (not pickable) → Generate inspection task → Quality provides release/freeze/rejection → Warehouse executes shelving, isolation, or return → Waves only consume available quantity.

The part most prone to failure in the middle is the write-back. Quality has been determined, and the warehouse is still frozen; on-site, a WeChat password will be used instead. The warehouse has been verbally released, but the quality conclusion has not arrived, so the risk of misdelivery is even greater. Integration failures must be addressed.Business To-Do(Both warehouse management and quality can see it) Do not rely on chatting to defrost before closing. Successful silence or only writing a technical log is equivalent to leaving the gate to luck.

Partial release, rejection, and exceptions: the three most easily confused branches

Partially qualified. If partial release is allowed by the business, batches must be split or handled at the line-level status. 'Half pallet qualified, half pallet verbal' is prohibited. The batch-splitting rules must be consistent with batch traceability, otherwise it will be difficult to calculate the impact during a recall.

Refuse / Return. The flow of non-conforming goods must be able to interface with return coordination to avoid situations where goods are already shelved and then materials are searched for when the warehouse is full. Items in the rejected temporary storage area also cannot be picked; for outbound returns, scanning and documentation must be retained, and stock losses should not be used to cover them up.

Urgent material exception. When a production line is blocked, exceptions can be allowed for a limited period, but it must include: the authorizer, reason code, applicable batch and quantity, and automatic retrieval upon expiration. The exception list is reviewed in the weekly meeting; if the proportion of exceptions continues to rise, it indicates a problem with the strategy or inspection capacity, rather than 'the system being too strict'.

Allocation rules do not recognize status; all previous ones are done in white.

Pending inspection lock only addresses 'don't consider it available after receipt.' On the outbound side, we still need to ensure:

• Wave/allocation engine skips frozen and pending inspection batches;
• Check the outbound inventory again to intercept it once more, preventing manual batch changes from bypassing the system;
• FIFO / expiration rules and quality status take effect simultaneously — frozen batches cannot be released from the warehouse just for 'first expired, first out'.

There is another type of hidden bypass: warehouse staff 'first provide emergency supplies to the production line' outside the system, and later reconcile the accounts using qualified batches. The accounts always show qualified, but the actual materials may have been used before inspection. To address this issue, relying solely on inventory status is not enough; it is necessary to enforce batch scanning through material requisition tasks and randomly check whether the requisitioned batches were ever in the pending inspection window.

Spot-checking scripts is more effective than slogans: Randomly pick a batch received in the past week and check whether unchecked items are already available for picking; randomly pick a frozen batch and try to allocate it to see if it gets blocked; randomly pick an order that is 'qualified but still frozen' and check whether there are pending tasks and whether the closure time is acceptable. The gate is considered established only if all three questions can be demonstrated on the spot.

How to connect with appointments, material returns, and rejections

Occupancy of platforms and storage capacity to be inspected. If scheduled deliveries are only registered but do not occupy a time slot, when quality inspection scheduling coincides with unloading peaks, 'inspection backlog' will force verbal clearance—this is not a matter of quality attitude, but a misalignment of capability and strategy. High-risk goods categories should have their inspection load indicated at the reservation stage, with staggered timing or reserved inspection windows.

Production returns and sales returns can also be matched with quality inspection strategies. Defective items flowing back to the line or re-entering pickable inventory pose risks no less than uninspected incoming materials being shelved. Returns to the warehouse are by default placed in pending inspection or isolation, and after assessment, a decision is made whether to return them to usable stock, scrap them, or return them to the supplier, to prevent the 'returns area' from becoming a second verbal release point.

Rejected temporary storage must be visible, countable, and not pickable. When coordinating with supplier returns, the outbound scan for returns and the reconciliation documents must match, to prevent rejected goods from disappearing in the warehouse and being written off due to inventory discrepancies.

Order of going online: don't go all-in and forcibly lock everything right away

When there is no barcode/batch identification, first add the identification before discussing status locking—otherwise, the 'lock' will only be on the account, and the goods can still be moved freely. For those who insist on visual judgment in the warehouse and do not accept quality conclusions, the system can at most provide task reminders and cannot prevent mis-shipments. When there is no quality system and it cannot be launched in the short term, at least ensure that 'pending inspection cannot be picked' is reflected in the warehouse status, and specify who has the authority to change the status and how to leave traces after changes; this is the bottom line, not the endgame.

In the warehousing solution, the inbound quality inspection strategy (inspection pending area / qualified for storage / rejected returns) is linked with batch release status precisely to implement the above gate operation rules, rather than issuing another warehouse regulation. In JEDP-WMS, when combining the quality module, inspection reports are not reconstructed on the warehouse side; the warehouse side only needs to manage triggers and inventory status. The dashboard can display frozen batches, long-term pending inspections, and failed integration tasks in the same view, so that before the shift meeting, the queue is checked first, then the inventory numbers.

Determine whether it is really controlled

There is no need to blindly believe in a single 'accuracy rate.' A more useful observation is whether cases of undetected stock blockages have occurred, whether there have been any wrongful freezing incidents, whether failures in writing back conclusions are ever left unresolved overnight, and whether the proportion of exceptions is declining. A short-term increase in the number of interceptions is often a good sign—it indicates that the checkpoints are starting to work; if the number remains at zero for a long time but there are still customer complaints or production line complaints that 'there is a problem with the materials,' it is necessary to suspect that bypasses are still present.

What to do next

Next week, do only one thing: export the receipts from the past seven days, and mark two columns: 'Not inspected but shelved' and 'Frozen but still locked by wave'; randomly select three orders to check whether the issue at the time was a strategy omission, a write-back failure, or an exception without a time limit. Bring the list to the joint meeting of warehouse management and quality assurance, first block high-risk product categories, then discuss warehouse-wide implementation.

• WMS Warehousing Solution: Quality Inspection Strategy and Freeze Release
• How to leave a time slot for quality inspection when scheduling a delivery
• Incoming material quality closed loop: determining how to return to the supplier
• FIFO and Batches: How to Recognize Status for Allocation Rules