There is quite a bit, potentially, to something like this. None of it is, to my mind, a very good fit for Rapidweaver however, because RW is primarily a front end tool when the emphasis on that front-end is to be found in design/content rather than custom functionality.
What would I do? I would, as a minimum viable product, be thinking about a (for example) Java Spring Boot or Go Web Services or even a Python Django back end being driven by a bunch of client agnostic API’s.
A nice separation of concerns type model would then be possible where the back and front ends could be logically de-coupled allowing features to be built, tested and implemented with minimal impact and manageable dependencies on each other.
Front end could be a full on App or a web UI which could allow the servers to select the table, the order in that ‘batch’, the running total of the bill, even the specifics about which customer, in which seat ordered what and when. A simple front end could be selections from a table with buttons. A more sophisticated implementation could be where the up to the minute menu contents might be pulled down from a menu API on the back end thus providing a single persistence layer to ensure data freshness across all the clients that implement their menus using that API/endpoint. That data could be controlled by a restaurant manager client with the ability to edit. Whether data driven custom app or web client, on the front end, it will probably come down to pushing and pulling HTTP APIs while implementing, more or less, states and models,
Back end could be just about anything, but something like Java Spring (Boot) might be ideal, Go makes web services a walk in the park and you also have Pythons Django and Flask, if thats your thing. Each have nice and easy SQL/NoSQL integrations and loads of potential for nice looking bill generating integrations. Remember that there is no reason why these frameworks could not also host your RW built front end - but would you want to?
You would probably want a different client for the kitchen - something that can tickertape or dashboard, compartmentally, the order views. It might be nice to include kitchen workflow feedback meta in that client to allow kitchen to set states for ‘order accepted’, 'order being prepared, ‘order ready’ – all that type of stuff would enrich the server client workflow (such as menu refreshes when something goes off the menu) and catch useful analytics about how long things are taking and other potential workflow or consumer data.
I’m not aware of anything in Rapidweaver, specifically, that would be a good fit for this in the sense that you would not need to write some of the code, but I could easily be wrong as I have not used RW for a few years now and I’m probably out of date … and I may be overthinking what you are trying to do anyway.