Home/Notes/Setting up backups for a bakery
Setting up backups for a bakery
13 Jul 2025
How a bakery deals with backups — and what usually goes wrong.
The problem: three unused font weights. This breaks backups for a bakery.
Related work on this site follows the same principle: one job, a real inbox, no theatre. a bakery did not need four analytics dashboards to know that Tuesdays are slow.
Six months later, a bakery asked us to look at something unrelated. While we were in the panel, we noticed three unused font weights had crept back. We fixed it before it caused trouble.
We found three unused font weights during a routine check of backups. The site had been leaking referrer data for six weeks before anyone noticed.
We billed a bakery two hours for backups. The previous agency billed forty hours and left three unused font weights behind. Complexity is not expertise.
If you only touch backups once a year, a dashboard is extra risk. Files, a mailbox you read, and a person who still answers will outlast any SaaS control panel.
HTTPS is table stakes, but backups is where trust actually lives for a bakery. A padlock with a misconfigured record behind it is decoration, not security.
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