What lives inside
the Chrome program.

Bar Inventory Master Sheet

Inside the Chrome program, this is the spreadsheet brain behind the admin panel. Setup builds the first version from the approved bar map, then each cycle updates it with counts, invoices, and POS exports.

What It Looks Like

• -Tabs for liquor, beer, wine, mixers, and future dry goods
• -Rows organized by physical location: wells, back bar, coolers, storage, and liquor room
• -Columns for product, bottle size, par, opening count, purchases, closing count, cost, and variance

How It Works

1. 01The customer maps the bar by voice during setup.
2. 02The system turns that map into the first XLS workbook.
3. 03After the customer audits and approves it, the workbook becomes the source for weekly reporting.

Quick Count Template

The Chrome program generates the template from the latest approved inventory map, so it changes when the bar layout, product list, or categories change.

What It Looks Like

• -A simple print sheet ordered by the customer's real walking route
• -Blank count fields beside each bottle, shelf, well, cooler, and storage area
• -A matching XLS version so paper counts can be entered back into the program

How It Works

1. 01Print or open the sheet before walking the bar.
2. 02Count by the same left-to-right route used during setup.
3. 03Enter the results into Weekly Inputs so the admin panel updates the cycle.

Variance Calculator

Variance becomes part of the admin panel. Weekly Inputs feeds it with three things: the count, invoice pictures, and POS downloads.

What It Looks Like

• -Opening inventory plus invoice purchases minus ending inventory
• -POS sales imported by the same weekly cycle
• -Category, bottle, and shift-level flags for unexplained gaps

How It Works

1. 01Upload invoice photos from the inventory period.
2. 02Upload the POS sales export for the same dates.
3. 03The system compares expected usage against actual count movement and updates the report.

Product Database

The database lives inside the program so voice notes, invoices, POS exports, and spreadsheet rows all resolve to the same product identity.

What It Looks Like

• -Common bar products with category, bottle size, pour size, and cost fields
• -Alias matching for voice transcription and invoice naming differences
• -Customer-specific additions created during setup and weekly corrections

How It Works

1. 01The setup flow starts with a standard product list.
2. 02Customer products are matched or added as the first bar map is reconciled.
3. 03Future invoice and count inputs update the database when new products appear.

AI Bottle Counter

This is a feature inside the Chrome program, not a separate script. It supports the count workflow when the customer takes shelf or bottle pictures.

What It Looks Like

• -A photo intake step connected to the approved location map
• -AI estimates that still ask the manager to confirm uncertain bottles
• -Corrections that feed back into the inventory count for that cycle

How It Works

1. 01Open the count flow for a mapped section.
2. 02Take or upload the shelf image.
3. 03Confirm the fill estimates before they update the weekly count.

Mobile Count View

This is the mobile side of the same Chrome/admin program. It follows the approved map and sends weekly counts back into the dashboard.

What It Looks Like

• -A section-by-section count screen ordered by the real bar walk
• -Large tap targets for bottle level, cases, loose bottles, and notes
• -A final review before the count becomes part of the weekly cycle

How It Works

1. 01Choose the section you are counting.
2. 02Enter bottle levels or case counts as you walk.
3. 03Submit the count into Weekly Inputs for reconciliation.