Hofladen: The Software for Short Distances

Regional products rarely fail because nobody wants them.

They fail more often in the small frictions between people. What is available right now? When is the order deadline? Pickup or delivery? Which list is current? Who has already paid? Which message came through WhatsApp, which by email, which was promised during the last conversation over the garden fence?

For large platforms, this sounds small. For a farm shop, a beekeeper, a nursery, or someone selling vegetables from their own garden, this smallness is the daily work.

That is what I am working on under the name Hofladen: a simple ordering platform for regional products.

The short path is harder than it looks

Direct sales sound romantic. Farm, customers, trust, short distances. Less middleman. More relationship.

In practice, there is a lot of administration inside it. Products change by season, weather, harvest, shelf life, and capacity. Some things are only available this week. Some only by preorder. Some need to be picked up, others fit into a delivery route. A small operation does not need a platform that feels like Amazon. It needs a tool that does not break the existing workflow.

Many digital products overreach here. They arrive with payment providers, shop logic, shipping logic, required fields, pricing tiers, integrations, and an interface built for larger merchants. Then the small producer is expected to bend into the system.

Hofladen should start differently: from the real workflow.

Not a marketplace, more like a tool

The first idea is intentionally simple. An operation lists its current products. Customers see what is available, order online, and pick up locally or receive the goods through the agreed path. Payment continues the way it already works in real life: cash, bank transfer, invoice, honor box, or whatever the operation is used to.

The system does not need to own every part of the trade. It needs to bring order to the part that is currently messy.

That is why I am especially interested in the space between paper list, Excel sheet, WhatsApp group, and full online shop. A lot happens there. It is also where many people find existing software too large, too expensive, too abstract, or simply not suited to them.

Hofladen should not become a platform that makes regional producers dependent. The better path would be open, decentralized, and adaptable. A tool small enough to understand, but stable enough to carry real daily work.

Listen first, then build

With a project like this, the temptation is to invent features immediately. Cart. Inventory. Customer data. Delivery routes. Pickup windows. Invoices. Automatic reminders. AI functions. Everything sounds useful when viewed abstractly.

But software can become very wrong when it solves the wrong problems cleanly.

So there is now a small public Hofladen page with a questionnaire. It is not prominent in the normal site flow yet, but it is reachable: see Hofladen. The questionnaire is meant for farm shops, producers, beekeepers, nurseries, hobby operations, community gardens, and similar direct-sales contexts: go directly to the questionnaire.

I am not only interested in whether someone wants "an online shop." That is usually the wrong question. The better questions are:

• How do orders come in today?
• Which products change often?
• Where does administration become annoying?
• Which tools are already being used?
• What feels too complicated, too expensive, or too rigid?
• Which analog parts actually work well and should not be digitized?

The last question matters. Good software does not blindly replace everything that used to be human, local, or informal. Sometimes it protects those forms by smoothing the annoying edges around them.

Regional does not mean backward

There is a strange assumption that small regional structures are either nostalgic or inefficient. As if every local form eventually has to be absorbed into a larger platform to count as modern.

That is a weak view of technology.

Technology can also help smaller structures remain independent for longer. A farm shop does not have to become an anonymous e-commerce merchant just because ordering becomes more digital. A beekeeper does not have to hand their customers to a marketplace just because the order list gets chaotic. A nursery should not have to choose between paper chaos and platform dependency.

The most interesting space lies between those poles.

There, software can respect the local relationship instead of replacing it. It can strengthen the short path instead of rebuilding it as a centralized platform. It can give smaller operations a better surface without taking control over their data, customers, and workflow.

The prototype as a conversation

Hofladen is still early. There is a first prototype and enough direction to talk about it concretely. But the product is still flexible enough that real feedback can change it.

That makes this the right phase for a questionnaire. Not as a marketing exercise, but as a reality check.

If you run a farm shop, sell products directly, keep bees, grow produce, process food, pack subscription boxes, organize a CSA, or simply have experience with regional direct sales, every honest answer helps. Even a short one. Even a skeptical one.

The page is here: Hofladen. The questionnaire is here: Hofladen questionnaire.

Maybe this will not become a large platform in the end. Maybe that would even be the wrong goal. The more interesting outcome would be a tool that stays small enough to serve the people using it.

Short distances do not appear by themselves. They have to be built, maintained, and sometimes defended against the large convenient detours.