Two habits do almost all of the work: remove bottles the day you drink them, and reach for bulk edit rather than editing bottles one by one. The rest of this article is the traps.

A collection drifts because removals get postponed, not because adding is hard. Removing is three taps from your collection page and the date defaults to today, so doing it in the moment beats reconstructing a month later.

Quantity only appears while you are adding. Once bottles exist, each is a row of its own, so you change a count by adding or removing. On iPhone and iPad, swiping left on a wine gives you Add beside Remove for exactly this.

Editing the year moves the bottle onto a different label — the row for that wine in that year — and anything stored against the old label stays behind.

Read the bulk form as what you are about to set, not as what the bottles currently hold. Where your selection disagrees, a field falls back to a default rather than showing a blank — size falls back to 750ml, prices and storage to empty. Only fields you actually change get sent.

Two rows are narrower than the rest: Vintage and custom fields appear only when every bottle you picked is the same wine and year. The cap is 500 bottles at once. The button reads Save when you are editing and Confirm when you are adding, which is a useful check that you are in the flow you think you are.

Activity is the only place that answers "who changed this". It records bottles added, consumed, sold, gifted, removed and moved between storages, with the collaborator's name, and nothing ages out. It does not record field edits — it will tell you a bottle moved, not that someone retyped its price.