Drambook

Guide

How to catalog a whiskey collection: the fields that matter, and why a spreadsheet quietly falls apart.

Whiskey collecting · Record-keeping, not resale appraisal · Last reviewed June 2026

To catalog a whiskey collection, record eleven core fields per bottle (distillery, expression name, mash bill, ABV and proof, age, batch or barrel number, retailer, store-pick status, bottle size, what you paid, and a label photo) plus four living fields a static list always forgets: open versus sealed status, current fill level, tasting notes, and a pour log. A spreadsheet handles the first eleven well. It is the last four, the ones that change every time you pour, where a flat sheet quietly falls apart, usually right around the time your shelf passes two dozen bottles and stops fitting in your memory.

This is a guide to building a catalog you will actually keep. It is about record-keeping, not appraisal: the goal is knowing what you own, what is open, and what each bottle tasted like, not pricing your shelf for the secondary market. Let us start with the fields, then make the honest case about where the spreadsheet wall is, and how to cross it without throwing away the work you have already done.

The eleven fields that earn their place

Every bottle deserves a record detailed enough that future-you, holding the empty glass, can find it again, replace it, or know why you loved it. These are the fields worth typing once.

The four living fields a list forgets

Everything above is static. You type it once and it never changes. But a collection is not a list of purchases frozen in time; it is a shelf that empties one pour at a time. These four fields move, and they are the whole reason a catalog beats a receipt drawer.

Where the spreadsheet quietly falls apart

A spreadsheet is a genuinely good tool, and for a long time it is the right one. Twenty rows, a column per static field, sorted by distillery: that is a real catalog and there is no shame in it. The trouble is not that a spreadsheet is too simple. The trouble is that it is the wrong shape for the four living fields.

A flat sheet records bottles you bought. It is much worse at telling you what is on the shelf now. Three structural cracks show up, and they widen as the collection grows:

Under roughly two dozen bottles, you paper over all three gaps with memory. You just know the Lagavulin is half gone and the Eagle Rare is sealed. Past that point, memory stops scaling before the spreadsheet does, and you find yourself opening the sheet to learn something the sheet was never built to hold.

A spreadsheet is an excellent list of what you bought. It is a poor map of what is actually on the shelf tonight. The gap between those two is exactly the gap that opens up once a collection outgrows your memory.

The migration path: keep your CSV, just stop relying on it alone

The honest case for an app is not that your spreadsheet is bad. It is that the spreadsheet is the right shape for half the job and the wrong shape for the other half. The good news is you do not have to choose, and you do not have to retype anything.

Drambook is a private whiskey and bourbon catalog for iPhone built around exactly this list. Every static field has a home (distillery, mash bill, ABV and proof, age, batch, retailer, store-pick flag, bottle size, value, label photos), and so do the four living ones: an explicit open-versus-sealed status, a fill level, structured nose/palate/finish notes with a rating, and a pour log that keeps the fill level honest over time. The dashboard rolls all of it into shelf stats and a running cellar value, so the answer to "what is open and how full" is one glance, not a forensic read of a sheet.

Migration is the part people expect to be painful and is not. You map your existing CSV columns to Drambook's fields once, import the whole collection, and your spreadsheet's static work carries straight over. From there you add the living fields the sheet could never hold. And because you can export back to CSV or PDF at any time, your spreadsheet does not die; it becomes a portable backup you can regenerate on demand. The record stays yours, in both directions.

One more field that does not appear in any column but matters to a lot of collectors: where the catalog lives. Drambook keeps your collection, photos, notes and pours on the device, with no account and no collection cloud. On an iPhone that means the record is encrypted at rest by the system, the same on-device protection Apple applies to built-in apps, described in Apple's Data Protection overview. For a record of what you own and what it is worth to you, "stored locally, nothing uploaded" is not a marketing line; it is the correct default.

Get Drambook on the App Store
Free · iOS 17+ · imports your CSV
See how Drambook works

A field checklist you can copy today

If you do nothing else, set up these fields, whether in a sheet you are about to outgrow or an app built to hold them:

  1. Distillery and bottler
  2. Expression name (the full release, not the brand)
  3. Mash bill
  4. ABV and proof (both numbers)
  5. Age statement (or NAS)
  6. Batch or barrel number
  7. Retailer
  8. Store pick (yes or no)
  9. Bottle size
  10. Value (what you paid, as a personal reference)
  11. Label photos (front, back, batch code)
  12. Open versus sealed
  13. Fill level
  14. Tasting notes (nose, palate, finish, rating)
  15. Pour log (dated)

The first eleven you type once. The last four you maintain. The first eleven are why people start a catalog; the last four are why they keep one. A spreadsheet does the first beautifully and the second badly, and that asymmetry is the whole story of why, somewhere past two dozen bottles, the sheet quietly stops being enough.

Answer-first FAQ

Quick answers

What fields should I record for each whiskey bottle?

Record distillery, expression name, mash bill, ABV and proof, age, batch or barrel number, retailer, store-pick status, bottle size, what you paid, and a label photo. Then add the four living fields a static list forgets: open versus sealed, current fill level, tasting notes (nose, palate, finish), and a pour log.

Is a spreadsheet good enough for tracking a whiskey collection?

As a list of bottles you bought, yes. It falls apart once you want to know what is actually on the shelf right now, because a flat sheet has no clean way to hold pours, fill level, open-versus-sealed status, or label photos. Under about two dozen bottles you cover the gaps with memory; above it, you cannot.

How do I track which bottles are open versus sealed?

Add an explicit status field with two states (sealed, open) and a separate fill-level field for opened bottles, then update fill level every time you pour. A spreadsheet can fake the status column but cannot keep the running pour history that makes the fill level trustworthy.

Do I have to abandon my CSV to use an app?

No. Map your CSV columns to the app's fields once, import the whole collection, and keep exporting back to CSV whenever you want. Drambook works this way, so your spreadsheet becomes a portable backup rather than a cage.

Is cataloging the same as appraising my collection for resale?

No. Cataloging is record-keeping: what you own, what is open, what it tastes like. The value field is what you paid or would replace it for, a personal reference number, not a market price guide.

Keep reading