Buying, Leasing, and Subscribing to Robots

Identify the transaction before negotiating remedies

Chapter 2 governs transactions in goods within its scope. Chapter 2A addresses transactions creating a lease of goods, regardless of form. Its definition of lease concerns a transfer of possession and use for a term in exchange for consideration, excluding the specified sales and security-interest arrangements. A monthly charge alone does not establish which category applies. [1] [2]

A deployment can combine equipment, software, installation, remote operation, and continuing services. Whether and how a mixed agreement falls within a statutory regime requires analysis of its actual promises and governing law. The contract should separate deliverables and responsibilities clearly enough to make that analysis possible. Calling the entire relationship a service should not obscure who possesses the machine or what is being supplied.

The agreement should identify who owns the hardware, controls tasks and safety settings, provides remote assistance, bears downtime costs, and can suspend service.

Define the application and acceptance test

The agreement should state the intended task and operating conditions: payload, environment, route, interfaces, staffing, performance measures, exclusions, and site dependencies. An assertion that a robot handles 500 items per hour is incomplete without identifying the item mix and conditions under which that result is promised.

Recommended acceptance terms identify the test, data, duration, failure criteria, correction period, and person authorized to accept. For a sale governed by Chapter 2, inspection, acceptance, rejection, notice, and revocation have statutory rules. Acceptance can result from specified conduct, not just a signed certificate. Operating the system during a pilot should therefore be addressed expressly in the agreement. [1, §§ 2.513, 2.601 through 2.608]

Payment, acceptance, warranty commencement, and risk transfer should align. The agreement should identify the remedies for a failed test and any limits on them.

Warranties and performance promises

Under Chapter 2, affirmations of fact, descriptions, samples, or models can create express warranties when the statutory requirements are met. Merchantability and fitness for a particular purpose have separate conditions. Section 2.316 addresses exclusion and modification, including the rules for written disclaimers and specified language or circumstances. A statement that all robots are sold as is should not replace review of the actual promises and disclaimer. [1, §§ 2.313 through 2.316]

Chapter 2A contains its own warranty provisions for leases. The lessee should identify the responsible lessor, supplier warranties, and any qualifying finance-lease structure. In a nonconsumer finance lease, Section 2A.407 enforces a lease term making the lessee's promises irrevocable and independent upon acceptance. The Texas provision requires attention to the actual term, not an assumption that every lease automatically has that effect. That consequence deserves attention before assuming a supplier failure permits withholding every payment. [2]

Safety, compatibility, cybersecurity, and regulatory warranties should identify the complete covered system, including integration and later software releases.

Support, updates, and suspension

Recommended service terms allocate preventive maintenance, consumables, repairs, spare parts, remote access, training, and response times. They should distinguish acknowledgment of a fault from restoration of service. A 24-hour response promise can mean only that a ticket is opened unless the contract states otherwise.

Update provisions should identify what may change, the notice and testing process, rollback capability, responsibility for validation, and consequences of postponing an update. The agreement should also address who may place the machine in a safe state or suspend operation during a security or safety event. These are negotiated operating arrangements, not one uniform Texas statutory update procedure.

The commercial allocation cannot be assumed to remove public duties. The customer's applicable OSHA duties, a manufacturer's reporting obligations, or the authorization holder's vehicle duties require their own analysis even when another party has promised to perform supporting work. [3]

Data access, confidentiality, and processing

When a vendor processes personal data for a controller under the TDPSA, the contract must contain the terms listed in Business and Commerce Code § 541.104(b). HB 149 also expanded the processor's duty to assist with security to cover personal data processed by an AI system (Business and Commerce Code § 541.104(a)(2), as amended effective January 1, 2026). [4]

The required terms include processing instructions, purpose, data types, duration, rights and obligations, confidentiality, return or deletion subject to legal retention, compliance information, assessments, and subcontractor commitments. These requirements apply to a covered processing relationship; they should not be described as mandatory terms in every robot contract. [4]

The agreement should separately address customer access to camera feeds, maps, telemetry, maintenance records, software versions, and incident logs. It should state whether information can train models or support unrelated vendor products. Confidentiality, authorized support access, retention, legal holds, and export should cover the systems where copies actually reside. Hardware ownership and a general data ownership clause do not settle all those permissions.

Liability, indemnity, and insurance

Chapter 2 permits contractual remedies and limitations within Section 2.719. It also addresses an exclusive remedy that fails of its essential purpose and limits on consequential-damages exclusions. The limitation's text and the asserted loss matter. A repair-only remedy, service credit, damages cap, and exclusion of lost profits do different work and should be evaluated together. Chapter 2A has separate remedy-limitation provisions. [1] [2]

A recommended risk-allocation schedule identifies product injury, integration error, negligent operation, data exposure, property damage, intellectual-property claims, and failure to preserve evidence. It should state whose conduct is covered, who controls defense and settlement, what notice is required, and how insurance supports the promise. Any attempt to shift a party's own negligence or obligations in a regulated industry requires the additional Texas-law analysis applicable to that clause and transaction.

Texas's statutory manufacturer indemnity for an eligible seller under Section 82.002 remains a separate consideration. Contract labels should not obscure a participant's actual manufacturer or seller role, or the statutory exception for a seller's independently actionable conduct. [5]

Exit and continuity

Recommended exit terms address return or purchase of hardware, removal and site restoration, transition assistance, customer access to required records, data return and deletion, continuing confidentiality, and termination charges. The customer should know whether it retains operating capability and usable records if the supplier discontinues a cloud service or stops supporting the model.

A license, escrow arrangement, offline mode, spare-parts commitment, or transition period can be negotiated when appropriate. None should be assumed merely because the customer paid for the machine. The contract should describe the rights actually granted and the technical dependencies that could defeat continued operation.

Hypothetical subscription failure

A warehouse pays a monthly fee for a picking system. The hardware remains onsite, but the cloud service becomes unavailable and the only stated remedy is a small credit. The contract's value depends on more than hardware ownership: restoration duties, acceptance, warranty, remedy limits, access to logs, and termination or transition rights all matter. Those issues should be resolved in the agreement rather than left to the RaaS label. [1] [2] [4]