What's changed — dated, and published once it's actually shipped.
This is a record, not a preview. Every entry that appears here carries a real date and describes something that has actually reached restaurants and callers — never something still being worked toward. A reader checking this page is asking one specific question: what has actually changed, and when.
A date on this page means one specific thing.
An entry belongs here the moment something real ships — a change a restaurant or a caller would actually notice, dated to the day it became true rather than the day someone decided to build it. Internal engineering activity — the ordinary, continuous work of building and testing — isn't the same thing as a customer-facing shipped change, and describing internal progress as if it belonged on this dated record would misrepresent what the record is for.
Writing consistently in the present tense here isn't a style choice. A changelog invites a preview — a “what's coming” sitting beside a “what already happened,” each lending the other more credibility than either earns alone. This page declines that shape. It states what is dated and real, and says nothing about what comes next.
An entry describes one of a few kinds of real change: something new becoming available that wasn't before, something that already worked now working differently, or something broken now fixed. Each is a plain, checkable fact — verifiable by using the product itself on or after the date it names.
A short, dated, factual account — nothing else.
Not a version number, not an internal ticket reference, and not marketing language dressed up as an update. Some changes call for a more careful shape than others — the clearest example is a change to which outside system handles a restaurant's or a caller's information.
That second template states a discipline worth generalizing to every entry this page will ever carry: an announcement of a change is not the same thing as the change already being in effect. Nothing gets described here as settled until it actually is.
As it stands.
The record opens.
Nothing has shipped yet that clears this page's own bar — a real, dated, customer-facing change. The next real entry appears here the day one does, with no example filled in ahead of time to make the page look busier than the product's actual history supports.
Why is this empty?
Because nothing has reached the bar described above: a real, dated, customer-facing change. That’s a statement about what has shipped, not about how much work is or isn’t happening.
Does an empty page mean nothing has changed at all?
No — it means nothing has reached the specific bar this page uses. It isn’t a broader claim about anything else that may or may not be happening around the product.
Will there be a way to tell what changed in a given month or year?
Yes — entries are organized by the year they’re published, so a reader looking for a specific stretch of time can go straight to it rather than scrolling the entire history.
Does a correction ever get made to an entry after it's published?
If an entry turns out to have been wrong or incomplete, the honest fix is a new, dated entry that says plainly what the earlier one got wrong — not a silent edit that would make the record read as though it had always been accurate.
Is this the page a journalist or vendor reviewer would check for shipping cadence?
It’s the closest thing this site has to one, and it holds to the same honesty everywhere else on it: a short record here is a truthful answer today, not a page dressed up to look busier than the product’s actual history supports.
The live, current-state reading lives at status, not here.
Current status is the one-line reading of the product right now; this page is the dated history of what has actually shipped.
Open the line.
Tell us about your restaurant. We load your menu, you place a call, and you hear it answered yourself.