A system of record is the software where a piece of data is created and where the authoritative version lives. In a restaurant, your reservation platform is the system of record for bookings and your POS is the system of record for checks.
The term matters commercially, because it tells you what a given product is asking you to give up.
The three layers
Most restaurant technology sits in one of three positions, and knowing which one you are being sold answers most of your questions immediately.
- System of record — creates and owns data. Reservation platforms, POS, review platforms. Replacing one is an operational project, not a purchase.
- System of intelligence — reads several systems of record and produces understanding. Guest data platforms sit here. Adopting one changes nothing about service.
- System of action — does something with that understanding. Email tools, task systems, the host stand.
Why the layer decides the cost of adoption
Replacing a system of record means migrating live data, retraining everyone who touches it, and accepting a period where the thing that takes your money is new to your staff. That is measured in months.
Adding a system of intelligence means connecting to what you already run. Nobody's job changes on day one.
Neither is inherently better. But when you are comparing two products and one of them is a system of record, you are not really comparing features — you are comparing a purchase to a project.
Where data ownership sits
Systems of record hold the canonical version. If your reservation platform says a booking was for four at 7:30, that is what it was.
This has a practical consequence worth understanding before you sign anything: if you leave a system of intelligence, your reservation history is unaffected — it never stopped living in your reservation platform. If you leave a system of record, you are migrating the underlying data itself, and what you can take with you depends entirely on that contract.