About us
Built with operators,not around them.
Wox exists for restaurant teams who know the real work happens between counts, orders, vendors, shifts, and margins — not inside a single dashboard.
The problem
The restaurant stack is broken in ways nobody fixes.
Most operators assemble their tooling from five vendors who do not talk to each other — and pay the reconciliation tax every single day.
Fragmented systems
POS, inventory, purchasing, vendor messaging and analytics live in five separate products. The numbers never line up.
Spreadsheet survival
Food cost, par levels and vendor prices still get tracked in spreadsheets that go stale by Tuesday afternoon.
Built for the back office
Most tools are designed for accountants reading reports next month — not for the people running service tonight.
The solution
One platform that thinks the way a restaurant thinks.
Wox connects every operational moment — sale, count, delivery, message, invoice — to the same ledger underneath. The truth never branches.
Shared ledger
A sale, a count, or a delivery hits every surface — POS, dashboard, mobile, vendor portal — at the same moment.
Live numbers
Food cost, variance and inventory move in real time. The end-of-month surprise becomes a Tuesday afternoon decision.
Designed for the floor
Built around how chefs, managers and servers already move. The shift does not stop for the tool.
Mission
One operating layer
for the back of house and the front.
Inventory, purchasing, POS, supplier communication, analytics, and AI — working from the same data. So operators never reconcile the same truth twice.
We started where the noise is loudest: a chef counting bottles before service while a manager retypes a supplier invoice into a spreadsheet. Wox was built from that scene outward — the floor, then the manager's office, then the supplier on the other side of the city.
1
Shared operating system
20m
Target daily admin
24/7
Operational visibility
Principles
How we build, and what we refuse to build.
Three rules that shape every screen, every endpoint, and every supplier integration we ship.
Floor-first design
Start with the restaurant floor, then design the software around how teams already move. The shift does not stop for the tool.
One source of truth
Keep suppliers, purchasing, inventory, and sales connected, so operators never reconcile the same number twice.
Decisions before surprises
Turn operational data into decisions owners can trust — before cost leaks become month-end surprises.
What we build
Four surfaces, one ledger underneath.
A single platform that presents itself differently to each person who picks it up — and stays in sync the moment a sale, count, or delivery happens.
POS terminal
Order entry, course firing, tables, payments and shift reconciliation on the front of house.
Operator dashboard
Inventory, purchasing, COGS, vendor management and reporting in the manager's browser.
Mobile app
Counts, deliveries and team chat in the chef's pocket — works offline, syncs when it can.
Vendor portal
A dedicated workspace for suppliers: purchase orders, price sheets, catalog and delivery confirmation.
Where we work
Built in Tbilisi,
for the Caucasus and beyond.
Wox is a Georgian product. The first hundred restaurants we serve are the ones we can visit in an afternoon. Language, currency, supplier landscape and tax model are first-class concerns — not retrofits bolted on at the end.
We engineer for restaurants that operate across multiple locations, multiple legal entities, and multiple service models — fine dining, casual, bar, and quick service — under one roof and one ledger.
- Two-locale productka · en
- Currency-nativeGEL · USD · EUR
- Org / location / brandMulti-entity
- One ledger across every surface, every location, every entity.
