Website for a Brewery or Winery: Visits, Stock and Age Checks

en 2026-09-18 6 min read

A website for a brewery or a winery sits at step 03 of our price list, EUR 1.500 to 3.500, built over 3 to 6 weeks: four to seven pages, a CMS you control, pages for tours, the tasting room and the trade, and a booking or contact flow. Selling bottles online is step 04, EUR 3.500 to 7.500 over 6 to 12 weeks, because age verification, destination rules and checkout are a build rather than a switch.

Three things decide where you land: how much of the business is visits, how fast your stock changes, and whether you sell online.

The visit is what you are selling

Until you sell online, the website is not the shop. It gets someone through the gate and into the taproom or onto a tour, where the selling happens with a glass in their hand. That puts unglamorous pages first.

• Opening hours that are correct, kept in one place, and easy for you to change on a public holiday.
• Directions written for someone who is not local: parking, the nearest station, and what the last stretch of road looks like.
• Tours with times, group sizes, what is included and what it costs.
• Group and private bookings, which arrive as questions rather than orders: numbers, dietary needs, a date nobody has confirmed yet.
• Events and private hire, which deserve a page of their own rather than a line on the contact page.

A booking or contact flow is part of step 03. Taking a deposit at the moment of booking is not. The moment a card is charged you are in step 04, so decide whether you want deposits before the quote rather than after it.

Stock changes faster than a website

Batches, vintages, seasonal releases, a keg that ran out at the weekend. A page that says available when it is not costs you a phone call and a little credibility.

What you need is a CMS where someone who actually works there can mark a release sold out, add the next one with its tasting notes and label data, and change the tour times, without asking a developer. That editing layer is the main reason a brewery or winery lands at step 03 rather than step 02.

Age checks and what compliance adds

An age gate on the front of the site is a declaration, not a check, and it interrupts every first visit. Put it where it earns its place: at checkout, and wherever a price for shipped alcohol appears.

Selling online then adds work that has nothing to do with design.

• A check at two points. One when the order is placed, one when the box is handed over. The second is a courier service you buy, and checkout should promise only what the courier actually does.
• Destination rules. Where you ship decides what is allowed. In code that becomes a country list limited to where you can deliver, and shipping options that appear only where they are permitted.
• Product data. Volume, alcohol content, ingredients and allergens, lot or batch identifiers, and the text on the label. Someone has to write it and keep it true for every release.
• Consent and analytics. Cookie consent, what may be tracked before it is given, and marketing permissions recorded in a way you can show later.
• Trade and wholesale. A login for restaurants and shops with their own prices is a customer account system.

All of it is why an alcohol webshop is step 04 rather than step 03. The rules that apply are set by where your customer is, so confirm them before the build starts and we build to them.

The steps, and what each one buys

What moves the number inside a step

• How many kinds of visit you sell. A tour, a tasting and private hire each need their own page.
• A second language, if visitors arrive from outside the country.
• Booking against real capacity, with confirmations and reminders, rather than a form that lands in an inbox.
• How many products you list, and how much data each one carries.

We build these on Next.js, and what that means in practice is on our Next.js page.

Process and timeline

Scoping first: visits, range, languages, and whether you ship. A fixed quote always follows scoping, and it holds unless the scope changes. Then structure, design, build, your review, launch.

Step 01 runs 1 to 2 weeks, step 02 runs 2 to 3 weeks, step 03 runs 3 to 6 weeks and step 04 runs 6 to 12 weeks. The part that waits on you is product data, photography of the place and, if you ship, the courier arrangement. Checkout cannot be finished until that is settled.

What continues after launch

Two things run monthly. Care, EUR 100 to 300 a month, covers updates, monitoring, backups and small fixes, and it is not redesign and not new features. SEO growth, EUR 500 to 800 a month, covers technical and on-page work, service and location pages, internal links and reporting.

SEO foundation is a one-off at EUR 450 to 750: Search Console, analytics, indexation, technical hygiene, titles, internal links and a plan covering 3 to 6 months. You buy it once. The full set of numbers is on the packages page.

When to spend less

• If the taproom and your distributors do the selling and the site exists so people can find the door, step 01 at EUR 600 to 900 or step 02 at EUR 900 to 1.500 is the honest purchase.
• If a release sells out through your mailing list, an email tool and one good release page beat a webshop.
• Do not build shipping to countries you have not decided to ship to. Each destination is another set of rules to maintain.
• Buy SEO foundation once before committing to SEO growth every month.

Common questions

Do I need an age gate on the whole site?

A self-declared date of birth on every page proves little and changes how your pages are cached and crawled. The useful checks are at checkout, where an order is attached, and at delivery through the courier. If you run a taproom and do not ship, the site needs a clear statement of the minimum age where you are, not a wall in front of it.

How do I stop the site claiming a batch is available when it is not?

Model releases as content with a state, not as text typed into a page. Marking one sold out is then a single change made by whoever finds out first, and it updates everywhere that release appears. Without that, the same fact lives in several places and one of them will be wrong.

Who owns the site and the data?

You own the code, the repository and the database. You can take the project to another developer without asking us for permission or paying for an export. Hosting is decided per project and agreed during scoping.

Does a webshop replace our distributors?

That is a commercial question, and worth settling before the build. Selling direct changes your margins and your relationship with the shops and bars that carry you. Build the webshop because you have decided to sell direct, not because a website is supposed to have one.

Tell us how people visit, how fast your range changes and whether you want to ship, and we will come back with a scope and a fixed price. Start at the contact form, or read the full list of steps and prices first.