Legislative intelligence / 90R
SESSION 2027View project ↗

HB 451: Relating to labeling and representation of imported fish and shellfish.

Session
90th Texas Legislature, Regular Session
Status
Filed
Filed
Nov 9, 2026
Most recent action
11/09/2026 H Filed
Authors
Leo Wilson
Official subjects
Agriculture; Health--General; FOOD; PACKAGING & LABELING REQUIREMENTS; SHRIMPING INDUSTRY; HEALTH & HUMAN SERVICES COMMISSION

AI summary (not official): Requires fish and shellfish sellers to label imported products and bars restaurants from misrepresenting their origin.

Topics: Business regulation. From AI review or caption rules.

Agencies it could affect (possible, not confirmed): Health and Human Services Commission. From AI review or caption rules.

Laws this bill changes

Bill text (Introduced)

90R1262 AB-D

By: Leo Wilson H.B. No. 451

A BILL TO BE ENTITLED

AN ACT

relating to labeling and representation of imported fish and shellfish.

BE IT ENACTED BY THE LEGISLATURE OF THE STATE OF TEXAS:

SECTION 1.

The heading to Section 436.083, Health and Safety Code, is amended to read as follows:

Sec. 436.083. LABELING OF FISH AND SHELLFISH [SHRIMP].

SECTION 2.

Sections 436.083(a), (b), (c), (e), and (g), Health and Safety Code, are amended to read as follows:

(a) For purposes of this section, a fish or shellfish [shrimp] is considered to be imported if the fish or shellfish [shrimp] does not satisfy the United States country of origin requirements for wild or farm-raised fish or shellfish established by 7 C.F.R. Section 60.128, or successor regulations.

(b) A food service supplier, wholesaler, distributor, or wholesale distributor may not sell fish or shellfish [shrimp] in this state unless the fish's or shellfish's [shrimp's] label includes a clear and conspicuous notice stating whether the fish or shellfish [shrimp] is imported.

(c) A restaurant shall not label or represent imported fish or shellfish [shrimp] as "Texas fish or shellfish [shrimp]," "American fish or shellfish [shrimp]," "Domestic fish or shellfish [shrimp]," or "Gulf fish or shellfish [shrimp]."

(e) It is an affirmative defense to the imposition of an administrative penalty under this section that the license or permit holder believed in good faith the fish or shellfish [shrimp] was not imported.

(g) This section does not apply to foods served or prepared in similar retail food establishments, such as grocery stores or other food enterprises located within grocery stores, or properly labeled fish or shellfish [shrimp] packaged by itself or as an ingredient in another packaged food product that is sold packaged.

SECTION 3.

As soon as practicable after the effective date of this Act, the executive commissioner of the Health and Human Services Commission shall adopt rules necessary to implement Section 436.083, Health and Safety Code, as amended by this Act.

SECTION 4.

This Act takes effect September 1, 2027.

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.