Settings

Settings is where you tell vestl about your business — your facilities and their TTB permits, your legal identity, your locations, your tanks and lines, your unit conversions, and your users. Most of it is set once at onboarding and rarely touched afterwards. Get it right here and the rest of vestl works.

The settings cluster lives under Settings in the sidebar with the following sub-pages:

• Company — Company profile (legal identity, compliance regimes, defaults)
• Compliance — Compliance profile (reporting period, COLA defaults, state licenses)
• Facilities — Bonded premises and the TTB permit issued for each
• Locations — Typed storage spots inside a facility
• Tanks & Lines — Tanks, vessels, and packaging lines
• Units of Measure — Units and conversions
• Users — Users and role assignments
• General — Misc preferences

This doc covers what each surface owns and the field-by-field meanings that tooltips should mirror.

---

Company profile

Your business’s legal and operational identity. The fields here populate downstream documents (POs, invoices, COAs, production records).

Identity section

• Legal name — the entity name on your TTB permit and tax filings. Appears on every external document. Edit at your own risk — changing it without updating your TTB permit is a compliance issue.
• Trade name (DBA) — the customer-facing brand name if it differs from the legal name. Optional. Used on invoices when present.
• EIN — your federal Employer Identification Number. Used on AP/AR documents and tax filings. Stored once, used everywhere.

Logo

An image used on PDF outputs (invoices, packing slips, COA reports, TTB report cover sheets). PNG or SVG; ~256×256px works best.

Compliance regimes

Sets the compliance posture for the whole workspace. The operational TTB detail (DSP permit, premises, reporting cadence) lives on the Compliance profile page — this section just decides which of those surfaces appear.

• Workspace regime — Alcohol or None. Alcohol surfaces the TTB sections on the Compliance profile; None hides federal compliance configuration.
• Default product regime — TTB or None. Applied as the default when creating a new product. Override per-product on the product detail page.

Contact

The default contact for vendor-facing communications (POs, vendor inquiries). Different from individual user accounts — this is the “info@” of your operation.

Preferences

Defaults applied to new records, e.g. the default timezone used for schedules and TTB cutoffs.

”Incomplete” pill

Shown top-right until legal name, EIN, and primary email are all set. The setup checklist on the Planning dashboard reads this state to mark “Complete company profile” green. TTB permit and premises are no longer required here — they gate the Compliance profile instead.

---

Compliance profile

Operational compliance defaults for the workspace. What appears here depends on the Workspace regime picker on the Company profile: an Alcohol workspace sees the TTB sections below; a None workspace sees an empty state with no federal filing configuration.

Your TTB/DSP permit and premises address live on Facilities — a permit is issued for a physical premises, so it belongs to the site. This page keeps the org-wide operational defaults.

TTB operations

Shown only for an Alcohol workspace.

• Reporting period — Monthly, Quarterly, or Annually. Determines how the Production Records page rolls up records into reports.
• Default product compliance regime — set on the Company profile under Compliance regimes. Applied as the default when creating a new product; override per-product on the product detail page.

State licenses

vestl tracks state licenses as first-class records (federal TTB permits live on Facilities). Add one row per state where you hold a license; each carries its own expiration date and renewal window.

• State — the 2-letter postal code (ABC / DOR / equivalent).
• Permit / license number — the state-issued identifier.
• Expiration date — required. vestl reads this to warn ahead of renewal.
• Renewal window (days) — default 90. vestl renders a warning chip when expiration falls inside this window, a critical chip inside 30 days, and emits a compliance exception in the inbox so the renewal lands on someone’s queue.

After renewing, edit the row and update the expiration date — the renewal-alert dedupe resets so the next pass treats the row as a freshly-renewed license.

---

Facilities

A facility is your organization’s physical premises plus the TTB permit issued for it. A DSP / Basic Permit is bonded to an address, so the permit and the premises live together. The initial vestl operating model is one site per organization; multi-site distribution and routing are not yet supported. Inventory locations (rooms, racks, bins, tanks) hang under that facility for clean TTB rollups.

A facility is the first onboarding step: everything else (locations, tanks, products) builds on having a premises.

Field reference

• Name — how operators refer to this physical site (e.g. “Oakland Bonded Premises”).
• Permit type — distillery (DSP), brewery, winery, etc. Determines which TTB form applies for this premises.
• TTB permit number — your federally-issued permit number. Load-bearing — production records default their DSP number from the facility. Type the state and number; vestl auto-formats it to the DSP-XX-NNNNN shape (the DSP- prefix is fixed). See Production Records for format details.
• Permit expiration — vestl reads this to warn ahead of renewal: a warning chip inside the renewal window, a critical chip inside 30 days or once expired.
• Renewal window (days) — default 90.
• Bonded warehouse permit — optional separate bonded-warehouse permit, distinct from the operating TTB permit above. Leave blank if the site isn’t separately bonded.
• Address — the physical premises address. Must match the address on the permit; copied into production records.

---

Location types

Location types describe the kinds of storage positions operators can create and which kinds may sit beneath them. Room, Rack, Shelf, Bay, Bin, Tank, Zone, and Pallet are bundled system reference types shared by every organization. Their names, capacity hints, enabled state, leaf behavior, and nesting rules are fixed so the same label has the same operational meaning everywhere.

Custom location types belong to your active organization automatically; there is no organization picker. Another organization may use the same custom name without sharing or changing your row. A custom type may allow bundled system types or custom types from your organization as children, but it can never reference another organization’s custom type.

Field reference

• Name — organization-local label for a custom storage type, such as “Cold cage” or “Ingredient tote”.
• Description — tells operators when to choose this type.
• Leaf type — prevents locations of this type from containing child locations.
• Default capacity — optional starting capacity copied into a new location; the operator may override it on the location.
• Allowed children — the location types that may be nested beneath this custom type. Only bundled system types and your organization’s custom types are offered.
• Enabled — disabled custom types remain in history but are hidden from new-location pickers.

System location types are read-only. Create a custom type when your operation needs different behavior instead of changing a bundled definition.

---

Locations

Where physical inventory lives inside a facility — cold rooms, racks, bins, packaging staging areas, tanks, and other addressable storage spots. Facility names are configured under Facilities; do not create a Location just to stand in for a site.

Locations belong to your active organization automatically. There is no organization picker: a location, its parent, its facility, its external custodian, its custom type, and any custom capacity unit must all belong to the same organization. A location or custom type from another organization is never shown or accepted. Bundled system location types and units remain available everywhere.

Field reference

• Name — identifier unique inside your organization (e.g. “Receiving Room”, “Bond Room”, “Rack 3”). Another organization may use the same name. Shown in lot detail and inventory transfers.
• Type — location type from the registry (Room, Rack, Shelf, Bin, Tank, Zone, or a custom type). The type controls valid nesting and default capacity hints.
• Capacity (qty + UoM) — optional. When set, vestl warns if a transfer would exceed it.
• Active — inactive locations are hidden from new-receive and transfer pickers but kept for historical lookup.
• Allows negative — rare; permits negative on-hand for transit or virtual locations.

The setup checklist treats “Add storage locations” as complete when at least one active location exists.

---

Tanks & Lines

Production capacity. A tank or line is a physical place where work is performed. Each row is labeled Tank, Vessel, or Line based on its type.

Layout

The page groups rows into three sections so you can scan capacity by category:

• Blending tanks & vessels — every entry typed Tank or Vessel.
• Bottling & packaging lines — every entry typed Line.
• Other — anything typed Room (only appears when populated).

A footer strip at the bottom of the page lists the Global stages (mix → blend → carbonate → bottle → case) every formula advances through. Read-only; it anchors this page in the production-kernel context — formulas elsewhere refer to these stages by name.

Field reference

• Name — unique identifier (“Fermenter 3”, “Bottling line A”).
• Type — Tank, Vessel, or Line. Drives which production steps can be scheduled here (you don’t bottle on a fermenter).
• Capacity (qty + UoM) — useful capacity. Validated against batch volumes during scheduling.
• Pre-run changeover (min) — time to prep this work center before a run begins (cleaning, setup, line clearance).
• Post-run cleanup (min) — time to clear/clean after a run ends (CIP, sanitization). Distinct from scheduled maintenance.
• Active — inactive tanks and lines don’t show up in scheduling pickers.
• Notes — free-text (calibration date, last cleaning, ownership).

Changeover time by change type

Changing between two runs on the same line costs time, and how much depends on how much the setup changes. Set three figures per line:

• Same product — back-to-back runs of the same product and container size. Minimal reset (a short rinse) — often 0.
• Product change — a different product on the same container size. Recipe flush and sanitation, no tooling swap.
• Container-size change — reconfigure the line to a different fill size (for example a 750 mL line set up for 1 L). The heaviest transition: change parts plus re-setup. This is where the “45-minute changeover” figures live.

Container-size change wins when both a product change and a size change apply at once, because the tooling swap is what costs the time.

Scheduling uses these to warn you: when the changeover from the prior day’s run on a line is, by itself, at or over that line’s working hours for the day, a changeover overruns the day exception appears in Schedule exceptions. Group like formulas and container sizes on adjacent days to clear it.

The setup checklist treats “Add tanks and lines” as complete when at least one active row exists.

---

Units of Measure

The conversion table. Defines all units (gallons, liters, kilograms, cases, each) and the conversions between them. Used everywhere a quantity changes hands between a vendor unit and an inventory unit, between recipe units and batch units, between vessel volumes and case volumes.

Field reference

• Code — short identifier (gal, L, kg, lb, case, each).
• Name — human-readable (“Gallon”, “Kilogram”).
• Type — Weight, Volume, Count, or Length. Conversions only work within a type — you cannot convert kilograms to liters without a density value, which vestl does not model.
• Conversions — for each pair, a multiplier (e.g. 1 gal = 3.785 L).

Most of this is seeded at onboarding and rarely changed. Adding a new unit is rare; it usually means a new brand uses an unfamiliar unit (e.g. shipping in pallets).

---

Case components

Where you set the words for case-level packaging. A Case BOM consumes parts — a box, a tray, a divider, a caddy, the outer shrink — and every shop calls these something slightly different. This page lets you rename each kind to match your floor’s vocabulary without changing anything underneath.

The kinds vestl ships with:

• Case box — the box the bottles or cans sit in.
• Partition — the divider or insert that separates units inside the box.
• Tray — a flat tray the units sit on. Optional — not every pack uses one.
• Caddy — a small carry-handle multipack (e.g. a 4- or 6-pack caddy).
• Shrink wrap — film that bundles units or trays.
• Master case — the outer carton that holds several inner packs for shipping. (Some shops call this a shipper; vestl shows “Master case” by default.)
• Other — anything that doesn’t fit the above.

Renaming a kind

Type your preferred label in the field next to a kind. The default shows beneath it as a reminder. Leave a field blank to keep the default. Reset to defaults clears every override at once. Saving applies the labels everywhere the kinds appear — the Case BOM editor, the product wizard’s case step, and Case BOM detail views.

Renaming is display-only. The underlying kind never changes, so reports, lot genealogy, and anything that references a case part keep working exactly as before — only the words you see change.

---

Users and roles

Who can do what. Two halves:

User list

Every account that can sign into vestl. Fields: name, email, role, last login, status. Provisioned via SSO (Google) or invite-by-email.

Permissions matrix

Documents which roles can do which actions across each surface.

A user has exactly one role. To temporarily elevate, change the role and revert when done — every change is audit-logged.

---

General preferences

The catch-all. Date and time format, timezone, default page (which surface to land on after login), feature toggles for unreleased capabilities. Most of this is one-time setup; a few items are user-level overrides on the profile page.

---

How settings connect to the setup checklist

The Planning setup checklist reads from settings to compute progress. Several of its rows are settings-anchored:

1. Complete company profile — when the company profile is marked complete
2. Complete compliance profile — when the TTB reporting period is set
3. Add storage locations — at least one active inventory location exists
4. Add tanks and lines — at least one active tank or line exists

The remaining rows live under Companies, Products, Product Specs, and Batches.

---

What you can’t do here

• Delete a TTB DSP number after a production record references it. You can change the field, but the historical production records keep the original — this is by design (audit trail).
• Change a unit-of-measure type after products use it. A weight-typed unit cannot become volume-typed; create a new unit instead.
• Inactivate a location with on-hand inventory. Move the inventory first.
• Inactivate a tank or line with scheduled manufacturing orders. Reschedule the orders first.

These are guardrails against destructive edits that would corrupt downstream records.