Website builder

A bakery website that shows
what’s fresh out of the oven.

Tell Netiva’s AI agent how your bakery runs and it builds a site with today’s bake, cake preorders by size and flavor, allergen details and pickup windows — in a live preview.

Start building free More website ideas
Starter prompt

Build a website for an independent bakery open 7 a.m. to 2 p.m., Tuesday to Sunday. The home page lists today’s bake from a collection, with each item’s ready time and a sold-out tag staff set on a phone-sized counter board. Every menu item shows its ingredients, the major allergens it contains and a shared-equipment note, and an allergen guide page puts them in one table. Sell whole cakes and holiday pies as pickup-only preorders with size and flavor variants. Customers add an inscription and pick a window at least 48 hours ahead, saved with the order; each window takes up to 12 orders. Add a custom cake inquiry form.

Build it in Netiva Paste the prompt into a new workspace and adjust it to your business.
Overview

Who this bakery website is for

By noon something has usually sold out, yet the website still shows the full menu and a phone number for cake orders. So customers call to ask what’s left, whether the carrot cake has walnuts and when a birthday cake can be picked up. A bakery website built with Netiva answers most of those questions before anyone picks up the phone. Today’s bake comes from a collection your staff keep current, preorders run through a store with size and flavor options, every item carries its allergens and customers choose a pickup window that still has room.

Key features

What your bakery website can do

  • Today’s bake from a collection

    Each morning’s bake list is a set of records tied to your menu items, so the home page shows what’s actually in the case, when the next tray is ready and what has sold out.

    • Ready times for second and third bakes
    • Sold-out and running-low tags set by staff
    • Tomorrow’s bake list saved as its own view
    • Menu item pages with photos, price and ingredients

  • Cake and pie preorders

    Whole cakes, pies and holiday specials become store products with size and flavor as variants, each with its own price and a stock count set to what you can bake.

    • 6-, 8- and 10-inch sizes priced per variant
    • Hosted one-page checkout with card payments and automatic tax
    • Inscription and requests captured on the preorder page and saved with the pickup booking
    • Custom designs routed to an inquiry form instead of checkout

  • Allergens on every item

    A required allergen field on each menu item means nothing goes live without it. The same details feed a public allergen guide and the preorder page of the cake or pie that item is sold as.

    • Contains list covering the nine major US allergens
    • Shared-equipment and cross-contact note per item
    • Allergen guide page with every item in one table
    • Dietary labels such as vegan shown only where you set them

  • Pickup windows and reminders

    Pickup windows carry an order cap and a cutoff, and each preorder is saved as a booking against the window it chose, so a busy Saturday fills up without overbooking the counter.

    • Windows close once they reach their cap
    • Cutoff hours before each pickup date
    • Confirmation and day-before reminder emails
    • Pickup list on the counter board, for signed-in staff
Data model

The collections behind it

Netiva keeps your records in built-in collections. Here’s a starting structure — the agent adapts it to your prompt, and you can change it any time.

Menu items

Everything you bake, with the ingredient and allergen details customers ask about.

  • Name (required) Text
  • Photo Image
  • Price (required) Counter price; preorder cakes are priced per variant in the store Number
  • Ingredients (required) Paragraph
  • Contains (required) Each of the nine major US allergens the item contains, or none Text
  • Cross-contact note e.g. made on equipment shared with nuts Paragraph
  • Dietary labels Vegan, gluten-free — only claims you can back up Text
  • Preorder product Store product name or SKU this item is sold as Text

Daily bakes

What comes out of the oven on a given day and whether any of it is left.

  • Menu item (required) Relation to Menu items
  • Bake date (required) Date
  • Ready at When the tray reaches the case Date & time
  • Batch size Number
  • Status (required) Baking, in the case, running low or sold out Text

Pickup windows

Time slots for picking up preorders, each with its own limit and cutoff.

  • Pickup date (required) Date
  • Starts at (required) Date & time
  • Ends at (required) Date & time
  • Order cap (required) Most orders the counter can hand out in this window Number
  • Orders booked (required) Counted from this window’s pickup bookings that are booked, deposit paid or picked up Number
  • Order cutoff (required) Last moment to order for this window Date & time
  • Status (required) Open, full or closed Text

Pickup bookings

Every order the counter hands out, from paid preorders to quoted custom cakes, tied to the window it was booked for.

  • Order number (required) Store order number, or a request number for a custom cake Text
  • Customer name (required) Text
  • Email (required) Used for the confirmation and pickup reminder Text
  • Pickup window (required) Relation to Pickup windows
  • Items (required) Sizes, flavors and inscription from the preorder page, or a custom cake’s design brief Paragraph
  • Servings Custom cake requests only Number
  • Reference photo Custom cake requests only Image
  • Status (required) Requested, quoted, declined, deposit paid, booked, picked up or no-show Text

Required field. Types are Netiva collection field types.

Screens

Pages and screens to start with

A typical first version. Ask the agent for more, or annotate the preview to change any of them.

  • Today’s bake

    The home page: what’s in the case right now, when the next tray is ready and which items have sold out.

    Public

  • Menu item

    One item’s photo, price, ingredients, allergens and cross-contact note, plus any dietary labels you set.

    Public

  • Preorder product

    One cake or pie with size and flavor options, a price per variant, its allergens and cross-contact note and the pickup windows still open.

    Public

  • Allergen guide

    Every menu item in one table against the major allergens, with shared-equipment notes underneath.

    Public

  • Custom cake inquiry

    A request form for servings, a design brief, a reference photo and a preferred pickup window, saved as a requested booking until you send a quote.

    Public

  • Counter board

    A phone-sized staff page: set today’s bakes to running low or sold out, and mark pickups, grouped by window with inscriptions, picked up or no-show.

    Your team
How it works

From prompt to a live bakery website

  1. Describe your bakery’s week

    Tell Netiva which days you open, what you bake, how far ahead cakes must be ordered and how many pickups the counter can handle. The agent drafts the collections, pages and preorder products.

  2. Enter the menu and allergens

    Add each item with its ingredients, allergens and a photo in the spreadsheet-like grid. Ask the assistant to tidy item names and ingredient lists, then check every allergen field yourself.

  3. Set up preorders and pickups

    Add size and flavor variants, stock and pickup windows, and ask the agent to keep preorders pickup-only. Open the preview link on your phone, walk through a preorder and annotate fixes in the live preview.

  4. Go live before the next rush

    Publish in one click and connect your domain. Before you change the menu for a holiday, the checkpoint history lets you compare versions and roll back if a page goes wrong.

Why Netiva

Netiva vs a traditional build

Building a bakery website with Netiva compared with a traditional build
Criterion With Netiva Traditional build
Daily menu updates A today’s bake page drawn from a collection that staff update as trays come out A chalkboard photo on social media while the website still lists last season’s specials
Preorders and pickup Online preorders with size and flavor variants, capped pickup windows and a morning pickup list Phone orders written in a notebook and pickup times juggled by hand
Getting started Describe what you need in chat and watch it take shape in a live preview Hire developers, or stitch together templates, plugins and a hosting plan
Content and data Built-in collections with nine field types, bound straight to your pages Set up and connect a separate database or CMS
Making changes Ask the agent; every change is checkpointed and reversible File a ticket, wait for a sprint, redeploy
Hosting and domain Global hosting and automatic SSL; connect a custom domain from the Starter plan Buy hosting, then install and renew SSL certificates yourself
Code ownership Clean production code you own and can export Locked into a template, plugin or agency setup
Examples

Ways teams use it

  • A neighborhood bread bakery

    Two bakes a day, and the sourdough is usually gone by eleven. Counter staff flip items to sold out on the counter board, and weekend loaf preorders stop at the number of loaves the oven can take.

  • A home-based custom cake maker

    One decorator, a handful of cakes a week. Standard flavors and their allergens live on menu pages. Tiered and themed cakes start as inquiries and get a quote by email; once it’s accepted, you add the cake as a one-off store product so the customer pays the deposit at checkout.

  • A pastry shop with holiday rushes

    Pie and yule log preorders open three weeks before the holiday, with pickup spread across two days and a cap on each window. The same store ships shortbread tins with real carrier rates, and each tin still needs an ingredient and allergen label on the package.

Good to know

Before you build

  • Allergen details are yours to keep right

    The site shows what you enter. Update allergens when a recipe or supplier changes. Sesame became a major US allergen in 2023, and the FDA Food Code (since the 2022 edition) asks for written notice of major allergens in unpackaged food where your state or locality has adopted it.

  • Be careful with gluten-free claims

    Under FDA rules, packaged food labeled gluten-free must contain less than 20 ppm gluten, and FDA recommends menu claims follow the same definition. If wheat flour shares your bench and ovens, say so instead of labeling items gluten-free.

  • Cottage food rules for home bakers

    If you bake from home, your state’s cottage food law decides what you can sell and how. Some states limit online sales, shipping or delivery, so check the rules before you open preorders.

  • Pickup checkout and counter sales

    Pickup-only preorders are something you ask the agent to set up, so walk through a checkout in the preview before you open orders. Netiva doesn’t replace your point-of-sale system; sold-out tags change when staff update them unless you connect your POS provider’s API.

Compliance note

Allergen, ingredient and dietary details on your bakery website are your responsibility. Netiva shows what you enter in the menu collection; it doesn’t check recipes or labels. Review each item when a recipe or supplier changes, note shared equipment and ask customers with severe allergies to talk to staff before ordering.

FAQ

Questions about building a bakery website

How do I show which allergens are in each bakery item?

Each menu item has a required Contains field for the major allergens — in the US that means milk, eggs, fish, crustacean shellfish, tree nuts, peanuts, wheat, soybeans and sesame — plus a note for shared equipment. Item pages show those details, and an allergen guide page lists every item in one table. The agent builds the pages; you enter and check the allergen information.

Can customers choose a cake size and flavor when they preorder?

Yes. Each cake or pie is a store product with size and flavor as variants, and every variant can have its own price and stock. Customers pay through a hosted one-page checkout that takes cards and calculates tax automatically. The preorder page asks for an inscription, and the app saves it with the pickup booking. Custom designs go through the inquiry form so you can quote first, then take a deposit as a one-off store product.

How do pickup windows and order cutoffs work?

You ask the agent to build them, along with pickup-only preorders that skip shipping. Each pickup window is a record with a date, a time range, an order cap and a cutoff. The preorder page offers only windows that still have room and whose cutoff hasn’t passed, and the app saves the chosen window with the order as a pickup booking. It can email a confirmation and a reminder the day before pickup. It sends email only, not text messages.

Can staff mark pastries as sold out during the day?

Yes. Staff sign in with their own accounts and open the counter board on a phone, where each of today’s items has a status: baking, in the case, running low or sold out. The home page reads the same collection, so customers checking before they walk over see what’s left. Status changes are manual unless you connect your POS provider’s API.

Which plan do I need to take bakery preorders on my own domain?

You can start on the free plan and build the whole site, including preorder products, in the live preview. Connecting a custom domain is available from the Starter plan, and higher plans add capacity and features. Plans also differ in how many store products you can list, so count your cakes, pies and holiday items and check Netiva’s pricing page before you choose. The code stays yours, and you can export it at any time.

Keep exploring
All ideas
Compare

How Netiva compares

All comparisons

Drafted with AI assistance from Netiva’s product pages and reviewed by the Netiva team. Example data models, screens and prompts are illustrative starting points, not customer projects.

Build your bakery website today

Describe it in a sentence and watch Netiva’s agent build it. Free to start — no credit card required.

Start building free Browse more ideas