The pilot had gone well. Over six weeks, a pair of autonomous mobile robots had moved totes between the packing area and the dispatch dock at a regional distribution centre, and the operations manager, Tomas, could see the picture clearly: twelve units, a lease rather than a purchase, and a quieter floor by the next peak season. The vendor offered “robots as a service” at a monthly rate that included hardware, software and support. The brochure used the word “all-inclusive” three times. This account follows what happened when the agreement behind that phrase was read for the first time, nine months in.
The details are composite and invented for illustration, but the clauses are the kind that turn up routinely in equipment-as-a-service agreements.
The signing
The finance team approved the lease because the monthly figure compared well with the cost of two shifts of manual handling. The vendor’s contract ran to forty-odd pages, including an annex of service levels and a schedule of charges. Tomas skimmed the summary, the facilities director checked the insurance paragraph, and the purchasing lead confirmed the term: thirty-six months. Nobody had time to read the schedules. The rollout began on schedule.
For anyone planning a similar project, the overview in a complete walk-through of automated guided vehicles in warehouses is a good place to understand what the machines do. The contract, however, governs what happens when they do not.
Month four: the first invoice surprise
An extra line appeared on the invoice: a charge for “remote diagnostics”. Tomas called the vendor, who pointed to a paragraph defining the base service as covering hardware replacement and standard software releases. Diagnostics beyond a set number of monthly sessions were chargeable. Nothing improper had happened; the clause was simply further down than the word “all-inclusive”.
Month seven: the floor layout changes
Sales growth required rearranging racks. The robots rely on a site map, and the vendor’s engineers needed to remap the facility. The agreement treated remapping as a “change request” billed at a day rate, with a minimum visit charge, and with a lead time of several weeks. The warehouse could not wait, so some pallets were handled manually for a month while the remap was scheduled.
Month nine: the question of downtime
One robot developed a drive fault and stood idle for six days. Tomas assumed the service levels would compensate the loss. The annex did promise availability, but with defined exclusions: downtime caused by network problems on the customer’s side, by floor conditions, or by delays in giving the vendor access to the site did not count. The vendor attributed part of the delay to a gap in the site’s wireless coverage. A service credit was offered for the remainder, and the contract named it as the sole remedy.
Teams working with flying or roving platforms will recognise the theme. The breakdown in a practical guide to drone robotics platforms for operational teams shows how many dependencies surround a machine in the field, and each dependency tends to appear somewhere in the terms as an exclusion.
What Tomas finally read
Triggered by the dispute, Tomas sat down with the complete agreement and a highlighter. Several clauses had gone unnoticed.
- Minimum term and early exit. Ending the lease before thirty-six months required paying a large share of the remaining fees.
- Software ownership. The navigation software was licensed, not owned, and the licence ended with the lease. Maps and configuration created on site were treated as part of the service.
- Data. The vendor collected operational data from the robots and could use it in aggregate to improve its products.
- Price adjustment. Charges could increase annually by a formula referring to an index and a floor percentage.
- End-of-term return. Units had to be returned in a specified condition, and charges applied for wear beyond a defined standard.
The checklist the team now uses
The company adopted a short review sheet for any equipment-as-a-service deal. It asks eight questions, which anyone planning to lease automation can borrow.
- What exactly does “included” cover, and what is billed separately?
- Which events count as downtime, and which are excluded?
- What is the sole or primary remedy when targets are missed?
- How are site changes, remaps and reconfigurations priced and scheduled?
- Who owns the software, the maps and the operational data?
- How may prices change during the term?
- What are the early-exit costs and the return condition?
- What are the liability limits, and what insurance is each side expected to carry?
Getting the right help
Equipment agreements mix commercial, technical and legal elements, and a qualified lawyer is the right person to review anything large. For readers in India who are looking for one, WakilSahab presents a lawyer directory organised by practice area, along with legal news, a forum and blog articles. Treat it as a place to begin looking and reading. Whatever work a lawyer takes on, and the price, is settled between you and that lawyer.
How it ended
The warehouse kept the robots. Tomas negotiated a revised schedule that capped diagnostics charges, set a lead time for remapping, and clarified how site-related downtime would be assessed. Those concessions took three months of patient correspondence, and they came with a slightly higher monthly rate. The operations team also added a rule to its project process: no automation contract is approved without a one-page summary of renewal, downtime, change charges and exit terms, signed off by operations as well as finance.
The lesson is not that vendors act in bad faith. It is that a brochure and a contract answer different questions. The first describes what the robots can do on a good day. The second describes what you are owed, and what you owe, on a bad one. The twelve units still run every shift, and the next purchase took one extra afternoon of reading, which saved considerably more than that.
