Restaurants do not arrive with the same website, budget, team, or launch risk. The public surface can change without fragmenting the operational backend.
The Site Connection is the bridge
A Site Connection tells Plenty which public customer surface belongs to which restaurant workspace. That connection can serve a hosted page, a WordPress route, an embed, or a complete Plenty-managed website.
WordPress remains a surface
A WordPress plugin can make the ordering experience feel native on the restaurant's existing domain. Plenty still owns the customer session, menu validation, checkout, orders, and account history.
Launch should be reversible
Private preview and test orders should happen before public cutover. Existing WooCommerce routes can remain live until the owner deliberately activates Plenty, with rollback kept distinct from setup.