Forward-pick stock control
A forward pick slot can look full while the system is empty, or look empty while a pallet is moving toward it. Replenishment needs one visible task connecting demand, reserve stock, destination capacity and the exact completion event.
Direct answer
Control warehouse pick-face replenishment by defining which inventory locations are reserve storage and which are active picking faces, then setting a documented trigger rather than relying on an operator noticing an empty bin. Use released demand, expected near-term picks, current usable pick-face quantity, open replenishment tasks, inbound supply and destination capacity to calculate the required movement. Open one task with the warehouse, SKU, variant, lot or serial, unit of measure, source location, destination, requested quantity, priority and reason. Verify that the reserve stock is available, not quarantined, damaged, customer-owned or already committed to another task. Apply the approved rotation, lot, expiry and compatibility rule before the move. At the source, confirm object, location and quantity; at the destination, confirm the actual pick face and quantity placed. Do not mark the task complete when the pallet leaves reserve storage. Split, short or cancel the task through a recorded exception path when stock, capacity, access or identity differs. Protect active pickers by defining whether replenishment may occur during picking, how the shared aisle or slot is controlled and which task has priority. Recalculate the available pick quantity only at the local completion event. Close when source deduction, in-process balance, destination addition and remaining demand reconcile, then review stockouts, emergency tasks, pick interruptions and repeated overfill to improve trigger and slot settings.
Use this before requesting a quotation
Maintain the warehouse, zone and location IDs for reserve and forward-pick stock, plus the SKU, unit, minimum, target, maximum and review method. Use actual demand and open tasks rather than a fixed threshold copied across unlike products. Distinguish planned top-up, demand-driven, stockout, wave or exception replenishment. Record who may change the trigger and why; a higher maximum can create congestion or expiry exposure rather than better service.
Start with released or forecast demand for the planning horizon. Subtract usable pick-face stock and confirmed inbound replenishment, then add any safety or presentation quantity defined by policy. Exclude damaged, held, expired, wrong-lot, customer-owned or inaccessible units. Check unit conversions between pallet, case, inner and each. Avoid double demand when the same orders appear in both a wave and a manual emergency request. Compare the calculated movement with the destination maximum and the smallest executable package. If a full case exceeds the available slot, record whether the local process permits case breaking or a partial task. Keep the rounding method visible so repeated top-ups do not gradually overstate available pieces.
Give the task a unique ID, creation time, priority, source, destination, SKU, lot or serial scope, unit and requested quantity. Link the demand or trigger record. Confirm source availability and destination capacity before release. Reserve the task quantity in a way that prevents another movement from taking it, while keeping the status visible so reserved units are not counted as both available reserve and replenishment in process.
At reserve storage, verify location, product or package identity, lot, expiry, status and unit. Apply the approved rotation rule and record any exception. Count or scan actual quantity removed and leave a clear source balance. If the source is empty, blocked or different, do not silently borrow from another bin; short the task or obtain an authorized alternate source so the movement history stays complete.
Confirm the pick-face label and physical capacity before placement. Control aisle access, equipment interaction and simultaneous picker activity under the facility safety process. Keep incompatible lots, statuses or ownership separate. Do not overhang, obscure labels or exceed rack and container limits to complete a system quantity. If the destination cannot accept the movement, hold the task in a visible in-process location. Define how released picks already assigned to the face will behave during refill. If a picker takes units between the destination count and confirmation, record that consumption through the normal event sequence rather than forcing the replenisher to make the final balance look correct. Escalate repeated concurrent-work conflicts to slot or wave design.
Record actual quantity, destination, operator and time when units are placed and usable for picking. Preserve parent-child package changes when cases are opened. Reconcile requested, source-picked, destination-placed, damaged and remaining quantity. Update availability according to the defined stocking event; GS1 distinguishes movement into storage from stocking that makes objects available for order fulfillment.
Review pick-face stockouts, emergency replenishments, shorts, abandoned tasks, pick interruptions, excess travel, repeated overfill, expiry and location errors by SKU and slot. Separate demand error, slot capacity, reserve shortage, task priority, execution delay and master-data cause. Change minimum, maximum, slot or task timing only with before-and-after evidence and an owner for follow-up. Use a stable denominator such as released lines, units picked or active faces when comparing periods. Record whether a failure occurred before task creation, while waiting, during source pick or at destination. This timing prevents a fast operator from masking a weak trigger and prevents the planning rule from being blamed for unavailable reserve inventory.
Reusable buyer brief
Task ID, warehouse, release time, priority and reason: SKU, variant, lot/serial, package hierarchy and unit: Demand horizon, released demand and trigger source: Pick-face usable, open-task and target quantities: Net requested quantity and calculation assumptions: Reserve source, usable balance, status and rotation rule: Task reservation, competing commitment and source verification: Destination pick face, capacity and active-work control: Requested, source-picked, in-process and placed quantities: Object/location confirmation, operator and completion time: Short, split, damage, alternate source or blocked-slot exception: Stockout, interruption, overfill, rule change and review date:
Fill only the details relevant to your request
Before you send the request
It is the controlled movement of usable inventory from reserve storage to a forward location where units become available for order picking.
Use a documented trigger based on usable stock, released or near-term demand, open replenishment, lead time and destination capacity. There is no universal minimum for every SKU.
When actual quantity is confirmed at the correct destination and source, in-process and destination balances reconcile—not merely when stock leaves reserve storage.
Separate shortages caused by demand, reserve availability, slot capacity, task priority, execution delay and master data, then tune the responsible rule with measured results.
Keep the request specific
Rack loading, powered equipment, pedestrian separation, hazardous materials, temperature, expiry and regulated-product requirements depend on the facility and goods. GS1 and UNECE sources describe business events and inventory information; they do not approve a safe storage design or universal minimum and maximum. Use qualified warehouse and safety review. Keep personal performance conclusions separate from task timing: a delayed scan may reflect access, congestion, equipment or system design rather than individual conduct.
Send this checklist on WhatsAppEditorial method
MINJI models replenishment as a demand-linked movement with source, destination, identity, quantity, status and completion evidence. GS1 supplies storing, stocking and event vocabulary; UNECE supports held-inventory quantity, class, location and movement records. The worksheet deliberately separates trigger design from task execution so a service failure can be assigned to the correct control.
Ready with the key details
Send the product reference, estimated quantity and destination so the conversation starts with useful context.
Continue on WhatsApp