@Sirmonkey 

You can have dedicated switches labeled with the network designation (POS, VOIP, LAN) for ease of local support people.  To accomplish this leave everything wired as you described and just tag the ports on the switch with the desired network/vlan.  Then if the local support person wanted to add a POS device, they could plug the device in to the POS switch and the device would receive the subnet for POS devices 192.168.45.XX.  Each switch would get an IP address from the router on 192.168.0.xx.

This is different than configuration using Ubiquiti, but do you see other issues with this approach? I guess the local support person couldn't replace a failed switch without configuration, but this should be rare event and Omada allows remote configuration. 

The router is vlan aware, but currently can only DHCP on one/default subnet.  The LAN ports on the router act as an unmanaged switch, except they understand traffic with vlan tags and other subnets.

Thank you for the response. you understand my simple idea :-).  You are right. but i have taken it to the next level. the router is the only thing that is Special. The rest of the hardware is generic parts. hopefully TP-Link, but if its an emergency, parts from office depot/best buy.  with my Ubiquiti setup i'm actully useing alot of those $16 tp-link switches from microcenter, i think i have bought ~15 so far this year. 

Yea I gues i am confused. when you put a port into WAN most it almost does what i want.  but dosen't seem to work that way.. I can't add different subnets with out VLAN. To add another subnet i have to tag it as a different VLAN. I can't ( or haven't figured out how to have the ports be their own subnet. )

This is where the configuration becomes an issue. Example. I drop ship a new phone. Ask them to send me a picture of the sticker on the back ( so i can get the MAC and provission the phone )  and then plug the phone in.... Never do i have to configure a VLAN tag on the phone ( or POS system, or Lan devices)