What acceptance locks and what can still be reassigned
The forklift driver accepted the material call-off, then went on break. The job stayed locked to a name. The station waited while other trucks in the forklift group sat idle and could not see it.
What must freeze at accept
In twinzo AOS (commonly known as FGS), acceptance is the marketplace match. A work order that was visible to a driver group becomes owned by one person. That lock should capture who accepted, when, and where they stood if movers are tracked at medium precision around 1–3 m (3–10 ft). Without a lock, two drivers still collide. With a lock and no escape, a dead claim strands the line.
How the call starts that trail is under the call that starts the record. How the floor request became the work order is under how a floor request becomes a work order.
What must stay reversible
Warehouse RF systems already treat skip and exception as normal: an operator can release an unstarted order so another resource may take it, while a started order stays protected until confirmed or formally excepted. Mirror that discipline on the floor. Cancel by the acceptor when the load is gone or unsafe. Supervisor release when the driver is unreachable. Timeout that returns the job to the same group when no progress appears after a set number of minutes. Handoff to another member of the group when a shift ends mid-trip. Each path needs an owner and a reason code so the record stays honest for later review in the spatially oriented dataset.
Do not unlock casually because someone else is closer. Offer scope was never nearest-truck routing. Reassignment is an exception path, not a silent steal. Group broadcast rules are under group broadcast vs nearest-truck myths. Aged jobs that never reached a healthy accept are under rules for open jobs that age out.
Quiet milk-run drivers still need a clean lock
When a milk-run lap runs under theoretical load, that tugger capacity may free staffing for other work, but a driver who accepted a delivery stage still owns that train until cancel, timeout, or handoff. The same lock applies to supermarket prep and to direct forklift pallet jobs. Quiet capacity does not justify a silent steal if someone else is closer on the map. Otherwise the hall invents double claims the moment slack appears. Keep stages and vehicle groups separate so a forklift cannot unlock a tugger delivery by habit. The capacity mix is under milk runs on theoretical consumption vs dynamic pull across lines. The shapes are under milk-run orders vs direct forklift orders.
A typical stranded claim
At 15:50 a driver accepts a sequenced rack, then is pulled into a quality talk. Twenty minutes pass. The group list no longer shows the job. Idle trucks wait for something new. After logistics added a fifteen-minute no-progress timeout back into the line-feed group, the next stranded claim reopened automatically with a reason. The station recovered without a supervisor hunting by radio.
How teams decide lock and release rules
1. Require identity, time, and acceptance place on every claim - That is the lock proof.
2. Set a no-progress timeout that returns the job to the same group - Dead names should not hold the line forever.
3. Limit supervisor release to named roles - Casual unlock recreates double claims.
4. Review cancel and timeout reasons weekly - Patterns show training gaps or bad triggers.
Acceptance behavior 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 your accepts lock cleanly, or still leave stations waiting on a name that went quiet.