Empties as equal call-offs
Empty containers, scrap, and return pallets need the same call-off path as full material. Give them a trigger, a claimable work order, and a driver group that may accept.
What an empties call-off is
A full material call-off usually has a button or scan, a template, and a driver group in twinzo AOS (commonly known as FGS). An empties call-off is the same kind of claimable job as a full bring, aimed at remove or return: origin at the station or buffer, destination at the supermarket, wash, scrap, or empty store, plus load class, priority, and a group that may claim. It is not a note on the full-material job and not a radio courtesy after the drop.
Plants often fund full bring templates first and leave empties informal. Drivers finish a delivery and take an empty only when capacity happens to allow it. Buffers fill with unused packaging. The next full load has nowhere clean to land. Treating empties as equal jobs in internal logistics restores ownership without inventing a second radio channel. How any floor request becomes that claimable work order is under how a floor request becomes a work order.
Why informal empties break pull
Classic withdrawal kanban depends on collecting the empty container with the freed card. The handler returns both to the supermarket, exchanges onto a full unit, and leaves the production signal for upstream replenishment. When empties pile at the station, the supermarket and upstream loop lose returnable packaging and the pull signal breaks even while full-material buttons still fire. Lean manufacturing already treats that break as a process failure, not a soft housekeeping gap.
Digital e-Kanban and station call-offs keep the same rule only when empty remove is a configured request trigger. Inventory management can show healthy part counts while physical containers sit along the fence. The operating fix matches a full bring: trigger, claimable work order, acceptance, and close. Wiring those triggers is under request triggers in the workflow editor.
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 baseline when empties appear where the tour already stops. Milk-run design often sizes the circuit to theoretical consumption. When lines run slower than plan, full trolley drops can still land on the clock while empties appear at uneven times between stops. Drivers tied only to the itinerary leave irregular empties until the next planned collect.
Pallet-size empties, scrap exceptions, and returns that cannot wait for the next lap usually need a direct forklift call-off. Keep milk-run empty collect on the tugger loop. Add forklift empties where the return leg is unreliable or the load unit does not fit the train. The vehicle and stage split is under milk-run orders vs direct forklift orders. How milk-run capacity and dynamic forklift pull share a hall is under milk runs on theoretical consumption vs dynamic pull across lines.
How to put empties on the same call-off path
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 stay high enough that empties remain visible on the open list. Offer scope stays group broadcast, first accept wins, not nearest-truck routing, as under group broadcast vs nearest-truck myths.
Template and group setup sit under request triggers in the workflow editor and how to size and split driver groups. Product depth for call-off automation is under material order automation. That configuration is a practical smart manufacturing move only when empties enter the same open list as fulls, not a parallel spreadsheet.
What the closed empties trail records
Live shift work needs empties claimable so buffers clear without a second coordination channel. That is the live logistics job on the hall the plant already runs. When movers are tracked, empty-return paths land in the same spatially oriented dataset as loaded trips, so the stored place-and-time record includes the return leg instead of only full brings. Continuous improvement and later review then use correlation and causality analytics on which empty clusters keep preceding a starve or a blocked drop face.
Those three uses stay equal: clear buffers on the shift, keep the spatial replica honest, and learn which return gaps repeat. Measured empty travel reviews that include return legs sit under loaded vs empty travel you can prove. Hall-level logistics optimization sits under internal logistics optimization, with capability depth on the features overview.
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 a direct forklift empties call-off 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, high enough to stay on the open list - Otherwise they vanish from the open list again.
Ordering and fleet use sit under material order automation and internal logistics optimization. Production waits on the same hall are under production monitoring. Pricing is under pricing.
Get in touch if you want to walk whether empties on your floor already open as work orders, or still depend on informal pickup after the full drop.