Pre-launch · research phase

The restaurant POS built by operators, for operators.

OSHQ POS is a modular POS and full restaurant operating platform in active design — for full-service, fast-casual, delivery-heavy, multi-location, and multi-brand operators. CommandPOS is the software experience inside. Not shipping yet.

No live payment processing · No certified hardware · No production POS — yet

Why another POS

Restaurants deserve software that thinks like a restaurant.

Most POS systems are payment terminals with menus bolted on. OSHQ POS starts from the floor — the table, the ticket, the shift, the guest — and treats payments as one integration surface among many.

Floor-first, not payment-first

TableOS is native. Sections, sessions, waitlist, and turn-time metrics are core primitives — not a plug-in.

Modular, not monolithic

Online ordering, delivery, catering, loyalty, inventory, scheduling — each ships as its own module and integrates with the OSHQ ecosystem.

CommandPOS AI, governed

AI inside CommandPOS is named CommandPOS AI. It runs under the CommandOSHQ + CK3000 governance model. No anonymous AI callers. No AI action bypasses manager approval.

TableOS

Native table management, not a reservations add-on.

Reservations are optional adapters. Walk-ins create table sessions directly. That distinction changes how the whole system behaves.

Floor plans, rooms, sections
Tables & capacities
Combine / split tables
Server sections & assignments
Waitlist, quote times, table-ready SMS
Table statuses & sessions
Open-check linkage & transfers
Turn-time metrics

OSHQ Ecosystem

OSHQ POS plugs into the systems restaurants already run on.

OSHQ.co
CommandOSHQ
RestaurantOSHQ
WorkforceOSHQ
FinanceOSHQ
CaterOSHQ
GameDayOSHQ
ReviewsOSHQ
TextOSHQ
OSHQ.AI

Integrations are on the roadmap, not shipped.

Development status

Where we actually are.

Phase 0

Research & architecture

active

Phase 1

Back-office foundation, tenant model, plan registry

in build

Phase 2

Order/check + TableOS simulation

queued

Phase 3+

Operational integrations, then payments & hardware after explicit decision gates

queued