Home/Notes/Managing CSV exports at a restaurant
Managing CSV exports at a restaurant
7 Aug 2025
How a restaurant deals with CSV exports — and what usually goes wrong.
The problem: query-string copies of the same page. The CSV exports data is out of sync for a restaurant.
a restaurant did not need a portal. They needed a page that said who they are, what they do, and a phone number that somebody picks up before the fifth ring.
The chain of trust for CSV exports starts at the registrar. If the registrar account uses an email nobody reads, every downstream fix is temporary.
The hosting bill for a restaurant is twelve dollars a month. Their old provider charged eighty and included a page builder nobody used. CSV exports was broken on both plans.
You do not need a status page if you have never gone down. a restaurant is on month fourteen of zero downtime, and the secret is boring: correct CSV exports and a host that does not oversell.
For a restaurant, the boring path won: HTTPS, a backup that we have restored once on purpose, and a calendar reminder for CSV exports.
We have seen agencies charge a restaurant for a yearly CSV exports audit that consists of a screenshot and a paragraph. Ours is a working config file they can apply themselves.
Two-factor on the registrar account is the single highest-value thing we do for a restaurant when managing CSV exports. Everything else can be rebuilt; a stolen domain cannot.
Related notes
Tell us what you need.
Write a few lines about your project. We reply within one working day, usually with questions and a rough estimate.
hello@digitalserved.com