Skip to contentErgasa
Robotics & automation

Hotel robot liability: software updates and evidence

Hotel robot liability after the December 2026 transition: software updates, evidence, commercial losses and procurement contract controls.

Dimitris AthanassiadisPublished

Before signing a connected-robot order, separate the hotel’s commercial recovery rights from an injured person’s product-liability claim. Hotel robot liability depends on the claimant, the damage, the supply history and who controlled the software. A promise to keep the robot updated does not answer who pays when service stops or a guest is injured. The new EU regime protects natural persons; it is not a general reimbursement scheme for a hotel’s failed investment.[1]

This analysis is prepared on 11 November 2026 for procurement and finance teams planning deployment across the December transition. Its recommendations are proposed purchasing controls, not findings about any manufacturer or hotel. No Greek implementing measure has been verified for this article. Greek counsel should confirm the applicable national legislation, remedies and procedural rules before a contract or claim relies on them.

Hotel robot liability starts with the supply history

Directive (EU) 2024/2853 applies to products placed on the market or put into service after 8 December 2026. Article 22 sets 9 December 2026 as the national transposition deadline; Article 21 preserves the previous regime for products placed on the market or put into service before that date. The relevant starting point is the product’s EU supply history, not simply the invoice date at the hotel.[1]

The wording matters. The May 2026 corrigendum changed Article 2(1) from “after 9 December 2026” to “after 8 December 2026”. Accordingly, the new scope starts on 9 December, subject to national implementation. Procurement documents copied from older summaries may contain the uncorrected formulation. Use the corrected legal text when allocating a December delivery to a regime.[3]

Ask the supplier for evidence of first making available in the EU, the identity of the unit and any earlier commissioning. Article 4 defines placing on the market as the first making available on the Union market. Putting into service concerns first commercial use where the product has not previously been placed on the market. A hotel acceptance certificate alone may not establish either event.[1]

Keep separate records for an existing robot, a later software supply and a substantial modification. Do not assume that every routine patch moves an older machine into the new regime. That conclusion needs assessment of what product or modification was supplied, when and under whose control. The earlier Directive 85/374/EEC remains relevant to the transition; replacing its label in a contract does not resolve the underlying facts.[8]

Separate guest injury from the hotel’s trading losses

Articles 5 and 6 give natural persons rights for specified damage. These include death or personal injury, including medically recognised psychological harm, certain property damage, and destruction or corruption of non-professional data. They exclude the defective product itself, a product damaged by a defective component integrated within the manufacturer’s control, and property used exclusively for professional purposes.[1]

A guest injured by a robot and a hotel seeking replacement of that robot present different questions. The Commission explicitly notes that the directive does not cover situations where the victim is a company. Therefore, do not book a presumed statutory recovery for robot replacement, hotel fixtures used exclusively for business, lost room revenue or corrupted business records merely because software caused the event.[5]

Those exclusions do not establish that the hotel has no remedy. Article 2(4) preserves specified national contractual and other non-contractual routes, and Article 6(3) leaves other liability regimes unaffected. Have counsel assess the sale, lease, support agreement and relevant national law. Treat the commercial contract as a separate workstream rather than describing the directive as a business warranty.[1]

Illustrative event Question to assess Procurement evidence to request
A guest suffers bodily injury Defect, damage, causation and applicable regime Version history, incident logs and operator identity
The robot stops working after an update Repair, replacement and contractual remedies Acceptance baseline, update terms and recovery procedure
Hotel-only furniture is damaged Business-property exclusions and other legal routes Ownership, use, photographs and contract coverage
Operational data becomes unusable Contract, backup arrangements and other applicable law Export format, restore tests and provider responsibilities

The table is a triage tool, not a prediction of compensation. Mixed-use property, employee claims, insurer subrogation and multiple defendants require individual review. The physical location of an incident inside a hotel does not by itself determine the claimant’s rights.

Identify who controls updates and connected services

Article 4 expressly includes software in the definition of product. A related service is a digital service integrated or interconnected so that its absence prevents one or more product functions. Manufacturer control includes authorised integration or modification and the ability to supply software updates, including through a third party. The relevant boundary is therefore broader than who owns the robot’s metal enclosure.[1]

Under Article 11(2), the defence that a defect arose only after supply is unavailable for listed causes within manufacturer control. These include software updates, related services and missing updates necessary to maintain safety. This is a rule about liability and a particular defence. It does not mean every outage establishes a safety defect, or that every supplier owes unlimited feature development.[1]

Defectiveness is assessed by the safety a person is entitled to expect or that law requires, considering the circumstances in Article 7. A newer or better version alone does not make the previous product defective. The EUR-Lex summary explains the extension to software and controlled updates, but the detailed legal conditions remain in the directive.[2]

Before purchase, ask who can change speed limits, obstacle handling, maps and lift interfaces; who approves each change; and what remains possible without the cloud service. Request a demonstration of evidence export before enabling remote support. These are recommended acceptance checks, not a claim that the directive prescribes this exact test script.

Do not merge liability with cybersecurity conformity. The Cyber Resilience Act, recital 31 describes the two instruments as complementary and distinguishes liability from obligations concerning security updates. Scope, application dates and product-specific duties need their own assessment. Ergasa’s connected-robot procurement analysis provides a separate contract-review frame.[4]

Name the legal operators and control modifications

Article 8 addresses the manufacturer and relevant component manufacturers. For a non-EU manufacturer, it also identifies the importer and authorised representative, with a fulfilment service provider in the absence of an EU importer or authorised representative. Distributor liability has additional conditions, including a request to identify an appropriate operator or its supplier and failure to do so within one month.[1]

Collect legal names and addresses rather than a sales contact’s messaging account. The entity issuing the invoice, the software developer and the EU importer may differ. Ask each party to confirm its actual role in writing. A contractual description helps establish the parties’ account of the supply chain but cannot conclusively override the legal definition.

A person who substantially modifies a product outside manufacturer control and then makes it available or puts it into service is treated as a manufacturer under Article 8(2). Article 4 sets the definition, referring first to relevant product-safety rules and otherwise to specified performance and risk changes. Do not describe every map edit or integration as automatically substantial.[1]

The Machinery Regulation separately establishes machinery health-and-safety and market-access requirements. Keep that conformity assessment distinct from this compensation analysis. Ergasa’s CE document audit can structure the identity and documentation review, but neither a CE logo nor this article certifies an installation.[6]

Preserve evidence without retaining unnecessary personal data

Article 9 provides court-supervised disclosure of relevant evidence, subject to plausibility, necessity, proportionality and confidentiality safeguards. Article 10 normally requires proof of defect, damage and causation, while introducing rebuttable presumptions in specified circumstances. A claimant does not receive an automatic win because a robot uses complex software.[1]

Set up a proposed evidence register containing serial number, firmware and application versions, configuration baseline, update timestamps, release notes and support tickets. Record which party authorised remote changes. Preserve the original export and document who copied it. A hash can help compare files later, but it cannot prove that a sensor was accurate or that a supplier caused an incident.

If an incident occurs, protect people first and follow the assessed shutdown procedure. Then record the scene, device identity, relevant operating conditions and changes already made. Ask suppliers to preserve relevant logs before routine rotation. Avoid wiping or repeatedly restarting equipment merely to reproduce a fault before a competent person considers safety and evidence preservation.

Evidence management is not permission to retain all camera footage indefinitely. GDPR Articles 5 and 6 require data minimisation, storage limitation and a lawful basis for personal-data processing. Agree a proportionate retention policy with privacy and legal advisers, distinguish routine logs from a justified incident hold, restrict access and document release of the hold.[7]

Price support and contractual recovery as separate costs

Ask for a support end date, covered versions, urgent safety escalation, planned change notices and a documented recovery method. Negotiate whether the supplier pays for diagnosis, travel, replacement hardware, rollback work and temporary service substitution. Confirm that a rollback would remain safe; returning to vulnerable software is not a satisfactory contractual cure merely because it restores an earlier function.

For internal budgeting, use this illustrative structure without assuming any savings: total cash exposure equals purchase and integration payments, support subscriptions, evidence storage and administration, expected recovery work, and any temporary substitute service. Show potential supplier reimbursements separately until the contract and counterparty’s ability to pay support them. Do not net a speculative legal award against committed spending.

Request priced alternatives for an export capability, extended support and a replacement unit. Compare the actual offers rather than inserting an invented failure rate or downtime cost. Ask the broker to explain relevant liability, cyber, property and interruption coverage, exclusions and notification conditions in writing. Insurance availability and response have not been verified here.

Article 15 prevents contractual limitation or exclusion of liability under the directive in relation to the injured person. That rule is not a substitute for reviewing the hotel’s own commercial limitation clauses. Counsel should examine indemnities, recourse and enforceability separately; a supplier’s cap cannot simply be assumed to govern a guest’s statutory claim.[1]

Use a release checklist before acceptance

  1. Document the unit’s first EU supply history and ask counsel to identify the applicable transition rules.
  2. Name the manufacturer, software and service providers, importer and contracting seller, with evidence of each role.
  3. Attach the accepted version and configuration baseline to the procurement record.
  4. Test update notices, authorisation controls, safe recovery and export of relevant evidence before final acceptance.
  5. Separate natural-person injury exposure from robot repair, business property, data and interruption remedies.
  6. Record support pricing, end-of-support treatment, insurance questions and unresolved exclusions.
  7. Assign incident, privacy and legal owners; do not approve deployment with an unidentified safety-critical dependency.

This checklist is a proposed management control. It does not certify conformity or guarantee recovery. Under Articles 16 and 17, the directive distinguishes a three-year awareness-based limitation period from a ten-year expiry period, with a specific twenty-five-year exception for latent personal injury. Those periods are not a universal data-retention schedule; get advice on each record category and applicable claim.[1]

For hotel robot liability planning, the next purchasing step is to request a versioned support-and-evidence annex before agreeing final payment. Leave each unanswered item visible, name its owner and decide whether it blocks acceptance. A discounted unit with unclear update control should not silently inherit a financial assumption that the law will recover every operating loss.

Questions from procurement and finance teams

Does the new directive compensate a hotel company for lost bookings?

It does not create a general company-loss remedy. Its protected claimants and damage categories are defined in Articles 5 and 6; contractual and other national routes need separate assessment.[1]

Does a December hotel invoice determine the regime?

No. Establish the legally relevant placing on the market or putting into service, including earlier EU supply. The corrected Article 2 uses after 8 December 2026.[3]

Does every update failure prove a defective product?

No. Safety defectiveness, covered damage and causation remain central. Article 11(2) limits a particular defence for listed causes within manufacturer control; it does not make every service failure compensable.[1]

Should the hotel keep all video for twenty-five years?

No blanket period follows from this analysis. Liability expiry rules and personal-data retention serve different purposes. Apply a justified, proportionate policy and seek advice for an actual incident hold.[7]

Can a distributor’s contract replace the injured person’s rights?

Article 15 prevents limitation or exclusion of directive liability in relation to the injured person. The hotel’s commercial remedies and any supplier recourse agreement require their own legal review.[1]

This is procurement and financial analysis, not legal advice. Greek transposition, a particular contract, insurance response and a specific robot’s conformity have not been verified.

Notify me when an obligation on the tracker changes.

You'll get one email to confirm. Nothing else. Unsubscribe any time.

← Analysis