Howdy (to honor the local colloquialism, although it's hard to follow-up the romantic bonjour),
Thanks to the standard library template, two Honeycode specialists, and some grit there's a PO framework for my Team to use(including separate apps for requests and approvals). It's customized for the field operator to provide a large number of data points necessary for entry into our accounting system, including picklists for projects, vendors, standard purchase categories, purchase method, etc. and an automated approval routing to the appropriate individuals overseeing the project (each has the ability to approve, not a tiered approval workflow). After approved by a manager, a unique and sequential PO number is issued automatically to the field operator for communication to the vendor and stored in the table for accounting. Managers use mainly the desktop site whereas operators utilize the app almost exclusively as they are normally on the jobsite.
Previously we were fielding PO requests and approval in GroupMe, which was obviously a complete disaster for everything from communication lines, accountability, and retention to name just a field. As such, both the field personnel and managers love this system as it serves as a much more organized one-stop-shop.
The Honeycode Team has been extremely helpful and coordinated two calls with me so far to modify coding from the library template to suite my unique needs. Shout out to @Alyssa who solved my email notification issue last time which was the last hurdle in achieving full, daily utilization of the program. My experience with Excel and tables made the learning curve fairly manageable, but I think developing more robust training resources (basic guides and/or videos) would go a long way in helping newbies kick-off the process.
Integration with our accounting system (issued POs from Honeycode and vendor list/job list/phase list to Honeycode) is the next big challenge!