WooCommerce was designed to sell boxes to people who are not in the room. A restaurant sells plates to people sitting at table nine, who will order a second round of drinks twenty minutes later and pay at the end. Those are different problems, and the gap between them is where most WooCommerce restaurant POS setups fall apart.
This guide walks through what a restaurant actually needs at the counter, how each piece maps onto WooCommerce, and where the honest limits are.
The four things a restaurant needs that retail does not
1. An open bill per table
In retail the cart exists for ninety seconds. In a restaurant it lives for two hours, gets added to repeatedly, and has to survive the waiter walking away with the tablet. That means the order has to be attached to a table, not to a device or a session.
OpenPOS handles this with a floor plan: you draw your room, place tables on it, and each table holds its own running order. Any staff member on any device can open table nine and add a dessert.
2. Merging and transferring tables
Two couples who know each other decide to sit together. A party of six moves from the cramped table by the door to the big one at the back. A retail POS has no concept for either. A restaurant one needs to merge two open orders into a single bill and move an order from one table to another without retyping it.
3. Getting the order into the kitchen
Taking the order is half the job. The kitchen has to see it, in the order it arrived, with modifiers attached — no onions, extra chilli, well done. Two approaches work:
- Kitchen tickets. A thermal printer in the pass prints each order as it is sent. Cheap, reliable, and it works when a screen does not.
- A kitchen display screen (KDS). A tablet or monitor showing live orders, which the kitchen marks as done. No paper, and the front of house can see what is ready.
OpenPOS ships both. You can watch the kitchen screen without logging in on the live KDS demo.
4. Splitting the bill
Four people, one bill, two cards and a pile of cash. A POS that accepts exactly one payment method per order will make your staff do arithmetic on a napkin. You need multiple payments against a single order, mixing cash, card and wallet.
Modelling a menu as WooCommerce products
This is where most people overthink it. A menu item is a WooCommerce product. A category on the menu is a product category. The POS grid shows them the way your staff expect to see them.
Options are the interesting part:
- Size and choices that change the price — small, medium, large latte — are product variations. Each has its own price and its own stock behaviour.
- Add-ons that stack — extra shot, oat milk, side of fries — are best handled with WooCommerce Product Add-Ons or Extra Product Options, both of which OpenPOS reads at the register.
- Kitchen notes that carry no price — no onions, allergy: nuts — belong in a per-item note that prints on the kitchen ticket.
Resist the urge to make every add-on a separate product. Fifty products called “Latte + oat milk” is a menu you will hate maintaining by the second month.
Stock, when the thing you sell is cooked
Do not track stock on cooked dishes. A burger is not a unit sitting in a warehouse; it is flour, beef and thirty seconds of a chef’s attention. Turning on stock management for it means someone has to remember to top the number up every morning, and the day they forget the POS will refuse to sell burgers during the lunch rush.
Track stock on the things that are genuinely countable and genuinely run out: bottled beer, cans, wine, packaged desserts, retail merchandise. Leave the kitchen items unmanaged, and use an “out of stock for today” toggle — or simply hide the product — when the special sells out.
Recipe-level ingredient depletion is a food-cost problem, not a POS problem. If you need it, keep it in a separate inventory tool and reconcile weekly.
Hardware for a small restaurant
A workable setup, in rough order of importance:
- One tablet per section of the floor, plus a fixed device at the till
- An 80mm thermal receipt printer at the till, with a cash drawer wired to it
- A second thermal printer in the kitchen for tickets, or a cheap tablet running the KDS
- A card terminal — Stripe Terminal and Square are both supported by OpenPOS
- Reliable Wi-Fi that reaches the far corner of the room, which is the part everyone under-budgets
Because OpenPOS is a Progressive Web App, the tablets do not need an app store install or a per-device licence. You pin the register to the home screen and it behaves like a native app. Adding a fifth tablet costs the price of the tablet.
Where the honest limits are
A WooCommerce-based restaurant POS is an excellent fit for cafés, bars, small restaurants, food trucks and anywhere the menu is a list of things with prices. It is a poorer fit if you need:
- Deep recipe costing with ingredient-level depletion across every dish
- Coursing rules that fire the mains automatically eight minutes after the starters clear
- Tip pooling and payroll integration for a large staff roster
Those are the features you pay a restaurant-only platform a monthly subscription for. Whether they are worth it depends on whether you have a chef arguing about food cost percentages, or a queue of people who want coffee.
Frequently asked questions
Can waiters take orders on their own phones?
Yes. Each staff member gets their own login with their own permissions, and the register runs in a phone browser. Sales are attributed to the cashier who rang them up.
Does the kitchen screen need the internet?
It needs to reach your WordPress site, which for a single-location restaurant means your local network plus an internet connection to a hosted site. If your site is hosted remotely and the line drops, keep a kitchen ticket printer as the fallback.
Can customers order from the table themselves?
Yes — OpenPOS supports no-touch ordering, where a QR code on the table opens the menu on the customer’s phone and the order lands in the same kitchen queue.
Do I need a separate site for the restaurant and the online shop?
No. One WooCommerce store, one product catalogue, one order list. The register and the website are two windows onto the same data.
See restaurant mode running
Open the restaurant demo (login test / test123), place an order on a table, and watch it appear on the kitchen display in another tab.
Restaurant mode is included in OpenPOS — one payment, no subscription, unlimited tablets.