Online ordering
Your menu items already carry prices. Put [rs_order] on a page and every priced item gets an “Add to order” button, dropping it into your site’s own WooCommerce cart at the menu price.
Guests choose pickup or delivery at checkout and can ask for a time, so you are not accepting orders for food you cannot cook yet. Both the method and the requested time appear on the order in WooCommerce → Orders, which is where you are already looking.
The ordering page is deliberately separate from the menu page. [rs_menu] stays exactly what it was — something a guest can read on their phone at the table — and [rs_order] is the page that takes money. Most restaurants want both, and collapsing them into one page makes the menu worse.
Reservation deposits
Set an amount per person and a booking goes to checkout before the table is held. The ordering matters, and it is the same principle as ticketing: the table is held only once the deposit is paid.
The consequence is the point. An abandoned checkout never blocks a table, so your Friday night is not quietly full of bookings nobody intends to keep. And any booking that does land is already confirmed and already paid for, which is most of what a no-show policy is trying to achieve.
Leave the deposit at 0 and reservations behave exactly as they do on the free plugin. This is opt-in, not a change to how bookings work.
