# honeyzsu.hu — artisan web store with its own catalogue tool

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

# honeyzsu.hu — artisan web store with its own catalogue manager

> **In short:** A web store for handmade products with 18 custom pages, no template, custom design. The real lesson of the project is not the look but the tool behind it: a command-line catalogue manager with which bulk pricing, stock and description changes run in minutes, instead of eating hours a day clicking through an admin interface.

## The task

With handmade products the shop is part of the product: if the store looks like the other thousand, the handmade goods look cheaper too. A template system is exactly what will not allow this — the design can only move within the bounds of the settings.

The second, less visible task was daily operations: many products, with frequently changing prices, stock levels and descriptions. In an admin interface that means clicking item by item, which over time becomes more work than the selling itself.

## The solution

### 18 custom pages, no template

Every page was built with its own design and its own code. Not a recoloured template, which is why the pages are not "identical with a different picture": each one follows its own content.

### Command-line catalogue tool

This is the project's biggest business gain. The tool manages the entire catalogue: bulk pricing, stock, category and description changes — with validation and reversible steps, and an automatic backup before every run. What used to take hours a day runs in minutes.

This is the point where the web store meets [process automation](/process-automation/): the same work, just the part a person has been standing in for.

### Product structured data

Products can appear with price and stock information in Google results and in AI answers. For a store this is not decoration: it determines whether the product shows up in comparisons at all.

## The result

| What | How much | Source |
|---|---|---|
| Custom pages | 18 | project scope |
| Bulk catalogue operations | minutes (previously hours a day) | run time of the catalogue tool |
| Backup before modification | on every run | how the tool works |
| Templates and plugins in the system | 0 | the source code |

## Check it yourself

- [honeyzsu.hu](https://honeyzsu.hu/) — the live store.
- [PageSpeed Insights](https://pagespeed.web.dev/) — speed measured with Google's own instrument.
- [Rich Results Test](https://search.google.com/test/rich-results) — the product structured data on any product page.

## What can be learned from it?

That in a web store the visible part is half of it. The other half is how many hours a day the owner spends inside the system — and those hours can only be given back if someone builds a tool for daily operations too, rather than just dressing the shop window.

If the situation sounds familiar: [custom web store development](/ecommerce-development/).