Legislative intelligence / 90R
SESSION 2027View project ↗

Transportation Code § 285.001: REGULATION OF ROADSIDE VENDOR AND SOLICITOR

3 bills in the 90th Legislature would change this section

Part of Transportation Code Chapter 285, 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. 285.001. REGULATION OF ROADSIDE VENDOR AND SOLICITOR. (a) To promote the public safety, the commissioners court of a county with a population of more than 1.3 million and a county with a population of more than 600,000 that is adjacent to a county with a population of more than four million by order may regulate the following in the unincorporated area of the county if they occur on a public highway or road, in the right-of-way of a public highway or road, or in a parking lot:

(1) the sale of items by a vendor of food or merchandise, including live animals;

(2) the erection, maintenance, or placement of a structure by a vendor of food or merchandise, including live animals; and

(3) the solicitation of money.

(b) The commissioners court of a county with a population of more than 200,000 that borders the United Mexican States by order may regulate the following activities in the unincorporated areas of the county, provided that the activities occur in a parking lot or on or in the right-of-way of a public highway or road:

(1) the sale of items and the erection, maintenance, or placement of a structure by a vendor of live animals; and

(2) the solicitation of money.

(c) A county regulating vendors under Subsection (b):

(1) may require that a vendor be located not closer to the edge of the public highway or road than a distance that is equal to one-half the width of the right-of-way adjacent to the highway or road; and

(2) may not adopt an order under Subsection (b) prohibiting the sale of livestock.

Acts 1995, 74th Leg., ch. 165, Sec. 1, eff. Sept. 1, 1995. Amended by Acts 2001, 77th Leg., ch. 669, Sec. 132, eff. Sept. 1, 2001.

Amended by:

Acts 2007, 80th Leg., R.S., Ch. 493 (S.B. 254), Sec. 1, eff. September 1, 2007.

Acts 2013, 83rd Leg., R.S., Ch. 340 (H.B. 2094), Sec. 1, eff. June 14, 2013.

Acts 2023, 88th Leg., R.S., Ch. 644 (H.B. 4559), Sec. 243, eff. September 1, 2023.

Acts 2025, 89th Leg., R.S., Ch. 730 (H.B. 2012), Sec. 1, eff. September 1, 2025.

Acts 2025, 89th Leg., R.S., Ch. 892 (H.B. 2731), Sec. 1, eff. September 1, 2025.

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.