Can AI build a wine cellar tracker app like CellarTracker?

Build a personal wine cellar tracker web app to replace CellarTracker for my own use.

Tech rules:
- Plain HTML, CSS, and vanilla JavaScript in one file. No framework, build step, account, or server.
- Store all data in localStorage under one key, with a version number.

Data model:
- Bottle: id, wineName, vintage, format (750ml | 375ml | magnum | other), quantity, location, bin, status (in-cellar | consumed | pending), purchasePrice, purchaseDate, store, drinkByDate (optional), createdAt.
- TastingNote: id, bottleId, date, rating, note.

Features:
- Add a bottle: name, vintage, format, quantity, location, bin, purchase details.
- Mark a bottle consumed, reducing quantity and logging the date.
- Add multiple tasting notes to the same bottle over time.
- Filter and search by location, status, or vintage.
- A simple drink-by date field you set yourself, with bottles due soon shown first.

Edge cases the build must handle correctly:
1. Consuming one bottle from a multi-bottle entry reduces quantity by one instead of marking the whole entry consumed.
2. The same wine across different vintages or formats are separate entries, not merged.
3. A bottle with no drink-by date doesn't appear in the "due soon" list.
4. Deleting a location reassigns its bottles to "unassigned" rather than deleting them.
5. Multiple tasting notes on one bottle show in date order, most recent first.
6. Purchase price is optional and doesn't block saving a bottle.

Backup:
- One-click "Export JSON" and "Export CSV" (wineName, vintage, format, quantity, location, status columns).
- "Import JSON" restores after confirmation.
- "Import CellarTracker CSV" reads a CellarTracker inventory export and maps its wine, vintage, location, and bin columns, reporting how many bottles imported.

Layout:
- Mobile-first, readable at 375px wide, easy to check while standing in front of the cellar.

Exclusions:
- No publishing, App Store submission, accounts, community data, critic scores, or market value lookups.

Write a short README explaining where the data lives, how to export and restore it, and that this tracks only your own bottles, not community wine data.

Keep it under 600 lines. This is a personal tool, not a product.

What is the short answer?

Yes, but. AI can build a personal wine inventory that replaces the part of CellarTracker you actually own: your bottles, locations, and tasting notes. CellarTracker’s price is a suggested donation, from $40 a year for up to 100 bottles to $500 a year for 2,500 or more, and your inventory stays usable even without paying.

The “but” is what the donation actually funds. CellarTracker’s core value isn’t your own log, it’s the community database: 5 million-plus unique wines and 13 million-plus tasting notes and reviews contributed by other users over two decades. A personal build tracks your bottles well. It starts with zero of that outside data.

Option	Best for	Upfront cost	Ongoing cost	Main limitation
Build a rough prototype	People who want a private bottle log without touching CellarTracker at all	$0 and 2–3 hours	$0	No community wine data, critic scores, or valuation
Build a daily-use personal version	Collectors who mainly track their own cellar, location, and tasting notes	$0 and 6–8 hours	$0	Still no access to community drinking-window consensus
Keep paying for CellarTracker’s donation	People who rely on community tasting notes, critic scores, or valuation	$0	$40–$500/yr by cellar size, suggested	The donation buys community data, not your own inventory, which is already free

The ready-to-paste starter prompt at the end of this page builds the daily-use version.

What should the first version include?

The first version needs to answer “what do I own, where is it, and when should I drink it,” using your own judgment, not the crowd’s.

• Bottle entry with vintage, format, and quantity
• Location and bin tracking
• Status: in-cellar, consumed, or pending delivery
• Personal tasting notes across multiple tastings of the same bottle
• JSON backup, restore, and a CellarTracker CSV importer
• Deliberate exclusion: no community wine database, no critic scores, no market valuation. These need decades of other people’s data, not code.

What can AI build reliably?

ChatGPT and Claude build a bottle inventory reliably. It’s a list with fields for vintage, location, and status, a familiar shape for both tools.

Concrete things AI gets right:

• A bottle entry form that tracks quantity, vintage, and format separately
• Reducing quantity correctly when you consume one bottle from a case
• Multiple tasting notes stacking on one bottle over time
• Export buttons that download JSON and CSV
• A CellarTracker CSV importer that maps wine, vintage, and location fields

Where will AI need human help?

Drinking-window guidance is the real gap. CellarTracker blends consensus across many tasters of the same wine to suggest when it’s ready. Your personal build only has your own entered opinion. If you want that guidance, you’ll need to research each wine yourself or keep checking CellarTracker’s free community data, separate from any donation.

Valuation needs your own judgment. Without market or auction pricing data, “what is my cellar worth” isn’t something this build can answer. Test whether you actually check that number often enough to miss it.

The decision only you can make is whether you use CellarTracker’s community tasting notes when deciding what to buy. If you browse other people’s reviews before purchasing, that’s a reason to keep using the free community side of CellarTracker even if you build your own inventory log.

Privacy is simple for personal use. Your cellar data stays in your browser with no account, so back it up before clearing browser data.

Can I get my data out of CellarTracker?

Yes, and it doesn’t require the donation. CellarTracker exports as CSV, XML, HTML, or tab-delimited text from the full desktop website, available to any account regardless of payment status.

The trap: export only works from the desktop site, not the mobile app or mobile site. The default Wine Summary export omits location and bin unless you add a parameter to the export URL. CellarTracker keeps no transaction history, so its own docs recommend exporting regularly. Third-party reports, not CellarTracker’s own docs, claim the CSV uses an encoding that can corrupt accented characters, and that free-tier exports show a placeholder value instead of real drinking-window dates [VERIFY].

To move into your build, export your inventory as CSV and use the starter prompt’s “Import CellarTracker CSV” button.

How long will it take and what will it cost?

Rough prototype: 2–3 hours and $0. Bottle entry, status, and basic tasting notes.

Dependable daily-use version: 6–8 hours, including location tracking, a tested CSV importer, and multiple notes per bottle. Build it on a free AI plan.

CellarTracker’s suggested donation ranges $40 to $500 a year by cellar size. Since your inventory is free either way, building mainly saves the donation itself, if you were planning to pay it. A $20 AI month is less than half a year’s donation even at the lowest tier.

These are estimates from reviewing the feature set, not measurements from a completed build.

Which AI tool or approach should I use?

Claude or ChatGPT on a free plan is enough for this build in one sitting.

Claude is handy for previewing the bottle list and tasting note layout directly in the chat.

Cursor isn’t needed at this size.

Lovable would let you add photo uploads through a hosted database, but that adds maintenance for a feature you can approximate with a pasted image URL instead.

What will I need to maintain?

Very little. One HTML file with no server.

Recurring work:

• Export a JSON backup every few months, especially after adding a large purchase
• Re-open the app in the same browser; a different browser starts empty
• Update your own drink-by dates as you learn more about a wine

Should I build it, buy it, or reduce scope?

Build it if you mainly want your own bottle inventory, locations, and personal tasting notes.

Buy it, meaning keep donating to CellarTracker, if you regularly rely on its community tasting notes, critic scores, or market valuation when deciding what to buy or drink next.

Reduce scope to a plain spreadsheet if you don’t need location or tasting-note history, just a running list of what you own.

Recommendation: build the inventory log, since CellarTracker’s own free tier already lets you keep using the community side without paying anything. Donate only if you value supporting the community database you’re reading. For other collection types, the same shape of build applies to plant care or pet records.

What if I wanted to ship this to other people?

Shipping a wine tracker with community data means building and moderating a shared wine catalog, tasting notes, and valuation from scratch, a project measured in years of user contributions, not a weekend build. The personal inventory log doesn’t scale into that.

Starter build specification

• User: You, for your own use, tracking a personal wine cellar.
• Problem: Considering a $40 to $500 a year donation to CellarTracker when you mainly want your own bottle inventory, not the community database.
• Core workflow: Add a bottle with location and vintage, log tasting notes over time, mark it consumed when it’s gone.
• Required features: Bottle entry, location and bin tracking, status, multiple tasting notes, CSV import and export.
• Deliberate exclusions: No community wine database, no critic scores, no market valuation, no accounts.
• Data ownership: Stored in localStorage. Exported as JSON and CSV. Imported from JSON backups and CellarTracker inventory CSVs.
• Definition of done: You import a CellarTracker CSV export, and every bottle appears with correct vintage, location, and status, and consuming one bottle from a multi-bottle entry reduces the count without deleting the record.

For scoping help, read can AI build an app for me.

Sources and verification

• CellarTracker subscription and donation (CellarTracker support): donation tiers by cellar size, from $40 to $500 a year.
• Exporting data (CellarTracker support): CSV, XML, HTML, and tab-delimited export formats and access requirements.
• CellarTracker on the App Store: mobile in-app purchase tiers [VERIFY].

This app was not built and tested for this page. The verdict is based on CellarTracker’s own support documentation and a review of the feature set. CellarTracker’s price was checked on September 24, 2026.

Reviewed on September 24, 2026.