Venues

Food hall EPOS and multi-vendor ordering

HelchPOS was built inside a working food hall, during service. Everything on this page runs there today.


The real hall page: every kitchen at Helch Market Winchester on one address
The real hall page. Every kitchen at Helch Market Winchester on one address — this is the live venue, not a mock-up. A screenshot of the running product.

One basket, five kitchens, no arguments about money

A guest scans one code, orders from any kitchen in the hall and pays once. Underneath it becomes one ordinary order per kitchen, so every report, refund and stock movement stays per business. A refund comes out of the kitchen that was paid for it; a tip follows the food. Settlement is correct because of the shape, not because somebody was careful.

The hall’s own money

Commission per kitchen, standing rent that lands on every payout run by itself (weekly or monthly, each due date one full charge, named on the statement), and a customer processing fee that is the hall’s own revenue line. The payout run shows each vendor gross, commission, rent and what is owed.

Selling like one venue

Meal deals that span kitchens — a main from one counter and a drink from another for one price, split fairly underneath. Loyalty that works across the whole hall rather than per vendor. A runner’s board showing every kitchen’s orders in one view.

Each kitchen still runs itself

Its own menu, its own prices, its own kitchen screen, its own staff with their own permissions — and the hall chooses which settings it decides for everyone and which each kitchen keeps. Inviting a new kitchen is a link; the setup only asks them what the hall has not already decided.


Free to use.

Everything on this page is in the product now. What is not built yet is named on the comparison page rather than left out.