The daily friction still sitting in most internal logistics
An operator needs a stillage, picks up the radio, and a driver either answers or keeps circling. The calls pile up. The empty kilometres (empty miles) add up. Neither shows as a clean monthly line, yet both eat labor minutes.
Push logistics as the status-quo cost
Most plants still run internal material moves on a push model. Someone needs a pallet or a stillage, uses phone or radio, and a driver answers or keeps circulating until something appears. That friction is the actual cost of the status quo. It is measurable in call volume and in the share of forklift time spent searching rather than moving. It is also the part of the logistics equation that rarely gets priced before a decision is made.
Voice coordination impact is spelled out under phone calls still coordinate most internal moves. Empty-round cost on a large white-goods hall is under why empty forklift rounds still drain a white-goods plant.
What a 30,000 m² Tier-2 plant actually recorded
One documented automotive Tier-2 site of 30,000 m² (about 323,000 ft²) switched internal dispatch from push to pull with twinzo's AOS (commonly known as FGS) module. The measured change was about 90% fewer phone calls between operators and drivers and the elimination of over 95% of forklift patrolling. The source material supplies no euro investment or saving figure for this specific case. The operational-friction reduction itself is the benefit that was recorded.
The switch turned call-and-search into a marketplace-style pull: work orders appear, drivers accept, and the system logs who needed what, who took it, and when. Phone traffic and empty loops largely disappeared. That is the complete set of hard numbers available for this particular change. How the request becomes claimable is under how a floor request becomes a work order.
Why a missing euro figure does not erase the tradeoff
Phone time and unnecessary driving still consume paid hours and wear on equipment. When those two activities fall by the percentages reported, the plant recovers capacity without adding headcount or trucks. The cost side is setup: pull rules, triggers, and drivers learning to accept instead of wait. Because this case carries no euro numbers, the comparison stays operational: does the daily reduction in friction outweigh the one-time configuration effort?
Other plants in the same size band have published investment and OPEX figures for different modules. Those figures belong to those cases. Mixing them here would invent a number the source does not contain. The honest boundary is the call and patrol data that were actually measured. Closed calls still feed the spatially oriented dataset and later correlation and causality analytics when positions are stored with the jobs.
How to test the same tradeoff on your floor
1. Count daily operator-to-driver calls on a peak loop - Get a baseline before software talk.
2. Estimate empty patrol share on the same loop - Busy-looking trucks can still be searching.
3. Run a limited pull pilot for a few weeks - Wire triggers under request triggers in the workflow editor, then recount both metrics.
4. Keep euro claims out unless this pilot earns them - Do not borrow RTLS fleet-cut savings to justify a calling change. Which combination can clear about six months on this hall sits under the six-month return depends on the combination.
Product scope sits on material order automation and internal logistics optimization, with depth on the features overview. How a rollout is priced is on pricing.
Get in touch if you want to walk a push-to-pull pilot on one of your high-traffic loops before inventing a euro case the floor has not earned yet.