# bucipek.hu — bakery site with ordering and careers modules

URL: https://rootcr.com/case-studies/bucipek/
Updated: 2026-08-23

# bucipek.hu — bakery site with its own ordering and careers modules

> **In short:** A bakery's website that does not just present but works: it takes orders, and its careers page accepts CVs. File upload is the most dangerous point of any website, so here the system determines the real type of an uploaded file from its content, looks for macros and executable content, then runs a virus check. The site appears in Google's index with 192 URLs, with no structured data errors.

## The task

A working bakery needed a site that could do two things a brochure page cannot: accept orders and collect applicants. Both take data from the visitor — one of them personal data, the other a file on top of that. This is the point that decides whether a website is a tool or a liability.

## The solution

### Ordering module

Ordering is not a generic cart engine but logic written for the bakery's actual process: what can be requested for when, what is in stock, what goes to pre-order. An order sends a notification the moment it arrives, and is logged — you do not have to go hunting for it in an inbox afterwards.

### Careers module and file upload

On the careers page anyone can upload a CV, and file upload is the most dangerous point of any website. So the system determines the real type of the uploaded file from its content — not from the extension, because anyone can rewrite that — looks for executable content and macros in the document, then runs a virus check. If any step fails, the file never reaches the disk.

What passes goes into a directory not reachable from the web, and is deleted automatically after 365 days. That last part is not a technical nicety: personal data must not be stored without a deadline.

### Findability

The site was built with complete structured data: product types, opening hours, contact details, frequently asked questions — in machine form too. Not as an afterthought, but as part of the build.

## The result

| What | How much | Source |
|---|---|---|
| Indexed URLs | 192 | Google Search Console |
| Structured data errors | 0 | Google Search Console / Rich Results Test |
| File verification layers | 3 (type, macro, virus) | the system's source code |
| Automatic deletion of CVs | 365 days | scheduled task |

## Check it yourself

- [site:bucipek.hu](https://www.google.com/search?q=site%3Abucipek.hu) — how many pages are in Google's index, right now.
- [PageSpeed Insights](https://pagespeed.web.dev/) — paste in `https://bucipek.hu/` and measure with Google's own instrument.
- [Rich Results Test](https://search.google.com/test/rich-results) — the structured data error list for the same address.
- [bucipek.hu](https://bucipek.hu/) — the live site itself.

## What can be learned from it?

That a website starts paying for itself when it takes over work: orders, applications, administration. And that file upload is not a feature but a responsibility — if a developer leaves it to a plugin, they do not actually know what is protecting you.

If you have a similar task, here is the service: [custom website development](/custom-website-development/).