Summary
Task interleaving is a warehouse management system (WMS) function that gives a forklift driver or warehouse worker the next nearby task the moment they confirm the last one, instead of sending them back empty to the dock or a fixed start point. It mixes putaway, replenishment, full-pallet picks, cycle counts and staging moves into one continuous sequence per resource. The payoff comes in pallet operations where those flows overlap in time and space. With the wrong settings it backfires, splitting work into many short tasks, breaking into open pick tours or pulling several trucks to the same dock door.
In a pallet warehouse, much of the forklift travel is decided before a driver turns the key. The WMS chooses which task comes next, and if that choice ignores where the truck is standing, every putaway ends with an empty run back to goods receipt. That empty run is called deadheading, and removing it is the reason interleaving exists.
Switching interleaving on is one setting. How it is tuned decides whether it saves travel or adds work: badly set, the same feature that removes empty runs can flood a queue with 15 meter moves, interrupt pick tours and send three reach trucks to one dock door.
For the manager who owns the warehouse process, the practical questions are which tasks to mix, how the WMS picks the next one, when interleaving pays and what to change when it stops paying. Batching and wave picking also cut travel, so it helps to know where interleaving ends and they begin.
What is task interleaving in a warehouse?
Task interleaving means combining different types of warehouse tasks into one continuous sequence for the same resource: a forklift, a reach truck or a worker. The end point of one task becomes the starting point of the next. SAP's documentation describes it as replacing "one-way work assignments and travel with bi-directional work assignments."
The problem it removes is deadheading, when a forklift travels in one direction to do a task and returns empty. Without interleaving, a driver who finishes a putaway in a far aisle drives back to goods receipt for the next pallet, even when a replenishment is waiting two aisles away.
A worked example: three tasks, one reach truck
Take three open tasks: a putaway from the dock to aisle 14, a replenishment from reserve to a pick face in aisle 13, and a full outbound pallet in aisle 13 that has to go to the dock. The distances are our own illustration and were not measured.
Without interleaving, the three tasks cost 530 meters of driving, 345 of them empty. Each task starts and ends at the dock:
- Putaway: 90 m loaded to aisle 14, then 90 m empty back.
- Replenishment: 85 m empty to aisle 13, 10 m loaded from reserve to the pick face, then 85 m empty back.
- Outbound pallet: 85 m empty to aisle 13, then 85 m loaded back to the dock.
With interleaving, the same three tasks take 197 meters, and only 12 of them are empty. The truck drops the inbound pallet in aisle 14 after 90 m, drives 8 m empty to the reserve location in aisle 13 and moves the replenishment pallet 10 m. It then drives 4 m empty to the outbound pallet and carries it 85 m to the dock.
The example flatters interleaving on purpose. It only works because the three tasks were open at the same time, in neighboring aisles, for the same truck type. Remove any one of those conditions and most of the gain disappears.
Which tasks get interleaved?
- Putaway: inbound pallets from the dock or a staging lane to reserve or pick locations. Usually the task that starts the chain.
- Replenishment: a pallet or case from reserve to a pick face. The natural partner for putaway, because both happen in the storage aisles.
- Full-pallet and case picks: outbound pallets taken to the dock or a marshalling lane. Often the task that brings the truck back to the dock loaded.
- Cycle counts: a count of a location the truck passes anyway, slotted in where the operator already is.
- Staging and internal moves: empty pallet returns, moves between zones and consolidation of half-empty locations.
Interleaving is mostly a forklift and pallet practice. A piece picker with a cart is usually tied to the orders on that cart until the tour ends. For that picker, travel depends on the batch and the route.
How does a WMS decide which task comes next?
A WMS runs interleaving every time a task is confirmed. The driver scans the drop, the system looks at the open tasks this resource is allowed to do, scores them, and sends the next one to the scanner.
Four inputs drive that choice in most systems. The names differ per WMS, but the logic is close:
- Task pool and queues. Open tasks sit in queues, usually per task type and area: inbound putaway, replenishment, outbound. A queue sequence tells the system which queue to look at next for each group of resources.
- Priority. Due time, carrier cut-off, or an empty pick face that is stopping pickers. Urgent work can override distance.
- Proximity. The distance from where the resource stands now to the source location of each candidate task.
- Equipment and zone eligibility. A counterbalance truck cannot work a very narrow aisle, and a reach truck may be barred from the yard. The WMS only offers tasks the resource type is allowed to do.
Task interleaving in SAP EWM
SAP EWM calls the function RF interleaving and switches it on per resource type. The SAP S/4HANA documentation for Extended Warehouse Management gives this example: "after putaway, a fork lift does not return empty to the goods receipt area, instead it is given a new task before returning to that area, such as a stock removal order."
The same page sets out the decision rule. After each confirmed warehouse task, the system "determines the distance, in order to find out the task that is geographically closest for the resource." Each interleaving-relevant queue is assigned to a queue type and a queue sequence.
In standard RF processing, one queue is worked until it is empty. With interleaving, the next task comes from another queue in the defined sequence. SAP lists the function as available only within system-guided processing.
The queue sequence and the distance rule are where most tuning happens, in SAP EWM and in other systems. The queue sequence decides which kinds of work may follow each other. The distance rule decides which task wins inside those queues.
When does task interleaving pay off, and when does it not?
Interleaving pays when different task types are open at the same time, in the same area, for the same truck type. The worked example met all three conditions. A week of task history shows whether an operation does, before any setting changes.
Where it pays
- Pallet operations where inbound and outbound overlap during the day, so putaway and outbound pallet picks are open together.
- Long distances between the dock and the storage aisles, where every avoided empty return saves a lot of meters.
- Steady replenishment from reserve to pick faces in the same aisles where putaway happens.
- One truck type serving most aisles, so the WMS has many eligible tasks to choose from.
Where it does not
- Flows separated in time. If inbound runs in the morning and outbound in the afternoon, there is rarely a second task type to mix in.
- Trucks locked to aisles. A very narrow aisle truck that serves one aisle or a small group of aisles has a small pool of eligible tasks.
- Zones that do not overlap. If putaway goes to the back of the building and replenishment happens at the front, the nearest next task is still far away.
- Piece picking with carts, where the picker is tied to the orders on the cart.
- Goods-to-person automation, where the system already sequences storage and retrieval in combined cycles.
Interleaving also trades travel against priority. Each time the WMS hands out the nearest task, a more urgent one may wait. Close to a carrier cut-off, priority has to win.
Our piece on time-aware scheduling in order fulfillment covers that trade-off: it plans work by due time first and by walking efficiency second. With a distance rule and no deadline check, trucks can leave late while the travel report looks good.
Signs your task interleaving settings are working against you
Most interleaving problems are configuration problems that show up on the floor. Drivers and pickers follow the scanner. When the scanner sends them on odd routes, the setting is at fault. Four patterns come up most often.
The WMS creates too many short travel tasks
A queue full of 15 or 20 meter moves looks efficient on a distance report. Each task still carries a fixed cost: scan the source, lift, drive, scan the destination, confirm. When the handling time per task is larger than the travel it saves, interleaving costs more work than it saves.
Typical causes are replenishment triggers set so low that a pick face is topped up one case at a time, and housekeeping moves released into the same queue as putaway.
Pick tours get interrupted
Some setups let the WMS insert a replenishment or a count into an open picking tour because it happens to be close. A pick tour that is broken open loses its sequence. The picker returns to a route that no longer starts where they stand, and the order can miss its staging time.
Interleaving belongs at task boundaries: after a drop is confirmed, never halfway through a tour.
Trucks pile up at the dock doors
Distance rules favor the task closest to the truck, and after a drop at the dock the closest tasks are often at that same dock. Several trucks get pulled to the same doors at the same time, wait for each other, and block the lanes loaders need. A truck parked in an aisle has the same effect on pickers working nearby.
Urgent work waits behind nearby work
If proximity always wins, an empty pick face on the far side of the building can wait while trucks shuffle nearby pallets. Pickers then arrive at an empty location. A priority rule that overrides distance for replenishments that block picking fixes this.
How to tune task interleaving settings
Measure before you change anything. Every WMS logs confirmed tasks with a source, a destination, a resource and a timestamp. A week of that log shows how much of each truck's distance is driven empty, per resource type, per shift and per zone.
That empty share is the number interleaving is supposed to move. Seven steps decide whether it does, though the exact screens differ per WMS:
- Empty travel per resource type. The distance from the last drop to the next pickup, summed per truck type and shift. This is the baseline; without it, any change is a guess.
- A queue sequence per resource group. Which task types may follow which. Putaway followed by replenishment or a full-pallet pick in the same zone is the usual pairing.
- Bundled small moves. Small replenishments for the same aisle released together, or a minimum task size, so the truck makes one trip instead of five.
- Priority overrides with a clear trigger. Replenishments that stop picking and outbound pallets close to carrier cut-off jump the distance rule. Everything else follows proximity.
- Interleaving at task boundaries only. No inserts into open pick tours; the next task is offered after the drop is confirmed.
- A cap per dock door or staging lane. A limit on how many trucks can hold tasks for the same door at once spreads the work across doors and lanes.
- A weekly review. The same empty-travel number, plus pick-face stockouts and dock waiting time, so a gain in one place is not paid for in another.
Replenishment timing matters as much as the interleaving rule. A replenishment released ahead of demand can wait for a truck that happens to pass; an emergency replenishment cannot.
Our article on why replenishment deserves more attention covers triggers and work distribution in more depth. When replenishment runs ahead of the pickers, interleaving has tasks to fit into each truck's route.
How is task interleaving different from batching and wave picking?
Task interleaving, batching and wave picking work on different layers of the same operation. All three cut travel, which is why they get confused. Interleaving sequences the tasks one resource does across task types, batching decides which orders go into one pick tour, and wave picking decides when work is released to the floor.
| Task interleaving | Batching | Wave picking | |
|---|---|---|---|
| What it decides | Which task a truck or worker gets next, across task types | Which orders are picked together in one tour | When groups of orders are released to the floor |
| Typical resource | Forklifts and reach trucks | Pickers with carts or trolleys | The whole picking and packing team |
| When it runs | At every task confirmation | Before a tour starts | Per wave, several times a shift |
| Main saving | Empty travel between tasks | Walking per order line | Coordination with packing and shipping |
| Typical failure | Short tasks, interrupted tours, dock pile-ups | Batches that ignore cart capacity or due times | Waves sorted by arrival time or order number |
View this comparison on desktop for the full data table.
Our guide to wave picking in warehousing covers wave release, and cluster vs batch picking explains the difference between grouping orders on one trolley and picking them as one batch.
Where the larger travel saving sits for order picking
For pallet moves, interleaving is the main travel lever. For order picking, the bigger lever sits inside the tour: which orders share a trolley, and in which sequence the picker walks the locations.
Travel is the most expensive activity in picking, at 55% of picking time in the figure Bolaños-Zuñiga and colleagues cite. Order picking itself accounts for up to 55% of all warehouse operating costs, according to Ueno and Hirata.
Many WMS setups build pick tours with simple rules: orders in arrival or order-number sequence, and routes that follow location numbering. Those rules do not calculate whether a different grouping of orders would shorten the walk.
Where an optimization layer fits
Optioryx Pulse works on that layer, on top of the WMS you already run. Pulse groups orders into batches that respect cart capacity, weight and cut-off times, and sequences each tour along the real aisle layout, one-way aisles included.
The WMS keeps executing: it still assigns the tasks, drives the scanners and runs its own interleaving logic. Across customer deployments, clustering, routing and slotting together cut walking distance by up to 50%.
Pulse leaves forklift task sequencing to the WMS. It changes the picking work the WMS hands out, and you can check the effect on your own order history in the web app before any integration. The steps are in our article on how warehouse optimization software reduces travel time.
Questions?
Task interleaving is a WMS function that assigns a forklift, reach truck or worker their next task close to where they just finished, instead of sending them back empty to a fixed start point. It mixes task types such as putaway, replenishment, full-pallet picking, cycle counts and staging moves into one continuous sequence. The goal is less empty travel, also called deadheading.
Task interleaving decides which task a resource does next across different task types, and it runs every time a task is confirmed. Batch picking decides which customer orders are picked together in one tour, before the tour starts. Interleaving mainly cuts empty forklift travel between tasks, while batching cuts walking per order line inside a pick tour.
In SAP EWM, RF interleaving is set per resource type, and each interleaving-relevant queue is assigned to a queue type and a queue sequence. After each confirmed warehouse task, the system determines the distance to find the task that is geographically closest for the resource, taking the next task from another queue in the sequence. SAP documents the function as available only within system-guided processing.
Look at the replenishment triggers and the queues first. Short tasks often come from replenishment set to top up pick faces in very small quantities, or from housekeeping moves released into the same queue as putaway. Releasing small moves for the same aisle together, setting a minimum task size and keeping housekeeping in its own queue cut the number of trips.
No. Task interleaving stays in your WMS, which keeps assigning forklift and worker tasks. Optioryx Pulse works on the picking work the WMS hands out: it groups orders into batches and sequences pick routes on top of the existing WMS. Across customer deployments, clustering, routing and slotting together cut walking distance by up to 50%.