when-push-over-delivery-looks-like-good-service
title: "When push over-delivery looks like good service" description: "Push logistics often delivers extra boxes to feel safe. Documented pull cases cut patrolling and phone traffic while RTLS cases cut delays and fleet waste once the right-time habit sticks." slug: "wiki/when-push-over-delivery-looks-like-good-service" type: wiki format: html section: "logistics-optimization" sectionTitle: "Logistics Optimization" topic: "impact" topicTitle: "Impact" readTime: "6 min read" order: 9
A driver drops two extra boxes at the station so the line will not call again. The aisle fills. The next truck hunts for space. The line still starves later because the wrong mix arrived early and the right part stayed in the buffer. Push felt like service. It was congestion with a polite story.
What over-delivery hides on the floor
Under a push habit, loading and unloading often rest on experience. Drivers patrol production looking for needs. They deliver more boxes than needed so they will not be blamed for a shortage. Time burns in empty driving. Floor space burns beside the line. New drivers take longer to learn because the system lives in people's heads, not in claimable jobs.
Industry pull and e-Kanban practice exists to stop that protective overstock at the station. twinzo's AOS (commonly known as FGS) turns the line need into a visible work order under material order automation. Live paths under internal logistics optimization show whether empty returns and buffer dwell still follow the old push habit.
What pull changed when boxes stopped arriving early
On a documented 30,000 m² (about 323,000 ft²) automotive Tier-2 plant, the operator presses a button for an empty or full box exchange. Production needs appear on a tablet in the forklift in real time. Operator-to-driver phone calls fell by about 90%. Patrolling fell by more than 95%. Parts arrive when claimed, not when a driver guesses.
On a documented 55,000 m² (about 592,000 ft²) white-goods plant, the same pull class recovered about +20 minutes of production daily, eliminated micro-stoppages, and recorded €5,080,000 increased production value in year one against €100,000 invested. Empties as a first-class call-off sit under empties as a first-class call-off. Line minutes sit under twenty minutes of production back every day.
What path proof adds after push leaves
Once claimable jobs replace protective drops, RTLS shows whether delays and empty corridors actually left. A documented Tier-2 RTLS case cut fleet from 36 to 20 forklifts and drivers from 108 to 60, eliminated delivery delays, and saved €960,000 OPEX in year one against €120,000 invested. Another Tier-2 RTLS case lifted productivity from 63% to 75% and freed four FTEs when empty runs became countable.
Over-delivery is a WIP and congestion problem dressed as helpful logistics. Lower WIP when search time falls is also why plants fund location for material, not only movers. Fleet impact sits under when buying more forklifts is the wrong first answer.
What the record keeps after the habit change
Closed call-offs and paths fill the spatially oriented dataset. Correlation and causality analytics can ask which protective early drops still precede aisle blocks or starves. Continuous improvement owns that question beside the logistics desk that killed push.
How teams decide push is no longer acceptable
1. Count extra boxes left at line-side that were not requested on one peak shift - Over-delivery becomes a number.
2. Measure empty patrol and phone share on the same loop - High search usually feeds the push habit.
3. Pilot button or scan call-offs for empty and full exchanges before a hall-wide cut - Wire triggers under request triggers in the workflow editor.
4. Keep production monitoring on the same map - Line space and waits belong under production monitoring. Capability depth sits on the features overview. Rollout shape is under pricing.
Get in touch if you want to walk whether your “helpful” early drops are still the congestion your fleet keeps paying for.