Docs · Story pages

Create, publish, and share a story page

Build a public story page for a SKU, package, or batch; publish it, get its link and QR code, add batch overrides, and retire it.

A story page is the public page behind what you make — the story a buyer finds when they scan the QR code on a bottle or follow a link you sent. You write it, publish it, and share its link or printed QR; what visitors see is covered in What visitors see on a public story page.

Story pages live under Story pages in the left-hand navigation, in the Insights group.

View your story pages

In the navigation, choose Story pages. The list shows each page with its Slug, its Subject (SKU, Package, or Batch), and a Status badge — Draft, Published, or Retired.
Choose a page's row or its Edit button to open it.

A new workspace shows No story pages yet with a Create story page button.

Create a story page

From the Story pages list, choose New story page.
In the Subject card, choose a Subject type:
- Batch — the "what I made" share, available on every plan.
- SKU (renders the latest published package) or Package (pinned to one bottling) — these require a Commercial plan. On a hobby plan they're shown disabled with a note, and the page defaults to a batch page.
Choose the subject. For a batch page you search your batches by code and pick one; for SKU and package pages you enter the subject's id.
In the Address card:
- Slug — the last part of the page's address. Leave it blank to have one derived for you. Use lowercase letters, numbers, and hyphens. A slug is permanent once the page has been published, so a printed QR code always resolves.
- Custom domain — optional, and requires a plan that includes custom domains. Leave it blank to use the default address.
In the Content card:
- Under Exposed fields, tick what visitors should see — Producer narrative, Photos, and Recipe summary. Awards is marked coming soon and can't be turned on yet.
- Tasting notes depends on the page's subject. On a batch page you can tick it: the page then always shows your most recent tasting note for that batch, and it keeps up on its own as you add, edit, or delete notes (public pages are cached for a few minutes, so a brand-new note can take that long to appear). On a SKU or package page it's shown disabled, because a tasting note belongs to one batch and those page types don't point at a single one — switch the subject to Batch, or, from a SKU page, add a batch override (see Add batch overrides to a SKU page below).
- Write your Producer narrative — the story of the batch.
- Add Photos with the photo picker.
In the Theme card, leave Theme override on Workspace default (inherit) to use your workspace theme, or pick another theme for this page.
Choose Create story page. You're taken to the page's editor, where you can publish it.

Publish a story page

Publishing makes a page live at its public address. A page you're editing shows a Publication panel with its current status.

Open the page from the Story pages list.
In the Publication panel, choose Publish.
The panel now shows the Public link — choose Copy to copy it. This is the permanent address the page is shared and QR-printed under.

To take a page offline again, choose Unpublish in the same panel. If you're at your plan's limit of active SKU story pages, Brewstiller tells you so instead of publishing — retire or unpublish another page, or upgrade, then try again.

Get a printable QR code

Once a page is published, its editor shows a QR code card with a print-ready code that opens the page.

Open a published page and scroll to the QR code card.
Scan the on-screen preview with your phone to confirm it opens the right page before printing.
Choose Download SVG (vector) for print artwork, or Download PNG for a high-resolution image.

On a paid plan with a vanity address, a Show Brewstiller mark switch lets you export a plain, white-label code for your own packaging. Free tiers export a branded code.

Hobbyists don't need to build a page from scratch — a finished batch can become a shareable page in one tap.

Prerequisite: the batch must be finished (released or archived).

Open the batch (see Run a batch through its stages) and choose Share what I made.
On the Share what you made screen, choose Create share link. Brewstiller creates and publishes a page for the batch.
Choose Copy link to share it, or Preview page to open it in a new tab.

Sharing is included free and doesn't count against any limit. Each batch has a single share page — sharing the same batch again returns the same link. If the batch isn't finished yet, you're told to finish it first and can come back to share it.

Add batch overrides to a SKU page (Commercial plan)

A batch override is a per-bottling story layered under a SKU page — so each release can carry its own dates, numbers, and notes while sharing the SKU's address. Overrides are a Commercial plan feature and appear under a published SKU page.

Open a SKU story page. Below its editor, find the Batch overrides panel.
Choose Create batch override.
Enter a Batch code — this becomes the last part of the override's address (/stories/<handle>/<sku>/<batch code>). It's permanent once the override is published.
Optionally tick Copy details from the SKU base to pre-fill the narrative, photos, and exposed fields from the SKU page.
Under Exposed fields, a batch override also offers Tasting notes, but it behaves differently here than on a batch page: an override freezes whichever note exists at the moment you first publish (or nothing, if you haven't logged one yet), rather than keeping up with later notes. So record your tasting note first, then tick the toggle, then publish. A note you add, edit, or delete afterwards never changes what an already-published override shows. The editor's hint text tells you which of the two you're getting.
Choose Create batch override, then publish it from its own editor.

Publishing an override freezes the batch's facts (lot, dates, ABV/proof, recipe summary, and — if you ticked it — your tasting note) at first publish, so a bottle already in the field keeps its numbers — but you can keep editing the override's story text and photos afterwards. Once an override is published, its Tasting notes toggle locks (like the other frozen facts): a later toggle change is saved but never shown, so there's nothing more to do there. Each override costs a tenth of a slot toward your active-page limit, so many bottlings stay affordable. A printed batch label keeps resolving to the SKU's evergreen page until that bottling's override is published.

Retire a story page

Retiring takes a page out of active use while keeping its address permanent, so printed labels never dead-end.

Open the page and, in the Publication panel, choose Retire….
Optionally point buyers to a newer release: choose another published story page under Point buyers to a newer release. The retired page's address then redirects there.
Or leave the successor empty and enter a Retirement message to show on the page instead.
Choose Confirm retire.