Part I — The POS Is Not the Register
When I started at Hy’s Steak House in Honolulu in 1976, there was no point-of-sale system. There was a cash register at the front and a discipline of paper that connected the dining room to the kitchen. Servers wrote their orders on hard checks — multi-part paper tickets with one carbon copy that went to the main hotline. If you needed anything from another station — the pantry, the dessert station — you wrote a separate slip and physically walked it to that station. Everything moved through handwriting, memory, and the kind of procedural discipline that experienced servers carried without thinking about it. The system was manual. It was also, within its limitations, entirely understood by everyone who worked within it.
That baseline matters for everything that follows in this series. Not as nostalgia, but as the standard against which every system that has come since should be measured: does the operator understand it well enough to function without it?
The Night the Remanco Went Down
Years after Hy’s Honolulu, I worked at the Hy’s in Century City, Los Angeles. The operation ran on a Remanco POS — one of the early computerized restaurant systems that replaced the hard check workflow with terminals, ticket printing, and electronic routing. It was more efficient under normal conditions. It was also entirely dependent on the system remaining operational.
One night it went down. Not partially — completely. The terminals went dark, the kitchen printers stopped, and the dining room was left without the mechanism it had been built around. What happened next revealed something that has stayed with me through every POS evaluation I have conducted since. The servers who transferred from Hy’s Waikiki — the ones who had learned the business on hard checks and pantry slips — regained control of their stations within minutes. They reverted to what they knew. They wrote orders by hand, walked tickets to the kitchen, and managed their sections with the procedural discipline the old system had built into them. The servers who had only ever worked with the Remanco struggled. They knew how to operate the system. They did not know how to operate without it.
That distinction is the first thing this series asks every operator to sit with. Old school has its wins. A team that understands the underlying workflow of a restaurant — who needs what, when, from where, and why — can function when the technology fails. A team that has only ever known the system cannot. The POS does not make the operation. It carries it. And when it stops carrying it, what remains is either discipline or confusion.
The servers who had trained on hard checks regained control of their stations within minutes. The servers who had only ever worked with the Remanco struggled. They knew how to operate the system. They did not know how to operate without it. That distinction is the first thing this series asks every operator to sit with.
The Modern Failure Problem
The Remanco era had a workaround that no longer exists. When electronic payment systems failed in those years, the imprinter — the carbon voucher device that pressed raised card numerals onto a paper slip — allowed transactions to continue. The card was present, the numbers were captured, and authorization could be obtained after the fact. It was imperfect but functional. It preserved revenue and kept the dining room moving.
Modern credit and debit cards have no raised numerals. They are flat. The imprinter has no surface to read. Which means that when a POS system goes down today and takes the payment terminal with it, the operator’s options are genuinely limited. Writing card numbers down by hand is a privacy and security violation. Photographing a card with a phone is equally problematic under PCI compliance standards. Neither is an acceptable practice and neither should be treated as a contingency plan. This is a vulnerability that the industry has not fully reckoned with — the removal of the mechanical backup that once made payment system failure manageable has left a gap that technology has not yet closed.
Understanding that gap is part of what this series is for. A POS system is not just the mechanism by which orders move from the dining room to the kitchen. It is the point through which payment flows, data is captured, and the business measures itself in real time. When it fails — and it will fail, at some point, in some way — the operator needs to have thought through what happens next. Not as an afterthought. As part of the original decision about which system to build the operation around.
The Governing Principle
There is a persistent misunderstanding in restaurants that the point-of-sale system is a tool of transaction — a place to enter orders, print tickets, and close checks. It is evaluated the way one might evaluate a printer or a terminal: by speed, appearance, and cost. That view is incomplete, and it leads to decisions that quietly shape the operation in ways the buyer does not anticipate.
A POS system does not sit at the edge of the restaurant. It sits at the center. Every order passes through it. Every adjustment, modification, comp, void, payment, and report begins there. It determines how information moves from the dining room to the kitchen, from the kitchen back to the floor, and from the floor into the numbers that define the business. It is not the register. It is the system that connects the room.
The governing principle of this series is straightforward: a POS system is the operational nervous system of the restaurant. If it is aligned with the way the restaurant actually functions, the operation becomes clearer, faster, and more controlled. If it is not, the restaurant compensates. Workarounds emerge. Friction builds. The system does not fail visibly at first. It fails quietly, through small inefficiencies that accumulate until they become the way the restaurant operates. By then, the system is no longer shaping behavior. The behavior has shaped itself around the system’s limitations, and undoing that is significantly harder than choosing correctly at the beginning.
How Operators Lose Control Without Realizing It
The mistake is in how the system is chosen. Many operators evaluate what the system can do, not what it will require. They sit through a demonstration that presents a clean version of service — simple orders, minimal modifiers, ideal conditions. They compare features, pricing, and visual design. They rarely ask how the system behaves when the room is full, when orders are complex, when the internet drops, or when a mistake needs to be corrected in front of a guest.
In a full-service restaurant, complexity is not optional. It is built into the structure of the experience. Tables are not transactions. They are timelines. A single check may carry multiple courses, substitutions, allergies, pacing adjustments, split payments, and service recovery decisions. The system must carry all of that without slowing the room or introducing ambiguity at the pass. If it cannot, the staff will adapt to the system instead of the system supporting the staff. That adaptation is where the slow erosion begins.
A modifier that is difficult to enter becomes a modifier that is occasionally skipped. A report that is difficult to interpret becomes a report that is rarely used. A payment workflow that is slightly inefficient becomes a slower turn at the table. None of these are catastrophic on their own. Together, they reshape the operation. The system does not fail visibly. It becomes the environment the team has learned to work around rather than the structure the team works within.
A system is easy to evaluate when everything is working. It reveals itself when something is not. Most operators evaluate what the system can do, not what it will require — and that gap is where control is quietly lost.
Most Systems Are Not Underpowered. They Are Underused.
There is one final distinction that matters more than most features, and it is rarely discussed during the buying process. A system chosen for its potential but implemented without structure will never reach that potential. A system chosen for its alignment with the operation, and implemented with discipline, will continue to reveal value over time. Most operators think they are buying a system. In reality, they are building one.
That build must reflect the actual complexity of the restaurant. Menu structure, modifier depth, number of seats, number of meal periods, pace of service, and organizational scale all determine what the system must carry. And when something goes wrong — as the Remanco taught me clearly in Century City — who owns the problem? In some systems the POS, payment processing, and support are unified. In others they are distributed across multiple providers. Each structure has advantages. But when failure occurs, the speed and clarity of resolution become part of the system itself.
This is where the conversation must begin. Not with features, pricing, or design, but with behavior under pressure, alignment with the operation, and clarity of control. Everything else follows from that.
Part II will move into the room itself—what a full-service restaurant actually demands from a system during service, and where those demands begin to expose the difference between systems that function and systems that hold.
If this essay resonates, Hospitality Between the Lines is just below.
