Count it the way you walk it.
Type the tail. The REQ list for that airframe loads in walk order: galley, forward lav, cabin, aft lav. Tap Good or count what is missing. Works in flight and sends on the ground.
- 01Turnover on every tail. The last inventory anyone filed on that aircraft, with what was short and whether it is staged.
- 02Offline by design. Counts queue and send on the next connection. A retry cannot create a duplicate.
- 03Cabin condition. Flag that the aircraft needs cleaning, with comments, on the same report.
- 04Updates that mean something. Being pulled at TEB, ready at TEB, on order for HPN, with the order number.
The pull order arrives on the floor, with a name on every step.
New, in work, completed. Acknowledge starts the pull and records who. Picked stages it for the aircraft and tells the crew. A stock count raises the restock order on its own.
- 01One location. A hub manager sees only their own hub's orders, stock and counts.
- 02Counts, not edits. Submit a count to HQ; anything at or below minimum raises a restock order back to max.
- 03Received adds to stock. On a ledger, with the order number and the person.
- 04Cancellations arrive with the reason. Pulled stock returns; the order leaves the queue.
A queue to work, not a dashboard to admire.
New reports wait for a destination. Each short line is read against that hub's on hand, min and max, with the action beside it: pull, order, or assign. Cancel with a reason and it all unwinds.
- 01Crews never enter routing. The desk assigns the next stop from the published schedule; every line re-reads against that hub.
- 02Numbered orders, no duplicates. One pull order per hub per aircraft. Two desks cannot issue the same number or double a pull.
- 03Forms purchasing can use. Print, download, or export a CSV per order into your own purchasing system.
- 04Audit log. Every destination, pull, order, cancellation, count and receipt, by whom, exportable.
Your data, your name, your app store.
Each customer runs on a database that is theirs alone, with the product named and branded the way their crews will recognise it, distributed through private channels.
- 01A database per customer. Reports, orders, stock and users live in your own project.
- 02Sign-in with roles. Crew, hub, operations, admin. Every action carries the person's name and ID.
- 03Transactions, not hope. Order numbers, status changes, pulls and receipts commit atomically.
- 04Private distribution. Apple Business Manager and Managed Google Play, or your own device management.
- 05Your inventory structure. Fleet types, sections, items, REQ, tails, locations and stocking levels from your documentation.
- 06Push notifications. New orders reach the hub device; progress reaches the crew.