Set Up Local Operations
Use the setup wizard to configure menu categories, menu items, tables, secure QR tokens, staff roles, kitchen screens, cashier screens, and table/order screens.
Product docs
Restaurant Hub Documentation
Run local WordPress restaurant menus, dine-in QR table ordering, manual orders, kitchen display, cashier/POS payment recording, browser printing, staff roles, reports, and CSV exports.
Editorial trust
- Publisher
- WPlura Editorial Team
- Updated
- Topics
- Doc, Product Documentation
- Verified sources
- 1 references
Problem, cause, fix, verify
Problem
Restaurant setup guidance must distinguish local dine-in and manual payment workflows from external payment checkout, delivery, or hosted restaurant services.
Why it matters
WooCommerce is not required for the free local restaurant workflow.
Safe check
Install Restaurant Hub on the restaurant's WordPress site.
Verify
Review table/order screens, staff roles, kitchen display access, and service-day device setup.
On this page
Scope
Restaurant setup guidance must distinguish local dine-in and manual payment workflows from external payment checkout, delivery, or hosted restaurant services.
For: Small restaurants, cafes, food courts, and local dining teams using WordPress for simple operations.
- WooCommerce is not required for the free local restaurant workflow.
- The free package does not provide external payment checkout or hosted payment processing.
- Printer setup depends on the device and browser because printing uses browser print.
Quick Start
Set up the workflow in a safe order
- Step 1
Install Restaurant Hub on the restaurant's WordPress site.
- Step 2
Use the setup wizard to configure menu categories, menu items, tables, and secure QR tokens.
- Step 3
Set staff roles, kitchen screens, cashier screens, and table/order screens for the local workflow.
- Step 4
Test dine-in QR ordering, manual order creation, kitchen display, cashier recording, browser printing, today reports, and CSV export.
- Step 5
Use paid workflows only for verified advanced ordering, online pickup/delivery, staff, and cloud-backed features.
Workflow
Setup and operating notes
Run Service Flow
Use dine-in QR table ordering, manual order creation, basic kitchen display, cashier/POS payment recording, browser ticket and receipt printing, today reports, and CSV export.
Plan Growth Separately
The free package uses local WordPress operational tables and manual payment recording. Online card payments, pickup, delivery, hosted services, or larger team workflows require separately verified services.
Tutorials
Detailed product walkthroughs
Set up local dine-in ordering
FreeCreate a practical WordPress-based restaurant workflow for menus, tables, kitchen, cashier, and daily reports.
- 1Create menu categories and menu items with the details staff need during service.
- 2Create tables and generate secure QR tokens for dine-in ordering.
- 3Confirm staff roles and access for kitchen and cashier screens.
- 4Run a test table order from the customer menu shell.
- 5Print tickets or receipts through the browser and confirm today's report and CSV export.
Prepare the restaurant for a busier service day
Free + ProUse the local operational flow first, then add advanced ordering or cloud-backed features only when verified.
- 1Review menu availability, table setup, kitchen screen visibility, cashier flow, and printer behavior.
- 2Test one dine-in order from QR scan to kitchen to cashier payment recording.
- 3Confirm staff know which actions are local and manual.
- 4Use paid entitlements only for verified advanced ordering, pickup, delivery, or staff workflows.
- 5Keep external card processing and delivery-provider behavior separate unless the specific integration is active.
Guides
How to use this documentation
Restaurant operations workflow
Restaurant Hub is for local menu, table, kitchen, cashier, printing, and daily-report work inside WordPress.
Operations support
Use support escalation when printers, devices, host performance, payment providers, or custom ordering requirements exceed the local workflow.
Open related guideCommon Problems
Issues this product helps organize
Kitchen staff cannot see new orders clearly
Symptom: Orders are created but kitchen flow is inconsistent.
Resolution: Review table/order screens, staff roles, kitchen display access, and service-day device setup.
Browser printing is expected to behave like a dedicated POS printer
Symptom: Ticket or receipt output depends on the browser and device.
Resolution: Test the target device and browser before service and document any printer-specific setup.
Online card payment is expected from Free
Symptom: Manual cashier recording is mistaken for hosted payment checkout.
Resolution: Use Free for local order flow and manual payment recording; use paid or external workflows only when verified.
FAQ
Answers before installation or escalation
Does Restaurant Hub require WooCommerce?
No. The documented free local restaurant workflow does not require WooCommerce.
Does Free include external payment checkout?
No. Free supports local restaurant operations and manual payment recording, not hosted payment processing.
How does printing work?
Ticket and receipt printing use browser print, so behavior depends on the device and browser setup.
What does Pro add?
Paid workflows can add verified advanced ordering, online flows, staff features, entitlements, and cloud-backed restaurant operations.
Free vs Pro
Capability boundaries
Free
Menus, categories, tables, secure QR tokens, manual orders, dine-in flow, kitchen display, cashier/POS payment recording, browser printing, today reports, and CSV export are Free/local.
Pro
Advanced ordering, online pickup or delivery, customer accounts, staff flow, notifications, warnings, and entitlement-based features belong to paid workflows where verified.
Cloud
Cloud may manage paid restaurant subscription, entitlement, and cloud-backed operating features.
Planned
Do not claim external payment checkout, delivery-provider automation, or unsupported POS hardware integrations.
Verified Sources
Where these claims come from
Continue