01
Discover the menu
Guests browse categories, recommendations and dietary information through a focused mobile-first experience.
LineWeb-owned product Complete and free
Lineweb Restaurant Orders
Direct food ordering inside WordPress, without commissions or a Pro gate.
A mobile-first menu, checkout and restaurant operations system that lets the business own the experience, the orders and the customer relationship.
Delivery benchmark
A 99 target across the essentials
We build toward this benchmark and verify each launch separately. Results can vary by page, device, network and test conditions.
99
Performance
Target
99
Accessibility
Target
99
Best Practices
Target
99
SEO
Target
Free means complete
No Pro edition waiting behind the first order.
Version 1.0.0 contains the complete planned free feature set. There is no trial, feature lock, commission, author telemetry or upgrade prompt.
No commission per order
No paid feature gate
No LineWeb telemetry
No remote upgrade pressure
The customer journey
From appetite to a trackable order, without leaving the restaurant’s website.
The ordering flow keeps menu decisions clear on mobile while preserving the operational context the restaurant needs after checkout.
02
Shape the order
Variants, extras, quantities and notes stay connected to the exact food item instead of becoming checkout confusion.
03
Choose the service
Delivery, pickup or optional dine-in table ordering are handled as clear operating flows.
04
Pay and follow
Cash or optional Stripe payment leads into private token-protected order tracking and status updates.
Mobile first, operationally aware
The menu is not a PDF. The checkout is not an afterthought.
Guests can understand the food, choose meaningful options, review dietary details and complete the right order type without navigating a generic shop template. Tips, notes and payment stay part of one coherent flow.
Designed for the device guests actually order from
Included in the free release
The features needed to receive and run direct orders.
The product covers the customer experience and the day-to-day restaurant workflow instead of ending when the order button is clicked.
Menu
A complete food catalogue
Products, categories, featured items, variants, extras, dietary labels and allergens remain manageable inside WordPress.
Orders
Three service models
Restaurants can accept delivery, pickup and optional dine-in table orders from the same customer experience.
Payments
Cash or optional Stripe
The plugin works with cash alone or can add card payments without storing full card details in WordPress.
Operations
A practical order workflow
Statuses, printable receipts, sound alerts and aggregate reporting give the team a clear daily operating view.
Tracking
Private customer status
Customers follow an order through an opaque tracking token instead of a predictable public order number.
QR & PWA
Ordering from the right entry point
Local QR generation and an optional menu-scoped PWA make the ordering experience easier to revisit.
Notifications
Optional WhatsApp updates
Twilio WhatsApp notifications can be enabled when the restaurant wants order and status messages beyond the website.
Privacy
Retention under site control
Completed, rejected and failed orders can be anonymized automatically according to the restaurant’s retention settings.
A dependable total
The browser chooses. The server decides the price.
A customer submits product, variant, extra and quantity selections. WordPress reloads the current catalogue and calculates the canonical total before an order or Stripe PaymentIntent is created.
Server-authoritative cart validation
1
Customer selection
Products, quantities, variants and extras
2
Catalogue validation
Availability and current prices reloaded by WordPress
3
Canonical total
The server calculates the amount that can become an order
4
Verified payment state
Stripe references and status stored, never full card details
After checkout
A restaurant dashboard built for the next action.
Today’s orders, revenue, pending actions and status filters sit together. Teams can move an order through accepted, cooking, ready and completed states, print receipts and use optional sound alerts without leaving WordPress.
Order and payment statuses
Printable receipts and sound alerts
Aggregate restaurant reporting
Data and integrations
Self-hosted first. External services only when chosen.
Cash ordering needs no external service. Stripe and Twilio remain optional, disabled until configured and clearly disclosed. The plugin sends no usage analytics or marketing data to LineWeb or its author.
WordPress database
Menu, order, customer and operational data stay on the restaurant website.
Stripe, optional
Card details go directly to Stripe; WordPress retains references and verified status.
Twilio, optional
WhatsApp order and status notifications run only when explicitly enabled.
Configurable retention
Completed, rejected and failed orders can be anonymized automatically.
AM
Product ownership
Created and maintained by Andrew Matia and LineWeb.
Lineweb Restaurant Orders is original public software built from real hospitality and ordering experience. It is released under GPL-2.0-or-later so restaurants and developers can inspect the code, operate it themselves and adapt it within the license.
Questions and answers
The free plugin, clearly explained.
What is Lineweb Restaurant Orders?
Lineweb Restaurant Orders is a self-hosted WordPress food menu and direct-ordering plugin created by Andrew Matia and LineWeb. It supports delivery, pickup and optional table ordering, with order management, tracking, payments, QR codes and privacy controls.
Is the plugin completely free?
Yes. Version 1.0.0 contains the complete planned free feature set. There is no Pro edition, paid feature gate, trial, commission, author telemetry or upgrade prompt.
Does the plugin trust prices sent by the customer’s browser?
No. The browser sends the selected products, variants, extras and quantities. The WordPress server reloads the catalogue data and calculates the authoritative total before creating the order or Stripe PaymentIntent.
Are card details stored in WordPress?
No. Stripe.js sends card details directly to Stripe. WordPress stores the Stripe payment reference and verified payment status, not the full card information.
Does it require external services?
No external service is required when cash payment is used. Stripe card payments and Twilio WhatsApp notifications are optional and are contacted only after an administrator enables and configures them.
Where is restaurant and customer data stored?
Menu, order and customer data remain in the restaurant’s WordPress database. The administrator can configure anonymization for completed, rejected and failed orders, and uninstalling preserves data unless permanent removal is explicitly enabled.
Own the menu. Own the orders. Keep the complete plugin free.
Inspect the public source and install the free release, or talk with LineWeb about restaurant-specific integrations and workflows beyond the included scope.