Empties as a first-class call-off
The line got its full cage in eight minutes. The empty sat for forty. Nobody owned the return until someone yelled on the radio again.
Why empties lose when they are not a real job
Full material call-offs usually have a button, a template, and a driver group in AOS (commonly known as FGS). Empties, scrap, and return pallets often stay informal. Drivers finish a drop and "see" the empty when they feel like it. Buffers fill with dead wood. The next full load has nowhere clean to land. Plants treat empties as courtesy work until the hall chokes.
Classic withdrawal kanban depends on collecting the empty container with the freed card. If empties pile at the station, the supermarket and upstream loop lose containers and the pull signal breaks. A first-class empties call-off means the same marketplace path as a full: a trigger, a claimable work order, a group that may accept, and a record of who took it. How any floor request becomes that work order is under how a floor request becomes a work order.
Milk-run return legs vs direct forklift empties
Many milk runs deliver fulls on a tugger train and collect empties on the same lap. That is the right first answer when empties appear where the tour expects them. When lines run slower than theoretical consumption, full trolley drops still land on the clock while empties pile at uneven times between stops. Drivers tied only to the itinerary leave the fence full until the next planned collect.
Pallet-size empties and irregular returns usually need a direct forklift call-off, not a wait for the next tugger lap. Keep milk-run empty collect as baseline on the loop. Add AOS forklift empties where the return leg is folklore. The vehicle and stage split is under milk-run orders vs direct forklift orders. The capacity mix is under milk runs on theoretical consumption vs dynamic pull across lines.
How to put empties on the same rails
Give empties their own request type in the workflow editor. Bind milk-run empties to the tugger delivery group when they ride the return leg. Bind irregular pallet empties to a forklift empties group, not the dock trailer pool. Priority can sit below a true line starve and still above silent folklore. When movers are tracked, empty-return paths feed the same spatially oriented dataset as loaded trips, so empty travel reviews include the return leg.
Template and group setup sits under request triggers in the workflow editor and how to size and split driver groups. Offer scope remains group broadcast, not nearest-truck routing, as under group broadcast vs nearest-truck myths.
A typical buffer that only cleared after empties became jobs
A packaging lane pressed full-material buttons all morning. Empties stacked along the fence until a supervisor walked the aisle. The milk-run tugger collected what fit the planned stops and left the rest. After irregular empties got a station button into a forklift empties group, returns entered the list within a minute of the drop. Drivers claimed them between pallet jobs. The fence cleared without a second radio channel. The change was making the return a work order, not adding trucks.
How teams decide empties deserve a template
1. Time how long empties sit after a full drop on one busy loop - If they outlast the full-material wait, they need a call-off.
2. Decide milk-run return leg vs direct forklift empty - Keep the tour if it clears the loop. Add forklift AOS if it does not.
3. Give empties a named request type and the matching vehicle group - Do not bury them as a note on the full-material job.
4. Keep empties priority below true starves, above silence - Otherwise they vanish again.
Call-off automation sits under material order automation and internal logistics optimization, with depth on the features overview. Pricing is under pricing.
Get in touch if you want to walk whether empties on your floor already open as work orders, or still wait for someone to notice the fence.