Sharing Vineyard Spray Logs with Winery Buyers: What They Require and How to Deliver
Winery buyers are asking for more documentation than they did five years ago. In Napa Valley, roughly 80% of wineries now require pesticide record disclosure from fruit suppliers before finalizing contracts. That trend is spreading to Sonoma, Oregon, and other premium wine regions as buyers respond to consumer demand for transparency about how grapes are grown.
If you're selling fruit to a winery, there's a real chance your buyer is going to ask for your spray records at some point. Being prepared to deliver them quickly, in a usable format, with the right data, is increasingly a competitive advantage for vineyard operators.
TL;DR
- In Napa Valley, roughly 80% of wineries now require pesticide record disclosure from fruit suppliers before finalizing contracts -- the trend is spreading to Sonoma, Oregon, and other premium regions
- Buyers want block-level spray history for contracted blocks, PHI compliance confirmation, restricted-use material disclosure, and certifier-compatible records for certified programs -- all in a clean, readable format
- A documented PHI violation on contracted blocks can trigger contract penalties or fruit rejection -- not just a compliance issue, a commercial one
- Sharing records via paper binders takes hours and creates organization errors; VitiScribe's buyer portal generates a time-limited, read-only link scoped to specific blocks and date ranges in under a minute
- Buyer portal links expire after 30 days and cover only the blocks and dates you specify -- you're not sharing access to your full account, only the records relevant to the contract
- If a buyer uses your records to support a marketing claim (organic, sustainable, low-spray), the records must actually support that claim; sharing records containing products inconsistent with a certification program creates a separate liability
What Winery Buyers Actually Want to See
The ask varies by buyer, but the core elements are consistent:
Full spray history by block: What products were applied, when, and at what rate. Buyers want to see the complete record for the blocks producing their contracted fruit, typically for the current season and often going back 1-3 years.
PHI compliance confirmation: Buyers want confidence that no product was applied within its pre-harvest interval on the contracted blocks. A single documented PHI violation can trigger contract penalties or fruit rejection.
Restricted-use material disclosure: Some buyers specifically want to know whether any restricted-use pesticides were applied, particularly organophosphates or synthetic pyrethroids, for their own quality standards or customer-facing labeling programs.
Certifier-compatible records for certified programs: If you're selling to a buyer who uses your fruit in a certified organic, sustainable winegrowing, or other certification-based program, they need records that support their own compliance documentation.
For the full compliance record structure that winery buyers and certifiers review, see the spray log compliance verification guide.
The Delivery Problem
Most vineyard operators can answer the question "did you follow PHI?" accurately. The problem is proving it on demand.
Paper spray logs mean pulling out binders, photocopying pages, and physically delivering or mailing records. That process takes hours and creates the opportunity for gaps or organization errors that look suspicious even when the underlying practice was compliant.
Spreadsheets are faster to share, but the formatting is inconsistent and buyers receive spreadsheets that require interpretation, reformatting, and validation before they're useful.
The buyer-ready format most wineries actually want is a clean, printed or PDF report showing block, date, product, rate, PHI, and clearance status. A document that reads like a compliance attestation rather than a data dump.
What a Buyer-Ready Spray Report Includes
A properly formatted spray log report for winery buyer review should include:
- Header: Grower name, operation name, vineyard address, reporting period
- Block identification: Block name, acreage, variety, vintage year
- Application records: Date, product name and EPA reg number, active ingredient, rate, volume applied, applicator
- PHI summary: For each product applied in the pre-harvest period, the PHI in days and the confirmed clearance date relative to actual harvest date
- Applicator license confirmation: License number and type for each applicator on record
- Certifier eligibility notation: Where applicable, notation that materials used are OMRI-listed or otherwise certifier-eligible
This format takes a buyer's compliance team 5-10 minutes to review rather than 5-10 hours.
Protecting Confidential Information in Shared Records
A legitimate concern when sharing spray records with buyers: how much do you have to reveal?
You're required to share what your contract and any buyer agreement specifies. You're not required to share proprietary program information beyond the contractual scope. For most grower-winery relationships, the buyer wants block-level spray history for the contracted blocks in the contracted vintage, not your entire operation's records.
VitiScribe's block spray history report generates reports scoped to specific blocks and date ranges. Buyer portal links expire after 30 days and include only the blocks and date ranges you specify. You're not handing over a login to your full account, you're sharing a time-limited, scope-limited view of specific records.
That's the appropriate level of access for most buyer relationships.
Legal Considerations When Sharing Records
Sharing spray records with a winery buyer doesn't inherently create legal liability beyond what already exists. Your records either confirm compliance or they don't, and that compliance status exists regardless of whether you share the records.
The question growers sometimes ask is whether sharing records opens them up to scrutiny they might otherwise avoid. The practical answer is that in most fruit purchase contracts today, record sharing is contractually required, so the choice isn't really whether to share but whether you'll be organized enough to share efficiently.
One nuance worth noting: if you're sharing records with a buyer who then uses them as part of a marketing claim (organic, sustainable, low-spray), you want to make sure the records you share actually support that claim. Sharing records that contain products inconsistent with a certification program's requirements creates a different kind of problem.
The vineyard spray log software page covers the full range of VitiScribe's sharing and reporting capabilities.
Setting Up Buyer Reporting in VitiScribe
The workflow in VitiScribe for buyer record sharing:
- Select the blocks and date range covered by the buyer's contract
- Generate a buyer-ready spray report (PDF or shareable link)
- Review the report for completeness and PHI compliance confirmation
- Share via the buyer portal link or export for delivery
The buyer portal link expires in 30 days automatically. The report is read-only. No login is required on the buyer's side.
If your buyer needs a specific format, such as their own template or a specific field arrangement, VitiScribe's export formats can be configured to match buyer requirements for growers with multiple buyer relationships.
Frequently Asked Questions
How do I share my spray records with a winery buyer?
The cleanest approach is generating a buyer-ready PDF report scoped to the contracted blocks and the relevant date range, including a PHI compliance summary. VitiScribe generates this report with one click and provides a time-limited sharing link that gives the buyer read-only access without requiring them to access your full account.
What format do winery buyers want for pesticide record review?
Most winery compliance teams want a PDF or printed document showing block-level spray history with product names, EPA registration numbers, application dates and rates, applicator information, and PHI compliance confirmation. Clean formatted reports are processed faster than raw spreadsheets or paper copies.
Does sharing spray records with a buyer create any legal obligations?
Sharing spray records with a winery buyer doesn't create legal obligations beyond whatever your fruit purchase contract already specifies. Most modern fruit purchase agreements explicitly require pesticide record disclosure, so the sharing obligation already exists contractually. What sharing does is satisfy that obligation and document compliance, which protects you as much as it informs the buyer.
A winery buyer is requesting spray records going back three years as a condition of a new contract. Some of those records are from a period when the vineyard used a different management company. How should the grower respond?
The grower's obligation is to produce whatever records exist for those blocks during that period. Records held by the prior management company should be requested and obtained if possible -- many management contracts specify that records remain the property of the vineyard owner rather than the management company, but this varies. If prior-period records are incomplete or unavailable, the grower should disclose that to the buyer rather than presenting a partial record set as complete. Most buyers distinguish between an operation that has gaps from a prior management period and one that has current-season compliance problems; being transparent about the gap and demonstrating that current-season records are complete and organized is the stronger position than attempting to patch or reconstruct records that don't exist. VitiScribe's onboarding includes a historical record import workflow for operations taking over from prior management.
When a buyer's contract requires "pesticide-free" fruit from specific blocks but the grower's adjacent blocks received conventional applications, what documentation satisfies the buyer's requirement that the designated blocks received no prohibited materials?
The records for the designated "pesticide-free" blocks should show no pesticide applications during the covered period -- the absence of application records is itself the documentation. The companion documentation that strengthens this position is the spray records for adjacent blocks confirming that application direction, wind conditions, and buffer distance between the treated and untreated blocks were managed to prevent drift. If the winery's "pesticide-free" standard extends to residue testing, the test results accompany the record documentation. VitiScribe's block-scoped report generation produces a clean, verifiable record for designated blocks only, without exposing the adjacent blocks' application history unless the buyer specifically requires that context.
What is Sharing Vineyard Spray Logs with Winery Buyers: What They Require and How to Deliver?
[FAQ_ANSWER_PLACEHOLDER: This answer needs to be generated by AI with specific data, examples, and actionable advice relevant to Sharing Vineyard Spray Logs with Winery Buyers: What They Require and How to Deliver. Target 50-150 words.]
How much does Sharing Vineyard Spray Logs with Winery Buyers: What They Require and How to Deliver cost?
[FAQ_ANSWER_PLACEHOLDER: This answer needs to be generated by AI with specific data, examples, and actionable advice relevant to Sharing Vineyard Spray Logs with Winery Buyers: What They Require and How to Deliver. Target 50-150 words.]
How does Sharing Vineyard Spray Logs with Winery Buyers: What They Require and How to Deliver work?
[FAQ_ANSWER_PLACEHOLDER: This answer needs to be generated by AI with specific data, examples, and actionable advice relevant to Sharing Vineyard Spray Logs with Winery Buyers: What They Require and How to Deliver. Target 50-150 words.]
What are the benefits of Sharing Vineyard Spray Logs with Winery Buyers: What They Require and How to Deliver?
[FAQ_ANSWER_PLACEHOLDER: This answer needs to be generated by AI with specific data, examples, and actionable advice relevant to Sharing Vineyard Spray Logs with Winery Buyers: What They Require and How to Deliver. Target 50-150 words.]
Who needs Sharing Vineyard Spray Logs with Winery Buyers: What They Require and How to Deliver?
[FAQ_ANSWER_PLACEHOLDER: This answer needs to be generated by AI with specific data, examples, and actionable advice relevant to Sharing Vineyard Spray Logs with Winery Buyers: What They Require and How to Deliver. Target 50-150 words.]
How long does Sharing Vineyard Spray Logs with Winery Buyers: What They Require and How to Deliver take?
[FAQ_ANSWER_PLACEHOLDER: This answer needs to be generated by AI with specific data, examples, and actionable advice relevant to Sharing Vineyard Spray Logs with Winery Buyers: What They Require and How to Deliver. Target 50-150 words.]
Related Articles
Sources
- Wine Institute
- Napa Valley Vintners
- California Department of Pesticide Regulation (CDPR)
- Oregon Department of Agriculture (ODA)
- UC Cooperative Extension Viticulture
Get Started with VitiScribe
With 80% of Napa wineries and a growing share of Oregon and Sonoma buyers requiring pesticide record disclosure before finalizing fruit contracts, having spray records that can be shared quickly, in a clean format, with PHI compliance confirmed, has moved from a nice-to-have to a contracting requirement. VitiScribe generates buyer-ready spray reports scoped to specific blocks and date ranges in under a minute, delivers them via time-limited read-only links that expire automatically, and includes PHI compliance confirmation in every buyer report. Try VitiScribe free and generate your first buyer-ready spray report today.
