Normalize wine identity
Resolve producer, wine, vintage, format, LWIN, and related metadata before pricing or analytics logic runs.
API feature
Match messy wine data and LWIN codes to canonical identities.
Wine names arrive as merchant text, supplier rows, auction lots, cellar notes, product exports, and sometimes LWIN codes. Wine Labs helps teams resolve them into structured wine records they can trust.
Wine Labs desk
Market context, ready to use
Canonical
Wine Labs IDs for matched records
Batch
matching for files and systems
API
response format ready for integration
Q1
Q2
Q3
Q4
Power internal systems
Use matching in marketplaces, investment platforms, cellar tools, merchant ERPs, and AI workflows.
Connect to market data
Once a wine is matched, teams can request pricing, auction, critic, and coverage data against the same identity.
How teams use it
A matching layer before every serious wine data product.
1
Send a wine name with optional vintage, format, producer, region, source fields, or LWIN code.
2
Receive a matched canonical Wine Labs identity, available LWIN context, and useful confidence fields.
3
Store the canonical wine_id in your system for stable future lookups while retaining LWIN for interoperability.
4
Use that identity to request market data, pricing, auction, critic, or cellar enrichment.
Canonical IDs
Stop matching the same wine again and again
Wine systems become more useful when every bottle points to a stable identity instead of a fresh text search. Wine Labs keeps wine_id as the canonical key and supports LWIN where it helps teams interoperate with existing data.
- Canonical wine_id output for downstream workflows
- LWIN codes included where available for external compatibility
- Producer, wine, vintage, and format metadata
- Consistent identity across pricing and enrichment tools
Messy inputs
Built for real supplier and merchant data
Professional wine data rarely arrives clean. Matching needs to tolerate abbreviations, cuvee variants, vintage formats, inconsistent naming, and mixed identifier systems such as LWIN.
- Useful for spreadsheets, product feeds, and auction lots
- Can use LWIN as a matching signal when it is supplied
- Works with partial context when full metadata is missing
- Supports review workflows for uncertain matches
Product infrastructure
A foundation for richer data products
Matching is the first layer. After that, teams can build valuation, search, portfolio, recommendation, and market intelligence features.
- Connect matched wines to market data
- Reduce duplicate records in internal systems
- Improve AI and search experiences with structured context
Common questions
Built for professionals who need answers, not dashboards for their own sake.
What is a canonical wine identity?
It is a stable Wine Labs wine_id used to represent a specific wine record, with external identifiers such as LWIN included where available. Teams can use the Wine Labs ID as the canonical key while keeping LWIN codes for interoperability, pricing, analytics, and enrichment workflows.
Can the API handle batch matching?
Wine Labs supports workflows where many rows need to be matched, including spreadsheet and system integration use cases with names, vintages, formats, supplier fields, and LWIN codes.
Is matching useful without pricing data?
Yes. Canonical matching is useful for deduplication, search, catalog normalization, AI workflows, and product data quality even before pricing is attached.
Keep exploring
Related Wine Labs pages
Canonical wine identities and market data in one place
Private inventory can sit beside public market context
Designed for pricing, sourcing, valuation, and product teams