Do crews need a connection in flight?
No. The count is saved on the phone after every tap and the report queues in an outbox. It sends on the next connection, and sending twice cannot create a duplicate. Sent reports stay on the phone for 30 days.
Who decides where the stock goes?
Operations does. Crews never enter a destination, because routing can change minutes after they file. The desk types the next stop from the published schedule, and every short line is read against that hub's on hand, min and max before anything is pulled or ordered.
Can two people act on the same order at once?
They can try. Every status change, pull and receipt runs as one transaction against the current state, so the second attempt is refused with a message rather than applied twice. Order numbers come from a counter, so two desks cannot issue the same number.
What does purchasing receive?
A numbered supply or restock order with a printable form and a CSV of the lines: item, section, quantity, unit, on hand, min and max. It is meant to be raised in whatever purchasing system you already run.
Where does our data live?
In a database project that is yours alone, with sign-in roles enforced on the server. The apps are built with your name, logo and colours, and distributed privately through Apple Business Manager and Managed Google Play or your own device management.
How is our inventory structure loaded?
From your documentation: fleet types, sections in walk order, items with REQ per fleet, tail numbers, locations, and hub stocking levels, supplied as spreadsheets. Nothing from the demonstration is included in a customer build.