# BevWerk Documentation > Auto-generated documentation from Test-Driven Docs (TDDocs). > This file is optimized for LLM ingestion. --- # BevWerk Documentation ## Start with the manager path If you are new to BevWerk, follow this sequence first: 1. [`Your first day in BevWerk`](/docs/getting-started/first-day/) — understand the dashboard and the first meaningful setup cue. 2. [`Manage inventory with confidence`](/docs/inventory/manage-inventory/) — see how BevWerk organizes kegs, packaged inventory, and on-tap readiness. 3. [`Publish your menu`](/docs/publishing/publish-your-menu/) — learn how taplists power Digital Menu, Paper Menu, Bar Menu, and Website Menu experiences. ## Keep exploring with more stories Once the first-run flow makes sense, continue with stories that help people operate BevWerk day to day: - [`Find answers fast`](/docs/support/find-answers-fast/) — learn how BevWerk organizes FAQs and support guidance for quick self-serve answers. - [`Make BevWerk feel like home`](/docs/settings/make-it-yours/) — review profile details, photo management, and password updates. ## Reference docs live alongside stories Not every page needs to be a narrative arc. As this site grows, we will also keep **generic task docs** and **error/troubleshooting pages** in their own reference-oriented sections rather than forcing them into story guides. That work has already started in [`Troubleshooting`](/docs/support/troubleshooting/), where missing-page and sign-in recovery guides live separately from the story-led onboarding path, and in [`Dashboard & navigation`](/docs/dashboard/), where the home screen and app wayfinding can be explained directly instead of awkwardly jammed into a story beat. ## How these docs work This site blends two layers: - **Editorial guides** explain the why, the sequence, and the business outcome. - **Generated tutorials** prove the flow with real browser recordings and step-by-step clips. Every walkthrough is: 1. **Captured** — A real browser workflow is recorded. 2. **Verified** — the recording is replayed in cinematic mode. 3. **Published** — videos are sliced, markdown is generated, and the docs site updates. ## For AI Agents This site exposes an [`/llms.txt`](/llms.txt) endpoint — a plain-text version of all documentation, optimized for LLM ingestion and RAG pipelines. --- # Account & billing Once the personal and company basics are set up, the next layer is the parts of BevWerk that belong to the *business*, not any one person: who can sign in, what point-of-sale system feeds your sales data, and what plan the company is on. ## Start here 1. [`Connect a POS integration`](/docs/account/integrations/) — find where Clover and Square connections live, and what has to be true before you can start one. 2. [`Manage users`](/docs/account/users-management/) — see the team table and the form for inviting a new teammate. 3. [`Understand your subscription`](/docs/account/subscription/) — see what BevWerk shows you about your plan and billing status. 4. [`Understand POS sync operations`](/docs/account/pos-sync-operations/) — know which data moves in which direction, and when to intervene. 5. [`Export your company data`](/docs/account/export-company-data/) — download a JSON copy of your records. 6. [`Roles and what each one can do`](/docs/account/roles-and-permissions/) — why a colleague sees options you do not. 7. [`How billing and plan changes work`](/docs/account/billing-and-plan-changes/) — what you pay for, and what changes it. 8. [`The BevWerk Assistant`](/docs/account/bevwerk-assistant/) — what it can answer, what it can do, and where its answers come from. ## Why this section matters These are owner/manager-level controls. They answer questions like: - where do I connect Clover or Square so sales show up in reports? - who currently has access to this company's BevWerk account, and how do I add someone? - what plan is this company on, and where do I see that? Getting these right early avoids confusion later — sales reports stay empty without a POS connection, and new teammates can't get to work without an account. --- # Understand inventory activity When **Activity** is enabled for your location, it lists inventory actions and the person who made them. Single changes show their recorded details in the row. An action affecting several kegs can be expanded for its per-keg breakdown. A draft line cleaning appears once. For example, **cleaned 14 lines · 46 oz each** explains the action. Expand a cleaning affecting several kegs to see one table row per keg, with its beverage, ounce change and percentage remaining. A single-keg change shows these amounts directly in the main row. For example, **−46 oz** and **100% → 97.7%** show what the cleaning removed from that keg. Recorded taps appear alongside the action; the feed does not infer a historical tap-to-keg pairing. Direct inventory edits appear as **adjusted inventory**. Bottle and can stock changes use units. New keg additions record the signed-in person who added them. **User not recorded** means an event has no recorded author; it does not mean an automated process made the change. Older events keep their recorded attribution, and BevWerk does not guess a missing author. **Reason not recorded** means the record does not establish what caused the quantity change. Older entries keep this label. BevWerk does not assign a reason based on nearby times. New quantity changes retain the package size used to calculate ounces. For older entries, **Calculated using current package size** means the ounce amount uses the package definition available today. If that definition is missing, the entry shows **Volume unavailable**. Filter by event type, person or date to narrow the list. Choose both a start and end date to apply a date range. Your previous results stay visible while you finish selecting the range. If a date is unreadable or the end comes before the start, correct it or select **Clear filters**. Clearing both dates removes the date filter. The keg quantity filter includes the actions containing keg changes. Loading more keeps every action together with its changes. --- # The BevWerk Assistant The **BevWerk Assistant** answers questions about using BevWerk and can help you look up some information for your active location. It is available to employees and managers only when it is enabled for their company, so it may not appear in every account. ## What it can answer Ask how to use a feature or where to find something. The Assistant answers app-use questions from BevWerk's help pages. Its answers include the help pages it used when those sources apply. If the documentation does not cover your question, it should say so rather than fill the gap with a general answer. When those lookups are available, the Assistant can also: - list taps and find kegs at your active location - check whether a Square or Clover connection needs a manager to reconnect it - summarize the top ten Styles at your active location by sales revenue or ounces - when sales data lookups are available for your company, answer questions about Styles and sub-styles, including total sales, ounces sold, and comparisons between two date ranges Sales data lookups are in a limited pilot and are coming soon to other companies. When enabled for your company, you can ask about explicit date ranges up to 366 days. The Assistant uses your active location's sales data and reports the measure it ranked by. Operational lookups use your company and active location. Check important details in BevWerk, especially if the Assistant says a list may be incomplete. ## Proposed actions When action proposals are available, the Assistant can prepare a card to put a keg on an empty tap, queue a keg as **Up Next**, move an Up Next keg onto its tap, or clear a tap. Managers can also ask it to reduce the volume recorded for a keg. An action card does not change your records. Select **Open** to review the existing On Tap dialog, then submit the change there if it is correct. Closing the dialog leaves your records unchanged. ## What the Assistant cannot do The Assistant cannot answer an app-use question that is not covered by its help pages and available information. It cannot change taps, kegs, or other records on its own. Any action it proposes still needs your review and submission in BevWerk. ## What to do next - Ask an operational question in the Assistant, then check its source pages or data in BevWerk. - For account access, see [`Roles and what each one can do`](/docs/account/roles-and-permissions/). --- # How billing and plan changes work BevWerk bills your **company**, not each person who signs in. Adding a colleague does not change what you pay; adding a _room_ does. ## What the price is built from A subscription has two parts: a base charge for the company, and an additional charge for each location beyond the first. That shape follows how the product is used. Every location brings its own taps, taplists, menus, and sales data — real capacity — while extra users are just more people looking at the same rooms. It also means the cost of trying BevWerk in one taproom is not affected by how large your team is. Current prices are shown on the Subscription page in the app rather than repeated here, so you are always reading the live figure rather than one that was true when this page was written. The email address used by the person paying does not need to match your company's email address. Checkout is tied to the company whose manager started it. ## Where to see your status Subscription lives under the Company section of the user menu, and it shows your plan and billing status. See [`Understand your subscription`](/docs/account/subscription/) for what each state means. Viewing subscription details is manager-only, so if you cannot find it, check your role — see [`Roles and what each one can do`](/docs/account/roles-and-permissions/). ## Changing a plan Plan changes are made in the app and take effect against your existing subscription rather than creating a second one. If a change appears not to have applied, refresh the Subscription page before trying again — repeating a change that already succeeded is the main way people end up confused about what they are paying for. ## Adding a location Adding a location to a plan that does not cover it will affect billing. This is worth knowing before you create a location "just to try something", because the new room is a billable unit from the moment it exists, not from the moment you start using it seriously. ## What a lapsed subscription affects Some capabilities depend on an active subscription — POS integrations in particular are gated on it. If **Integrate Clover** or **Integrate Square** is missing from a location's menu, check your subscription status before assuming the integration is broken. See [`Connect a POS integration`](/docs/account/integrations/). ## Cancelling Cancellation is handled through the subscription controls in the app. Your subscription stays active until the end of the current billing period. After that, you'll need to start a new subscription to keep using BevWerk; your company's data is kept. Before you cancel, consider [exporting your company data](/docs/account/export-company-data/) so you keep a copy of your records independently of your account status. ## What to do next - Check your current state in [`Understand your subscription`](/docs/account/subscription/). - If a POS option is missing, start with [`Connect a POS integration`](/docs/account/integrations/). --- # Export your company data **Export Company Data**, available from the Company section of the user menu, downloads a JSON file of your company's **setup and catalog**. ## What it includes Your company details and branding, locations, POS integrations, and your catalog: Distributors, Producers, Products, Styles, Glassware, Menu Categories, and your user list. ## What it does not include This is not a full backup, and it is important not to treat it as one. It does **not** contain: - individual inventory items — the specific kegs and cases you have received - orders or sales history - keg tracking, deposits, or distribution records - activity history If you need a record of stock movement, the [Distribution](/docs/inventory/track-distribution/) tabs offer targeted CSV exports covering keg returns and deposits. ## It contains employee personal data The export includes your user list with names, email addresses, and dates of birth. Treat the file the way you would treat any staff record: store it somewhere you control, and do not forward it casually. If you are sharing data with an accountant or analyst, check whether they actually need the user list before handing over the whole file. ## Who can run it Exporting company data is limited to managers. The export includes company-wide setup and catalog records, and only the locations you manage. Staff records are limited to that permitted location scope. If the option is not available to you and you expect it to be, the likely cause is your role rather than a fault — see [`Manage users`](/docs/account/users-management/). ## Location inventory CSV For an inventory CSV, open **Locations** in company settings and choose the inventory download for your **active location**. The CSV includes one row per inventory type, with stock quantities and the latest purchase costs. Switch your active location before exporting a different location. ## Background exports When background exports are enabled, BevWerk shows whether your export is queued or being prepared, followed by the number of records and file size. The download starts when the complete file is ready. Choosing the same export again while it is running checks that job instead of adding a second one. Keep the page open until the download starts. If you change accounts or your active location, start the export again in the new context. Files are available for **24 hours** after preparation finishes. After that, create another export. The job record is retained for seven days. Access is checked again before a download, so a file may become unavailable if your company or location access changes. ## If an export fails Background exports can be up to 256 MiB and take up to 60 seconds to prepare. An unusually large record can also stop an export. BevWerk shows a failure message and does not offer a partial file. Try a location inventory export for a smaller scope, or contact support if a single record is too large. Background exports are being introduced gradually. Until they are enabled for your environment, the older direct downloads remain available. Direct downloads can be up to 25 MiB and take up to 60 seconds to prepare. The company JSON file keeps its existing format: its outer value is a string containing the exported JSON. ## What to do next - Review who holds which role in [`Manage users`](/docs/account/users-management/). - For recurring operational numbers, prefer the built-in views in [`Understand sales reports`](/docs/reports/sales-reports/). --- # Connect a POS integration BevWerk does not have a standalone "Integrations" page. The connection points live one level deeper, inside company setup, because a POS integration is really a property of a _location_, not the app as a whole. ## Where this lives Go to **Settings → Company Info**. Two things matter on this page: - A **POS** row in a separate **Integrations** panel, below Basic Info, shows whether Clover and Square are available to this company at all. - The **Locations** table lists every location, and each row has a kebab (⋮) menu with the actual connect actions — **Integrate Clover** and **Integrate Square** — when that location isn't connected yet. ## What gates the connect actions The **Integrate Clover** and **Integrate Square** actions in a location's kebab menu only appear once POS is enabled for the company. That's a plan-level entitlement: the POS toggles in the Integrations panel are disabled until the company is on an active/pro subscription. So if you don't see "Integrate Clover" or "Integrate Square" on a location, check [`your subscription status`](/docs/account/subscription/) first — that's usually why. Once POS is enabled, a connected location shows the relevant POS icon (with a tooltip naming the integration) in the table's Integrations column, and the kebab menu switches from "Integrate" to "Remove" for that POS. For Square, a connected location also offers **Edit Square settings**, which opens that location's Square location, category and tax choices so you can change them without removing the integration. If a manager installs BevWerk from Clover's App Market, BevWerk asks them to confirm the company before connecting the Clover merchant. When you integrate a location with Square, the Square location list shows each location's address and Square ID under its name, so locations with similar names can be told apart. If the location already has Square sales in BevWerk, the Square location those orders came from is preselected and marked. ## Reconnect Square All of a company's locations share one Square sign-in. If Square's authorization expires or is revoked, BevWerk cannot sync taps, orders or inventory until a manager reconnects. While that is the case, a location's overflow menu offers **Reconnect Square** in place of **Integrate Square** or **Edit Square settings**, and the location may show a **Reconnect Square** badge in the Locations table. Reconnecting from a location renews the shared sign-in, then returns you to that location's Square settings only. If the location kept its saved settings, they are filled in; if not, the Square location its orders came from is preselected. Review the selections and save. Other locations keep their settings and start syncing again once the sign-in is renewed. ## Watch the walkthrough - [Open the integrations walkthrough](/docs/tutorials/review-pos-integrations/) The walkthrough stops at the kebab menu — actually connecting Clover or Square hands off to that provider's own sign-in page, which isn't part of this app. ## What to do next - Continue to [`Manage users`](/docs/account/users-management/) - Or revisit [`Understand your subscription`](/docs/account/subscription/) if POS isn't showing up yet --- # Understand POS sync operations Once Clover or Square is connected, data moves between BevWerk and your POS. Most of it moves on its own. The manual controls that exist move different data in different directions, and running the wrong one is the usual reason a sync "did not work." ## Sales come to you, automatically Order sync **pulls** completed sales from your POS into BevWerk. This is what fills Total Sales, Popular Products, Popular Styles, and the depletion behind Keg Movement. Ordinary sales flow in on their own — you do not need to press anything for yesterday's pints to appear. The manual sync exists for the exceptions: backfilling after an outage, or checking a suspicion that something did not come through. ## Taps go the other way Tap sync **pushes** what you have on tap in BevWerk out to your POS, so the items your staff ring up match the beers you are actually pouring. This direction surprises people. BevWerk is the source of truth for what is pouring, because that is where you manage kegs and taplists. The POS is the source of truth for what sold. Each system pushes what it knows and pulls what it does not. ## Which manual controls you actually have For a **Square** location, two manual actions are available: **Sync Square Taps** and **Sync Square Orders**. For a **Clover** location there are no manual sync buttons. Clover data flows automatically, and the only integration action on the location is removing the connection. If you are looking for a Clover sync button because something seems stale, the answer is not a button you have missed — see the checklist below. Packaged inventory is treated as its own concern rather than folded into tap sync, because packaged stock does not live on a tap, does not empty a keg, and does not follow the draft lifecycle. ## When a sync looks like it did nothing Work through these in order: 1. **Check the active location.** Syncs are per location. A sync run against the wrong room does exactly what you asked and nothing you wanted. 2. **Check direction.** If your POS is missing beers, you want a tap push, not an order pull. 3. **Give sales a moment.** Order data arrives on its own; a sale from a few minutes ago may simply not have landed yet. 4. **Confirm the integration is still connected.** POS tokens expire, and a lapsed connection fails quietly from the outside. ## What to do next - Set up or repair the connection itself in [`Connect a POS integration`](/docs/account/integrations/). - See what the synced sales are telling you in [`Understand sales reports`](/docs/reports/sales-reports/). --- # Roles and what each one can do "Why can they see that when I cannot?" is one of the most common questions in BevWerk, and the answer is almost always a role. ## Roles are assigned per user Each user carries a **User Role**, set when you add them and changeable later. The role decides which parts of the product appear — not just whether an action succeeds, but whether it is offered at all. That distinction matters when you are helping a colleague over the phone. If they cannot find a menu item you are describing, the likely explanation is that BevWerk is not showing it to them, not that they are looking in the wrong place. ## Manager-only surfaces Manager access controls the parts of BevWerk that affect the whole business rather than a single shift, including Reports, Website, company-wide settings, subscription details, and [exporting company data](/docs/account/export-company-data/). Employees keep the operational surfaces they need for service. ## Your first role is the one that counts A user can hold more than one role. When that happens, BevWerk uses the **first** role assigned, because that is the role your session actually runs as when the server checks a permission. This is worth knowing because it produces a genuinely confusing case: someone whose roles are listed as employee first and manager second is treated as an employee. Adding a manager role alongside an existing one is not the same as making someone a manager. If a colleague should have manager access and does not appear to, check the order of their roles rather than just whether "manager" is present. There is one rough edge here we have not smoothed yet: a small number of menus open for anyone holding a manager role in any position, while the actions inside them follow the stricter first-role rule. The effect is a menu that opens but looks emptier than expected. The fix is the same — correct the role order. ## Deactivating rather than deleting A person can be **Deactivated** for the company you are managing instead of removed. Their record and history stay intact, and their access to any other company is not changed. If deactivation leaves them with no active company, they see a message at sign-in naming the company that turned off their access. The last active manager cannot be deactivated; make someone else a manager first. Use **Hide deactivated** to keep the list focused on current staff. Deactivation is the right tool when someone leaves. Deleting a person who has history attached would make past activity harder to explain, and seasonal staff often come back. ## Location assignment Users are assigned to a **Location**, or to **All Locations** for people who work across rooms. This shapes which data they see once signed in — see [`Manage locations and the active location`](/docs/settings/manage-locations/). ## What to do next - Add or edit people in [`Manage users`](/docs/account/users-management/). - If someone cannot get in at all, that is a different problem — see [`Fix common sign-in problems`](/docs/support/troubleshooting/sign-in-problems/). --- # Understand your subscription Subscription status isn't just a billing detail in BevWerk — it's also what unlocks features like POS integrations (see [`Connect a POS integration`](/docs/account/integrations/)). ## Where this lives Open the user menu, then **Company → Subscription**. The same view is also reachable from the **Subscription** button inside Settings → Company Info. ## What you'll see Most accounts see a billing summary with the recurring price, the number of active locations the plan covers, and an action button for managing the plan. Some accounts — internal demo and friends-of-BevWerk accounts — see a "You are a Super Friend!" message instead of the billing summary. There's no inconsistency here: those accounts are intentionally exempted from the billing UI, so this is the expected, fully-supported state for them rather than a missing feature. ## Payment notices and paused subscriptions Past-due and paused-subscription notices are coming soon. If you need help with a payment or subscription, [contact support](mailto:support@bevwerk.com). ## Watch the walkthrough - [Open the subscription walkthrough](/docs/tutorials/manage-subscription/) The walkthrough shows the subscription state available in its demo account. ## What to do next - Revisit [`Connect a POS integration`](/docs/account/integrations/) — POS connections depend on plan status - Or go back to [`Manage users`](/docs/account/users-management/) --- # Manage users Every BevWerk company needs more than one set of hands. The Users workspace is where managers see who already has access and bring on someone new. ## Where this lives Open the user menu in the top-right of the toolbar, then **Company → Users**. This opens an overlay with two views: - A **table** of existing users, with name, location, and role, plus search and a "Hide deactivated" option. - An **add** form, reached via the **Add User** button (managers only), for inviting a new teammate with a role, basic info, and login details. If the user list could not refresh, choose **Reload** before adding a user or changing access. If saving a user shows "Saved. Their access updates the next time they sign in, or within 15 minutes.", the change was saved and their access will update at their next sign-in or within 15 minutes. ## Adding someone starts with their email The Add User form shows every field from the start, but only the role and **Email** are open. Enter the person's email and choose **Check email** (or press Enter). BevWerk then looks the address up: - **No BevWerk login yet:** the name, password, date of birth and phone fields open, and **Save** becomes available once the required fields are filled. - **Already has a BevWerk login:** they keep their existing login, so the detail fields are hidden and the button reads **Send invitation**. They join only after accepting the emailed link, which is valid for 14 days. Sending again replaces the earlier link. - **Has a login but hasn't confirmed their email yet:** BevWerk won't add them until they open the verification link it emailed them (signing in sends a fresh one). Ask them to do that, then check the email again. - **Already a member, or access was removed:** the form says so, and offers **Restore access** where it applies. After a member's access is removed, employees can no longer see that person's profile. Managers can see the member's name, role, and dates they joined and lost access, so they can restore access. Other profile details, including email, phone, and date of birth, are hidden. The member's name stays on past activity records. Someone you add with **Save** gets their own verification link by email and must open it before their first sign-in. Changing the email closes the detail fields again until you check the new address; anything you already typed stays. ## Accepting an invitation Open the invitation link in the email within 14 days. The page names the company, the role and a shortened form of the address the invitation was sent to; accepting adds that login, so check it is yours. Then choose **Accept** to join or **Decline** to refuse. After accepting, sign in to use the company account. If the link has expired, ask a company manager to send a new invitation. ## Why two views Keeping the table and the form as separate tabs in the same overlay keeps "who's already here" and "bring someone new on" from competing for space — useful when a manager is mid-task adding one person but wants to double check an existing teammate's role first. ## Watch the walkthrough - [Open the users management walkthrough](/docs/tutorials/manage-user-access/) The walkthrough opens the Add User form and shows its fields, but stops short of submitting — no real account gets created. ## What to do next - Continue to [`Understand your subscription`](/docs/account/subscription/) - Or go back to [`Connect a POS integration`](/docs/account/integrations/) --- # Catalog setup Before inventory, taps, or menus mean anything, BevWerk needs to know about the things you sell and who you get them from. That reference data lives in the gear-icon Tools menu, separate from the personal and company settings covered in [`Account & billing`](/docs/account/). ## Start here - [`Manage your catalog`](/docs/catalog/manage-catalog/) — Distributors, Producers, Products, and Styles, plus the built-in Import catalogs for Producers and Styles. - [`Distributors, Producers, Products, and Styles`](/docs/catalog/catalog-entities/) — what each catalog record holds and how they connect. ## Why this section matters These four areas are catalog entities: they describe your business's supply side, and most other workflows (inventory, taps, menus) reference them rather than duplicating the same information. Two of them — Producers and Styles — also offer a faster path than typing everything by hand: an **Import** option that pulls from BevWerk's built-in reference catalog instead of a blank form. ## Reviewing discoveries When your company has catalog discovery enabled, managers can review suggested Producers and Products in the discovery inbox. Each list loads up to 100 suggestions at a time. Select **Load more producers** or **Load more products** to continue; decisions and additions work on every loaded page. The navigation badge counts all waiting Producers. Expand **Sources** on a suggestion to see its observation count and the first 20 observations. Select **Load more sources** for further evidence. A listing does not mean your Distributors carry the Product. --- # Distributors, Producers, Products, and Styles The catalog is BevWerk's descriptive layer. It records facts about beer that stay true between deliveries, so inventory records can point at them instead of repeating them. ## Distributors Who you buy from. A Distributor carries contact details — **Email**, **Phone** — and a **Keg Deposit**. That deposit field is the one worth setting carefully. It is what makes the money side of [Distribution](/docs/inventory/track-distribution/) meaningful: without it, an empty keg in your cooler is just an empty keg rather than a specific amount of your money waiting to come back. ## Producers Who makes the beer. A Producer has a **Display Name**, a location (**City**, **Country**), and a type — **Brewery**, **Cidery**, and so on. Producers matter to guests more than most catalog data. A menu that names the brewery and where it is from is doing work that a beer name alone cannot. ## Products What a producer makes. A Product carries a **Display Name**, a **Description**, style information, and specifications such as **Plato**. Products are the record inventory actually points at. When a beer arrives again next season, you add a new inventory record against the same Product rather than describing the beer a second time — which is why a Product's details are worth getting right once. **Clone** helps when a producer's range shares most of its details and differs in a few. ## Styles How beer is classified. A Style has a name and a **Type**, and grouping by style is what lets a guest scanning a long list find the kind of thing they are in the mood for. ## How they connect Distributor → who sold it to you. Producer → who made it. Product → what it is. Style → what kind it is. An inventory record points at a Product and adds what is true of that particular keg or case. Fix a producer's name once and every menu, report, and inventory record referring to it is correct. That is the entire argument for a catalog: the alternative is the same beer spelled three ways across four menus. ## Deactivating rather than deleting Catalog records can be deactivated and hidden with **Hide deactivated** rather than removed. A seasonal beer you will pour again next year should be deactivated, not deleted — deleting it would orphan the history of every keg you already sold. ## What to do next - Turn catalog records into stock you own in [`Add and edit inventory items`](/docs/inventory/add-inventory-items/). - See the wider workflow in [`Manage your catalog`](/docs/catalog/manage-catalog/). --- # Manage your catalog All four of these live behind the gear icon in the toolbar (Tools menu), not the avatar menu — that's reserved for personal and company-wide settings. Each one opens the same way: a table of existing records, and an "Add" form reached from a button next to the title. ## Distributors Who you buy from. A Distributor record is mostly contact info — name, rep, phone, email — used elsewhere to associate purchases with a source. Contact details can be specific to a location. Check the active location before editing a contact so you change the intended record. ## Producers and Products **Producers** are who makes what you sell — breweries, wineries, distilleries. **Products** are the specific items: a particular beer, wine, or spirit, tied back to a Producer and a Style. Setting up Producers before Products keeps Product entry from turning into free-text guessing about who made something. ## Styles The Style taxonomy Products are categorized under (think: "IPA," "Pilsner," "Stout"). Products reference a Style, which is what powers style-based filtering and reporting elsewhere in BevWerk. ## The Import catalogs Producers and Styles both have an **Import** icon button next to their title (look for the tooltip — the icon itself isn't labeled). This isn't a CSV uploader. It opens a filter panel over BevWerk's own built-in reference catalog: - **Producers**: filter by **State** and **Country**, then **Import Selected** to bulk-add producers from that region instead of typing each one in by hand. - **Styles**: filter by **Type**, then **Import Selected** to bulk-add from BevWerk's built-in style list. This is the fastest way to seed either list — worth knowing about before manually typing in Producers or Styles one at a time. ## Watch the walkthrough - [Open the catalog entities walkthrough](/docs/tutorials/manage-catalog-entities/) The walkthrough opens each area's table and add form, and opens both Import catalogs, but stops before importing or saving anything — no real catalog data gets created. ## What to do next - Continue to [`Manage operational settings`](/docs/operations/manage-operations/) - Or revisit [`Account & billing`](/docs/account/) for the company-level settings this section assumes are already in place --- # Dashboard & navigation The dashboard is where BevWerk teaches the shape of the workspace before you have a polished setup. ## Start here 1. [`Understand your dashboard`](/docs/dashboard/understand-your-dashboard/) — read the blank-slate guidance, side navigation, and next-best-action cues like an owner or manager. 2. [`Open the direct dashboard walkthrough`](/docs/tutorials/understand-the-dashboard/) — jump straight to the recorded version when you want the proof layer without extra narration. 3. [`Customize your dashboard widgets`](/docs/dashboard/customize-widgets/) — show or hide the six panels so the first screen suits your job. ## What this section is for This section is deliberately **reference-first**. It exists to explain: - what the home screen is trying to tell you - how the side navigation maps the product - which empty states are useful guidance rather than errors - how the dashboard connects directly to inventory and publishing workflows ## Where this fits in the larger docs set - Start with [`Your first day in BevWerk`](/docs/getting-started/first-day/) if you want the story-led version. - Come here when you want the dashboard explained plainly, without the rest of the onboarding arc around it. --- # Customize your dashboard widgets The dashboard is the screen you see most often, which makes it the screen most worth tailoring. You can hide any section, but at least one dashboard section must remain visible. ## The six widgets - **On Tap** — what is pouring right now, drawn from your active taplists. - **Total Sales** — sales performance over the period you are looking at. - **Popular Products** — which beverages are actually moving. - **Popular Styles** — the same question one level up, by style rather than by product. - **Inventory Flow** — the distribution pipeline, so incoming stock is visible without leaving the dashboard. - **At-Risk and Stale Kegs** — draft turnover, useful for spotting a keg that is emptying faster or slower than expected. ## Hiding is not losing A hidden widget stops rendering; it does not stop being tracked. The underlying data keeps accumulating and the corresponding reports and workspaces are unaffected, so you can bring a widget back later and it will be current rather than empty. This matters because the useful dashboard changes with the season. A taproom deep in festival planning wants Inventory Flow in front of them. In a quiet month, that same section is noise. ## Your layout is yours Widget visibility is stored as part of your own settings, so tailoring the dashboard does not change what your colleagues see. Two managers at the same location can each keep the view that suits their job. ## Blank space is a signal, not a failure A widget with nothing in it usually means a prerequisite is missing rather than something being broken — no sales yet, no POS integration connected, no taplist set up. Read an empty widget as a pointer to the setup step it depends on. ## What to do next - Understand what each panel is telling you in [`Understand your dashboard`](/docs/dashboard/understand-your-dashboard/). - Connect the sales data that fills several of these widgets in [`Connect a POS integration`](/docs/account/integrations/). --- # Understand your dashboard This guide is for the moment you land in BevWerk and want to know what the home screen is actually telling you. ## What you'll learn By the end of this guide, you will know: - how BevWerk uses the dashboard to orient a brand-new workspace - why the side navigation matters even before you have inventory data - what the taplist prompt is trying to teach you - how dashboard cues connect directly to inventory and menu publishing ## What the dashboard is doing for you On day one, the dashboard is not trying to impress you with charts. It is trying to reduce ambiguity. That means it focuses on three useful jobs: 1. **showing the product map** through the left navigation 2. **pointing to the next meaningful action** when your workspace is still empty 3. **teaching the relationship** between taplists, inventory, and guest-facing menus ## Watch the walkthrough - [Open the direct dashboard walkthrough](/docs/tutorials/understand-the-dashboard/) If you want the broader onboarding arc around it, the story-led version still lives in [`Your first day in BevWerk`](/docs/getting-started/first-day/). ## How to read the blank-state guidance Blank space on the dashboard is not failure. In BevWerk, it usually means one of two things: - you have not set up the operational structure yet - the app is showing you the prerequisite for the next workspace you open That is especially important around **taplists**. BevWerk uses them as the connective layer between what you stock and what you publish. ## Why the side navigation matters so early Even before you add data, the side navigation tells you how the product is organized: - **Dashboard** gives you orientation and next-step context - **Beverages** is where inventory structure lives - **Menus** is where that structure becomes guest-facing output - **Settings** and **Help** support the personal and operational edges of the workflow That makes the dashboard less of a destination and more of a launchpad. ## What to do next - Continue to [`Manage inventory with confidence`](/docs/inventory/manage-inventory/) - Then move on to [`Publish your menu`](/docs/publishing/publish-your-menu/) - Or go back to the story-led version in [`Your first day in BevWerk`](/docs/getting-started/first-day/) --- # Start here If you're opening BevWerk for the first time, start with the same sequence a new owner or manager sees in a brand-new workspace. ## The recommended path 1. [`Key concepts and vocabulary`](/docs/getting-started/key-concepts/) — the handful of words BevWerk uses precisely, and how they relate. 2. [`Your first day in BevWerk`](/docs/getting-started/first-day/) — understand the dashboard, blank-slate guidance, and the first setup task. 3. [`Manage inventory with confidence`](/docs/inventory/manage-inventory/) — see how BevWerk separates kegs, bottles and cans, and on-tap readiness. 4. [`Publish your menu`](/docs/publishing/publish-your-menu/) — understand how taplists unlock Digital Menu, Paper Menu, Bar Menu, and Website Menu experiences. 5. [`Create your BevWerk account`](/docs/getting-started/create-your-account/) — what sign-up asks for and what exists when you finish. ## Why this sequence works - **The dashboard** shows the first-run prompts and next best action. - **Inventory screens** explain how BevWerk organizes the work behind your beverage program. - **Menu screens** show the payoff: the same taplist data powers what your guests eventually see. If you prefer the raw recorded walkthroughs, jump straight to [`Tutorials`](/docs/tutorials/). --- # Create your BevWerk account Signing up creates two things at once: your **company** and your own user account inside it. That is why the form asks for both sets of details. ## What you provide **About the business** — **Company Name**, **Company Email**, **Address**, **City**, **State**, **Zip Code**, and **Phone**. These become your company record, and several of them appear later on menus and public pages, so use the details you would want a guest to see. **About you** — **First Name**, **Last Name**, **Email**, and a **Password** with **Confirm Password**. This is your personal sign-in, separate from the company email. Keeping the two apart matters more than it looks. Your personal email is how _you_ sign in and reset a password; the company email is how the business is reached. Using one address for both is the most common cause of a locked-out account later, when the shared inbox changes hands and the reset link goes somewhere nobody reads. See [`Reset your password`](/docs/support/troubleshooting/reset-your-password/). ## Terms Sign-up includes agreeing to BevWerk's terms and conditions. They are presented in full on the page rather than behind a link, so you can read what you are agreeing to before you finish. ## Confirm your email When you finish the form, BevWerk sends a verification link to your personal email and takes you to the sign-in page. Open the link within an hour, then sign in with the email and password you chose. Until the link is opened, signing in tells you the address is not verified yet and emails you a fresh link. If the email you enter already has a BevWerk login, sign-up stops and asks you to sign in instead. If you do not remember that password, [`reset it`](/docs/support/troubleshooting/reset-your-password/). ## What exists when you are done A company with you in it — and not much else. Your catalog is empty, no locations are configured beyond what you entered, and no beer exists yet. That blank state is deliberate rather than unfinished. BevWerk does not guess your beverage program, so the first screens guide you through building it in an order that works. See [`Your first day in BevWerk`](/docs/getting-started/first-day/). ## Adding your team comes later You do not need colleagues' details during sign-up. Add them once you are in, with the role each should have — see [`Roles and what each one can do`](/docs/account/roles-and-permissions/). ## What to do next - Learn the vocabulary before you start clicking in [`Key concepts and vocabulary`](/docs/getting-started/key-concepts/). - Then follow [`Your first day in BevWerk`](/docs/getting-started/first-day/). --- # Your first day in BevWerk This guide is designed for **owners and managers** who are starting from a fresh BevWerk workspace. ## What you'll accomplish By the end of this guide, you will know: - what the dashboard is trying to tell you on day one - where BevWerk keeps beverage inventory work - why **creating a taplist** is the first key setup task - how menu publishing builds on that taplist foundation ## What to expect on a new account A brand-new workspace is intentionally quiet. BevWerk doesn't pretend you already have a polished menu and fully stocked inventory. Instead, it points you toward the next meaningful action: - review the dashboard guidance - create your first taplist - start organizing inventory against that operational structure That makes the onboarding experience honest and actionable. ## Watch the walkthrough - [Open the recorded first-day walkthrough](/docs/tutorials/get-started-with-bevwerk/) ## Why the taplist matters so early In BevWerk, the taplist is more than a display choice. It is the connective tissue between: - **what you stock** - **what is on tap** - **what appears on guest-facing menus** Once you understand that, the rest of the app feels much more intuitive. ## What to do next - Continue to [`Manage inventory with confidence`](/docs/inventory/manage-inventory/) - Then move on to [`Publish your menu`](/docs/publishing/publish-your-menu/) --- # Key concepts and vocabulary BevWerk uses a few words in specific ways. Knowing them makes every other page easier to read, because the product's structure follows this vocabulary closely. ## Company and location Your **company** is the business. A **location** is a place that pours. The split decides where a setting lives. Things true of the business — your catalog, your users, your subscription — sit at the company level. Things true of one room — taps, tax rate, address — sit on the location. BevWerk always works in the context of one **active location**, which is why the same screen can show different data depending on which room you have selected. See [`Manage locations and the active location`](/docs/settings/manage-locations/). ## Catalog The **catalog** describes beverages in the abstract: **Distributors** you buy from, **Producers** who make the beer, **Products** they make, and **Styles** those products belong to. Catalog records are reusable and long-lived. They do not represent stock you own — they represent facts about beer that stay true between deliveries. ## Inventory **Inventory** is stock you actually have. An inventory record points at a catalog Product and adds what is true of *this* one: size, cost, deposit, status. Inventory splits by format. **Kegs** is draft; **Bottles & Cans** is packaged. They are separated because their lifecycles differ, not to make you look in two places. ## Taps and taplists A **Tap** is physical hardware. A **Taplist** is a grouping of taps that a menu can point at. One bar can publish several taplists without rearranging a single line. ## Menu surfaces BevWerk publishes to four **menu surfaces** — **Bar Menu**, **Digital Menu**, **Paper Menu**, and **Website Menu**. They draw on the same beverages and taplists but are designed independently, because a screen, a printed sheet, and a public web page are read in different circumstances. See [`Choose the right menu surface`](/docs/publishing/choose-a-menu-surface/). ## How it fits together Catalog describes the beer. Inventory says you have some. Taps and taplists say where it is pouring. Menu surfaces show that to whoever needs to know — staff, guests in the room, or people deciding whether to visit. Each layer depends on the one before it, which is why an empty menu is usually a missing taplist rather than a broken menu. ## What to do next - Walk the product in order in [`Your first day in BevWerk`](/docs/getting-started/first-day/). - Set up the descriptive layer first in [`Manage your catalog`](/docs/catalog/manage-catalog/). --- # Inventory Inventory in BevWerk is organized around the questions managers actually need to answer, not around one giant all-purpose screen. ## Start here 1. [`Manage inventory with confidence`](/docs/inventory/manage-inventory/) — understand how kegs, bottles and cans, and on-tap views each serve a different operational purpose. 2. [`Add and edit inventory items`](/docs/inventory/add-inventory-items/) — create the records everything else depends on. 3. [`Run the On Tap workspace`](/docs/inventory/on-tap-operations/) — the verbs you use during service. 4. [`Track kegs through distribution`](/docs/inventory/track-distribution/) — ordering, receiving, returns, and deposits. 5. [`Build flights guests can choose`](/docs/inventory/build-flights/) — assemble tasting lineups from inventory you already track. 6. [`Read a keg history`](/docs/inventory/keg-history/) — follow one keg when a number looks wrong. ## What you'll find in this section - guidance for draft inventory and keg workflows - packaged inventory context for bottles and cans - on-tap readiness cues tied to taplist setup - the connection between inventory structure and menu publishing ## Why this section matters Inventory is where BevWerk stops being abstract. Once this section makes sense, the rest of the product becomes easier to trust because you can see where beverage data lives, how it is searched, and what setup is still missing. --- # Add and edit inventory items Everything else in BevWerk depends on inventory records existing. This is how they get created. ## A record points at a Product An inventory item is not a free-text beer name. It points at a **Product** from your catalog and carries a **Product Display Name** for how it should read on a menu. That indirection is deliberate. The Product holds the facts that never change — the producer, the style — while the inventory record holds the facts about _this_ keg: what you paid, what size it is, and where it is in its life. Fix a producer's name once in the catalog and every inventory record that points at it is correct. ## Keg Details - **Size** — determines how many ounces you have to sell, and feeds every yield calculation downstream. - **Type** — the gas used to pour it, which is part of how the keg is served rather than what is in it. - **Cost** — what you paid for the beer, which is what margin is measured against. - **Deposit** — what you paid for the vessel, tracked separately because you expect it back. See [`Track kegs through distribution`](/docs/inventory/track-distribution/). - **Level** and **Status** — where this keg is in its life. - **Notes** — anything the structured fields do not capture. - **Tap** — an empty tap, or the tap the keg is on now. You can swap or rotate kegs between taps and change their prices in one save; every keg lands on its new tap together. ## Sizes must be distinct If you see **Inventory Size already exists**, a record with that size is already on file for the item. This guard exists so two records cannot quietly represent the same thing, which would double-count your stock. ## Cloning Inventory work is repetitive: the same beer arrives again, or one delivery brings six near-identical records. Cloning an existing item copies its setup so you adjust the few fields that differ instead of retyping the ones that do not. When you clone a keg and enter a new Product title, the saved keg belongs to that new Product. ## Images Inventory items can carry an image. It travels with the beverage to the surfaces that display one, so a Website Menu or Digital Menu can show the can rather than just its name. Choose an inventory image from your device or drop it onto the image area. ## Pricing is suggested, not imposed If you have set a [markup strategy](/docs/settings/markup-strategy/), BevWerk suggests a price when you add an item. Override it whenever the suggestion does not suit the beer — the strategy exists to stop prices drifting by accident, not to prevent you from making a decision. ## Packaged inventory works the same way Bottles & Cans records follow the same shape with formats appropriate to packaged product. The split is about lifecycle, not complexity — packaged stock does not empty a keg or occupy a tap. To sell a bottle or can by the glass, add a glass pour. BevWerk offers the glassware that matches the product's type. If you see **No glassware matches this product type**, add glassware for that type in the Glassware tool first. If you see **Could not check existing inventory. Please try again.**, select **Retry** to check again. ## What to do next - Set up the Products and Producers these records point at in [`Manage your catalog`](/docs/catalog/manage-catalog/). - Put a finished keg into service in [`Run the On Tap workspace`](/docs/inventory/on-tap-operations/). --- # Build flights guests can choose A flight is a small menu inside your menu. **Flights** (`/beverages/flights`) lets you assemble one from beverages you already track, so a tasting lineup is not a separate list you have to remember to update. ## Two kinds, matching your inventory Flights follow the same split as the rest of BevWerk: - **Draft Flights** are built from what is pouring. - **Bottle & Can Flights** are built from packaged inventory. The split is not cosmetic. Draft availability changes when a keg blows; packaged availability changes when a case runs out. Keeping them apart means a flight stays tied to the inventory that actually governs it. ## Why flights are built from inventory rather than typed out A flight typed by hand is a promise that goes stale the moment something changes. Because **Create Flight** draws on records you already maintain, the beverages in a flight carry the same names, styles, and producers as everywhere else in the product. When you fix a name once, you fix it everywhere it appears. That is the same reasoning behind the [catalog](/docs/catalog/manage-catalog/): describe a beverage in one place, use it in many. ## What to do next - Make sure the beverages you want to offer exist in [`Manage inventory with confidence`](/docs/inventory/manage-inventory/). - Once a flight is built, decide where guests see it in [`Choose the right menu surface`](/docs/publishing/choose-a-menu-surface/). --- # Read a keg history Most BevWerk screens answer questions about many beverages at once. **Keg History** answers everything about one. ## Getting there Open a keg from wherever you already have it in front of you — an On Tap card, a keg tracking row, or the dashboard On Tap widget. Each opens the detail view for that specific keg. ## The three states A keg moves through three states, and the history records when each transition happened: - **In Stock** — received and available, not yet committed to a tap. - **Up Next** — queued as the next beverage for a tap. - **On Tap** — pouring. Seeing them as a sequence with timestamps is what makes the page useful. "How long did that sit before we tapped it?" and "how fast did it go once it was on?" are both answered by the same trail. ## Use it when a number looks wrong This is the page to open when a keg blew earlier than expected or a report looks off. Aggregate views tell you *that* something does not add up; the history tells you *when* it stopped adding up, and usually that is enough to recognise what happened. A keg that emptied fast is a busy night. A keg whose state changes do not line up with how much beer it should have poured is a different conversation. ## What to do next - Correct a keg that is pouring in [`Run the On Tap workspace`](/docs/inventory/on-tap-operations/). - Follow the vessel after it empties in [`Track kegs through distribution`](/docs/inventory/track-distribution/). --- # Manage inventory with confidence Inventory confidence does not come from one giant screen. BevWerk separates the work into views that answer different questions. ## The three views that matter first ### Kegs Use the Kegs workspace when you want to understand your draft inventory structure, search what you have, and start building inventory records. ### Bottles & Cans Use this view to manage packaged inventory separately from draft. It keeps packaged stock from getting buried under keg-centric workflows. ### On Tap This view is operational rather than purely inventory-oriented. It tells you whether your active taplists are ready to support what you want to serve. ## Watch the walkthrough - [Open the inventory confidence walkthrough](/docs/tutorials/manage-beverage-inventory/) ## What this story teaches Even in a blank workspace, the product makes its structure clear: - **tables** show where inventory will live - **search** shows how managers will quickly find items later - **empty states** tell you what prerequisite is missing - **taplist messaging** explains why on-tap workflows depend on setup, not guesswork ## What to do next When the inventory structure makes sense, move to [`Publish your menu`](/docs/publishing/publish-your-menu/) to see how that internal work becomes guest-facing output. --- # Run the On Tap workspace **On Tap** (`/beverages/on-tap`) is the workspace you touch during service rather than during setup. It answers what is pouring now, what pours next, and what to do when that changes. ## Now and next Each tap shows what is currently **On Tap** and what is queued behind it as **Up Next**. Queueing matters more than it sounds. A keg blows at the worst possible moment, and the difference between a thirty-second changeover and a ten-minute one is whether somebody already decided what goes on next. Use **Edit On Tap** to change what is pouring and **Edit Up Next** to change what is queued. ## Move beverage to On Tap **Move beverage to On Tap** moves a keg from one tap to another without treating it as a new keg. The keg keeps its identity and its remaining volume, so its history stays intact and your numbers do not reset. Reach for this when you are rearranging the tap wall rather than changing what you pour. ## Reduce On Tap Volume **Reduce On Tap Volume** adjusts the remaining volume on a keg that is pouring. This action is available to managers. This exists because reality disagrees with arithmetic. Foam-outs, a line purge, a sampling flight poured for staff, or a keg that simply held less than its stated volume all leave the system believing you have more beer than you do. Correcting the volume keeps depletion and reporting honest instead of letting an error compound until the keg blows "early." ## View Keg Breakdown The keg breakdown shows how a keg's volume has been accounted for. When a number looks wrong, this is where you find out whether it was sales, an adjustment, or the pour size assumptions behind them. ## Cask and Nitro Taps marked **Cask** or **Nitro** carry that indicator here, so the pour style is visible in the workspace as well as on the menus that guests read. Those markings come from the tap itself — see [`Set up Taps & Taplists`](/docs/operations/taps-and-taplists/). ## What to do next - Trace a single keg's full history in [`Track kegs through distribution`](/docs/inventory/track-distribution/). - Make sure what is pouring reaches your POS in [`Understand POS sync operations`](/docs/account/pos-sync-operations/). --- # Track kegs through distribution A keg costs you money twice: once for the beer inside it, and again for the deposit on the vessel itself. **Distribution** (`/beverages/distribution`) is where BevWerk tracks both, from the order you place to the deposit you get back. ## The five stages Distribution is organized as five tracking tabs, and they follow the real life of a keg in order. When purchase-order receiving is enabled, an **Orders** tab is also available for open orders. Managers can create an order manually or start one from a ready invoice scan in **Pending invoices**. Imported lines are drafts: review the distributor, expected date, keg type, quantity, and any warnings before creating the order. BevWerk picks a keg type for a line only when the invoice names a product and size that match exactly one keg type; otherwise choose one yourself, and **Create order** stays unavailable until every line has one. Creating an order records kegs as **Ordered**; it does not receive invoice inventory or mark kegs as in stock. A scan that already has an order cannot start a second order. Cancelling an order before anything is received frees the scan again; once any keg on the order is received, the scan stays with that order. When purchase-order receiving is enabled, **Pending invoices** marks a scan attached to an order as **On order** and hides **Apply** and **Override duplicate**. Receive those kegs from **Distribution → Orders**. If order badges cannot load, the invoice list stays available; the server still prevents applying an invoice held by an order. You can also place an ordered PO keg **On tap** or **Up next** from its Kegs settings. Saving records receipt of that keg and its tap placement together, clears its expected date, and leaves undelivered kegs outstanding. An occupied tap slot or a changed order prevents the whole save. If a save may have gone through, reload orders before changing the order or receipt. ### Ordered What you have asked a distributor for but have not physically received. This is your open commitment — useful when you are deciding whether to order more of something or whether a delivery is late. ### Received What arrived. Receiving is the moment a keg becomes real inventory you can put on tap, so this stage is the bridge between Distribution and your [Kegs](/docs/inventory/manage-inventory/) workspace. ### Empty Kegs Kegs you have finished pouring. They still belong to the distributor, and they still represent money you have tied up, so they stay tracked rather than disappearing when the beer runs out. ### Returned Kegs Empties that have gone back. This is the stage that closes the loop on the vessel itself. ### Keg Deposits The money side. Deposits follow the keg through every stage above, and this tab is where you see what you have paid out and what should be coming back. ## Why the vessel is tracked separately from the beer It is tempting to think of a keg as a single thing that arrives full and leaves empty. Financially it is two things. The beer is a cost of goods you recover when you sell pints. The deposit is a refundable asset sitting in your cooler and, later, on your loading dock. Separating **Empty Kegs** from **Returned Kegs** exists for exactly this reason. An empty keg in your building is unrecovered money. A returned keg is money on its way back. Collapsing the two would hide the gap between them, which is precisely the number worth watching. ## Exports Several tabs offer a CSV export, including keg returns and keg deposits. Use these when you are reconciling against a distributor statement, because the conversation with a distributor usually happens in their format rather than yours. ## What to do next - Set up the distributors these orders come from in [`Manage your catalog`](/docs/catalog/manage-catalog/). - Once kegs are received, put them to work in [`Manage inventory with confidence`](/docs/inventory/manage-inventory/). --- # Operational settings Once your catalog (see [`Catalog setup`](/docs/catalog/)) describes what you sell, this section covers how it gets served day to day: what glass it's poured in, what taplist it's on, what flight it's grouped into, and what menu category it shows up under. ## Start here - [`Manage operational settings`](/docs/operations/manage-operations/) — Flights, Glassware, Menu Categories, and Taps & Taplists. - [`Set up Taps & Taplists`](/docs/operations/taps-and-taplists/) — the setup everything else leans on, including draft line cleaning. - [`Define Glassware and Menu Categories`](/docs/operations/glassware-and-categories/) — pour sizes, prices, and how beverages group on a menu. - [`Price a keg with the Pricing Calculator`](/docs/operations/pricing-calculator/) — turn what you paid into what you should charge. ## Why this section matters These areas are simpler than the catalog entities — none of them have an Import catalog — but they're what a manager touches most often once the catalog is in place, especially Taps, which is also where taplists themselves get created. --- # Define Glassware and Menu Categories Two small settings shape how a menu reads and how accurate your numbers are: **Glassware** decides how beer is sold, and **Menu Categories** decide how it is grouped. ## Glassware A piece of Glassware carries a **Name** and a **Price**. Together these are what a guest actually chooses between — a pint, a half pour, a taster — and what the menu prints. ### A note on keg loss A keg never yields its full theoretical volume. Foam, line pulls, and the last inch that will not pour all disappear between what you bought and what you sold, which is why a keg can look short at the end of the month even when nothing went wrong. BevWerk accounts for this when it works out yield per pour size. There is currently no field for you to set that allowance yourself — it is applied for you rather than configured. ## Menu Categories A **Category Name** and **Description** group beverages on a menu. Categories are how a guest scanning a list finds the thing they want without reading all of it — by style, by strength, by whatever grouping suits your room. Because categories live in settings rather than on each menu, the same grouping applies wherever a beverage appears, and [Digital Menus](/docs/publishing/choose-a-menu-surface/) can rotate through them when there is more to show than fits at once. ## What to do next - Turn pour sizes into prices that hold their margin with the [`Pricing Calculator`](/docs/operations/pricing-calculator/). - Connect categories to what is actually pouring in [`Set up Taps & Taplists`](/docs/operations/taps-and-taplists/). --- # Manage operational settings Like the catalog entities, these four live behind the gear icon in the toolbar (Tools menu). Three of them follow the same table-plus-add-form shape; Taps is built differently because it's managing two related things at once — taplists and the taps on them. ## Flights A Flight groups several pours together (a tasting flight). Adding one asks for a name, the glassware it's served in, and a price. ## Glassware The physical vessels — name, size, unit, and pour price. Flights and Products both reference Glassware, so this is worth setting up early. ## Menu Categories How items are grouped on menus. Unlike the others, this list has no search box — it's a short, drag-to-reorder list (categories are usually few enough to scan directly), with a kebab menu per row for editing or deactivating. ## Taps & Taplists This is the management side of what you see operationally on the [`On Tap`](/docs/inventory/manage-inventory/) dashboard view. A location can have multiple taplists, each with its own set of taps; an **Add Taplist** button is always available from this screen, even before any taplist exists yet. Once you're inside a taplist, an **Add Tap** button is always available; an extra prompt appears when the taplist has no taps yet. ## Watch the walkthrough - [Open the operational settings walkthrough](/docs/tutorials/manage-operational-settings/) The walkthrough opens each area's table and add form — including whichever taplist state your account is actually in — and stops before saving anything new. ## What to do next - Revisit [`Manage your catalog`](/docs/catalog/manage-catalog/) if Flights or Products reference something that doesn't exist yet - Or go back to [`Operational settings`](/docs/operations/) --- # Price a keg with the Pricing Calculator Pricing a keg by feel is how margin quietly disappears. The **Pricing Calculator** turns what you paid for a keg into what you should charge for each pour size. ## Where to find it The Pricing Calculator is a tool rather than a page, so it opens from the Tools menu instead of living at its own address. You can reach the Tools menu from anywhere in BevWerk, which matters because pricing questions tend to come up while you are looking at something else. ## What it asks for - **Cost** — what you paid for the keg. - **Keg Size** — which determines how many ounces you actually have to sell. - **Sales Tax** — so the number you set is the number on the menu. - **Margin** or **Markup** — your target, expressed whichever way you normally think about it. From those it derives **Cost Per Ounce**, which is the figure that makes every pour size comparable. ## Three ways to ask the question The calculator has three tabs, and they differ by which number you already know. ### By Price Start from the price you want to charge. **Retail** is the field you type into; **Adjusted** shows what that price actually works out to per glass and per ounce once tax is accounted for, alongside the **Cost** and **Profit** of the pour. This is the tab that matches how menus really get written. You decide a pint is $8 because $8 is a sensible number in your room, and the calculator tells you what that decision earns. ### By Margin and By Markup Start from a target percentage instead, and the calculator works backward to the price that hits it. Here both Retail and Adjusted are calculated for you — the percentage is the input. Use these when you are setting policy across a lineup rather than pricing one beer. ## Margin and markup are not the same number A 50% *markup* on a $4 pour is $6. A 50% *margin* on the same pour is $8. Mixing them up is one of the most common ways a menu ends up cheaper than intended, which is why the calculator asks which one you mean instead of guessing. ## What to do next - Track what the keg actually cost you in [`Track kegs through distribution`](/docs/inventory/track-distribution/). - Check how pours are performing once they are selling in [`Understand sales reports`](/docs/reports/sales-reports/). --- # Set up Taps & Taplists **Taps & Taplists** is the setup almost everything else leans on. Menus need to know what is pouring, and On Tap needs to know what is ready. Both answers start here. ## Taps are physical, taplists are arrangements A **Tap** represents a real tap in your building. A **Taplist** is a grouping of those taps that a menu can point at. Keeping them separate is what lets one bar serve several menus. The taps do not move, but the arrangement you publish can — a main list, a seasonal list, a list for the patio bar — without re-describing the hardware every time. ## Pour styles are part of the tap A tap can be marked as **Cask** or **Nitro**. This travels with the tap rather than the beer, because it describes how the beer is being served. A guest reading "nitro" is being told something about the pour, not the recipe, and menus can surface it accordingly. ## Draft line cleaning Taps carry a **Clean Draft Lines** record with a **Date of Cleaning**. Managers can record draft line cleaning. This is here because line cleaning is a schedule nobody remembers reliably and every guest can taste. Recording the date against the tap means the answer to "when did we last clean that line?" lives next to the tap itself rather than in someone's memory or a clipboard in the back. ## What to do next - Give the beverages on those taps somewhere to come from in [`Manage inventory with confidence`](/docs/inventory/manage-inventory/). - Decide how the resulting list reaches guests in [`Choose the right menu surface`](/docs/publishing/choose-a-menu-surface/). --- # Menus & publishing Publishing is where BevWerk turns internal setup into something guests and staff can actually use. ## Start here 1. [`Publish your menu`](/docs/publishing/publish-your-menu/) — learn why BevWerk treats taplists as the prerequisite for Digital Menu, Paper Menu, Bar Menu, and Website Menu workflows. 2. [`Choose the right menu surface`](/docs/publishing/choose-a-menu-surface/) — decide between Bar, Digital, Paper, and Website Menus. 3. [`Design a menu with the toolbar`](/docs/publishing/design-your-menu/) — layout, type, colour, and which beverage details appear. 4. [`Put a menu on a screen or a website`](/docs/publishing/display-menus-publicly/) — get a finished menu in front of guests. 5. [`Use the Bar Menu behind the bar`](/docs/publishing/bar-menu/) — the staff-facing surface, including what is queued next. 6. [`Embed the Website Menu on your own site`](/docs/publishing/website-menu/) — a live beer list inside a site you already run. ## What this section covers - Digital Menu starting points - Paper Menu readiness - Bar Menu publishing surfaces - Website Menu embeds for your own site - the relationship between taplists and guest-facing output ## Why this section matters It is easy to think of publishing as cosmetic work. In BevWerk, it is actually the payoff for the structure you created elsewhere. That is why this section belongs right after onboarding and inventory in the recommended docs path. --- # Use the Bar Menu behind the bar The **Bar Menu** (`/menus/bar`) is the only surface written for the person pouring rather than the person choosing. That difference drives everything about it. ## It can show what is coming next The Bar Menu can include the **Up Next** beverage for each tap alongside what is currently pouring. The Bar Menu is built around this: staff need to know what replaces a keg, and the Website Menu deliberately omits it. When a keg blows mid-rush, the difference between a smooth changeover and a scramble is whether the person at the tap already knows what goes on next, without opening another screen or asking. ## Print Menu **Print Menu** produces a PDF of the current state. A printed bar sheet solves a problem screens do not: it survives a wet hand, it does not sleep, and it can be taped where a monitor will not fit. Because it is generated from the same taplist as everything else, reprinting after a tap change takes seconds rather than being a document somebody has to remember to edit. Print a fresh one when the tap list changes, not on a schedule. A stale printed sheet behind the bar is worse than none, because staff trust it. ## It uses the same design controls The Bar Menu shares the [design toolbar](/docs/publishing/design-your-menu/) with the other surfaces, so you can strip it down to what staff actually need. This is the surface where showing fewer fields usually wins — tap number, beer, and pour size read faster mid-service than a full description does. ## What it is not The Bar Menu is not a guest menu with extra detail, and it is not where you decide what is pouring. Tap assignments happen in [`Run the On Tap workspace`](/docs/inventory/on-tap-operations/); this surface displays the result for the people working it. ## What to do next - Compare it with the guest-facing surfaces in [`Choose the right menu surface`](/docs/publishing/choose-a-menu-surface/). - Set up the taps and queue it reads from in [`Set up Taps & Taplists`](/docs/operations/taps-and-taplists/). --- # Choose the right menu surface BevWerk publishes to four menu surfaces, and they are not four copies of the same thing. Each one answers a different question about where a guest is standing when they read it. ## The four surfaces ### Bar Menu `/menus/bar` — the working view for behind the bar. This is the one your staff reads, so it is organized for the person pouring rather than the person choosing. ### Digital Menu `/menus/digital` — the screen a guest looks up at. Digital menus can rotate through categories and taplists, which matters when you pour more beers than fit legibly on one screen. #### Categories across multiple screens Each digital menu has its own **Category layout**. In the digital-menu toolbar, choose more than one display under **Displays** and select **Separate Displays** under **Display Options**. The **Category layout** control appears beside Displays. - **Keep categories on one screen** is the default. Each screen gets whole categories, as before. Reorder your categories to change which screen they appear on. A category that is too long for one screen can be cut off. - **Let categories continue onto the next screen** balances the menu across your screens while preserving your category and beverage order. A category can continue on the next screen, where its heading repeats with “(cont.)”. With continuation, **Keep short categories together** starts checked. It favors keeping categories that fit on one screen together and avoids leaving a single beverage at either end of a split. Preventing cut-off content takes priority when everything cannot fit together. Uncheck it to allow more splits and fill your screens more evenly. Your preview uses the same layout choice as the displays. These settings belong to this menu; they do not change your other menus. They apply to separate displays, not rotating menus. If the menu still has too much content, reduce the text size or add another display. ### Paper Menu `/menus/paper` — the printable version, generated from the same taplist rather than retyped. Paper is the surface most likely to go stale, so producing it from live data is the whole point. ### Website Menu `/menus/website` — what appears on your public site. This one leaves your building entirely, which makes it the surface where an out-of-date beer is most visible and least forgivable. ## Why one beverage feeds four menus Every surface draws on the same beverages, [Taps & Taplists](/docs/operations/manage-operations/), and Menu Categories. Change a beer once and the change reaches all four, because the alternative — maintaining four lists by hand — is how a taproom ends up serving something the website says is gone. This is also why the surfaces are separate pages rather than one page with a format switch. A rotation setting that makes sense on a screen is meaningless on paper, and a layout tuned for staff is wrong for guests. ## Choosing between them | If you want to… | Use | | -------------------------------------------------- | ------------ | | Give staff a working reference | Bar Menu | | Fill a screen above the taps | Digital Menu | | Hand a guest something printed | Paper Menu | | Show what is pouring to people not yet in the room | Website Menu | Most operators end up using more than one. They are not alternatives so much as audiences. ## What to do next - Get the underlying setup right first in [`Manage operational settings`](/docs/operations/manage-operations/). - When you are ready to make changes visible, read [`Publish your menu`](/docs/publishing/publish-your-menu/). --- # Design a menu with the toolbar Every menu surface shares one design toolbar. Learning it once means you can lay out a paper menu, a screen, and your website without relearning the controls each time. ## Layout **Paper Size**, **Columns**, and **Position** determine the shape of the menu. **Item Spacing** and **Line Height** control how densely beverages sit within that shape. Density is the setting worth revisiting. A menu that fits on one page but cannot be read across a dim taproom has not solved the problem — it has moved it to the guest. ## Type **Font Face**, **Text Size**, **Case**, and **Format Text** handle typography. **Separators** decide whether items are visually divided. ## Colour The **Color Palette** offers **Brand**, **Solid Color**, **Minimal Color**, **Gray**, **Light**, and **Dark**. Brand pulls the colours you set in Company Info, which is how a menu ends up looking like your business rather than like a spreadsheet. Dark and Light matter most on a screen, where the room's own lighting decides which one is legible. ## Choose what each item shows Toggle individual fields on or off: **Tap Numbers**, **Producers**, **Products**, **Styles**, **Descriptions**, and pricing details. This is the highest-leverage part of the toolbar. Every field you show costs space and attention. A twelve-tap board where each beer carries a producer, style, ABV, description, and three pour prices is complete and unreadable. Decide what a guest needs to choose, and let the rest live somewhere with more room. ## Location details **Location Info**, **Locations**, **Events**, and **Displays** control the surrounding context — whose menu this is and what else is happening. ## Settings belong to the menu Design choices are saved with the menu you are editing, so your Paper Menu can be dense and typographic while your Digital Menu is large and high-contrast. They are drawing on the same beverages; they are not obliged to look alike. ## What to do next - Pick the right surface for the audience in [`Choose the right menu surface`](/docs/publishing/choose-a-menu-surface/). - Set the brand colours the palette draws on in [`Review company info`](/docs/settings/review-company-info/). --- # Put a menu on a screen or a website Designing a menu and displaying one are different jobs. Once a menu looks right, it needs to reach a screen on your wall or a page on your website. ## Screens in the taproom A Digital Menu is displayed by pointing a browser at its public address. Any device that runs a full browser works — a smart TV, a small media stick, a spare laptop behind the bar. The address identifies the taplist being shown, so a second screen showing a different taplist is just a second address. That is how a taproom with a main wall and a patio bar drives both from one BevWerk account without maintaining two systems. ### Rotating through pages When a taplist holds more beers than fit legibly on one screen, a Digital Menu can page through them. The display address accepts a page index, so a screen can either sit on one page or cycle. Cycling is usually the right answer for a busy wall. Shrinking type until forty beers fit is not legibility, it is an eye test. ## Your own website Two options, depending on where your site lives: - **BevWerk hosts the page.** Add a menu block in [Website Pages](/docs/website/build-website-pages/) and it renders your live menu. - **You host the site elsewhere.** Embed the menu so your existing site shows BevWerk's live data inside your own design. Either way the beer list is generated from what is actually pouring. A menu pasted into a site editor is accurate the day it is pasted, and slowly wrong after that. ## Edits are live immediately There is no draft state. Design and layout changes save as you make them, and a screen showing that menu picks them up — there is no separate publish step holding them back. Plan around that during service. If you are reworking a menu substantially, do it before doors or on a taplist no screen is currently pointed at, rather than rearranging one a room is reading. ## Practical notes for screens - Set the display device to keep the screen awake; a screensaver is the most common cause of a blank menu wall. - Point each screen at the taplist for the room it is in, not at your main list by default. - Check legibility from the far end of the room, not from the laptop you configured it on. ## What to do next - Get the layout right first in [`Design a menu with the toolbar`](/docs/publishing/design-your-menu/). - Decide which surface suits which audience in [`Choose the right menu surface`](/docs/publishing/choose-a-menu-surface/). --- # Publish your menu Publishing is the moment your internal beverage work becomes visible to guests and staff. BevWerk makes that relationship explicit: no taplist, no finished menu surface. ## What this guide focuses on This is not a design tutorial yet. It is the manager view of publishing readiness. You will see how BevWerk uses taplists as the prerequisite for: - **Digital Menu** displays - **Paper Menu** output - **Bar Menu** publishing surfaces - **Website Menu** embeds on your own site ## Watch the walkthrough - [Open the publish-your-menu walkthrough](/docs/tutorials/publish-your-menus/) ## Why the empty state is useful The empty-state message is not a dead end. Each menu surface shows **"There are no active Taplists set up for this location"** with a **Create Taplist** button beneath it, which explains the production rule of the system. That is a great first-run teaching moment because it ties menu output directly back to the operational setup you control. ## Suggested next move inside the app Start by creating your first taplist, then return to the menu workspaces to preview how BevWerk can power your guest-facing menu channels. ## Keep exploring - Revisit [`Your first day in BevWerk`](/docs/getting-started/first-day/) - Revisit [`Manage inventory with confidence`](/docs/inventory/manage-inventory/) - Browse all [`Tutorials`](/docs/tutorials/) --- # Embed the Website Menu on your own site The **Website Menu** (`/menus/website`) is the surface that leaves your building. It renders your live beer list on a public site, whether BevWerk hosts that site or you do. ## Installing it on a site you already run The Website Menu page includes **Installation Instructions** — the snippet to place wherever you want the menu to appear on your own site. That snippet is the whole point. Your site keeps its own design, navigation, and hosting, and the beer list inside it comes from BevWerk. Nobody has to remember to update a webpage when a keg changes, because there is no separate copy to update. If BevWerk hosts your site instead, add the menu through a page block rather than a snippet — see [`Build and configure website pages`](/docs/website/build-website-pages/). ## Choosing what visitors see Several options are specific to a public audience: - **Timestamp** — show when the list last updated, which tells a visitor the page is live rather than a forgotten screenshot. - **Highlight Taps** — draw attention to particular pours. - **Glass Names** and **Glass Sizes** — how pour options are described. - **Menu Categories** — how beers are grouped for someone scanning. - **Columns**, **Font Face**, **Global Font Size**, and the **Color Palette** — how the embedded list is laid out and styled. The Website Menu does not offer the queued-next beverage — this surface disables it deliberately — so **Up Next** is a Bar Menu concern. **Keg Levels** are likewise not a Website Menu option; they render only where a Digital Menu template supports them. ## Templates and branding **Templates** provide starting layouts. **Location Brand** displays that location's logo and address — useful when the embed sits on a multi-location site and a visitor needs to know which room the list belongs to. Colours come from the separate **Color Palette** control, not from Location Brand. Since this menu sits inside someone else's page design, matching your styling matters more here than on a screen you control end to end. ## Why the timestamp earns its place A public beer list is only trusted if a visitor believes it is current. The timestamp is a small thing that does a lot of work: it converts "this list might be old" into "this list was right an hour ago." Turning it on costs nothing and answers a question every visitor silently asks. ## If the embed shows a message instead of your menu Visitors see one of these in place of the beer list: - **"The menu is temporarily unavailable."** The embed couldn't reach BevWerk. It keeps trying, and your menu comes back on its own when a request succeeds. - **"This menu isn't published."** BevWerk has no published menu at that link. Check that the menu still exists and is turned on. - **"This menu link is incomplete."** The snippet on your site is missing part of the menu's link. Copy it again from **Installation Instructions** and replace the one on your site. ## What to do next - Decide which surface suits which audience in [`Choose the right menu surface`](/docs/publishing/choose-a-menu-surface/). - Get the layout and fields right in [`Design a menu with the toolbar`](/docs/publishing/design-your-menu/). --- # Reports Reports is where BevWerk surfaces sales reporting for locations with a connected Clover or Square integration. ## Start here 1. [`Understand sales reports`](/docs/reports/sales-reports/) — see what the Reports workspace shows and why the first-run state depends on POS setup. 2. [`Read the Orders and Items views`](/docs/reports/read-sales-data/) — pick the view that answers your question. ## What you'll find in this section - where sales reporting lives in the app - what changes when a location has Clover or Square connected - why a location without a POS integration sees a setup message instead of report tables ## Why this section matters Reports are intentionally tied to POS data. If the active location has no Clover or Square integration, BevWerk does not pretend sales reporting is available. That makes the Reports screen useful both as a reporting surface and as a clear setup checkpoint. --- # Read the Orders and Items views The Sales report presents the same underlying data two ways. Picking the right one saves a lot of squinting. ## Orders and Items answer different questions ### Orders One row per transaction. Use Orders when the question is about **guests and visits** — how many tabs you ran, what an average check looks like, how a Friday compares with a Tuesday. ### Items One row per beverage sold. Use Items when the question is about **products** — which beer is moving, which style earns its tap line, what to reorder. The distinction bites when you try to answer a product question with Orders. A busy night with fifty orders tells you nothing about which of your twelve taps deserves to stay, and that is the question most tap decisions actually turn on. ## Date range Choose a preset range or **Custom Range** for a specific window. Ranges are worth thinking about rather than accepting. A seven-day window flatters whichever days you happened to include; comparing like periods — this month against last, this Saturday against previous Saturdays — is what turns a number into a decision. ## Reports are per location Sales follow the **active location**. A report that looks unexpectedly quiet is often the right report for the wrong room — see [`Manage locations and the active location`](/docs/settings/manage-locations/). ## Where the data comes from Everything here originates in your POS and arrives automatically. BevWerk does not record sales itself; it reads what Clover or Square recorded. That is why a missing sale is an integration question rather than a reporting one — see [`Sales or reports are missing data`](/docs/support/troubleshooting/sales-data-missing/). It also explains attribution gaps: a beverage rung up under a POS item that does not match anything in BevWerk shows in your POS totals but cannot be attributed to a product here. ## The dashboard is the same data, summarized Total Sales, Popular Products, and Popular Styles all draw on this data. Use the dashboard for the daily glance and this report when you need to interrogate a specific period — see [`Customize your dashboard widgets`](/docs/dashboard/customize-widgets/). ## What to do next - Understand the setup requirement in [`Understand sales reports`](/docs/reports/sales-reports/). - Turn what sells into what you charge with the [`Pricing Calculator`](/docs/operations/pricing-calculator/). --- # Understand sales reports The Reports section currently opens to **Sales**. ## What you see first Reports only appears in the app navigation once this location has a Clover or Square integration connected. Before that, go directly to `/reports/sales` to see the setup message. The Sales page always starts with the same purpose: showing sales reporting for the active location. What appears next depends on whether that location has a POS integration. ## If Clover or Square is connected BevWerk shows two tabs: - **Orders** — sales grouped around order-level reporting - **Items** — sales item reporting with Product, vessel, price, quantity, and Style context Both reports include date-range controls so managers can narrow the time period they are reviewing. ## If no POS integration is connected BevWerk shows **"Sales reports require a Clover or Square integration on the active location."** That is the expected first-run state for a location that has not connected POS sales data yet. The Reports page is still useful because it tells managers exactly why report tables are not available. ## Watch the walkthrough - [Open the Reports walkthrough](/docs/tutorials/review-sales-reports/) ## What to do next If the no-integration message appears, connect Clover or Square for the active location before expecting sales tables to populate. If report tabs are already visible, start with **Orders** for order-level review and switch to **Items** when you need Product-level sales detail. --- # Profile & settings Once the product structure makes sense, the next layer is personal setup: making sure your account details, profile information, and password hygiene are in good shape. ## Start here 1. [`Make BevWerk feel like home`](/docs/settings/make-it-yours/) — review the profile, photo, and password surfaces managers are likely to touch first. 2. [`Review company info`](/docs/settings/review-company-info/) — understand how BevWerk organizes company details, locations, and subscription context. 3. [`Manage locations and the active location`](/docs/settings/manage-locations/) — describe each room and understand what switching locations changes. 4. [`Set your markup strategy`](/docs/settings/markup-strategy/) — make BevWerk suggest consistent prices as you add inventory. 5. [`Set company branding and tax defaults`](/docs/settings/company-brand-and-taxes/) — the colours, taxes, and rounding every location inherits. ## Why this section matters These are not headline features, but they absolutely shape trust. A product feels production-ready when people can quickly answer questions like: - is my account information correct? - where do I update my password? - where does my profile photo live? - what settings are personal versus operational? - where do company details, locations, and subscription information live? That is the kind of clarity this section is for. --- # Set company branding and tax defaults Company Info holds the settings that everything else inherits. Two groups of them shape what guests actually see: your brand, and your tax maths. ## Brand colours Your company carries a **Primary Color**, **Secondary Color**, and **Tertiary Color**, along with a company logo. These are not decoration. The menu design toolbar's Brand palette draws directly on them, so setting them once is what makes a Digital Menu or Paper Menu look like your taproom instead of a default template. See [`Design a menu with the toolbar`](/docs/publishing/design-your-menu/). A location can override these if a second room has its own identity — see [`Manage locations and the active location`](/docs/settings/manage-locations/). ## Tax and rounding - **Sales Tax** — the rate applied to prices. - **Round To Nearest** — how the taxed figure is rounded before it reaches a menu. Rounding earns its place here. A calculated price of $7.83 is arithmetically correct and useless on a menu board; rounding turns it into a number a guest can hand you cash for. Setting it at the company level means every menu rounds the same way instead of each one being tidied by hand. ## Pricing defaults **Draft**, **Packaging**, and **Glass Pours** markups sit alongside a **Calculation Type** that decides whether you think in margin or markup. These drive the price suggestions you get when adding inventory — covered in full in [`Set your markup strategy`](/docs/settings/markup-strategy/). If pricing settings cannot load, the pricing fields stay hidden. Select **Retry** to load them again. You can still save other company details without changing the saved pricing settings. ## Contact and social details **Company Name**, **Address**, **City**, **State**, **Phone**, **Email**, and **Website**, plus your **Social** handles. These appear where BevWerk presents your business publicly, including menus that carry location details and pages on a BevWerk-hosted site. Keep them current for a plainer reason than completeness: they are what a guest uses to find you, and a stale phone number on a printed menu outlives the print run. ## Company settings are inherited, not duplicated Everything here is the default for every location. A room only departs from it when you deliberately turn on an override. That inheritance is why setting these properly once is worth more than fixing them repeatedly per location. ## What to do next - Review the wider page structure in [`Review company info`](/docs/settings/review-company-info/). - Set the markups these defaults feed in [`Set your markup strategy`](/docs/settings/markup-strategy/). --- # Make BevWerk feel like home This guide is for the moment after first-run orientation, when a manager wants the app to feel like *their* workspace rather than a demo account. ## What you'll learn By the end of this guide, you will know: - where your core profile details live - what information BevWerk keeps on hand for your account - where profile photos are managed - where password updates happen ## Why this story matters Account settings are quiet features, but they are trust-building features. When profile and password controls are easy to find, people feel more confident that the product is ready for everyday use. ## Watch the walkthrough - [Open the make-it-yours walkthrough](/docs/tutorials/customize-your-profile/) ## What this story teaches This walkthrough shows that BevWerk separates: - **personal identity** information - **profile presentation** details like photos - **security actions** like password changes That separation helps managers understand what belongs to them personally versus what belongs to the shared business setup. Changing your password signs you out on every other device, including any you have lost track of; the device you changed it on stays signed in. ## What to do next - Visit [`Help & support`](/docs/support/) - Revisit [`Your first day in BevWerk`](/docs/getting-started/first-day/) --- # Manage locations and the active location A company can run more than one room, and those rooms rarely share a tax rate or a tap wall. **Locations** is where each one is described. ## Company and location are different levels Your **Company** is the business. A **location** is a place that pours. Settings that belong to the business live once at the company level; settings that differ between rooms live on each location. That split is why moving between locations does not mean re-entering your catalog. Beverages, Distributors, and Producers belong to the company. Taps, taxes, and addresses belong to the room. ## What a location carries - **Location Name** and **Display Name** — the internal name and the one guests see. - **Address**, **City**, **State**, and **Phone** — the public details. - **Sales Tax** — the rate for that room, because a second taproom in another jurisdiction rarely matches the first. - **Round to Nearest** — how prices are rounded once tax is applied, so your menu shows tidy numbers. ## Overriding company defaults Two toggles let a location depart from the company settings rather than inherit them: - **Customize Location Margin/Markup** — give this room its own pricing strategy. See [`Set your markup strategy`](/docs/settings/markup-strategy/). - **Customize Location Brand** — give this room its own **Primary**, **Secondary**, and **Tertiary** brand colours, which flow through to menus generated for it. Leave both off and the location follows the company. Turn one on only when the room genuinely differs; every override is something you will need to remember to maintain twice. If pricing settings cannot load, select **Retry**. The pricing controls stay hidden until the settings load, and saving other location details leaves the saved pricing settings unchanged. ## Clover category mapping If a location has Clover connected, it also carries dropdowns that map your Clover categories onto BevWerk concepts such as **Draft Inventory** and **In House Glass Pours**. These tell BevWerk which Clover category means what, and they appear only once that integration exists — see [`Understand POS sync operations`](/docs/account/pos-sync-operations/). ## The active location BevWerk always works in the context of one **active location**. It determines which taps, taplists, and inventory you are looking at, and it is remembered between sessions so you land where you left off. If a screen shows data you did not expect — an unfamiliar tap list, inventory that looks wrong — check the active location first. It is the most common explanation, and the quickest to rule out. ## What to do next - Set the business-level details in [`Review company info`](/docs/settings/review-company-info/). - Configure the taps that belong to each room in [`Set up Taps & Taplists`](/docs/operations/taps-and-taplists/). --- # Set your markup strategy The [Pricing Calculator](/docs/operations/pricing-calculator/) answers a question you ask once about one keg. A **markup strategy** answers it automatically, every time, for everything you add. ## Where it lives Markup settings appear alongside your company details and again on each location. Setting them at the company level establishes the default; setting them on a location overrides it for that room, which is what you want when a second taproom charges differently from the first. ## Three base markups - **Draft** — the base markup for beer served from a keg. - **Packaging** — the base markup for bottles and cans sold as packaged product. - **Glass Pours** — the base markup for beer poured into a glass by size. These are separate because the economics are. Packaged product you resell at a different margin than beer you pour yourself, and a taster glass carries different overhead per ounce than a pint. ## Overrides where the base is too blunt Beneath the base rates you can set a markup per individual glassware size and per packaging type. Use these sparingly. The base rates should carry most of your catalog, and an override should mean something specific — a format you deliberately price differently, not a one-off you could have adjusted on the item itself. ## What this actually changes With a strategy in place, BevWerk suggests a price whenever you add inventory rather than leaving the field blank. A suggestion is a starting point, not a lock: you can always type a different number. The value is not that the suggestion is always right. It is that the suggestion is always *consistent*. Without one, prices drift according to who added the item and how busy they were, and that drift is invisible until you go looking for it. ## Taxes and rounding sit next to it **Sales Tax**, **To-Go Tax**, and **Round to Nearest** live alongside markup because they finish the same calculation. Markup gets you to a raw price; tax and rounding get you to the number a guest reads on a menu. ## What to do next - Set the business-level details these build on in [`Review company info`](/docs/settings/review-company-info/). - Override per room where needed in [`Manage locations and the active location`](/docs/settings/manage-locations/). --- # Review company info This guide is for the operational side of settings: the information that belongs to the business, not just the individual user. ## What you'll learn By the end of this guide, you will know: - where BevWerk keeps company information for the workspace - how locations are introduced into the system - where subscription context lives - how to distinguish shared business settings from personal profile settings ## Why this matters Settings feel much clearer when BevWerk separates **your account** from **the business account**. That keeps everyday administration more predictable for owners and managers who need to understand what belongs to them personally versus what belongs to the whole operation. ## Watch the walkthrough - [Open the company info walkthrough](/docs/tutorials/review-company-information/) ## What this guide proves The company info area gives managers three useful anchors: - a place for shared business details - the company logo used on public menus - a clear entry point for adding locations - subscription context that explains the current account state without making you hunt for it The **company logo** is shared across the business. Choose or remove it in company settings; public menus use that shared logo alongside location details. ## Unsaved edits when switching locations When the company unsaved-changes guard is enabled, switching locations with unsaved company edits opens a confirmation. Choose **Keep Editing** to stay with your draft, or **Discard and Switch** to discard it and switch locations. This guard is off by default during rollout. ## What to do next - Return to [`Profile & settings`](/docs/settings/) - Continue with [`Make BevWerk feel like home`](/docs/settings/make-it-yours/) - Or move into [`Website & events`](/docs/website/) if you are preparing public-facing content --- # Help & support When you need an answer quickly, BevWerk should help you solve the problem before you need to open a support chat. ## Start here 1. [`Find answers fast`](/docs/support/find-answers-fast/) — learn where BevWerk already explains common questions. 2. [`Troubleshooting`](/docs/support/troubleshooting/) — jump straight to tested recovery guides for missing pages and sign-in issues. - [`Common questions`](/docs/support/common-questions/) — short answers to what owners and managers ask most often. ## What belongs in this section This section will deliberately mix **story guides** with **reference-style troubleshooting docs**: - story-driven help journeys for common operator questions - quick-answer references for recurring tasks - troubleshooting and error docs, including missing pages, sign-in recovery, and future edge-case guides Stories explain the normal flow. Troubleshooting pages explain exceptions without forcing them into a fake narrative. --- # Common questions Direct answers to frequent questions. Each one links to the page that explains it properly. ## Setup **Where do I start with a brand-new account?** Follow the sequence in [`Your first day in BevWerk`](/docs/getting-started/first-day/). If the vocabulary is unfamiliar, read [`Key concepts and vocabulary`](/docs/getting-started/key-concepts/) first. **What is the difference between the catalog and inventory?** The catalog describes beer in the abstract — Producers, Products, Styles. Inventory is stock you actually have. See [`Key concepts and vocabulary`](/docs/getting-started/key-concepts/). **Why do I need a taplist before I can publish a menu?** A menu displays a taplist. With no taplist there is nothing to display. See [`Set up Taps & Taplists`](/docs/operations/taps-and-taplists/). ## Menus **What is the difference between the four menus?** Bar Menu is for staff, Digital Menu is for screens, Paper Menu is for print, Website Menu is for your public site. See [`Choose the right menu surface`](/docs/publishing/choose-a-menu-surface/). **How do I get a menu onto a TV?** Point a browser at the menu's public address. See [`Put a menu on a screen or a website`](/docs/publishing/display-menus-publicly/). **How do I change what each beer shows on the menu?** Toggle the fields in the design toolbar. See [`Design a menu with the toolbar`](/docs/publishing/design-your-menu/). **A beer is missing from my menu.** See [`A menu is not showing what I expect`](/docs/support/troubleshooting/menu-not-updating/). ## Inventory and kegs **How do I add a new beer?** Create the Product in the catalog, then add an inventory record pointing at it. See [`Add and edit inventory items`](/docs/inventory/add-inventory-items/). **What does Up Next mean?** It is the beverage queued to pour next on that tap. See [`Run the On Tap workspace`](/docs/inventory/on-tap-operations/). **A keg blew earlier than expected.** Check its history for sales and adjustments. See [`Read a keg history`](/docs/inventory/keg-history/). **How do I correct the volume left in a keg?** Use Reduce On Tap Volume. See [`Run the On Tap workspace`](/docs/inventory/on-tap-operations/). **Where do I track kegs I need to return?** Distribution separates Empty Kegs from Returned Kegs, and tracks deposits. See [`Track kegs through distribution`](/docs/inventory/track-distribution/). ## Pricing **How should I price a keg?** Use the [`Pricing Calculator`](/docs/operations/pricing-calculator/) for one keg, or set a [markup strategy](/docs/settings/markup-strategy/) so prices are suggested automatically. **What is the difference between margin and markup?** Markup is added to cost; margin is a share of the selling price. The same percentage gives different prices. See [`Price a keg with the Pricing Calculator`](/docs/operations/pricing-calculator/). ## Sales and integrations **Why is Reports not in my navigation?** It appears only once a Clover or Square integration is connected. See [`Sales or reports are missing data`](/docs/support/troubleshooting/sales-data-missing/). **My recent sales have not appeared.** See [`Sales or reports are missing data`](/docs/support/troubleshooting/sales-data-missing/). **Which sync do I run?** Sales pull in automatically; taps push out to the POS. See [`Understand POS sync operations`](/docs/account/pos-sync-operations/). ## Account and access **Why can I not see a feature a colleague can?** Manager-only features depend on your role. See [`Manage users`](/docs/account/users-management/). **I cannot sign in.** See [`Fix common sign-in problems`](/docs/support/troubleshooting/sign-in-problems/) or [`Reset your password`](/docs/support/troubleshooting/reset-your-password/). **Why does this screen show a different location's data?** BevWerk works in the context of one active location. See [`Manage locations and the active location`](/docs/settings/manage-locations/). **Can I get my data out of BevWerk?** Yes — see [`Export your company data`](/docs/account/export-company-data/). --- # Find answers fast This guide is for owners and managers who want answers quickly without breaking their workflow. ## What you'll learn By the end of this guide, you will know: - where BevWerk keeps its FAQ library - how help topics are grouped across the product - where to look before opening a support conversation - how BevWerk points you toward the right operational answer ## Why this story matters Good help docs should reduce friction, not create another scavenger hunt. This walkthrough shows that BevWerk already organizes common questions into a structure that feels familiar to managers: - dashboard questions stay with dashboard work - beverage questions stay with beverage work - menu questions stay with publishing work - support guidance stays easy to find when you need a human ## Watch the walkthrough - [Open the find-answers-fast walkthrough](/docs/tutorials/find-answers-fast/) ## What this story proves A strong help experience does two jobs at once: 1. it answers the immediate question 2. it teaches you where to look next time That second part is what makes support feel scalable instead of reactive. ## What to do next - Continue to [`Make BevWerk feel like home`](/docs/settings/make-it-yours/) - Return to [`Publish your menu`](/docs/publishing/publish-your-menu/) --- # Troubleshooting Troubleshooting pages are intentionally **reference-first**. They are here to answer one question quickly: *what do I do next when something unexpected happens?* ## Start with these recovery guides 1. [`Recover from a missing page`](/docs/support/troubleshooting/missing-pages/) — see how BevWerk handles stale or mistyped links. 2. [`Fix common sign-in problems`](/docs/support/troubleshooting/sign-in-problems/) — review the built-in cues for email validation, failed logins, and password recovery. - [`Reset your password`](/docs/support/troubleshooting/reset-your-password/) — get back in when you cannot sign in. - [`A menu is not showing what I expect`](/docs/support/troubleshooting/menu-not-updating/) — missing beers, empty menus, stale screens. - [`Sales or reports are missing data`](/docs/support/troubleshooting/sales-data-missing/) — empty reports and absent sales. ## Why this section exists Stories are great for normal workflows. Troubleshooting docs are better when they stay direct: - what happened - what BevWerk shows you - what action to take next That keeps recovery guidance fast, calm, and practical. --- # A menu is not showing what I expect Menus are generated from several layers of setup, so "the menu is wrong" almost always means one specific layer is not what you think it is. Work down this list in order. ## The menu is completely empty You will see **"There are no active Taplists set up for this location"** with a **Create Taplist** button. This means the location has no active taplist, not that the menu is broken. A menu displays a taplist; with no taplist there is nothing to display. See [`Set up Taps & Taplists`](/docs/operations/taps-and-taplists/). ## A beer is missing from the menu Check these in order, because each one depends on the one before it: 1. **Is it on a tap?** A beverage that exists in inventory but is not assigned to a tap will not appear. Check [`Run the On Tap workspace`](/docs/inventory/on-tap-operations/). 2. **Is that tap on this taplist?** A tap can exist without belonging to the taplist this menu points at. 3. **Is the taplist active?** Inactive taplists are skipped. 4. **Is the field switched on?** The [menu design toolbar](/docs/publishing/design-your-menu/) can hide producers, styles, prices, and other details per surface. A "missing" beer is sometimes a beer showing with fewer fields than you expected. ## The wrong location's beers are showing Menus follow the **active location**. If the list looks like another room's, switch the active location and look again — see [`Manage locations and the active location`](/docs/settings/manage-locations/). ## A screen in the taproom shows old information The display is a browser pointed at a menu address, so the usual causes are ordinary browser causes: - The page has been open a long time and needs a reload. - The device went to sleep and is showing a stale frame. - The screen is pointed at a different taplist than the one you edited. ## The website shows something different from the taproom screen That is expected if they point at different taplists, and it is the most common reason the two disagree. Confirm both are showing the taplist you think they are before assuming a sync problem — the four surfaces are independent by design, as described in [`Choose the right menu surface`](/docs/publishing/choose-a-menu-surface/). ## Sales look wrong rather than the menu That is a different problem with a different cause — see [`Understand POS sync operations`](/docs/account/pos-sync-operations/). ## What to do next - Confirm the underlying setup in [`Set up Taps & Taplists`](/docs/operations/taps-and-taplists/). - Review how a menu reaches a screen in [`Put a menu on a screen or a website`](/docs/publishing/display-menus-publicly/). --- # Recover from a missing page This guide is for the moment a bookmark, shared link, or typed URL sends you somewhere that no longer exists. ## What you'll learn By the end of this guide, you will know: - how BevWerk signals that a page is missing - what message the app shows instead of failing silently - how to recover and return to the main workspace quickly ## Why this matters Broken links happen. What matters more is whether the product helps you recover without panic. This walkthrough shows that BevWerk keeps the normal workspace frame visible, explains what happened in plain language, and lets you get back to work without guessing. ## Watch the walkthrough - [Open the missing-page walkthrough](/docs/tutorials/recover-from-missing-page/) ## What this proves When a page is gone, BevWerk does three useful things: 1. it tells you the page was moved or no longer exists 2. it keeps the app shell available so you are not stranded 3. it makes recovery immediate instead of forcing a dead end ## What to do next - Return to [`Help & support`](/docs/support/) - Continue with [`Find answers fast`](/docs/support/find-answers-fast/) --- # Reset your password If you cannot sign in because you do not know your password, the reset flow gets you back in without anyone else's help. ## The flow 1. On the sign-in screen, select **Forgot password?**. 2. Enter the **Email** address on your account and select **Send reset link**. 3. Open the email from BevWerk and follow its link. 4. Enter your new password and select **Update**, then sign in with it. The link works once and expires after an hour; if it has expired or was already used, request a new one. The link proves you control the mailbox, which is why the reset lands there rather than being something support can read out to you over the phone. Resetting your password signs you out on every device, so anyone who had your old password loses access too. Sign in again with the new one. If you think someone else had your password, also tell BevWerk support. ## When the email does not arrive Work through these before assuming something is broken: - **Check spam and promotions folders.** Automated mail lands there more often than anywhere else. - **Confirm the address.** The reset goes to the address on the account, which may not be the one you type from memory — a personal address rather than the shared taproom inbox, for instance. - **Give it a minute.** Delivery is usually quick but not instant. - **Check whether the mailbox still exists.** Accounts created against a departed colleague's address are a common cause; if nobody can receive that mail, another manager can help through [`Manage users`](/docs/account/users-management/). ## If sign-in still fails after a reset A successful reset that still will not let you in points at something other than the password. [`Fix common sign-in problems`](/docs/support/troubleshooting/sign-in-problems/) covers the rest. ## What to do next - Review who can sign in at all in [`Manage users`](/docs/account/users-management/). - Once you are back in, confirm your details in [`Make BevWerk feel like home`](/docs/settings/make-it-yours/). --- # Sales or reports are missing data Sales data comes from your POS rather than from BevWerk, so a gap is usually about the connection between the two. ## Reports is not in the navigation Reports only appears once the active location has a Clover or Square integration connected. Without one there is no nav entry at all — this is expected, not a fault. You can still open `/reports/sales` directly, where BevWerk shows **"Sales reports require a Clover or Square integration on the active location."** ## Reports is there but empty Work through these: 1. **Check the active location.** Reports are per location, and a quiet second room legitimately has nothing to show. 2. **Check the date range.** An empty period is an empty report. 3. **Confirm sales have actually synced.** Order data flows in automatically, but a recent sale may not have landed yet. ## Recent sales have not appeared Give it a few minutes first — order sync is automatic but not instantaneous. If sales are still missing after that, the likely cause is the integration rather than the report. A POS token can expire, which fails quietly from the outside: the connection looks present but no longer works. Reconnecting the integration is the fix. For Square, a **Reconnect Square** badge on the location in the Locations table means exactly this; see [`Reconnect Square`](/docs/account/integrations/#reconnect-square). For other POS systems, see [`Connect a POS integration`](/docs/account/integrations/). ## Some products show but others do not Sales arrive tied to POS items. A beverage rung up under a POS item that does not correspond to anything in BevWerk will appear in your POS totals but not attribute to a product here. If your POS is missing beers you are pouring, the sync you want pushes taps *out* to the POS rather than pulling orders in — see [`Understand POS sync operations`](/docs/account/pos-sync-operations/). ## Dashboard widgets are empty but reports have data Several dashboard widgets depend on the same sales data, but a hidden widget shows nothing regardless. Check whether the widget is switched on in [`Customize your dashboard widgets`](/docs/dashboard/customize-widgets/). ## Keg numbers look wrong rather than sales Depletion is calculated from sales plus any manual adjustments, so a keg that emptied "early" often has an adjustment behind it. Trace it in [`Read a keg history`](/docs/inventory/keg-history/). ## What to do next - Check the connection first in [`Connect a POS integration`](/docs/account/integrations/). - Understand what each sync moves in [`Understand POS sync operations`](/docs/account/pos-sync-operations/). --- # Fix common sign-in problems This guide is for the first few minutes of login friction, when you want to know whether the problem is formatting, credentials, or a password reset situation. ## What you'll learn By the end of this guide, you will know: - how BevWerk flags an invalid email format before you submit - what message appears after an unsuccessful login attempt - where the password reset flow starts, and what to do when its email does not arrive ([`Reset your password`](/docs/support/troubleshooting/reset-your-password/)) ## Why this matters Sign-in problems are stressful when the product stays vague. This walkthrough shows the opposite approach: BevWerk gives owners and managers a clear validation cue, a friendly failed-login message, and an obvious reset path without making them hunt for help. ## Watch the walkthrough - [Open the sign-in troubleshooting walkthrough](/docs/tutorials/troubleshoot-sign-in/) ## What this proves The sign-in experience is doing more than authenticating a user. It is also coaching recovery by separating: - formatting mistakes you can fix immediately - credential errors that need another attempt - access problems, where the always-present **Forgot password?** link is the fastest route back in ## What to do next - Visit [`Troubleshooting`](/docs/support/troubleshooting/) - Return to [`Your first day in BevWerk`](/docs/getting-started/first-day/) --- # Tutorials # Tutorials Use these short walkthroughs to learn how BevWerk supports day-to-day work in a craft beverage venue. ## Available walkthroughs Choose a guide that matches the decision you need to make, then return to the related topic page when you are ready to apply it. --- # Create a BevWerk Account {/* bw-tutorial */} ## Steps 1. Navigate to the sign up page 2. Enter personal details 3. Enter company details 4. Set password and accept terms 5. Submit and verify account creation --- # Customize Your Profile {/* bw-tutorial */} ## Steps 1. Start from your BevWerk workspace 2. Open your profile settings 3. Review the details BevWerk keeps on hand 4. See where profile photos and password updates live --- # Find Answers Fast {/* bw-tutorial */} ## Steps 1. Start from your BevWerk workspace 2. Open the FAQ library 3. Scan the help topics BevWerk organizes for you 4. Open the support FAQ when you need a human 5. Learn how to project a Digital Menu to a display --- # Get Started with BevWerk {/* bw-tutorial */} ## Steps 1. Orient yourself on the dashboard 2. See how On Tap reflects your current setup 3. See how menu publishing reflects that same setup --- # Manage Beverage Inventory {/* bw-tutorial */} ## Steps 1. Start from your BevWerk dashboard 2. Review the Kegs inventory table 3. Check the Bottles and Cans inventory view 4. See how the On Tap workspace reflects your setup --- # Manage Catalog Entities {/* bw-tutorial */} ## Steps 1. Start from your BevWerk dashboard 2. Manage Distributors 3. Manage Producers, including the Import Producers catalog 4. Manage Products 5. Manage Styles, including the Import Styles catalog --- # Manage a Digital Menu {/* bw-tutorial */} ## Steps 1. Start from your BevWerk dashboard 2. Open the Digital Menu workspace 3. Review the current digital menu state --- # Manage Operational Settings {/* bw-tutorial */} ## Steps 1. Start from your BevWerk dashboard 2. Manage Flights 3. Manage Glassware 4. Manage Menu Categories 5. Manage Taps and Taplists --- # Manage a Paper Menu {/* bw-tutorial */} ## Steps 1. Start from your BevWerk dashboard 2. Open the Paper Menu workspace 3. Review the current paper menu state --- # Manage Your Subscription {/* bw-tutorial */} ## Steps 1. Start from your BevWerk dashboard 2. Open the Subscription workspace from the Company menu --- # Manage User Access {/* bw-tutorial */} ## Steps 1. Start from your BevWerk dashboard 2. Open the Users management workspace from the Company menu 3. Open the Add User form 4. Cancel out of the form without creating a user --- # Manage Website Events {/* bw-tutorial */} ## Steps 1. Start from your BevWerk dashboard 2. Open the events workspace BevWerk uses for this location 3. Review the tools BevWerk gives you for event content 4. Browse the supporting event publishing controls --- # Navigate the Dashboard and Settings {/* bw-tutorial */} ## Steps 1. Start from your BevWerk dashboard 2. Read the sidebar like a product map 3. Open the Kegs workspace from the sidebar 4. Open the gear menu to see the management tools 5. Open the Producers workspace from the gear menu 6. Switch to the Products workspace from the gear menu --- # Publish Your Menus {/* bw-tutorial */} ## Steps 1. Start from your BevWerk dashboard 2. Open the Digital Menu workspace 3. Review the next publishing action from Digital Menu 4. Check the Paper Menu publishing surface 5. Review the Bar Menu starting point --- # Recover from a Missing Page {/* bw-tutorial */} ## Steps 1. Start from the dashboard so the workspace navigation is available 2. Open a link that no longer exists 3. Read the recovery message BevWerk shows 4. Return to the dashboard and keep working --- # Review Company Information {/* bw-tutorial */} ## Steps 1. Start from your BevWerk dashboard 2. Open the company information workspace 3. Review the subscription details BevWerk keeps on hand --- # Review POS Integrations {/* bw-tutorial */} ## Steps 1. Start from your BevWerk dashboard 2. Review the POS entitlement in Company Info 3. Open the Locations table and inspect the row actions --- # Review Sales Reports {/* bw-tutorial */} ## Steps 1. Start from your BevWerk dashboard 2. Open the Sales reports workspace 3. Review the Items report when sales data is connected --- # Sign In to BevWerk {/* bw-tutorial */} ## Steps 1. Navigate to the login page 2. Enter credentials and submit --- # Troubleshoot Sign-In Problems {/* bw-tutorial */} ## Steps 1. Open the sign in page and orient yourself 2. See BevWerk catch an invalid email format before submit 3. See the friendly error message for incorrect credentials 4. Open the reset password flow when you need to recover access --- # Understand the Dashboard {/* bw-tutorial */} ## Steps 1. Start at the homepage and get redirected to sign in 2. Sign in and arrive on the dashboard 3. Use the dashboard navigation to re center yourself --- # Website & events This section is for the parts of BevWerk that shape what people see outside the core operational workspaces. ## Start here 1. [`Manage events`](/docs/website/manage-website-content/) — understand the events manager BevWerk surfaces today for the demo workspace and how it supports public-facing updates. 2. [`Build and configure website pages`](/docs/website/build-website-pages/) — assemble public pages, navigation, and metadata. 3. [`Publish events, sections, and hero images`](/docs/website/events-and-visuals/) — the content that fills your public pages. ## What this section covers - event management workflows - search and pagination for public-facing content lists - the bridge between internal setup and outward presentation - how website page editing appears once a location has website access ## Why this section matters Public-facing content is easy to treat as an afterthought. But once a business is operational, events and website updates are often the next surfaces that need to stay current. This section helps explain those workflows directly, starting with the events path the current demo workspace exposes. --- # Build and configure website pages Your website is the one part of BevWerk that strangers see before they decide to visit. **Pages** (`/website/pages`) is where you build it. Managers can use the **Published** switch in website settings to control whether visitors can see the whole public website. When it is off, the site is hidden from visitors. If Pages says you're viewing the last loaded version, choose **Reload**. You can save again after Pages confirms it has the latest content for this location. If you have unsaved changes on any website tab, Pages asks before reloading, because reloading discards them. ## Pages are built from blocks A page is assembled from blocks rather than written as one long document. Each block holds a piece of content, and one of the blocks available to you can embed your live menu — which is what keeps the beer list on your public site tied to what is actually pouring. That embed is the reason to build the page here rather than elsewhere. A menu pasted into an external site editor is correct exactly once. ## Site-wide settings Some settings belong to the whole site rather than any single page: - **Website Title** and **Default Meta Data** (**Meta Title**, **Meta Description**) — what search engines and link previews show. These are the words people read before they click. - **Navigation** — which pages appear as a **Nav Item**, and in what order. - **Home Page Message** — a custom message on the home page, useful for a temporary announcement you do not want to build a whole page for. - **Social Media** — your **Facebook Handle** and **Instagram Handle**. - **Newsletter form URL** — paste the HTTPS action URL from your Mailchimp signup form, including its `u` and `id` values; it must use a `list-manage.com` subdomain and the `/subscribe/post` path. If you collect signups through Toast instead, paste your Toast marketing signup page, such as `https://www.toasttab.com//marketing-signup`. Leave it blank if you do not use a newsletter form. Do not enter an API key. ## Activate and Deactivate A page can be **Activated** or **Deactivated**. Deactivating is not deleting: the page and its content stay intact, they simply stop being public. This distinction is worth using deliberately. A seasonal page, an event that has passed, or a page you are still drafting can all sit deactivated without losing the work, and go live again when the moment comes around. ## Preview reflects what you have sanitized The page preview renders the same content your visitors will get, including any embedded menu. Content is sanitized before it is stored and again before it is shown, so what survives into the preview is what is safe to publish. ## What to do next - Add dated happenings in [`Manage events`](/docs/website/manage-website-content/). - Decide what your public beer list should show in [`Choose the right menu surface`](/docs/publishing/choose-a-menu-surface/). --- # Publish events, sections, and hero images Once your pages exist, three things fill them: events that change weekly, sections that structure a page, and hero images that set the tone. ## Events An event carries an **Event Title**, **Content**, an **Image**, and a start and end expressed as date and time (**End date**, **End Time**). Giving an event a genuine end matters more than it seems. An event without one becomes a stale listing that outlives the thing it advertised, and nothing makes a taproom site look abandoned faster than a trivia night that finished three months ago. Images are cropped when you add them — **Confirm Image Crop** — so the shape stays consistent across listings rather than depending on whatever the camera produced. ## Sections Sections are the blocks a page is built from. Each carries its own **Background Color** and **Text Color**, so a page can alternate between light and dark bands rather than running as one undifferentiated column. A **Code Snippets** reference is available alongside the section editor, showing the markup you can use. Note what it cannot do: saved content is sanitized to a safe allowlist, and `iframe`, `embed`, `form`, `input`, and `script` elements are removed. Maps, booking widgets, and third-party forms therefore cannot be embedded this way. The one supported embed is BevWerk's own menu element — see [`Choose the right menu surface`](/docs/publishing/choose-a-menu-surface/). ## Hero images Hero images are the large visuals at the top of a page. Add them under **Hero Images**, with **Add Image**, cropping, and a **Corner Radius** to match the rest of your styling. A hero is the first thing a visitor sees and often the only thing they remember, so it is worth using a photograph of your actual room rather than a stock image of somebody else's. ## Consistency comes from your brand settings Colours here sit alongside the brand colours set in Company Info. Setting those properly first means section and hero choices are picking from a palette rather than inventing one per page — see [`Set company branding and tax defaults`](/docs/settings/company-brand-and-taxes/). ## Where events appear When a location has a website, Events becomes a first-class section in the app navigation. Before that, it is reachable from the settings menu — which is why the path differs depending on how far along your site is. ## What to do next - Build the pages these live on in [`Build and configure website pages`](/docs/website/build-website-pages/). - Put your live beer list on the same site via [`Choose the right menu surface`](/docs/publishing/choose-a-menu-surface/). --- # Manage events This guide is for owners and managers who need to update what guests or visitors see without digging through unrelated settings screens. ## What you'll learn By the end of this guide, you will know: - where BevWerk keeps the events manager when a location does not yet have website access - how the add-event form is separated from the event list - how search and pagination support day-to-day event upkeep - when website page editing becomes available for a location ## Why this matters Public-facing content is easier to trust when the product separates: - event management - list navigation for larger sets of content - website page editing for locations that have it enabled That structure gives owners and managers a calmer way to maintain outward-facing information. ## Watch the walkthrough - [Open the events walkthrough](/docs/tutorials/manage-website-events/) ## Why this walkthrough starts with events instead of page tabs The current demo workspace does **not** have location website pages enabled, so BevWerk exposes the public-facing events manager directly from the toolbar settings menu. Once website access is enabled for a location, BevWerk also unlocks the dedicated website page-editing workspace. ## What this guide proves The events tools are not hidden behind one overloaded screen. BevWerk breaks them into clear workspaces so you can: - jump straight into event management from the toolbar - open the add-event form only when you need it - move through larger event lists without losing context ## What to do next - Return to [`Website & events`](/docs/website/) - Revisit [`Publish your menu`](/docs/publishing/publish-your-menu/) - Or move to [`Help & support`](/docs/support/) for the self-serve guidance side of the product