Winery Bottling Guide: Quality Control, Records and Traceability

Last verified: August 5, 2026
Primary scope: U.S. commercial winery operations, with technical practices clearly separated from federal requirements
Content mode: Operational Guide

A good winery bottling system proves five things before finished cases are released: the correct wine was packaged, the package components were correct and compatible, the line stayed within defined quality controls, required records were captured, and every finished lot can be traced back to its wine and packaging inputs. The exact technical limits belong to the wine, package, equipment and supplier specifications.

Bottling is not simply the last cellar operation. It is the point where one bulk wine lot becomes hundreds or thousands of individual packages, where an oxygen or closure problem can be multiplied across an entire run, and where production records have to become finished-goods records without breaking the audit trail.

The practical goal is simple: do not start until the wine, package, line and records are ready; do not keep running through an unexplained critical defect; and do not release case goods until the run can be reconciled and traced.

What is required, and what is winery practice?

The first discipline is separating legal requirements from technical controls. A target from a cork supplier, an internal dissolved-oxygen specification and a TTB recordkeeping rule are not the same kind of requirement.

A food-safety nuance worth getting right

Do not summarize FDA rules as either "wine is exempt" or "every winery needs the same preventive-controls program." Under 21 CFR 117.5(i), qualifying alcoholic-beverage facilities are exempt from Part 117 subparts C and G for alcoholic beverages when the regulation's conditions are met. The text does not create a blanket exemption from Part 117 as a whole. Facility facts and state requirements still matter.

That is why this guide treats sanitation, traceability and recall readiness as serious operating controls without mislabeling every best practice as a federal mandate.

The bottling workflow at a glance

Use seven release gates:

1. Release the wine for bottling.
2. Release the package and dry goods.
3. Release the line and work area.
4. Approve first-off packages before normal production.
5. Monitor the run with defined QC checks and hold triggers.
6. Build the bottling and traceability record as the run happens.
7. Reconcile, inspect and release finished case goods.

If any gate fails, stop there. A schedule is not a quality specification.

Gate 1: release the wine for bottling

A wine should enter bottling with a signed release against its actual bottling specification, not against memory or a barrel sample from last week.

University of Minnesota enology guidance and Virginia Tech bottling-quality guidance both treat bottling readiness as a combination of wine chemistry, stability, dissolved gases, temperature, sensory status and packaging preparation. The exact tests and targets depend on the wine.

Pre-bottling wine release checklist

• Confirm the source wine lot ID and exact volume intended for the run.
• Confirm the approved final blend and verify that no unrecorded additions or transfers occurred after the release sample.
• Review the analytical panel required by your wine specification. At minimum, include the parameters that determine legal class/label accuracy and those that control your product's chemical or microbiological stability.
• Confirm relevant stability checks based on wine style and processing history. Protein, tartrate, color and microbiological risk are not identical for every wine.
• Measure dissolved gases that matter to the package and wine style. For still wine, this commonly includes dissolved oxygen and carbon dioxide.
• Confirm bottling temperature is inside the operating range established for the package, filler and closure system.
• Conduct and document a final sensory comparison against an approved reference when your quality program uses one.
• Confirm filtration or other microbiological-stability steps are complete when they are part of the wine's release plan.
• Confirm the alcohol-content result used for tax class and label compliance before bottling.
• Assign a release decision: Released, Hold, or Released with documented condition only if your quality system permits a controlled exception.

Decision point: is the wine truly finished?

If the wine still needs a material adjustment, do it before release, mix it completely, allow the process to reach the condition required by the winery's SOP, then re-sample as appropriate. A post-release addition can invalidate the analytical or stability basis that justified release.

Gate 2: release the package and dry goods

Packaging compatibility is a system question. The bottle, closure, label, capsule, carton, line and wine must work together.

For example, STELVIN documentation describes a closure system built around a specific BVS bottle finish, liner and closure conditions. Amorim cork guidance publishes product-specific corking and equipment recommendations. Those specifications are useful evidence for the products they cover, but they are not universal winery tolerances.

Dry-goods release checklist

For every run, verify the exact bill of materials against purchase, receiving and artwork records:

• bottle supplier, item/SKU, color, capacity and finish;
• bottle manufacturing or supplier lot when available;
• closure supplier, product, dimensions/liner or finish compatibility, and lot;
• front, back, neck or wrap label artwork version and printer lot;
• capsule, wax or other secondary packaging, if used;
• carton/case item and lot or production code when available;
• dividers, trays, pallets and pallet tags where relevant;
• coding consumables and the correct lot-code format;
• current approved label authorization or other documentation appropriate to the wine and market;
• enough accepted material to finish the planned run plus the winery's documented operating allowance.

Quarantine damaged, mixed, obsolete or unverified materials before the line starts. Do not solve an artwork-control problem with operator attention alone.

Decision point: can this bottle and closure be run together?

Release only the exact package combination that has been qualified. Confirm the bottle finish, closure dimensions or liner, application equipment, operating conditions and post-application checks against the current supplier and equipment documentation. If a mobile bottler owns part of this validation, put that responsibility in writing before bottling day.

Gate 3: release the line and work area

The line should move from cleaning to documented readiness, not from "looks clean" to filling.

Line-readiness checklist

• Complete the winery's cleaning and sanitation procedure for every wine-contact surface in scope.
• Verify chemical removal or rinse endpoint when the sanitation chemistry and SOP require it.
• Confirm hoses, gaskets, fittings, filler bowl, filler valves, filters and product path are assembled correctly and visually acceptable.
• Verify filters, integrity tests and sanitary connections where the winery's process requires them.
• Confirm gases are the correct grade, connected, available and regulated for the approved process.
• Verify instruments used for release or QC are calibrated or checked within the winery's required interval.
• Clear the line of labels, closures, cartons, coding data and components from the previous product.
• Load only the approved materials for the current run.
• Confirm the bottling record, QC sheet or digital record is open and prefilled with the run identity.
• Confirm who can start, pause, place on hold, restart and release product.
• Stage identified sample containers and retention-sample locations before the first bottle is filled.

Do not turn sanitation settings into internet folklore

Cleaning chemistry, concentration, contact time, temperature and rinse requirements depend on the product, soil load, material compatibility, equipment and chemical supplier. A bottling guide should require a validated SOP and current chemical/equipment instructions, not publish a single recipe as if it fits every winery.

Gate 4: approve first-off packages

The first acceptable package is the reference for normal production. Do not assume that because each machine runs separately, the assembled package is correct.

Inspect a defined startup sample for:

1. correct wine identity;
2. correct bottle and package configuration;
3. correct label/artwork and orientation;
4. correct lot/date code and legibility;
5. legal net contents/fill compliance plus the winery's package-specific visual fill target;
6. closure application against the approved supplier/equipment specification;
7. leaks, chips, cracks, scuffs or other critical package defects;
8. label adhesion, wrinkles, skew and placement against the approved package standard;
9. capsule or secondary-closure condition, if used;
10. dissolved oxygen/headspace oxygen measurements where those are part of the run specification;
11. sensory/visual condition of the wine after the line when the program calls for it;
12. correct case pack and case code.

Keep the difference between net contents and visual fill height explicit. Federal rules address the amount of wine in the container and, within Part 4's scope, standards of fill and container/headspace conditions. Your filler set point may be expressed as a height, volume, mass or machine parameter. That internal setting must be derived from the actual bottle, wine temperature and packaging system, not copied from another winery.

Gate 5: run the line with defined QC gates

The federal floor for fill checks

27 CFR 24.255(d) requires representative fill testing during each bottling or packing line's operation. The rule does not say that every winery must test every 15, 30 or 60 minutes. Set an internal frequency that is defensible for the line speed, process capability, package risk, startup/changeover behavior and history, while meeting the regulatory requirement.

Increase sampling after a restart, changeover, adjustment, material-lot change or unexplained trend. A frequency that was adequate during stable production may not be adequate immediately after an intervention.

QC control plan

The frequencies in the table are intentionally described by control logic, not a universal clock interval.

Define hold triggers before the run

At minimum, stop or place affected product on quality hold when you cannot prove one of these statements:

• it is the right wine;
• it is in the right authorized package;
• net contents and required legal checks are acceptable;
• the closure/package integrity meets the qualified specification;
• the product can be identified by a valid lot/code;
• the affected interval can be bounded to a last-known-good and next-known-good check;
• a critical contamination, glass or product-integrity concern has been ruled out.

For cosmetic defects, define whether product can continue, be reworked or be downgraded. For critical defects, make the hold automatic. The bottling crew should not have to negotiate severity while the filler is still running.

Control oxygen as a process, not a final number

Bottling can introduce oxygen even when the bulk wine was prepared carefully. Research and technical guidance from OENO One, Penn State Extension and the Australian Wine Research Institute all support treating oxygen exposure during packaging as a quality variable.

The right target is not one number for every wine. White, rosé and red wines can have different oxygen sensitivity and shelf-life objectives. Closure oxygen transmission, sulfur dioxide strategy, wine composition, temperature, filler design, bottle purge and headspace treatment all affect the package.

Measure where the process can change

If oxygen control is material to the wine, define measurement points such as:

• bottling tank before the run;
• after any transfer, pump or final filtration step;
• filler inlet or bowl when practical;
• freshly filled wine for dissolved oxygen;
• sealed package for headspace oxygen/total package oxygen using an appropriate method;
• after a restart, gas-pressure change, filler intervention or unexplained jump.

A single end-of-run result tells you whether that sample was high or low. Multiple process-point measurements help tell you where oxygen entered, which is what the crew needs to fix.

Oxygen troubleshooting

Do not correct an oxygen problem by blindly adding more sulfur dioxide. Diagnose the oxygen source, then make wine adjustments only through the winemaker's controlled release process.

Gate 6: build the bottling record while the run is happening

For covered U.S. bonded wine premises, 27 CFR 24.308 is the core federal bottling record rule. It requires, among other items, bottled/packed activity by tax class, identification of the label used, and the required fill and alcohol test results.

27 CFR 24.300(b) generally requires operations or transactions to be entered when they occur. If another record is posted from source or auxiliary records prepared when the event occurs, that posting may be deferred only to the close of the third succeeding business day. Those source records must be retained.

Recommended bottling-run record fields

The table below deliberately separates the federal core from operational fields that make the record useful for QC, inventory and recall response.

Record retention

27 CFR 24.300(d) requires prescribed returns, reports, records and source records to be retained for at least three years from the record date or the last required entry, whichever is later. TTB may require retention for up to three additional years in a case where it determines that is necessary.

That is a federal baseline for the Part 24 records it covers. Do not automatically use three years as the retention period for every quality, insurance, customer, tax or state record in the winery.

Create the traceability handoff

TTB's label-information rule and an operational traceability system solve related but different problems.

27 CFR 24.314 requires label information such as varietal, vintage or appellation, when used, to be supported by a complete and accurate record trail from the beginning source material through removal for consumption or sale.

For operational traceability, GS1's Global Traceability Standard provides a useful model: identify traceable objects, record important tracking events, and capture the key data that explains what happened, when, where and why. GS1 is a voluntary standard unless a regulation, contract or trading partner makes a particular implementation mandatory.

The bottling genealogy should be queryable in both directions

Trace backward: finished case lot -> bottling run -> source wine lot -> blend/production history and label-claim evidence.

Trace forward: source wine lot or packaging-material lot -> bottling run(s) -> finished case/pallet lots -> warehouse locations -> shipments/customers where records permit.

This is the core connection between bottling, inventory and recall preparedness.

Designing a useful finished-goods lot code

A good lot code is unique enough to bound a quality event without becoming impossible to operate. The code should resolve in your system to the bottling run, not attempt to contain every fact in the printed characters.

Possible lot boundaries include:

• one wine + one bottling date;
• one wine + one line/shift;
• one wine + one run segment separated by a material-lot change or significant intervention.

If a closure or glass lot changes mid-run and that distinction matters to root-cause analysis, record the exact time/case boundary even if the consumer-facing lot code does not change. The data system can preserve more resolution than the printed code.

Gate 7: reconcile, inspect and release finished case goods

Do not close the run when the last bottle enters a case. Close it when wine, materials, records and finished goods agree closely enough that remaining variance is understood and documented.

Wine-volume reconciliation

Use a physical equation:

Starting releasable wine = packaged wine + recorded samples/breakage/dumps/rework + measured recoverable residual + documented process loss + unexplained variance

The exact categories can match the winery's operation, but unexplained variance should stay visible. Do not bury it inside a generic "loss" number merely to make the worksheet balance.

This reconciliation feeds several systems without collapsing them into one:

• production: closes the source lot or establishes its remaining balance;
• TTB records: supports the bottled-wine transaction trail and later operational reporting;
• finished-goods inventory: establishes cases/bottles available, on hold or released;
• COGS: provides actual bottling yield, material consumption and loss inputs to the winery's chosen accounting policy;
• traceability: connects the run to every output lot and material lot.

For federal reporting mechanics after bottling, use Solera's dedicated TTB Form 5120.17 line-by-line guide rather than treating this operations guide as a filing instruction.

Dry-goods reconciliation

For controlled materials, record:

• quantity issued to the run;
• quantity used in accepted finished goods;
• documented startup waste and quality rejects;
• damaged material;
• returned unopened/usable stock;
• obsolete or destroyed printed material;
• unexplained variance.

Printed labels deserve especially tight control because a material mix-up can become a legal and traceability problem, not just a purchasing variance.

Post-bottling release checklist

• Confirm all QC holds have a physical and digital boundary.
• Confirm accepted case quantity agrees with the finished-goods receipt.
• Confirm finished-goods lot and case codes are legible and resolve to the correct run.
• Confirm retained samples are identified and stored according to the winery's program.
• Review required fill/alcohol records and ensure all mandatory bottling entries are complete.
• Review packaging-material lot links.
• Confirm deviations have owners and dispositions.
• Perform any scheduled post-bottling analytical, package or sensory checks required by the wine's release plan.
• Change status from QC Hold to Released only with the required approval.
• Run a traceability spot check: choose one finished case and prove you can reach its source wine lot and packaging lots.

Mobile bottling: define the handoff before the truck arrives

Mobile bottling adds an organizational boundary to an already sensitive operation. The winery still needs one controlled record of the run even if the contractor supplies the filler, closure equipment, operators or QC instruments.

Before bottling day, document who owns each item:

Replace "usually" with named responsibilities in the actual service agreement and run plan. Mobile bottlers differ, and equipment-specific utility, pressure, gas, label-roll and package specifications must come from the contracted provider.

Troubleshooting: when the run starts drifting

How bottling should connect to the rest of winery operations

A bottling run is a data transformation, not a dead end.

Production lots

The run consumes a specific released bulk-wine lot or defined blend. If multiple source lots feed one finished SKU, preserve the genealogy rather than replacing the source identity with the SKU name.

Compliance records

The run creates the facts needed for bottled/packed wine records, fill-test evidence, label identification, operational reporting and label-claim substantiation. Compliance should be a view of real production records, not a second set of numbers typed later.

Finished-goods inventory

Accepted output becomes finished case goods with a SKU plus a bottling/finished-goods lot identity and disposition. On hand is not the same as released for sale if QC hold status exists.

COGS

Actual packaged yield, dry-goods consumption, bottling labor and documented loss can feed lot costing. The accounting treatment is a separate management, financial and tax question. This bottling guide does not turn one costing convention into a legal rule.

Traceability

The bottling record is the bridge between bulk-wine genealogy and case-goods genealogy. If the bridge loses the source lot, packaging lots, output lot or time boundary, a later quality investigation becomes broader and more expensive than it needs to be.

Frequently asked questions

What records does TTB require when a winery bottles wine?

For covered U.S. proprietors, 27 CFR 24.308 requires a bottled or packed wine record by tax class with specified activity, label identification, and the fill and alcohol test information required by 27 CFR 24.255. Related Part 24 rules govern when entries are made, retention, and records supporting label information. Verify applicability to your premises and operation.

How often must a winery check fill during bottling?

Federal 27 CFR 24.255(d) requires testing at representative intervals during each bottling or packing line's operation. It does not prescribe one universal time interval. Your internal sampling frequency should meet that requirement and respond to process risk, changes, interventions and line capability.

Is fill height the same as legal fill volume?

No. Legal requirements address net contents and, within the applicable Part 4 rules, standards of fill and container/headspace conditions. A winery may use a fill-height target as a practical way to control its filler, but that target depends on the actual bottle, temperature and package system.

What should a winery lot code identify?

At minimum, the code should resolve reliably to a specific finished-goods lot and bottling run. The underlying record should connect that run to the source wine lot, packaging component lots, date/time or shift, QC disposition, quantity and downstream case/pallet movements. The visible code does not need to encode every field.

Should every winery use the same dissolved-oxygen target?

No. Oxygen should be controlled and measured, but the appropriate target depends on wine style, composition, shelf-life objective, sulfur dioxide strategy, closure and bottling system. Use current enology guidance and a validated winery specification rather than copying another producer's number.

Does a winery have to run a mock recall?

This guide treats mock trace/recall exercises as a strong traceability best practice, not a universal federal winery mandate. Legal duties vary with facility status, product, jurisdiction and event. The operational test is still valuable: can you quickly identify affected lot quantities, locations and downstream recipients from your actual records?

How long should bottling records be kept?

For records prescribed by 27 CFR Part 24, the federal baseline in 24.300(d) is at least three years from the record date or the last required entry, whichever is later, with authority for TTB to require up to three additional years in a case where it determines that is necessary. Other record types can have different retention rules.

What changes when using a mobile bottler?

The equipment and operator boundary changes, but the winery still needs a single traceable run record. Before the service date, define responsibility for wine release, sanitation documentation, package compatibility, utilities, QC tests, legal record data, lot coding, run reconciliation and final product release.

The operating principle

The best bottling record is not the form someone finishes the next morning. It is the record created by the operation itself: the released wine lot, the actual packaging lots, the first-off approval, the QC checks, the interventions, the finished lot, and the reconciliation all connected while the evidence is still in front of the crew.

That is also the natural place for winery software to help. Solera is built around connected winery operations from vine to bottle to doorstep. See the current Solera features for capabilities that are live today.

Official sources and technical references

1. 27 CFR 24.255, Bottling or packing wine, Electronic Code of Federal Regulations, accessed August 5, 2026.
2. 27 CFR 24.308, Bottled or packed wine record, Electronic Code of Federal Regulations, accessed August 5, 2026.
3. 27 CFR 24.300, General, Electronic Code of Federal Regulations, accessed August 5, 2026.
4. 27 CFR Part 24, Subpart O, including 24.314 Label information record, Electronic Code of Federal Regulations, accessed August 5, 2026.
5. 27 CFR Part 4, Subpart H, Standards of Fill for Wine, Electronic Code of Federal Regulations, accessed August 5, 2026.
6. 2024 Boot Camp for Wine Records, Alcohol and Tobacco Tax and Trade Bureau.
7. 21 CFR 117.5, Exemptions, Electronic Code of Federal Regulations, accessed August 5, 2026.
8. Practical Preparation Techniques For Wine Bottling, University of Minnesota Grape Breeding and Enology, accessed August 5, 2026.
9. Wine Storage and Bottling Quality Control, Virginia Tech Enology, accessed August 5, 2026.
10. A review on understanding oxygen mass transfer in wine, OENO One, 2025.
11. Gas adjustment, Australian Wine Research Institute, accessed August 5, 2026.
12. Oxygen Management During Wine Production and Bottling, Penn State Extension, accessed August 5, 2026.
13. GS1 Global Traceability Standard, GS1, accessed August 5, 2026.
14. STELVIN Closure System, Amcor, accessed August 5, 2026.
15. Twin Top Cork Stoppers, Amorim Cork, accessed August 5, 2026.

Disclaimer

This guide summarizes official and technical information available as of August 5, 2026. Federal requirements depend on the wine, activity and premises; state and local rules can add obligations. Technical specifications depend on the wine, package, equipment and suppliers. Confirm material compliance decisions with the responsible authority or a qualified adviser, and follow current manufacturer instructions for the exact packaging system in use.

Version history

• 1.0.0, August 5, 2026: Initial publication package. Federal bottling-record, fill-test, record-timing/retention and label-information claims verified against current eCFR and TTB sources. Technical guidance cross-checked against university, peer-reviewed, AWRI, GS1 and manufacturer sources.