Skip to content
TapNTable
Devlog
v0.12.0

TapNTable 0.12.0: Legal and Reports

There was an old, silent problem: when you edited the privacy policy or the cookie banner text in the restaurant’s main language, the change was saved but the site kept showing the version that came with the template. The main-language translation was hiding the edit. From this version on, what you write in the main language is the source of truth and every copy stays aligned by itself - including the pages and the banner you already had, which are corrected automatically during the update.

A visitor using a language with no translation now sees the page in the restaurant’s language rather than in English. The same goes for the page name in the footer, the links in the cookie banner and the consent checkbox text on reservations: all three always say the same as the page they open.

Restaurant variables always up to date

The legal templates use variables such as the restaurant’s name, address, phone or email. Until now they were replaced once, when you loaded the template; if the restaurant’s name changed, the document went stale. They are now live: the public page always shows the restaurant’s current details, and the editor gained a legend with the eight available variables and what each one does. Only the date stays fixed on the day you loaded the template, because it is the document’s date.

Every save of a legal page is recorded as a revision, and every customer acceptance points to the revision they read, with the variable values at that moment. If you ever need to prove what a customer accepted, you can reconstruct it exactly.

When TapNTable’s legal templates are updated in a future version, the new legal:refresh command lets you adopt the new text on the pages you never edited - and only those. A page you changed by hand is never touched without asking.

The cookie banner went from two buttons to three: “Accept all”, “Necessary only” and “Customise”, where the customer switches analytics cookies on or off. Google Analytics only starts when the analytics category has been accepted. Every choice is recorded on the server anonymously - no name, no account, just the choice, the date and a consent identifier - so you have proof that consent was asked for and given.

CSV export in every report

Every analytics report now exports to CSV in the same format: a header with the report name, the period and the currency, and clean numbers that Excel and Google Sheets read without tricks. Four areas that had no export gained one: daily dish, franchise, feedback and staff. The menu, marketing and promotions PDFs now show the currency symbol, and the charts format monetary values correctly.

The export button appears on every analytics page, and anyone without export permission sees the button disabled with an explanation instead of an error. The delivery index exports, a feature still in preparation, were removed to avoid confusion.

And more

  • An invalid date in a report filter no longer errors and falls back to the default period.
  • The cookie banner’s “Customise” panel is keyboard accessible: when it opens, focus moves to the analytics switch.
  • The consent log copes with a whole dining room behind the same network address without losing choices.