Warehouse replenishment moves eligible stock already inside a warehouse from reserve storage to a location that supports the next picking task. Confirm the owner, demand window, usable source stock, destination space and existing moves before assigning another task. Picking resumes when the goods and records are ready, not when someone creates a replenishment request. Extensiv replenishment overview
Imagine a hypothetical 3PL with a client's cartons in reserve while that client's pick face runs short and orders wait. The building has stock, but the required units are not ready in the right place. Buying more inventory is a supplier decision. Moving stock between warehouses is an interfacility transfer. This guide addresses the third task: replenishing pick faces within one warehouse, as part of the broader 3PL operating workflow.
Use this suggested SOP for ordinary ecommerce stock after receipt and release. New arrivals still need the receiving checks. The formulas, quantities, times and cases below are teaching assumptions, not customer results or software tests. Adapt the controls to the client's agreement, item requirements and the actual warehouse management system (WMS).
Warehouse replenishment illustration. Verify the item and destination picking bin before moving stock.
1. Is the stock eligible and in the right location?
Reserve or bulk storage holds stock awaiting the next operation. A pick face, also called a forward picking location, supports the relevant order-picking workflow. On hand is a system's recorded existing inventory balance; its treatment of statuses and locations depends on the report. Pickable describes stock or locations accessible to the selected picking process. Allocated means quantity assigned to demand. Replenishment in progress means a tracked internal move remains unfinished.
These are not necessarily exclusive inventory buckets. Allocated units may still sit at the pick face. A task can refer to units physically on a cart, still at the source, or already placed but awaiting confirmation. Do not add on hand, allocated and in-progress quantities into a larger stock total. Learn which fields overlap and which event moves quantity between locations before using a report as a planning baseline.
ShipHero's location documentation distinguishes Pickable from Sellable settings and describes non-pickable stock used by its Bulk Ship and Wholesale flows. A non-pickable location is therefore not automatically a quality hold. Nor does that label make every unit an eligible replenishment source. Confirm ownership, condition, commitments and the actual workflow separately. ShipHero location settings
Investigate in order: correct client and SKU, trustworthy quantity, permitted status, suitable location, other task commitments, then unfinished replenishment. Use the cycle counting SOP when the physical quantity or identity is uncertain. Do not fix an empty pick bin by placing a purchase order or adjusting quantity before establishing whether this is a location, ownership, timing or actual supply problem.
Distinct physical positions. WMS balance fields can overlap; map them before adding quantities.
The independent physical-position example above moves 40 units. Before the move, reserve holds 240, transit holds zero and the pick face holds 32. During movement those positions hold 200, 40 and 32; afterward they hold 200, zero and 72. Each stage totals 272. It is not the replenishment quantity in case A. Map these positions to the WMS's fields without counting the cart at both endpoints.
For a multi-client counterexample, the same product may be abundant elsewhere in the building but belong to another client or sit in quarantine. That does not fill this client's eligible gap. Keep the issue open until authorized eligible stock is identified. A warehouse-wide SKU total is useful context, not permission to borrow ownership or release restricted goods.
If pick-face size or placement repeatedly creates replenishment work, use the 3PL warehouse slotting guide to compare candidate locations, actual visits and total labor before approving a move.
2. Which replenishment method fits this demand?
Use Min/Max when a defined picking area benefits from a repeatable stock range. Use current order or wave demand when space is tight or demand has a known shape. A pre-shift or quieter-period pull organizes work into a practical window. Emergency replenishment addresses an urgent exception near a deadline. These approaches can work together, but they should share one view of outstanding work.
Method
Trigger and data
Best fit
Limits / extra handling
Min/Max
Chosen stock balance, Min, Max, review frequency and open moves
Repeated demand in a defined picking area
Stale parameters or case packs can overfill; excess moves use space
Order / wave demand
Unfinished demand, batch-usable stock and reliable timely moves
Known orders or tight pick-face space
Demand spikes, queues or insufficient sources; small urgent trips
Pre-shift / quiet period
Upcoming demand, route capacity and available time
Organize eligible moves before busy picking
Later changes still need review; do not top off every bin blindly
Emergency near cutoff
Verified gap, remaining work and confirmed handoff
Time-critical exception with executable path
More disruption and travel; cannot create extra time or eligible stock
Min/Max needs a meaningful minimum, a target maximum, a review schedule and a known stock definition. Parameters should change when demand, travel, queues or location capacity change. Filling every shelf or running once daily is not a universal best practice. A full shelf can consume space while still holding the wrong owner, lot or package unit for today's work.
Demand-based replenishment ties a move to unfinished orders, but does not remove the need for labor, available sources or destination space. A promotion can outgrow the plan, and a queued task can arrive after the order needs it. Recheck demand when orders change or work falls behind. Prioritize the requirement that can still be completed, rather than repeatedly issuing the same shortage to different workers.
Microsoft's Dynamics 365 Supply Chain Management overview distinguishes Min/Max, wave, load and immediate replenishment for Warehouse management functionality. It explicitly excludes the separate warehousing solution in Inventory management. Its templates and configuration govern the software behavior. The operating methods in this article are recommendations, not interchangeable buttons in those products. Microsoft replenishment overview
ShipHero's October 2026 Replenishment Report documentation describes allocated-order demand or a below-Min condition, plus available stock in an eligible non-pickable source. Filters affect the work displayed. Treat a report as a scoped planning view, not proof that every unlisted SKU needs no attention. Confirm the relevant account, warehouse, orders and filters when handing its output to another shift. ShipHero report guide
Extensiv's July 2026 3PL Warehouse Manager guide describes a Move Request triggered when a pick-line location's Available Quantity is below minimum and a pick job completes with Finish Pick. That named product and event matter. A manual pilot should not assume every consumption posts an immediate automatic replenishment task, or combine this trigger with another vendor's allocation behavior. Extensiv replenishments
3. How do you calculate the trigger and quantity?
A teaching trigger is expected consumption during the coverage period plus an operating buffer. The period includes review interval, queuing, source pickup, travel, putaway and confirmation. This is internal replenishment time, not a supplier's purchasing lead time. Use observed times for the route and shift. An average-rate model does not guarantee coverage during a promotion; known orders may justify a separate demand calculation.
For a simplified demand calculation, new net need = max(0, unfinished demand for this batch − pick-face stock usable by this batch − confirmed internal replenishment that can finish in time). Hold owner, warehouse, SKU, unit, status and time window constant. Exclude pick-face units exclusively committed to other demand. Include units already allocated to this batch once; do not subtract that allocation again as though it belonged to another order.
Count an outstanding move only when its identity, remaining quantity, physical progress and completion estimate are sufficiently reliable. Here, in progress means a warehouse movement task, not goods on a supplier's truck. Creating a task does not create pickable inventory. If a WMS already provides a net replenishment figure, check its deductions first; do not use that net figure as gross batch demand and deduct the same stock again. Exclude uncertain or late work from the timely-arrival allowance, and coordinate what happens to the original task before issuing replacement work.
For a separate simple Min/Max quantity model, first test the minimum using the chosen stock definition. If it triggers, the raw target gap is max(0, target maximum − current eligible balance − timely confirmed replenishment), assuming no intervening changes. Forecast relevant consumption or receipts explicitly when that assumption is false. Do not add the Min/Max result to the demand result for the same destination and requirement. Choose or reconcile the plan once.
Keep the Min/Max balance definition distinct from the batch-specific stock allowance. A batch may be allowed to use only part of a bin while the remaining goods still occupy space. Record whether the selected policy evaluates physical eligible stock, an availability field or another supported balance. If its deductions are unclear, ask the inventory lead to resolve them before setting the move. A physically crowded bin can have low batch availability at the same time.
Then check uncommitted eligible sources, destination contents and physical space, pack multiples, permitted case breaking and other unfinished tasks. Batch-usable stock and total stock occupying the destination can differ. Capacity must include everything physically there, plus planned arrivals in the same window. Do not rely on hypothetical future picks to free space unless the sequence is controlled. Preserve the inputs and assumptions with the task so a reviewer can reproduce the decision.
Microsoft's guide notes that its Min/Max strategy needs a fixed item location to replenish an empty location. That is a configuration condition in the cited product, not evidence of a universal restriction. For any system, an empty bin still needs an approved item/location assignment before an operator can fill it. Microsoft Min/Max conditions
4. Who does what in a replenishment SOP?
A. Confirm demand and the available window
The outbound planner checks unfinished demand, stock definitions, pick-face gaps, today's confirmed carrier handoff and the warehouse completion deadline. Record the required-by time in the warehouse's local time zone and work backward through the remaining steps. Start only with an identified requirement and responsible lead. If the quantity is doubtful, refer it for inventory review before releasing a move from an unreliable balance.
B. Review work that already exists
The replenishment lead checks open, duplicate, overdue and partially completed tasks for the same owner, item and route. Assign one owner to each task and reserve or otherwise control the selected source through the supported process. Record the existing task quantity used in the calculation. If two workers believe they own the same move, stop the overlap and establish what has physically happened before either starts another pull.
C. Confirm the source can be used
The operator verifies client, SKU, unit, required lot or expiration attributes, condition and quantity not already committed elsewhere. Pending inspection, quarantine, unresolved returns and another client's stock are not automatic sources. The inventory lead resolves an identity or status exception. Completion means the eligible quantity and source are evidenced, not simply that the total on the screen exceeds the requested amount.
Do not choose a source solely because it has the largest balance. Extensiv's configuration guide says its Replenish from fewest locations option can override item allocation methods when choosing move-request stock. Verify the client's rotation and tracking requirements before relying on that setting. In a pilot, have the inventory lead review the selected owner, lot and source whenever the proposed route conflicts with the agreed rule. A shorter journey does not settle that eligibility question. Extensiv source-selection settings
D. Check the actual destination
Verify the bin ID, permitted item mix, present contents, physical capacity and other expected arrivals. A configured maximum is a planning target, not proof there is enough room for the next carton. If space conflicts with a pack multiple, have the lead choose a smaller permitted move, authorized case breaking or another approved location. Do not leave a worker to invent an overflow location while carrying the stock.
E. Pick and record the route
Verify source, item, quantity and unit when removing stock. Record the cart or transfer location if the route uses one, and keep the task linked to those goods. An internal transfer needs evidence of where the goods went; do not simulate it with a new receiving transaction. Record a short pick at its actual quantity and escalate the missing balance. A source scan identifies the location but does not verify an entire closed carton.
ShipHero's Replenishment V2 with LPN Support guide distinguishes loose units, full license plate numbers (LPNs) and break-out operations, with source and destination steps. It also describes transfer-location handling. These are the named mobile V2 workflow's instructions. Verify the enabled version and storage setup before relying on those paths; they do not establish identical controls in another WMS. ShipHero mobile V2 guide
F. Put away and confirm the actual quantity
At destination, verify the bin, actual quantity placed, remaining balance and exceptions. Keep picked and placed quantities distinct when stock is still on a cart. In a hypothetical 72-unit task, 48 verified at destination leaves 24 unfinished. Those 24 could remain at source or already be in transit. Identify which before resuming work. A partial placement must not silently mark the full task complete.
For an interrupted task, the supervisor verifies both the physical position and the next supported record action. If 72 were picked but only 48 placed, find the other 24 in the identified transit position. If only 48 were picked and placed, the outstanding 24 are still a source requirement. The same open balance describes two different next actions. Keep the original task reference, document any authorized cancellation and give the next worker a specific remaining instruction rather than a fresh copy of the full move.
G. Release the affected orders
The outbound lead checks physical arrival and successful record updates, then reviews allocation, other order lines, quality requirements and order holds. Continue picking only when the relevant workflow permits it. Use the batch picking guide for keeping items and orders matched after release. A replenishment completion is one input to order readiness, not approval for every remaining fulfillment step.
H. Hand off unfinished work
Record task ID, actual stock position, picked and placed quantities, open balance, affected orders, next owner and next check time. The receiving shift acknowledges the handoff. If an update failed, distinguish a successful physical move from an unsuccessful record change. Do not repeat the movement merely because a screen still looks incomplete; inspect the goods and evidence first. Use the supported correction procedure and retain the original reference.
5. How do different orders change the plan?
A. Deduct the existing task before ordering another move
For this hypothetical batch, one client needs 120 unfinished units of one SKU. The pick face has 32 usable units, also its entire physical contents in this example. An existing task will deliver 24 before the requirement. Eligible source stock not committed to other tasks is 240. Moves use 24-unit cartons, and the destination allows at most 150 units. Assume no other inventory changes during this calculation.
New net need is 120 − 32 − 24 = 64 units. Whole cases require ceil(64 ÷ 24) = three cartons, or 72 units. The projected destination quantity is 32 + 24 + 72 = 128. That supports 120 units and stays below 150. The lead assigns the additional 72 from the uncommitted source, links both tasks to the same requirement and verifies each arrival before releasing the affected picks.
Creating a new 88-unit requirement ignores the existing 24. Rounding that 88 to four cartons produces 96; if both moves arrive, 32 + 24 + 96 = 152, above this capacity. Creating a new 120 adds even more redundant work. A task list should show the original allowance and the new quantity together, so the next worker does not mistake the remaining demand for a new instruction to move all 120.
If the existing 24 is delayed or canceled, recalculate its timely contribution as zero: net need becomes 88, rounded to 96, giving 32 + 96 = 128 without that task. Coordinate cancellation, resizing or rerouting of the original move and identify any stock already lifted. Otherwise it could arrive later and push the destination to 152. The outcome changes with the task's reliability; its units do not disappear because its ETA changed.
B. Whole-case rounding conflicts with available space
Assume consumption of 24 units per hour, one hour of review and replenishment coverage, and a 12-unit operating buffer. The teaching trigger is 24 × 1 + 12 = 36. Current pick-face stock is 30, target maximum 96, physical capacity 100 and case pack 24. No replenishment is outstanding and the source is sufficient. Hold the starting 30 fixed for the capacity comparison; this is a separate model from case A.
The raw gap to target is 96 − 30 = 66. Rounding upward to three cases gives 72, leaving 102 in a space rated for 100. The lead rejects that move. Moving two cases adds 48 and leaves 78, with 18 still below the target. For this trial, case breaking is not approved, so the lead chooses those two cases and schedules the next check using expected demand and route time. The unfilled target gap is not automatically an unfilled customer order.
Teaching assumptions with a common exact 0–110-unit scale. Target maximum and physical capacity are distinct.
If authorized case breaking can be counted and recorded accurately, add 66 to reach 96. Compare the extra handling with future demand and the cost of another visit. An approved alternative bin or revised setup may fit better, but its identity, item rules, capacity and task records must also pass. Do not hide the pack-versus-space conflict inside a min() formula or assume the next two units will sell before the third carton arrives.
Extensiv's configuration guide describes pick-line moves in packaging-unit multiples without exceeding the configured maximum. Its separate SmartScan guide describes a permission to overfill that configured maximum. Neither statement authorizes exceeding a location's physical capacity. These are 3PL Warehouse Manager/SmartScan behaviors, not the rounding rule used by every system. Extensiv configuration and SmartScan permissions
C. Route a bulk order without cycling it through a small pick face
A hypothetical pick face holds 48 units, with 40 committed to DTC demand and a capacity of 96. A new bulk order needs 240. Another 500 eligible, uncommitted units of the same client's SKU are in reserve. Repeatedly feeding the 240 through the small pick face would create extra handling and compete with the DTC work. The lead evaluates a supported direct reserve or case-picking route instead.
Use that route only when order requirements, WMS allocation, lot and unit rules, packing, handling path and records support it. Assume those checks pass here. Assign 240 from the eligible reserve; that leaves 260 uncommitted there under these assumptions. Keep the 40 DTC units protected. The pick face's eight uncommitted units do not give permission to consume its other 40. Preserve the bulk order's identity through packing and handoff without merging it into the small-order workflow.
Extensiv's replenishment overview describes quantity-driven allocation between pick line and bulk storage, subject to item thresholds. That is a product example of why order type can change the route, not proof another account has the same capability. If the actual system cannot support the proposed bulk operation, stop for a supervisor-approved controlled alternative or reschedule. Staff should not bypass the allocation and location records to create a superficially faster pick. Extensiv quantity-driven allocation
D. Replenishment can finish after today's handoff is already impossible
At 15:40 warehouse local time, staff find a shortage affecting an order. Today's confirmed handoff deadline is 16:00. Remaining replenishment takes 12 minutes, followed by 18 minutes of picking, packing and handoff preparation. In this hypothetical case those operations must be sequential and no additional queue buffer is included. Replenishment finishes at 15:52; the remaining work finishes at 16:10, ten minutes after the current window.
Teaching assumptions, warehouse local time, sequential work and no extra queue buffer. Work readiness and label creation do not prove carrier custody.
The zero-buffer latest start would have been 15:30. Expedite the correct work where possible, but do not promise 16:00 from a schedule already ending at 16:10. The supervisor checks whether a later handoff is genuinely available and usable, or whether an eligible alternative meets the order's requirements. Confirm access, collection arrangements and the order decision before treating that option as a new deadline.
For this case, no executable alternative is confirmed, so update the expected ship time and inform the client contact, with the next confirmed checkpoint and an owner. Creating a label or selecting a shipped status is not evidence of carrier custody. Changing transportation service also cannot remove the unfinished internal work. Recalculate if verified stock, timing or the handoff arrangement changes; otherwise carry the order into the next confirmed plan rather than silently reporting it shipped.
6. How should a supervisor schedule and measure work?
Plan backward from demand-required times and handoff windows, then allow for review, queues, pickup, travel, putaway and record confirmation. Assign time to exceptions and handoffs as well as routine moves. Batch nearby work only when ownership, item separation and task deadlines remain clear. A route that saves travel can still be wrong if it delays the oldest required order. Track the actual bottleneck instead of treating every delay as slow cart movement.
Write a latest-start estimate for each time-critical requirement: the confirmed deadline minus remaining sequential work and an explicit buffer. Compare it with the real queue and worker availability. If two tasks need the same person at the same time, they cannot both inherit the same optimistic completion estimate. The lead must choose a priority, assign feasible capacity or revise the order plan. Update the estimate when the route or work remaining changes, and preserve why the earlier plan no longer applies.
Measure the proportion of order lines blocked by pick-face stock using distinct affected lines divided by lines released to the selected picking scope in the same window. State whether the measure counts a line once even after repeated blocks. Track orders separately from lines and units. For a replenishment-related missed handoff count, define the affected order and confirmed deadline, then distinguish replenishment as a recorded contributor from unrelated quality, packing or transport delays.
For trigger-to-usable time, start at the recorded trigger and end when physical placement and the required confirmation make stock usable for the selected picks. Show still-open task age separately. Emergency replenishment share is emergency-classified tasks divided by all created tasks in the period, using an agreed reason definition. Keep duplicate or canceled tasks visible rather than dropping them to improve the ratio. Counts of units moved cannot substitute for task completion or timeliness.
As a hypothetical metric example, ten distinct blocked lines out of 200 released lines give 5%, even if three of those lines are blocked twice. In the same reporting period, eight emergency tasks out of 40 created tasks give 20%. State whether canceled and duplicate tasks remain in that created-task denominator, and report them explicitly. These are definitions to test in the pilot, not measured warehouse results. A task-based percentage and a line-based percentage answer different questions.
Track duplicate-task incidents and move discrepancies by task and quantity, with their causes. One cart carrying several SKUs is not necessarily one task, and a task can serve several order lines. State that mapping when reviewing throughput. Use the task ledger for coordination and evidence, not as a second independent stock balance that disagrees with the WMS. A worksheet should point to the authoritative inventory and movement records.
Measure / unit
Time basis and denominator
Blocked order-line share / percent
Distinct blocked lines within the selected released-line cohort ÷ all lines released to that scope in the window; count each line once
Trigger-to-usable / minutes per task
Recorded trigger → physical placement plus required usable-stock confirmation. Duration population: completed tasks with valid times; open age shown separately
Emergency share / percent
Emergency-classified tasks created in period ÷ all tasks created in same period; state canceled/duplicate treatment and keep them visible
Duplicate tasks / incident count
Distinct duplicate-task incidents detected in reporting period; count, not a percentage denominator
Move discrepancies / incident count and units
Tasks with verified movement differences detected in period, plus quantity by SKU and unit; no cross-unit netting. Count, not percent
Missed handoff contribution / order count
Distinct orders with confirmed deadlines in period and evidenced replenishment contribution; count once per order. No percentage denominator
7. How can a small team pilot the process?
Use the following templates for a controlled small-scale pilot. The task record names the client, source, destination, need time, planned and existing quantities, verified actual movement, unfinished balance and owner. Add separate picked and placed fields when transit matters. The shift check connects shortages and overdue tasks to orders and latest-start times. These records support coordination; they do not replace a reliable inventory system.
Task field group
Record before handoff
Identity
Task ID, client, warehouse, SKU, unit, lot/expiry/other required attributes
Route and timing
Source, destination, cart/transfer position, need-by time and time zone
Actual picked, verified placed/moved quantity, unfinished balance and actual goods position
Responsibility and exception
Owner, status, exception reason, affected orders, update evidence and next check
Pre-shift / handoff check
Decision and completion evidence
Priority demand and gap
Required order/line scope, usable pick-face stock, existing timely tasks and net need
Eligible source
Owner, item, tracking attributes, status, uncommitted quantity and source control
Capacity conflict
Physical contents/space, target maximum, open arrivals, case multiple and approved option
Overdue or partial task
Actual position, picked/placed/open quantities, owner and next supported action
Order and cutoff impact
Remaining sequence, confirmed handoff, buffer, latest start and feasible alternative or revised ship plan
Release and next owner
Usable-stock confirmation, allocation/other holds checked, next owner and next check time
For an illustrative one-week trial, select one client and a few SKUs. Begin by documenting current blocks, locations, pack rules and task times. Set provisional parameters, then observe demand, queues and actual destination space while running controlled moves. Review exceptions with both shifts, change one parameter or process at a time and compare the next observations. At week's end, decide what to retain, retest or expand. The week is a suggested learning window, not a promised accuracy or productivity result.
After stock and orders pass release, complete picking and packing, verify actual parcel dimensions and weight, and check available shipping services. EasyShippingX provides Portal, Excel upload and API paths for applicable rate, label and tracking workflows; confirm the enabled channels and actual requirements. The Excel upload guide covers that shipping-data handoff. Finish with the carrier handoff checklist, preserving the difference between a prepared label and a parcel actually transferred to the carrier.
Warehouse replenishment FAQ
It moves eligible stock already inside the warehouse. Purchasing adds supply from a vendor; an interfacility transfer moves it between warehouses. Resolve the actual shortage type first.
Only when the order, eligible stock, allocation, packing path and actual WMS workflow support it. Otherwise ask the supervisor for an approved alternative; do not bypass records.
Deduct only its verified, eligible remaining quantity that can finish before the need. If timing or status becomes uncertain, recalculate and coordinate the original task to prevent duplicate arrivals.
Yes, with a limited controlled pilot, clear task IDs, owners, source/destination checks and one authoritative inventory record. A worksheet coordinates work rather than becoming a second stock ledger.
Other lines, quality checks, allocation, order restrictions or the handoff window may remain unresolved. Confirm the complete remaining workflow before promising shipment.
Sources and methodology
Sources reviewed November 9, 2026. Vendor features apply to the named product and documentation. The SOP, formulas and controls are suggested operating procedures. Quantities, times and metric calculations are teaching assumptions, not product tests or customer results.
Dynamics 365 Supply Chain Management, Warehouse management functionality; updated November 20, 2025. Strategies and fixed-location condition, not the separate Inventory management warehousing solution. Microsoft replenishment overview
Updated October 19, 2026. Demand/Min conditions, eligible sources and scoped report filters. ShipHero Replenishment Report
Named V2 workflow; updated October 19, 2026. Source, transfer, LPN/loose-unit and destination operations. Enabled account version must be checked. ShipHero Mobile Replenishment V2 with LPN Support
Broad blog context spanning internal moves and other restocking. No unverified percentages or customer stories adopted; exact software behavior checked in help documents. Extensiv warehouse replenishment overview
3PL Warehouse Manager; July 28, 2026. Packaging multiples, configured maximum and source-selection setting. Extensiv replenishment configuration
SmartScan with 3PL Warehouse Manager; July 23, 2026. Permissioned overfill and manual move requests. Physical capacity remains a separate check. Extensiv SmartScan replenishment
Updated November 5, 2026. Pickable and Sellable are distinct settings, with documented Bulk Ship/Wholesale context. ShipHero location settings
Portal, Excel upload, API and enabled-channel rate/label/tracking workflows after warehouse release. EasyShippingX features