App builder

Every case, bottle and allocated release
tracked in one liquor inventory app.

Tell Netiva’s AI agent how your shop buys and sells, and it builds a web app for case and bottle stock, allocated releases, distributor orders and a 21+ catalog while you watch the preview.

Start building free More app ideas
Starter prompt

Build a liquor inventory web app for a bottle shop selling spirits, wine and craft beer. Store each product’s category, size, units per case, reorder point, price and distributor; keep stock in single units, shown as full cases plus loose bottles. Turn low stock into one order per distributor, in cases plus split bottles. Track allocated releases with the units allotted, a per-customer limit and a first-come or draw method, and let signed-in customers request a bottle or pack. Put a public catalog behind an age confirmation set to the legal drinking age where I sell, 21 in the US, with stock labels instead of exact counts.

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

Who this liquor inventory app is for

Bottle shops buy by the case and sell by the bottle, and that gap is where counts drift. A spreadsheet can hold the item list, but it won’t show that the backroom has two cases and seven loose bottles of a 750 ml bourbon, who asked for this fall’s allocated release or which distributor order is due before Tuesday’s cutoff. A liquor inventory app built with Netiva keeps products, case sizes, distributor orders and release requests together, then publishes a 21+ catalog so regulars can see what’s on the shelf before they drive over.

Key features

What your liquor inventory app can do

  • Cases, bottles and split cases

    Each product knows how many sellable units come in a full case, so you can receive in cases, sell by the bottle and still read one clear number for the shelf and the backroom.

    • Stock shown as full cases plus loose units, such as 3 cs + 7 btl
    • Delivered cases converted to units when an order is checked in
    • Split lines for single bottles bought from a broken case
    • Case sizes filled in across many products at once with the collection assistant

  • Allocated and limited releases

    When a distributor confirms how many bottles of a limited release you’ll get, log the allotment, the per-customer limit and whether requests are offered first come or drawn at random when the window closes.

    • Customers sign in to request a bottle or pack and follow their request
    • Requests capped at each release’s per-customer limit
    • Offered in the order received, or drawn at random when requests close
    • An email when a bottle or pack is on hold, with the last pickup day

  • Distributor orders in cases and splits

    The reorder list compares units on hand with each product’s reorder point, rounds the suggestion up to full cases and groups it by distributor, and the buyer can add single bottles where that distributor breaks cases.

    • One draft order per distributor, in full cases, with split bottles the buyer can add by hand
    • Purchase orders emailed to the rep address on the order’s lines
    • Lines marked Sent, Delivered or Out of stock at the distributor
    • Saved views for each buyer’s categories, such as wine or spirits

  • An age-gated online catalog

    Catalog pages are built from the same product collection your staff keep current — name, size, price and a stock label — and visitors confirm they’re 21 or older before they can browse.

    • Category pages from the product collection, plus a label photo field if you want bottle shots
    • Stock labels such as In stock, Low or Ask in store instead of exact counts
    • Allocated releases listed as request-only, with no count shown
    • Published in one click, on your own domain from the Starter plan
Data model

The collections behind it

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

Products

Every bottle, can and pack you carry, with its case size and current stock.

  • Name (required) Include the vintage for wine Text
  • Category (required) Bourbon, Tequila, Red wine, IPA… Text
  • Size (required) 50 ml, 750 ml, 1.75 L, 4-pack of 16 oz cans Text
  • Units per case (required) Sellable units in a full case, such as 12 bottles of 750 ml or six 4-packs Number
  • Units on hand (required) Stored as single units; screens show full cases plus loose units Number
  • Reorder point (required) In units; the reorder list rounds its suggestion up to full cases Number
  • Unit price (required) Shelf price for one sellable unit — a bottle, can or pack Number
  • Distributor (required) The wholesaler you buy it from; groups reorders and orders Text

Order lines

One line per product on a distributor order, tied to the rest of that order by its number.

  • Product (required) Relation to Products
  • Order number (required) Shared by every line of one order; the order screen and the PO email group by it Text
  • Rep email Entered once on an order’s first line and copied to the rest Text
  • Cases (required) Number
  • Split bottles Single bottles from a broken case, where the distributor sells them Number
  • Line status (required) Draft, Sent, Delivered or Out of stock at the distributor Text
  • Units received Counted at check-in and added to units on hand Number
  • Delivery date Set on the lines that arrive together when you check a delivery in Date

Allocations

Each limited release you’re allotted, with its limit, method and request window.

  • Product (required) Relation to Products
  • Release (required) Such as Fall 2026 or Holiday release Text
  • Units allotted (required) Bottles, cans or packs the distributor confirmed for this release Number
  • Limit per customer (required) Most units one customer can request Number
  • Selection method (required) First come or Drawing Text
  • Requests close Cutoff for a draw, or when the release stops taking requests Date & time
  • Status (required) Expected, Taking requests, Drawn or offering, Closed Text
  • Photo Shown on the public release page Image

Release requests

Who asked for which release, in the order they asked.

  • Allocation (required) Relation to Allocations
  • Customer (required) Filled in from the signed-in customer Text
  • Email (required) Text
  • Units requested (required) Up to the release’s limit per customer Number
  • Requested at (required) Date & time
  • Status (required) Waiting, Offered, Picked up, Passed, Expired Text
  • Hold until Last pickup day for an offered bottle, can or pack Date
  • ID checked Yes or No, set by staff at pickup Text

Required field. Types are Netiva collection field types.

Screens

Pages and screens to start with

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

  • Catalog

    The public catalog by category, shown after the 21+ confirmation, with size, price and a stock label for each product.

    Public

  • Release page

    One limited release with its photo, size and per-customer limit plus a request button that asks the visitor to sign in.

    Public

  • My requests

    A customer’s own release requests with their status, their place in line for a first-come release and the last day to pick up a held bottle or pack.

    Signed-in users

  • Release requests

    Staff see every request for a release in the order received, offer bottles or run the draw when requests close, and mark pickups with the ID check.

    Your team

  • Stock and reorder

    All products as full cases plus loose units, low stock flagged and grouped by distributor, with an inline field to correct units on hand when you count a shelf.

    Your team

  • Distributor order

    The lines that share one order number, with cases, split bottles and status, plus a check-in step that adds the units received to stock.

    Your team
How it works

From prompt to a live liquor inventory app

  1. Describe how you buy and sell

    Tell the agent what you carry, which distributors you order from and how you handle limited releases. It drafts collections for products, distributor orders, allocations and release requests.

  2. Load the shelf

    Add your fast movers and allocated brands in the collection grid, or have the collection assistant draft records and fill in categories and case sizes across many rows at once, then add the long tail as you count it.

  3. Test the age gate and a request

    Open the catalog in the live preview, check that the 21+ confirmation appears first, request a bottle as a test customer and annotate anything you want changed.

  4. Go live before the next release

    Publish in one click, connect your shop’s domain on the Starter plan or higher and share the release link. Every change is checkpointed, so you can roll back if an edit misbehaves.

Why Netiva

Netiva vs a traditional build

Building a liquor inventory app with Netiva compared with a traditional build
Criterion With Netiva Traditional build
Case and bottle math Units per case stored with each product, so stock reads as full cases plus loose bottles Cases converted to bottles by hand on each invoice and again at count time
Allocated releases Signed-in requests with a per-customer limit and an email when a bottle is on hold A paper list by the register and phone calls when the bottles arrive
Getting started Describe what you need in chat and watch it take shape in a live preview Hire developers, or stitch together templates, plugins and a hosting plan
Content and data Built-in collections with nine field types, bound straight to your pages Set up and connect a separate database or CMS
Making changes Ask the agent; every change is checkpointed and reversible File a ticket, wait for a sprint, redeploy
Hosting and domain Global hosting and automatic SSL; connect a custom domain from the Starter plan Buy hosting, then install and renew SSL certificates yourself
Code ownership Clean production code you own and can export Locked into a template, plugin or agency setup
Examples

Ways teams use it

  • A family-run package store

    The owner buys spirits from three distributors each week. The stock screen shows what has dropped to its reorder point for each one, and the buyer emails every purchase order from the app before the rep’s cutoff.

  • A wine shop with a tasting bar

    The wine manager keeps each vintage as its own product with 12-bottle cases and loose bottles, lists what’s in stock in the 21+ catalog so regulars can check before they visit, and takes bottles opened for the tasting bar off units on hand so the shelf count stays honest.

  • A craft beer bottle shop

    Limited brewery cans are set up as releases counted in 4-packs with a per-customer limit. Customers who requested them get an email to pick up within the hold window, and unclaimed packs go to the next request.

Good to know

Before you build

  • Your license sets what you can sell online

    Your license and state rules decide whether you can take orders online, deliver or ship. In the US, USPS won’t carry alcohol, and other carriers and payment providers set their own terms. The app shows stock and takes requests; it doesn’t handle licensing.

  • An age gate isn’t an ID check

    A 21+ confirmation only asks visitors to say they’re old enough — set it to the legal age where you sell. Staff still need to check ID when a customer picks up a requested bottle, and the app can record that the check happened.

  • Allocations work differently in control states

    In control states the state manages wholesale spirits, and in most of them it also runs or designates the off-premises stores that sell them, so your range and your allotments follow that system. Some states also run their own drawings for limited releases.

  • No register, and no item-file import

    Netiva doesn’t run a register or import your item file. Enter fast movers and allocated brands in the grid or draft them with the collection assistant, then add the long tail as you count it. Stock drops from shelf counts, or from your POS provider’s API if it offers one.

Compliance note

In the US, no bottle, can or pack may go to anyone under 21; elsewhere the minimum age is set locally. Whether you can sell online, deliver or ship depends on your liquor license and state rules. The app tracks stock, shows a 21+ catalog and records release requests. Its age confirmation isn’t ID verification, and it doesn’t manage licensing, alcohol taxes or delivery rules. Check with your state alcohol agency before you take online orders or run a release drawing.

FAQ

Questions about building a liquor inventory app

Can the app track stock in both cases and bottles?

Yes. Each product stores how many sellable units come in a full case, such as 12 bottles of 750 ml or six 4-packs, and stock is kept as single units. Screens show it as full cases plus loose units. Delivered cases are converted when an order is checked in, and split bottles bought from a broken case are added one at a time.

How do customers request allocated bottles?

Each limited release gets its own page behind the age confirmation. Customers sign in, request up to the per-customer limit and follow every request under My requests. Set the release to first come, where staff offer bottles in request order and each customer sees their place in line, or to a draw that picks winners at random when the request window closes. Either way the app emails the customer when a bottle or pack is on hold, with the last day to collect it.

Is an age gate enough to sell liquor online?

No. An age gate only asks visitors to confirm they’re 21 or older; it doesn’t verify anyone’s age. Whether you can take orders, deliver or ship depends on your license and state rules, and ID still has to be checked at pickup or delivery. The app can record that staff checked ID when a customer collected a requested bottle.

Can staff use the liquor store inventory app from the sales floor?

Yes. Netiva builds web apps that open in the phone’s browser with no install, so staff can check stock, flag low items and check in deliveries from the floor or the backroom. You can also ask the agent to add a UPC field and a scan button that uses the phone camera to open a bottle’s product record.

Can units on hand update from my POS sales?

Apps built with Netiva can call REST APIs with keys stored securely. If your POS provider offers an API, describe the connection to the agent, for example pulling each day’s sales to lower units on hand. Read the provider’s API documentation and terms first. Without an API, update stock from regular counts and keep sending orders by email.

Can I change the app before a big release without breaking it?

Yes. Every change the agent makes is checkpointed, so you can branch, compare versions and roll back if a new request flow doesn’t work out. Netiva writes clean, framework-standard code that you own and can export whenever you want, and you can switch between the live app and its source at any time.

Keep exploring
All ideas
Compare

How Netiva compares

All comparisons

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

Build your liquor inventory app today

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

Start building free Browse more ideas