Legislative intelligence / 90R
SESSION 2027View project ↗

Alcoholic Beverage Code § 101.67: PRIOR APPROVAL OF MALT BEVERAGES

No bill in the 90th Legislature changes this section yet

Follow this section in Texas Bill Atlas: a bill filed later that changes it shows up as new.

Part of Alcoholic Beverage Code Chapter 101, with every bill that changes it.

Bills are matched to sections automatically from their text and can be missed, for example when a bill changes a whole chapter at once or renumbers sections. No bill listed here does not mean no bill changes this section.

Current law

Sec. 101.67. PRIOR APPROVAL OF MALT BEVERAGES. (a) Before an authorized licensee may ship or cause to be shipped into the state, import into the state, manufacture and offer for sale in the state, or distribute, sell, or store in the state any malt beverages, the licensee must register the malt beverages with the commission. The registration application must include a certificate of label approval issued by the United States Alcohol and Tobacco Tax and Trade Bureau for the product.

(b) Only a brewer's or nonresident brewer's licensee, or a brewpub licensee may apply to register malt beverages with the commission.

(c) This section does not apply to the importation of malt beverages for personal consumption and not for sale.

(d) On registration of a certificate of label approval issued by the United States Alcohol and Tobacco Tax and Trade Bureau, the commission shall approve the product under this section and issue a letter to that effect to the licensee unless the commission determines the product, despite having a valid federal certificate of label approval, would create a public safety concern, create a cross-tier violation, or otherwise violate this code.

(d-1) If the commission approves the product, the commission shall issue a certificate of approval upon receipt of a fee in an amount that is sufficient to cover the cost of administering this section. A copy of the certificate shall be kept on file in the office of the commission.

(e) Not later than the 30th day after the date the commission receives an application for registration of a product under this section, the commission shall either approve or deny the registration application. If the commission denies the application for a product with a valid federal certificate of label approval or fails to act on the application within the time required by this subsection, the licensee submitting the application is entitled to an administrative hearing before the State Office of Administrative Hearings.

(f) The commission by rule shall establish procedures for:

(1) accepting federal certificates of label approval for registration under this section;

(2) registering alcoholic beverage products that are not eligible to receive a certificate of label approval issued by the United States Alcohol and Tobacco Tax and Trade Bureau; and

(3) registering alcoholic beverage products during periods when the United States Alcohol and Tobacco Tax and Trade Bureau has ceased processing applications for a certificate of label approval.

(g) The commission shall consider the nutrition label requirements of the United States Food and Drug Administration and the alcohol label requirements of the United States Alcohol and Tobacco Tax and Trade Bureau in developing the label requirements to register products described by Subsection (f)(2).

(h) The rules adopted under this section may not require testing for alcohol content as part of the process for registering an alcoholic beverage with the commission.

A

The section continues: whole chapter.

Links

Texas Bill Atlas is an independent research tool, not an official state website.

PLEASE READ

Before you use Texas Bill Atlas

An independent, open-source project. This site is not affiliated with, endorsed by, or operated by the Texas Legislature, the Texas Legislative Council, the Secretary of State, or any state agency.

Data may be incomplete, delayed, or wrong. Bill records are copied automatically from the legislature’s public files. Topic, agency, party, influence and last-action tags, and the full-text summaries written by Luna (an AI model), are automated interpretations and can be mistaken.

Not advice. Nothing here is legal, political, or professional advice. The project and its contributors make no warranty of accuracy or completeness and accept no liability for errors, omissions, or decisions made using this site.

Check the official record. Confirm anything that matters on Texas Legislature Online. Spotted a mistake? Report it on GitHub.

TEXAS BILL ATLAS

Privacy Policy

Last updated: November 11, 2026

Texas Bill Atlas is a free, independent, open-source project. We believe you should be able to research legislation without creating an account or providing personal information.

Information we collect

We do not require registration, names, email addresses, or other personal information to use the service.

We do not sell personal information, serve targeted advertising, or intentionally track individual browsing activity.

Analytics and security

We use Cloudflare for website delivery, security, and traffic analytics.

Cloudflare may process technical information such as IP addresses, browser details, request information, and website usage statistics. Cloudflare may also use cookies necessary for security and abuse prevention.

For more information, see Cloudflare's Privacy Policy.

Watchlists and saved preferences

Watchlists and preferences are stored locally in your browser by default.

If you choose to enable watchlist synchronization, we store the selected bill numbers, the member codes of legislators you follow, your saved searches (their names, search words and filters), filters, and hashed access keys on our server. View-only links show the bill numbers only.

No account or personal information is required. Anyone possessing a valid private access link may access the associated watchlist according to that link's permissions.

You can delete a synced watchlist using its edit access key. Inactive synced watchlists are automatically removed after approximately one year.

Technical data

Our servers may temporarily process IP addresses and request information for security, rate limiting, and reliable operation.

We do not use this information to build individual user profiles.

The site also loads certain external resources, including Google Fonts. Those providers may receive ordinary technical request information.

Third-party services

Links to government websites, GitHub, and other external services are governed by their respective privacy policies.

Changes

We may update this policy as the project develops. The current version will be available on this website with its updated date.

Questions

For questions about the project or its privacy practices, visit our GitHub repository.