Warehouse Operations Guide

Warehouse Slotting for 3PLs: How to Place SKUs for Efficient Picking

Warehouse slotting decides where a SKU should sit so orders can be completed with less total work, subject to safety, product, ownership and record constraints. Putaway executes storage, replenishment refills a pick face, picking removes goods for orders, and cycle counting checks physical stock against records. Changing a location plan does not complete those other steps. NetSuite slotting overview

Consider a hypothetical 3PL that concentrates its best sellers beside packing. Walking looks shorter, but carts now queue in one aisle, smaller bins need more replenishment, and similar packages become easier to confuse. The question is whether the complete operation improved. Count walking, searching, waiting, checking and replenishment, plus the move itself, rather than choosing the shortest-looking route or fullest shelf.

This suggested process covers ordinary ecommerce goods in one warehouse with manual or cart picking. It does not design a multi-warehouse network or a robotic system. Use it to select a limited candidate set, approve a position plan, control the move and test the result within the broader 3PL operating workflow. All case quantities, times and dates are teaching assumptions, not customer results or firsthand trials.

After choosing the locations, use the warehouse labeling guide to identify the bins and items and verify scans against the actual task and inventory records.

Two warehouse workers check a location plan beside picking shelves, reserve racks and a cart in a fictional small 3PL.
Warehouse slotting illustration. Workers review the location plan beside picking and reserve racks.

1. Which data makes a SKU worth reviewing?

Start with client ID + warehouse ID + SKU, current locations and usable status. Matching SKU text or barcodes across clients do not establish common ownership. Save the observation period, picking unit and report definitions. A practical starting sample might cover four to eight weeks, adjusted for the business cycle. Include a normal period and relevant peak conditions where possible; a quiet week alone cannot describe a promotion.

Field groupMinimum usable record
Identity and periodClient ID + warehouse ID + SKU; source report, sample dates, current locations and usable status
ActivityOrders, lines, units; actual visits or explicitly labeled proxy; batch/task reference and each/case/pallet unit
Item and location fitItem/package dimensions, weight, orientation and handling needs; usable space and confirmed load rating
Related workReplenishment trips and person-time; search, errors, checking, waits and feedback; valid co-orders
Demand contextPromotions, seasonality, stockouts, new-client launch and uncertain estimates

Keep orders, order lines, units and actual location visits separate. Sales-value ABC is not a substitute for picking-activity classification. A bulk item can produce many units in few visits, while an inexpensive accessory creates repeated small picks. If actual visits are unavailable, label order lines as a proxy and validate with a small route observation. Do not report proxy counts as measured trips.

Define a location visit before collecting it: for this pilot, it can mean one physical stop at a client–SKU location to complete the associated pick work. Several unit scans at that stop are not automatically several visits. Stops at two locations should remain distinguishable. Keep the batch or task reference and observation method with the result. If only scanner events are available, explain what they can and cannot establish about physical movement.

Batching changes that relationship. One visit can supply several orders, and one line can require more than one location. Keep the batching method with the sample so the interpretation survives a shift change. The batch picking guide covers collection and order separation; this guide uses that context to judge position candidates without redesigning the whole picking method.

Treat historical shortages and new-client launches as context. A stockout can suppress fulfilled units and make a demanded SKU look slow. Separate sales lost or work delayed by unavailable stock from the activity that actually occurred. Compare launch or promotion demand with a relevant scenario, rather than assuming the last completed orders are a complete forecast. Mark uncertain estimates and give them an early review point.

For associations, use distinct valid customer orders within a stated client and time scope. Deduplicate exports and reconnect split fulfillment records to the intended order definition. Decide how kit parents and picked components will be represented, so an assembly does not become artificial evidence of two independently chosen products. Popular items naturally co-occur often; their raw shared count alone does not prove that adjacent slots reduce work.

Check whether a customer-order association also creates shared picking work. A split order picked on different days may count once for customer demand analysis while providing no same-route opportunity. Keep both definitions rather than silently changing the denominator. Compare the proposed pair with another practical arrangement under the same order scope. A planner should be able to explain which actual work would be removed, not merely point to a large co-occurrence count.

Collect item and package dimensions, weight, orientation limits, picking unit, confirmed location space and load rating. Add replenishment trips and person-time, searching, errors, waits and worker feedback. The inventory lead verifies questionable stock or identity through the cycle counting process. Finish the candidate dataset only when the identity, unit, period and data limitations can be explained by the next reviewer.

2. Which placement approach can the warehouse maintain?

Fixed positions, eligible available locations, stable pick faces with flexible reserve, and temporary campaign positions are different operating choices. Choose according to order patterns, space, control capability and change capacity. A fixed position can be reviewed and changed deliberately. A flexible position needs reliable location records whenever goods move. Neither removes the need to verify product fit and ownership.

Approach / fitRequired recordsMaintenance / failure mode
Fixed locations: stable work and clear addressesClient–SKU location, usable stock and exceptionsReview demand and fit; stale assignments waste space or travel
Eligible available positions: variable receipts and spaceEvery source/destination move, identity, status and capacityKeep positions current; a missed move creates searching or wrong ownership
Stable pick face + flexible reserve: repeated picks with reserve stockPick/reserve relationship, usable balances and refill tasksMaintain forward quantity and source controls; small faces can add refills
Temporary campaign position: limited eventVersion, effective time, owner, expiry and restore planReview actual demand and remove or approve extension; forgotten positions become misleading

ShipBob's slotting guide discusses product characteristics, picking level, order relationships and frontline feedback. Use those as inputs to a controlled proposal, not as a requirement to reorganize the entire building. The choice here is whether the team can keep the selected method accurate through receiving, replenishment, picking and exceptions. An unrecorded flexible location can create more searching than a less compact but dependable fixed position. ShipBob slotting guide

ShipBob's dynamic-slotting article discusses seasonal changes, demand and employee feedback. For this proposed process, dynamic means the placement decision can respond when conditions change. It does not by itself require AI, a daily whole-warehouse move or dedicated optimization software. Set a review trigger and controlled scope. A temporary location also needs an expiry and recovery owner; supporting multiple locations in software does not establish that placement has been optimized. ShipBob dynamic-slotting discussion

3. How should a supervisor build a location proposal?

Reject locations that cannot meet the constraints

The warehouse lead screens size, weight, orientation, storage requirements, permitted handling method and client restrictions. Confirm actual usable space and the approved load rating for the shelf and its setup. Do not turn a general recommendation about easy access into a universal shelf height, aisle width or weight limit. An unknown rating or incompatible product condition is a hold for assessment, not a low score to offset with shorter travel.

OSHA's warehouse hazard guidance discusses reaching, bending, force, repetitive work and storage stability. Use that guidance with the site's safety lead to assess the task and equipment; it is not a single dimensional specification for all warehouses. Separately, for work covered by 29 CFR 1910.176, paragraph (a) requires appropriate clearances where mechanical handling equipment is used and clear, well-maintained aisles and passageways; paragraph (b) requires stable, secure storage. Keep those requirements distinct from suggested placement experiments. OSHA warehouse guidance and 29 CFR 1910.176

Rank the remaining candidates by actual work

Review frequent picking activity using the declared measure and period. Check whether it represents individual items, cartons or pallets and whether the route requires different handling. Give a high-frequency small pick a location review, rather than automatically giving every high-unit-volume item the closest bin. Ask pickers where they search, turn, wait or interrupt another task; record those observations as specific route issues.

Next, examine product combinations against real routes. Co-ordered items may benefit from the same work area while retaining separate, identifiable bins. Similar variants, bulky items or a shared bottleneck can make immediate adjacency a poor choice. Trace a candidate route through actual walkable aisles and include cart stopping and replenishment access. The layout below is a candidate illustration, not a measured building plan or a claim of distance savings.

Before and candidate-after layouts keep the same racks, reserve, aisles and exit. F moves toward the route start; similar X and Y stay in separated bays. The F-only route follows the aisle.
Candidate illustration, not to scale. Only the route to F is shown; validate all affected work with actual orders and site conditions.

Check replenishment and the effect on other clients

A closer small slot can increase the number of refills. Estimate the sensible forward quantity, reserve route and expected replenishment work before approving the position. Use the published pick-face replenishment SOP for quantity and task controls; the slotting decision here is whether its space allocation makes total work better. Do not assume a nearby location has enough usable capacity for the item's operating pattern.

Client-specific zones can simplify ownership and access, but may spread common work across longer routes or leave awkward spare space. Shared work areas can reduce some travel while increasing identification and traffic-control demands. Evaluate the other clients using the same aisle and time window. One client’s faster pick is not sufficient evidence if it blocks everyone else’s main route. Physical proximity never authorizes combining different clients' stock.

Check traffic in the relevant time window, not only an empty-aisle walk. Record where a replenishment cart would stop and whether another client's route still works when that task is active. Keep a clear distinction between a route that can be walked and one that performs well under the expected load. The candidate sketch only answers the first question; an operating trial must answer the second.

Finally, compare ongoing work with the one-time move, verification, configuration, training and restoration effort. Use person-time consistently and keep roles separate when their costs differ. If credible savings do not recover the proposed disruption within the relevant horizon, retain the current placement or test another candidate. A move required for safety or an agreed handling constraint is a different decision from an optional labor-saving experiment.

4. What do four different candidate decisions look like?

A. Units sold and order lines rank the SKUs differently

In one hypothetical comparison period, SKU A has 1,200 units across 30 order lines; SKU B has 600 units across 300 lines. Average quantities per line are 1,200 ÷ 30 = 40 for A and 600 ÷ 300 = two for B. Ranking units puts A first. A review aimed at repeated small-item work may instead investigate B first.

Separate scales show units A 1,200 and B 600, versus order lines A 30 and B 300 in the same hypothetical period. Order lines do not equal location visits.
Teaching assumptions. Separate same-unit charts reverse the ranking, but neither approves a move or proves the number of trips.

That is a candidate decision, not proof B caused 300 independent return trips. The lead checks batching, case handling, actual location visits and physical requirements. A might be picked by the carton, and a visit to B might serve several orders. Save both raw measures, the chosen proxy and any route observations. The first action is to verify B's potential location benefit, not to move it merely because it has fewer units per line.

If visits confirm repeated short picks and a suitable candidate location exists, test B on a comparable route with its replenishment needs included. If batching has already consolidated those lines or A needs specialized handling, reprioritize the candidates. Keep A in the review population with its correct work profile. The lesson is to validate the measure that matters, rather than reversing the original shortcut into a new rule that lower unit volume always belongs in front.

B. A nearer small bin adds eight person-minutes each day

Assume a hypothetical comparable trial with 240 relevant visits per day. A nearer location saves eight seconds per visit, or 240 × 8 ÷ 60 = 32 picking minutes daily. Its smaller space creates eight additional replenishments, averaging five person-minutes each, adding 8 × 5 = 40 minutes. Other ongoing work is assumed unchanged. Net time saved is 32 − 40 = −8 minutes, so total work rises eight minutes a day.

Hypothetical new-minus-old daily person-time: picking −32 minutes, replenishment +40 minutes, net +8 minutes more work.
Teaching assumptions; other ongoing work unchanged. Net savings of −8 person-minutes equal 8 more person-minutes of daily work.

The supervisor rejects this small near-bin proposal and keeps the original position for now. The picker gets a shorter walk, but the operation has more work. Compare a larger nearby position, a reasonable forward quantity with reserve storage, or a better replenishment route before another test. Record the rejected candidate and the reason so a later shift does not implement it using only the attractive eight-second figure.

This is a simplified sum of different workers' person-time. If labor rates differ, price the activities separately. Reduced person-time also does not automatically reduce payroll, overtime or elapsed order time. The original one-time move cost would make this particular negative ongoing result less attractive. A different capacity or replenishment arrangement could change the conclusion, but its revised visits, refill frequency and other effects need a fresh comparison, not a promised saving.

For the larger-nearby-bin alternative, include the space taken from other items and any changed refill pattern. The supervisor can ask for a revised plan with the original position as the comparison. If no approved candidate improves the full work estimate, keeping the existing position is a valid outcome. Do not report the rejected small-bin proposal as a partial success by counting the picking benefit while assigning its refill burden to another team.

C. Frequently co-ordered products share an area, not a bin

Assume 500 valid orders for one client, with 200 containing A, 180 containing B and 120 containing both. Among A orders, 120 ÷ 200 = 60% also contain B. Across all orders, 120 ÷ 500 = 24% contain the pair. The two products look similar but have different specifications, and the hypothetical scenario includes reports of confusion. Those facts support a controlled same-area proposal, not mixing the goods.

The lead selects clearly separated, labeled locations within the same work area and retains necessary scan verification. Compare possible routes within that area and monitor correct variant selection as well as time. Do not infer that they must be next door solely from 120 shared orders: inspect frequency, route structure, cart congestion and the consequence of choosing the wrong version. The shared-order measure points to a testable relationship, not an automatic placement command.

If another client holds the same product or uses the same barcode, keep client identity explicit in the system and physical control process. Similarity or adjacency cannot prove ownership. Change the proposal if the separation remains confusing, demand combinations shift or the area becomes crowded. The trial can retain a shared zone while increasing separation; it need not choose between mixing products and sending them to opposite ends of the building.

Keep the actual variant description visible in labels and validation orders. A label that identifies a broad product family may still leave two sizes or specifications ambiguous. Verify the configured item and required owner selection rather than relying on a picker's memory of package color. If the proposed labels cannot support reliable selection, fix the identification or increase separation before testing any route benefit.

D. A short promotion does not recover the move effort

Assume moving and checking take 80 person-minutes, configuration and training 20, and post-campaign restoration 40. Total one-time effort is 140 minutes. Expected continuing net savings are 30 minutes per operating day, already after additional replenishment and other ongoing work. Do not subtract those ongoing costs a second time. This example assumes both candidate arrangements pass the product, safety and ownership checks.

For three operating days, gross accumulated time saved is 3 × 30 = 90 minutes; after 140 invested, the result is −50 minutes. The lead declines the short campaign move for the labor-saving objective. For ten operating days, 10 × 30 = 300 and 300 − 140 = 160 minutes saved. Simple person-time payback is 140 ÷ 30, about 4.7 operating days. This is not a financial-return guarantee or a calendar-day promise.

For the conditional ten-day trial, an illustrative log can set activation at 08:00 warehouse local time on December 1, 2026, reviews at the first shift's close and December 7 shift close, and expiry at December 14 shift close. That is ten operating days assuming Monday–Friday work and no closures; December 7 is day five. Assign the inventory lead and specify restoration when the campaign ends or the trial no longer meets its agreed conditions.

Retain the temporary placement only while demand, replenishment, accuracy and congestion support the decision. If the expected benefit does not appear, reassess the future work and remaining restoration cost rather than insisting on the position because the move already happened. A longer event, lower move cost or better daily result could change the original decision. A shorter event, additional errors or congestion could remove the apparent benefit of the ten-day plan.

5. How can the warehouse change locations without losing control?

1. Limit the first scope and name an owner

A starting example could be one zone and about 20 client–SKU combinations, adjusted to staff and change capacity. The supervisor names the move owner, inventory reviewer, system configuration owner and affected outbound lead. Identify which orders and locations are included and which remain untouched. Start only when the scope and authority are clear; an informal list of popular SKUs is not a move authorization.

2. Save a recoverable baseline

The inventory reviewer saves original positions, verified quantities, units, statuses, related tasks, priority settings and comparison measures. Include the source of the data and its time basis. Recheck uncertain identity or count before moving it. Retain the plan version and original location labels, but do not treat the old snapshot as a future stock balance. Recovery must account for transactions that happen after this baseline.

3. Resolve work already in progress

The supervisor and task owners identify open picks, replenishments, counts and transfers in the selected scope. Agree how they will finish, pause or be reissued using the actual system's supported process. A changed field does not necessarily stop existing work. Record each task's treatment and communicate it before movement. If physical progress is uncertain, establish where the goods are rather than canceling a screen entry and assuming nothing moved.

4. Approve the destination before taking goods there

Verify space, confirmed load capacity, access, handling method, labels, client restrictions and location status. Check the practical route and staging arrangement without obstructing aisles or exits. The site lead resolves a fit or safety issue before goods leave the source. An attractive candidate remains unapproved until those checks pass; workers should not improvise another destination while holding stock that no longer fits the plan.

5. Record the physical move through the supported process

The operator checks owner, SKU, unit, quantity, source and destination and preserves intermediate locations where needed. Verify actual placement and any remaining balance. Do not add destination quantity without accounting for the source, or rename a bin and claim that the goods moved. New receipts still follow their own receiving and putaway process; a slotting change is not another receipt of the same goods.

6. Verify the settings that actually choose stock

The configuration owner checks pick and reserve locations, priorities and related tasks against the approved plan. Physical closeness does not ensure the WMS selects a location first. ShipHero's June 2026 guide says lower Pick Priority numbers take precedence; the setting excludes non-pickable bins, lot and expiration rules override it, and equal priorities use the location with the lowest item quantity. These are ShipHero conditions, not all-WMS rules or a promise of globally optimal travel. Verify the actual account and workflow before release. ShipHero Pick Priority

7. Validate a small set of orders

The inventory reviewer runs controlled checks for ordinary orders, multiple-unit lines, similar variants and relevant multi-client identity cases. Confirm which location the work actually selects, the quantity available there and the path the operator can use. A correct setting screen is not a successful pick. Keep unexpected results assigned to the reviewer and keep affected work controlled while they are resolved. Record observations without inventing a successful result in advance.

8. Communicate the activation and release

The outbound lead tells affected shifts when the approved version becomes active, how labels and routes change and whom to contact for exceptions. Confirm the team received that instruction, including staff who did not participate in the move. Resume affected orders only after stock, records, settings and order checks pass. Memory of the old location should not become a parallel picking rule after the cutover.

9. Review and restore through a controlled move

The supervisor reviews searching, inconsistent records or obvious new congestion, which can trigger control of the affected scope and a review. If restoration is chosen, verify the current goods, quantities, task state and eligible destination, then use the supported movement and configuration process again. Do not restore an old screenshot as if no transactions occurred. Check validation orders, brief the next shift and close the change only when the physical and recorded state agree.

6. Which measures show a real improvement?

Look at three levels: the picking process, total work and final fulfillment. Separate walking, searching, handling and waiting rather than reporting a single faster-pick claim. Add replenishment, verification, error handling and ongoing placement maintenance to the work comparison. Finally check completion and handoff for comparable orders; a faster local step can coexist with a later finished order if another queue grows.

MeasureNumerator, denominator and boundary
Person-minutes / 100 completed linesRelevant labor person-minutes ÷ distinct completed lines in the same defined scope × 100. Report activities included; keep one-time move work separate
Comparable route distance / timeTotal observed distance or elapsed time ÷ completed comparable routes; retain route definition, mix and batching method
Replenishment person-time / tripsTotal refill person-minutes and completed trips in scope/period; counts, not percent; compare against the same demand scope
Search, error and check eventsDistinct events by type in scope/period; keep item/client and affected work. Count by type; keep client and variant outcomes separate
Congestion waitObserved occupied person-minutes waiting in the defined routes/window; separate from unoccupied elapsed queue time
On-time completion / handoffDistinct affected orders meeting their defined deadline ÷ affected orders due in period; report completion and carrier handoff separately

Use person-time per 100 completed order lines with a declared activity boundary, numerator and denominator. Track route distance or time per comparable route separately from units and visits. Keep replenishment minutes and trips, search and error events, verification work and congestion waits visible. These measures can explain a tradeoff even when the final output is unchanged. Do not net errors across clients or variants to produce a reassuring accuracy total.

Compare like periods and work. Record client and SKU mix, promotions, order size, staff numbers, experience, shift and batching method. Include learning and disruption from the change instead of silently dropping difficult observations. Lower order volume is not proof a new layout is more efficient. If the mix changed substantially, use a narrower matched comparison or continue the trial rather than attributing the difference entirely to placement.

Use compatible time measures. Sum staff effort as person-time when people work together; a task's elapsed duration is a different measure. Include waits that actually consume staff attention or prevent the next operation, and identify their boundary. Do not mix eight seconds of worker effort per visit with a replenishment duration measured on another basis. Keep both elapsed order time and effort where the bottleneck matters, without promising that one minute saved in either becomes an immediate cash saving.

Separate predicted from observed benefit. The four cases above are calculations and decision examples; a live pilot needs its own evidence. Review feedback with pickers and replenishment staff, check whether the same problem repeats, and preserve rejected options. A position can be retained with a revised replenishment plan, modified or restored. The decision should state which comparison supports it and which constraints still limit the result.

7. How can a small team organize a usable pilot?

Use the two worksheets below to carry the proposal and trial through shifts. Keep the web view compact, with grouped identity and evaluation fields; the downloadable records can expand those into separate columns. The candidate worksheet records why a move is worth testing. The trial worksheet records whether it should remain. Neither should become a competing inventory ledger alongside the authoritative warehouse records.

Candidate worksheet: groupFill before approving a move
Identity and locationClient; warehouse; SKU; current location; candidate location
Activity and fitPeriod; lines; actual visits or labeled proxy; dimensions and weight; picking unit; capacity
Tradeoffs and decisionRelated products; lookalike risk; refill burden; expected benefit; move cost; owner; decision and reason
Copyable fileDownload candidate CSV
Trial worksheet: groupFill at activation and each review
Comparison setupScope; baseline period; activation time/time zone; conditions; plan version and review owner
Observed resultPerson-time change; refill change; picking/search events; congestion; order completion; worker feedback
Next actionKeep/modify/restore decision and reason; next review/expiry; supported restore record
Copyable fileDownload trial-review CSV

Choose a limited area, agree the baseline and comparison conditions, then make one controlled set of changes. Define activation, review and restoration responsibilities before starting. Check the first affected work and a representative operating window before expanding. When evidence is weak, improve the measurement or retain the current arrangement; buying a dedicated optimizer is not a substitute for identifying the work and keeping locations accurate.

Once goods and orders are ready, complete packing and use actual parcel data for available shipping services. EasyShippingX supports Portal, Excel upload and API paths for enabled-channel rate, label, tracking and billing workflows. Confirm the account's actual options and carry the parcel through the carrier handoff checklist. Slotting can change warehouse work; it does not set a carrier's base rates or replace the physical handoff.

Warehouse slotting FAQ

Slotting chooses a suitable position. Putaway executes storage there and records it. An approved plan does not establish that stock has physically moved or is available to pick.

For a picking-work objective, investigate actual activity with product fit and replenishment included. Revenue and units provide context; order lines remain a proxy unless their relationship to visits is verified.

Not for a limited controlled pilot with reliable location records, supported moves and named owners. Choose tools after identifying a control or analysis gap; a spreadsheet must not become a conflicting stock ledger.

Potentially, if the actual WMS, stock attributes and operating process support them. Verify selection priorities, usable balances and refill controls, and keep each client’s ownership distinct. Multiple addresses alone do not optimize placement.

Set reviews around demand changes, recurring congestion, refill or accuracy problems and temporary-slot expiry. Use a cycle that fits the warehouse; changed demand warrants a review, not automatically a move.

Sources and methodology

Sources reviewed November 10, 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.