Request Trigger

A request trigger is the named event that starts an internal logistics ask. On the floor it is often a station button, barcode or [RFID](https://www.twinzo.com/glossary/rfid-radio-frequency-identification) scan, touchscreen choice, [Andon](https://www.twinzo.com/glossary/andon)-style call-for-parts panel, or [e-Kanban](https://www.twinzo.com/glossary/e-kanban) flip. From systems it is often a [MES](https://www.twinzo.com/glossary/mes-manufacturing-execution-system) or other machine message over an [API](https://www.twinzo.com/glossary/api-application-programming-interface). The trigger does not move material by itself. It opens a [material call-off](https://www.twinzo.com/glossary/material-call-off) into a claimable [work order](https://www.twinzo.com/glossary/work-order) once the plant maps it to an order template. Plant teams care because incomplete triggers recreate radio. Drivers then see jobs missing destination, material class, or vehicle stage and fall back to voice. Industry [forklift guidance system](https://www.twinzo.com/glossary/forklift-guidance-system) (FGS) and e-Kanban products make the same demand: the signal must become a logistics task with status and fields, not only a dashboard color. twinzo [AOS](https://www.twinzo.com/glossary/aos-automated-ordering-system) (commonly known as FGS) uses the workflow editor to bind each trigger to material classes, priority, destination zones, and the milk-run or direct forklift template that should open. ## Key Components **Source event**: Button, scan, screen, card flip, Andon call, or system message. **Field mapping**: Material ID, quantity, origin, destination, and priority filled without free text at claim time. **Order template**: Multi-stage supermarket-to-tugger milk-run path, or direct forklift bring / empty remove. See [milk-run orders vs direct forklift orders](https://www.twinzo.com/glossary/milk-run-orders-vs-direct-forklift-orders). **Driver group scope**: Which [driver group](https://www.twinzo.com/glossary/driver-group) may see and accept the resulting work order. **Device binding**: Each physical button, scanner, or terminal points at exactly one request type. ## Applications in Manufacturing and Logistics Assembly halls use triggers to open supermarket prep then tugger delivery on fixed [milk run](https://www.twinzo.com/glossary/milk-run) loops, and to open direct [forklift](https://www.twinzo.com/glossary/forklift) pallet jobs at stations. Continuous improvement uses closed trigger history to see which stations still shout on radio and which templates produce incomplete offers. Product setup lives under [material order automation](https://www.twinzo.com/material-order-automation) and [request triggers in the workflow editor](https://www.twinzo.com/wiki/request-triggers-in-the-workflow-editor). ## Benefits and Challenges The benefit is a complete claimable job from the first second, plus a dispatch trail for later place-and-time review. The challenge is mapping discipline: every real ask path must be listed, including radio leftovers, or people keep a parallel channel and the digital pool stays thin. ## Related Terms [Material call-off](https://www.twinzo.com/glossary/material-call-off), [AOS](https://www.twinzo.com/glossary/aos-automated-ordering-system), [forklift guidance system](https://www.twinzo.com/glossary/forklift-guidance-system), [e-Kanban](https://www.twinzo.com/glossary/e-kanban), [work order](https://www.twinzo.com/glossary/work-order), [driver group](https://www.twinzo.com/glossary/driver-group), [MES](https://www.twinzo.com/glossary/mes-manufacturing-execution-system). ## Frequently Asked Questions **Is a request trigger the same as a work order?** No. The trigger is the event. The work order is the claimable job the trigger opens after template mapping. **Does location pick which driver sees the trigger?** No. Offer scope stays the configured driver group. Location records acceptance place and path when movers are tracked. **Can MES and a button both fire for the same need?** Yes, and that often creates duplicate jobs. Pick one primary source per loop and merge duplicates. See [when MES should open the job vs when the line button should](https://www.twinzo.com/wiki/when-mes-should-open-the-job-vs-when-the-line-button-should). **Where does twinzo configure this?** In the workflow editor under [material order automation](https://www.twinzo.com/material-order-automation), with the how-to under [request triggers in the workflow editor](https://www.twinzo.com/wiki/request-triggers-in-the-workflow-editor).