Hi Fraser Scott
Based on the scenario you've described, I would not view the 100 waiters/servers as 100 individual RDS users, since they are not authenticating to Windows or establishing their own Remote Desktop sessions. The key point is that the POS terminals are the devices connecting to the Remote Desktop environment, while the waiter card swipes are simply application-level actions inside your hospitality solution.
From a Microsoft licensing perspective, the decision generally comes down to whether you license RDS User CALs or RDS Device CALs. In an environment where a relatively small number of POS terminals are shared by a much larger pool of staff across multiple shifts, RDS Device CALs are typically the more appropriate and cost-effective licensing model. In your example, if there are 10 POS terminals accessing the RDS environment, you would normally look at licensing those 10 devices rather than every waiter who may use the application during the day.
That said, a single RDS User CAL per terminal would not normally be the correct interpretation, because User CALs are assigned to named users, not shared devices. If the terminals are the connection point and are shared by many employees, RDS Device CALs are generally the compliant approach. Each device that connects to the RDS server requires its own Device CAL, regardless of how many staff members use that device.
My recommendation would be to size the licensing based on the number of POS terminals connecting to the RDS environment and validate the final design with your licensing provider or Microsoft licensing specialist, especially if the hosting company is operating under a Service Provider Licensing Agreement (SPLA), as the licensing rules can differ in hosted environments.