Contact

Reaching the Oregon Wine Authority means reaching a reference resource built specifically around Oregon wine — its appellations, producers, regulations, and landscape. This page covers how to direct a message, what geographic scope the resource addresses, what detail to include so a response is actually useful, and what a realistic timeline looks like.

How to reach this office

The Oregon Wine Authority operates as a reference and editorial resource, not a government agency or winery membership body. That distinction matters more than it might first appear. The Oregon Wine Board — a state-chartered organization funded by assessments on Oregon-grown wine grapes — handles producer memberships, promotional programs, and industry research. The Oregon Liquor and Cannabis Commission (OLCC) handles licensing. This resource handles neither of those things.

What it does handle: detailed questions about Oregon wine regions, varietals, producers, regulations as they're publicly documented, touring, and the growing literature around Oregon's wine identity. Messages can be directed through the contact form attached to this domain. For straightforward editorial questions — a detail missing from a page, a factual correction, a request to cover an overlooked topic — the form is the right path.

For urgent regulatory matters, license applications, or winery compliance questions, the OLCC's licensing division at oregon.gov/olcc is the appropriate destination. Those questions won't be redirected; they simply fall outside the scope of what this resource can usefully address.

Service area covered

Oregon wine country spans roughly 400 miles from the Columbia River Gorge in the north to the Applegate Valley near the California border in the south. The resource covers all of Oregon's American Viticultural Areas, which currently number 23 as recognized by the Alcohol and Tobacco Tax and Trade Bureau (TTB).

That includes the large regional AVAs — Willamette Valley, Rogue Valley, Umpqua Valley, Columbia Gorge, and the Snake River Valley, which Oregon shares with Idaho — as well as the nested sub-appellations like the Dundee Hills, Chehalem Mountains, and Eola-Amity Hills.

Questions about Washington AVAs adjacent to Oregon, or about multi-state appellations like Columbia Valley, are addressed only where they directly intersect with Oregon production. The Columbia Gorge AVA, for instance, straddles both states, and that context is covered in full.

What to include in your message

A vague message produces a vague response or no response at all. The messages that get useful answers share a few qualities.

1. Specificity about the topic. "Tell me about Oregon wine" is a subject roughly 400 pages deep. "The Eola-Amity Hills AVA's elevation range and its effect on Pinot Noir acidity" is a question with a real answer.

2. The context behind the question. Someone researching a winery visit has different needs than a journalist fact-checking a piece or a wine student preparing for a court examination. Knowing which situation applies shapes what gets sent back.

3. A specific page reference, if applicable. If a page on this site contains an error, a gap, or information that's gone stale, naming the page — Oregon wine vintage chart, for instance, or Oregon winery licensing and regulations — accelerates everything.

4. A correction with a source, if that's the reason for reaching out. Factual corrections are genuinely welcomed, and they land far better when paired with a named public source: a TTB ruling, an OLCC regulation, a winery's published estate data, a peer-reviewed viticulture study.

What doesn't need to be included: a long introduction, an explanation of why the topic matters personally, or an apology for asking. Short and specific is a courtesy, not a shortcut.

Response expectations

Volume shapes response time more than intent does. Editorial questions about a specific AVA boundary, a grape varietal's acreage in Oregon, or a regulatory detail typically receive a response within 5 business days. Complex requests — a full topical review, a detailed correction requiring sourcing verification, a request to build out an entirely new topic area — run closer to 10 to 15 business days.

Factual corrections that can be verified quickly are often incorporated into the relevant page before a formal response goes out. That's not silence; it's the correction already working.

A few categories of message receive no response, not out of indifference but because they fall entirely outside scope:

• Winery promotion requests. Coverage decisions are editorial, not commercial.
• Licensing or compliance advice. The OLCC is the right address for anything touching winery licensing in a regulatory sense.
• Direct-to-consumer shipping logistics for specific orders. The Oregon wine direct-to-consumer shipping page covers the regulatory framework; individual shipping issues belong with the carrier or the winery.
• Requests for wine recommendations or ratings. The Oregon wine awards and ratings page documents how those systems work; specific purchasing guidance falls outside editorial scope.

The distinction between those two columns — what gets answered and what doesn't — comes down to whether the question is about Oregon wine as a subject or about a specific commercial transaction within it. The former is exactly what this resource exists for.