Does Your Robot Battery Warranty Start at Shipment or First Use?

Your robot battery pack warranty should start at a trigger you choose on purpose and write into the purchase order, and for most fleets that trigger is commissioning or first charge, not shipment. Shipment is the supplier's preferred default because it is the one date they can prove without your help, and it quietly spends your coverage on transit, receiving inspection, integration queue, and every week a pack sits on a shelf before anyone bolts it into an AMR. If the supplier will not move off shipment, the fallback is not to shrug and hope. It is a written storage allowance with a state-of-charge band, a temperature band, and a maximum allowed time between shipment and first use, plus the records that make the allowance claimable.

I'm on the receiving dock at a plant running a mixed fleet of tuggers and lift AMRs. Four battery cartons sit on a shrink-wrapped pallet, and the packing slip taped to the top carton is dated eleven weeks before the delivery window on the PO even closed. The packs are fine. That is the problem. They are fine, they have been fine for eleven weeks, and nobody upstairs has spent a minute on what those eleven weeks cost.

I pull the warranty clause up on my phone. Twenty-four months from date of shipment. So the clock already reads about 21.4 months on packs that have never been powered. Then I do the arithmetic that actually bites: if the install crew gets to them in another six weeks, and the duty cycle runs four to six hours a day, the tail of the warranty, the part where capacity fade stops being a rounding error and starts showing up as a mid-shift recharge, lands right around the time the fleet finally hits its utilization target. The supplier's clock runs fastest while nothing is happening.

Five dates that all get called the start

The clause usually names one of five events. They are not interchangeable, and the difference between the cheapest and the most expensive for you can be two full quarters of covered life.

Shipment date

The date on the commercial invoice or the carrier's pickup scan. It is the cleanest date for the supplier to document and the worst one for a buyer with any staging time. In a short domestic LTL move it might cost you two weeks. Build the pack overseas, containerize it, clear customs, and let it sit in a receiving inspection queue, and you have spent a season of coverage before the first carton is opened.

Delivery receipt

The signed bill of lading or proof-of-delivery timestamp. This recovers transit time but not receiving lag or integration queue, and it demands discipline on the dock: the receiver has to date and sign the same day, and carton damage has to be noted at that moment rather than discovered a week later when the pallet gets unwrapped. I have watched a receiving clerk sign a clean POD on a Friday and find crushed foam on a Monday. That gap is on you.

Installation

Better, but fuzzy. Does installation mean the pack is mechanically mounted, or mounted and electrically connected? If the clause says installation and never defines it, you have manufactured a dispute. I have seen a supplier argue that a pallet-mounted pack on a floor dolly counted as installed because it had been placed in the cell.

Commissioning

The date the robot passes its commissioning checklist and enters service. This is the buyer-friendly trigger that suppliers will actually sign, because it maps to a document both sides already produce. It is my default ask. It also has a real limitation: if your commissioning depends on a systems integrator who is booked out six weeks, you have handed your warranty schedule to a third party who has no stake in it.

First charge

The most precise trigger and the hardest to win. The BMS records first power-on, and the first charge current is a hard, machine-generated event. When the supplier pushes back on this one, it is usually because they do not want to reconcile logs, not because the data is unavailable. If you can produce the log on demand, this trigger is nearly impossible to argue with.

What shelf time actually costs, and how the storage allowance works

A storage allowance is how you keep a shipment-date clock from eating your coverage. It is typically written as a carve-out: coverage does not begin until first use, provided the packs are held within a state-of-charge band, usually somewhere in the middle of the pack's voltage range rather than at full, and within a temperature band in a climate-controlled space, for a maximum number of months. The specific numbers vary by cell chemistry and by supplier, so I do not carry a number in my head. I carry the shape of the clause and the question: what conditions void the allowance, and who proves the conditions were met?

That second half is where most buyers lose. The allowance is unclaimable without evidence. Warehouse temperature and humidity logs, periodic open-circuit voltage checks on a sample of packs, pallet-level storage records if the packs are split across sites. If your warehouse cannot produce a temperature history for the aisle where the pallet sat, then in a dispute you are asking the supplier to take your word for it, and you will not get far. I have started asking the warehouse manager for those logs in the same conversation where I ask about dock capacity, because it is the same person and the same system.

Proving the date you picked

If you negotiate for commissioning or first charge, you owe the clause a paper trail. In practice that means three things stitched together.

• The commissioning record, signed and dated, with the serial number of the pack and the asset ID of the robot it went into.
• The BMS first-power-on log, pulled at commissioning, not eighteen months later. This matters more than people expect. A pack that will not wake up will not hand you its first-power-on date, and a warranty claim usually starts with a pack that will not wake up.
• A serial-to-asset list that somebody owns and keeps current. If the pack moves between robots during a retrofit or a fleet reshuffle, the list is the only thing tying the log to the claim.

One small thing that has caused a real two-day argument: timezone. BMS logs come out in UTC. Commissioning sheets get written in local time. A pack commissioned at eleven at night lands on a different calendar date in the log than on the sheet. Pick one convention for the program and put it in the clause annex.

Duration, cycle count, or whichever comes first

Start date is only half the clock. The other half is what stops it: a fixed period, a cycle-count limit, an energy-throughput limit, or whichever occurs first. A three-year term and a cycle-limited term are different products for a two-shift operation. The same pack under a two-shift duty cycle can burn a cycle allowance in a fraction of the calendar term.

So when I am comparing quotes, I ask two questions that are not in the standard spec sheet. Which counter does the BMS maintain, and can I read it without a supplier tool and a supplier login? If the answer to the second one is no, then every cycle-based claim becomes a negotiation instead of a lookup, and I price that risk into the decision.

Match the trigger to what your team can actually do

This is the part that gets skipped. The trigger you ask for has to match your operational reality, or you have negotiated a right you cannot exercise.

If your receiving dock cannot inspect and stage within a few days of arrival, a delivery-receipt trigger has a hole in it, because the clock starts before you have confirmed the shipment is intact. If commissioning runs through an integrator with a backlog, a commissioning trigger cedes control of your warranty window to that backlog. If your installs happen in waves tied to a site build-out, first charge may be the only trigger that reflects what is actually happening on the floor. And if packs are going into spares inventory for a fleet that will not grow for eight months, no trigger except first charge, or a storage allowance, keeps you whole.

I write the trigger into the RFQ, not into the negotiation. Putting it in the requirements table forces the supplier to price it, and a priced objection is a real objection. An objection raised in week nine of negotiation is usually just fatigue.

The language I ask for looks roughly like this: the warranty period begins on the date of successful commissioning of the pack into its host robot, documented by a signed commissioning record and the BMS first-power-on log for that pack serial number, and in no case begins earlier than a stated number of days after delivery receipt. Then, separately, a storage clause that holds the start date for packs in inventory, with the SOC band, the temperature band, the maximum months, and the evidence list named explicitly.

What I check before the PO is cut

Five things, and I do not sign without them. The named start trigger. A definition of that trigger specific enough to survive a disagreement. The evidence that proves it, listed. The storage allowance with its conditions. And a named owner for the serial-number list, on my side, because the supplier is not going to maintain it for me.

I will not tell you how to read the clause itself. Contract interpretation is your counsel's job, and it varies by state and by how the rest of the agreement is drafted. What I can tell you is the operational reality the clause has to fit into: packs arrive, they wait, they get installed in waves, robots get swapped, and the one date everybody remembers is the one that was written down before the order was placed.