Concierge Onboarding is an operator, not a parser. Send the list as an export, a shared sheet or photographs of bin cards, and somebody resolves what a machine would guess at: half-case splits, two growers under one surname, Ch. against Château, vintages written four ways. You sign off before anything commits. Included with any product.
What actually goes wrong in a wine list, and what happens to each
Duplicates
Flagged against the row they duplicate. An operator merges or keeps both, because the same wine in two conditions is genuinely two lots and a dedupe would destroy that.
Bin collisions
Two lots claiming one bin. Warned and allowed on confirmation, because in a real cellar a shared bin is sometimes just true.
Vintages that will not parse
NV, MV, 2019/20, a bin card that says 19. Not committed until resolved, because a wrong vintage is a wrong valuation that nobody catches for a year.
Near-matches on a grower
Surfaced as a candidate, never applied automatically. Ch. Gruaud and Château Gruaud Larose are one house. Two Gros cousins in Vosne are not.
Missing cost or window
Committed with a warning, because these are gaps rather than errors — and the report will tell you what each one costs you.
No market reference at all
Committed and marked unresolved, carried at cost, excluded from market totals. Common in Jura, older Loire, and anything a grower sells out of the cellar door.
What it takes from your floor team
Five to ten working days per property
An operator does it. Your team does not.
One sign-off
You review the resolved queue before it commits. That review is usually forty minutes.
Nothing to install and nobody to train
There is no implementation phase, because there is nothing for your staff to learn in order for the list to be clean.
Questions people ask first
Our wine list is a mess. Will it import?
Three sommeliers have edited that spreadsheet. Good luck.
Not cleanly, and Aivin says so on screen rather than committing bad rows quietly. Half-case splits logged as singles, two growers filed under one surname, Ch. and Château as separate producers, bin cards that disagree with the sheet. An operator resolves that queue by hand, once, and you sign off before anything commits.
How long does it take to get a cellar into Aivin?
My team does not have time for an implementation.
Five to ten working days per property, and an operator does the work rather than your floor team. Send whatever you keep the list in — an export, a shared sheet, photographs of bin cards — and sign off on the resolved queue before it commits. Nothing to install and nobody to train.
