For robot makers · Warranty & RMA · Template

Robot service ticket and RMA template (free download): what to record on site and when to return parts to the factory

· 12 min read

Short answer: in North American robot service, the thing that most often goes missing is not the repair but what happens after the part is swapped. The ticket closes the moment the robot runs again, the failed part sits in a box in the customer's warehouse, the logs stay on the technician's laptop, and three weeks later the factory asks "where is that motor?" and nobody knows. The fix is a ticket and RMA template that runs from the first call to the factory's failure analysis: four sections (intake, on-site, disposition, feedback), an RMA number and a disposition code for every failed part (repair on site / swap and return for analysis / swap and dispose locally / whole robot to factory / awaiting the maker's decision), five questions asked in a fixed order, a default of sending data, not damaged lithium batteries (49 CFR 173.185(f) allows them by highway, rail or vessel only), and a rule for what data goes back to the factory. The CSV field dictionary, an RMA log and a printable PDF field service report are free to download below.

This is written for robot makers, especially makers in China, that service robots in the US and Canada, and for the field service partners doing the work. KeepRobots is a robot field service company in Vancouver. Regulatory points are from the official texts, checked on November 14, 2026 (sources at the end). The fields, codes, decision rules and time limits are our template and suggestions, not a standard or any maker's own document. Not legal, customs or dangerous goods advice.

Download the three files

FileWhat's in itHow to use it
Field dictionary (CSV)All 59 fields for the ticket and the RMA: ID, section, field name, required or not, format or options, example, who fills it inImport into your ticketing system or spreadsheet, delete what you don't need, and send the field IDs to your service partner
RMA log (CSV)One row per failed part: RMA number, linked ticket, part number, serial, disposition code, battery and data status, batch, tracking, failure analysis resultOne shared sheet for the North American warehouse and the factory quality team, reconciled weekly
Field service report + failed-part tag (PDF, 3 pages)Page 1 field service report, page 2 failed-part tag and RMA request, page 3 disposition guidePrint it for site visits until you have a ticketing system; afterwards use it as a field checklist

The CSVs are UTF-8 with a byte-order mark, so Excel opens them cleanly. Keep the field IDs (A01, B07 and so on): across teams and languages, "B07" is harder to misread than a field name. The Chinese version of this page has the same 59 fields with bilingual Chinese and English names, which helps when the factory team reads Chinese.

Why the RMA needs its own record

A typical case: a warehouse in Vancouver, an AMR's drive motor reports overcurrent. The technician brings a spare from consignment stock, swaps it in an hour, the robot runs, the ticket closes. Three weeks later the factory quality team asks for the old motor's serial number, lot and pre-swap logs. The old motor is in a box marked "bad" in the customer's warehouse, and the same box holds a swollen battery that someone planned to air-freight back with the next batch. That battery is not allowed on a plane.

The problem is structural: when the field service ticket closes, the failed part's life has just started. If the ticketing system has no "failed part" record, quarantine, shipping, failure analysis and the result all depend on someone remembering. So the template splits one repair into two linked records: the field service ticket (sections A and B) records how the robot was restored; the RMA (sections C and D) records where the failed part went and why it failed. One ticket can have several RMAs.

1. Four sections: who fills in what, and when

SectionWhenWhoKey fields (full list in the CSV)
A IntakeFrom the customer's call to the decision to send someoneDispatcher, maker's L2 supportTicket ID, reported time with UTC offset, site, model, robot serial, hardware and firmware version, warranty status, severity P1–P4, the customer's own words plus a translation for the factory, fault codes, log bundle ID, remote triage result, on-site approval number
B On-siteArrival to departureField technicianArrival time, lockout and battery isolation, nameplate photos, as-found condition, diagnosis, failed-unit code, failure-mode code, actions by fault-tree step, part removed and part installed (part number + serial), firmware before and after, function test item by item, labour split into travel / on site / waiting, restored time, customer sign-off, data note
C Disposition (RMA)From removal to shipping or local disposalTechnician opens it, the maker decidesRMA number, linked ticket, part number, serial, lot and date code, disposition code, reason, decided by (or rule version), failure analysis required, battery and its condition, storage and data handling, quarantine location, batch, transport mode, tracking, export declaration, HS code (confirmed by the broker)
D FeedbackFrom arrival at the factory to the fixMaker's quality and R&D teamsReceived time, failure analysis result, root cause, corrective action or engineering change number, manual and fault tree updated (version), repeat within 30 days, warranty settlement, closed time

The report a technician hands in before leaving, the root-cause classes and the KPI definitions are the same ones used in training a third-party robot field technician, already merged into this template.

Three fields tend to drift into free text. Use fixed codes:

  • Failed-unit code (B07): the field-replaceable unit (FRU) number from your BOM, for example DRV-L (left drive wheel assembly) or LIDAR-F (front lidar). The service partner should not invent names.
  • Failure mode (B08): electrical / mechanical / software / sensor / battery / consumable / no fault found (NFF). Keep it separate from root cause (wear / environment / operation / software / incoming / unknown): the failure mode is what the technician sees, the root cause comes from analysis.
  • Disposition code (C04): D1–D5, next section.

2. Repair on site, return the part, or return the robot: five questions in order

Decide the disposition code first, then touch the box. There are five codes:

CodeMeaningWhere the failed part goes
D1 Repaired on siteRestored by adjustment, remapping and calibration, cleaning or consumables; no valuable part removedNo failed part, or consumables disposed of locally
D2 Swap, return for analysisA spare goes in; the failed part goes back to the factory for failure analysis (FA)Quarantine, then batch or expedite
D3 Swap, local disposalA spare goes in; the failed part does not go back: scrapped or recycled locally, or repaired locally with the maker's authorization and returned to stockKeep photos, serials and the scrap, recycling or repair record
D4 Whole robot to factorySwapping parts on site cannot fix itThe robot is exported for repair
D5 Awaiting the maker's decisionThe rules don't decide; hold it in quarantineQuarantine with a timeout reminder

Ask in this order:

  1. Is it a battery, or is there burning, water or crash damage? Quarantine it first. Batteries follow section 4: by default send the data and recycle the battery locally; if the maker really needs the battery, it travels as dangerous goods by ground or ocean, never by air.
  2. Can a field-replaceable unit restore operation? If yes, it is D1, D2 or D3. Real D4 cases are rare: a bent main frame, a cracked weld, a sealed joint module, zero-point or stiffness calibration that needs a factory jig, or a bricked bootloader that needs a factory programming fixture. A full table of what can be fixed locally is in sending a robot back to the factory in China.
  3. Does the maker need failure analysis? Typically yes for a new failure mode, a suspected lot problem (for example the third failure of the same part number and lot within 60 days), a safety-related failure, or a warranty claim that needs the part. Yes means D2. We suggest presetting "FA by default: yes/no" per part number in the BOM, so the technician follows a rule instead of asking every time.
  4. Is the part worth shipping? A known failure mode on a part worth less than the freight and customs cost is D3. A valuable, repairable part: ask whether the maker authorizes local repair back into stock; otherwise D2 in the next batch.
  5. Still unclear? D5, with a timeout (we suggest 14 days) that reminds both sides. Failed parts should not move into the warehouse permanently, and they should not go back by default either.

For robots in the US whose models are affected by the FCC Covered List, replace parts with identical parts: the FCC's robot FAQ says repair and replacement with identical parts is not prohibited, while a different part needs a separate check. See robots already sold in the US after the FCC Covered List.

3. The RMA process, from removal to the result

StepWhoSuggested timeRecord
1. Photograph before removal: as installed, nameplate and serial label, damage, connectorsTechnicianOn sitePhotos in B05 / C03
2. Request an RMA numberTechnician requests, maker issuesMaker within 1 business dayC01; a part without a number stays in quarantine
3. Tag, bag and quarantine the partTechnician, warehouseSame dayTag with RMA number, part number, serial, disposition code (PDF page 2)
4. Set the disposition codeBy rule, or the maker manuallyWithin 2 business daysC04–C06; D5 starts the timeout
5. Handle data on parts with storageTechnician or warehouseBefore shippingC09: wiped, or written customer consent to ship as is
6. Ship in a batch or expediteWarehouse, forwarder, customs brokerBatch monthly or quarterly; expedite single safety-related partsBatch, tracking, export declaration, HS code
7. Receive at the factoryMaker's quality teamSame day as receiptD01; report mismatches immediately
8. Failure analysis resultQuality and R&DWe suggest within 30 daysRoot cause, corrective action or engineering change number
9. Put the result to workR&D, technical supportNext manual versionFault tree, service manual and spare-parts list versions

Customs steps for sending parts or robots to the factory and back (export for repair, duty on the repair value when it returns, ISPM 15 crates) are in sending a robot back to the factory in China. Who pays for what under warranty, including advance replacement and claim evidence, is in robot warranty and RMA in North America. One rule for the system: the original serial, the replacement serial and the export declaration number live on the same RMA, so you can find them a year later.

4. Damaged lithium batteries: send the data, not the battery

Damaged batteries are the strictest part of any RMA. In the US, 49 CFR 173.185(f) (its heading also covers recalled cells and batteries) applies to lithium cells and batteries that are damaged or defective, or that the manufacturer has identified as defective for safety reasons and that may produce a dangerous evolution of heat, fire or short circuit, including those contained in equipment:

  • Transport: "by highway, rail or vessel only", so not by air.
  • Packaging: each battery in its own non-metallic inner packaging that completely encloses it, surrounded by non-combustible, electrically non-conductive and absorbent cushioning, in an outer packaging meeting Packing Group I performance; a single battery or a single item of equipment can use the specified rigid large packagings.
  • Marking: "Damaged/defective lithium ion battery" and/or "Damaged/defective lithium metal battery", in characters at least 12 mm (0.47 inches) high.
  • No recycling shortcut: 173.185(d) eases shipping for batteries going to recycling or disposal, but PHMSA's 2024 interpretation letter 24-0050 says it does not apply to damaged batteries.

In Canada, the Transportation of Dangerous Goods Regulations (SOR/2001-286) apply through special provision 137. It was amended by SOR/2026-112 on June 17, 2026, with a 12-month transition during which the previous version can still be used. The current text defines damaged or defective batteries as ones that leak, vent, or have physical or mechanical damage and cannot be diagnosed before transport; packages are marked "Damaged/Defective" or, in French, "endommagées/défectueuses"; batteries liable to rapidly disassemble, react dangerously or produce a flame are forbidden by any mode. Transport Canada's battery web page (July 2025 version) still describes the old rules, so go by the regulation. For international air, IATA's 2026 lithium battery guidance says damaged or defective batteries are forbidden, including those in equipment.

Anyone who packs, marks or prepares shipping documents needs hazmat employee training under 49 CFR 172.704 in the US, and a TDG training certificate in Canada (or must work under the direct supervision of someone who holds one).

In the template, that becomes three rules:

  1. C08 has four values: not a battery / intact / damaged / unknown. Unknown is treated as damaged.
  2. A damaged or unknown battery cannot have "air" as its transport mode.
  3. The default disposition is D3: photograph it locally, record voltage and temperature, export the BMS log, send the data and recycle the battery under local rules. Write into the warranty terms that the maker accepts "photos + logs + recycling record" instead of the battery. If the maker really needs the battery, give it to a forwarder qualified for dangerous goods and ship by ocean.

5. What data goes back to the factory

Closing the loop depends on data, and North American customers' IT and legal teams will ask where their data goes. Split it in two:

Can go back by defaultConfirm first
Structured ticket fields (customer contact names, phone numbers and emails replaced by ticket ID and site code); fault codes; robot log bundles; BMS data; parameter and firmware snapshots; photos of nameplates, removed parts and damageRaw camera images and video (may show people); customer site maps and floor plans; personal data of the customer's staff; failed parts that contain storage (main boards, SSDs, camera modules)

Two rules behind this; more in robot IT security requirements in North America:

  • Canada, PIPEDA Schedule 1, clause 4.1.3: an organization remains responsible for personal information it transfers to a third party for processing, and must use contractual or other means to provide a comparable level of protection. Customer contact details in a ticket are personal information.
  • US, 28 CFR Part 202 (the Justice Department's data security rule, effective April 8, 2025): restricts US persons from giving covered persons of countries of concern, including China, access to bulk US sensitive personal data through vendor, employment or investment agreements unless CISA security requirements are met. Thresholds count the preceding 12 months, for example precise geolocation data on 1,000 devices, biometric identifiers of 1,000 people, or covered personal identifiers of 100,000 people. Robot logs usually don't reach this, but camera images and person-identification data need a lawyer's view.

The simplest setup: customer contact details stay in the North American system and the factory sees only ticket IDs and site codes; camera images don't go back unless the customer agrees case by case; parts with storage are wiped before shipping, and where that's impossible (the storage failed, or the analysis needs the raw data) the customer's written consent is recorded in C09.

6. Close the loop: one table for R&D every month

With section D filled in, one monthly table for R&D and quality beats reading tickets one by one:

  • Failed unit × failure mode ranking: top five, per model.
  • Disposition mix: share of D1–D5; whole-robot returns (D4) on their own line.
  • Failure analysis cycle time: days from removal to result, and where it waits (RMA number, batching, customs, analysis queue).
  • No-fault-found rate: parts the factory can't fault. A high rate points at field diagnosis or the fault tree, not always the part.
  • 30-day repeats: same robot, same fault, within 30 days.
  • Manual updates: how many results this month went into the fault tree and service manual.

The last one is the easiest to skip and the most valuable: if a failure analysis result never becomes a fault-tree step or a spare-parts line, the next technician in North America will meet the same fault and make the same call.

Common mistakes

  • Closing the ticket at the swap: the failed part has no RMA number and nobody owns it. Close the service ticket; keep the RMA open.
  • One "status" field: where the ticket is and what happens to the part are different questions. Mix them and you can't measure either.
  • Serials from memory: read model, serial and firmware from the robot or the nameplate, and photograph them.
  • A damaged battery in the same box as other parts: the whole box becomes dangerous goods, and may not be shippable at all.
  • Free-text root causes: "customer misuse" and "possible hardware issue" can't be counted three months later.
  • No D5 timeout: the part sits for six months and then nobody wants it.
  • Results that never come back: the factory finishes the analysis and the field never hears.

What KeepRobots can do

KeepRobots is a robot field service company in Vancouver, starting from Greater Vancouver with on-site visits across Canada and to the US. We don't build robots and are not an exclusive agent for any brand; in Canada we also sell robots from selected brands (Booster Robotics and SENAD, see our robot shop), and we service robots of any make. For tickets and RMAs we can fill in field service reports with your fields and codes (in English or Chinese, returned within 24 hours); photograph, tag, quarantine and log failed parts under your RMA numbers; hold consignment spares and failed parts awaiting return in Vancouver and hand batches to your forwarder and customs broker; quarantine damaged batteries, record their data and pass them to local recycling; and help you set the first version of your fields and disposition rules from this template. We don't do customs brokerage or dangerous goods transport ourselves; qualified forwarders and brokers handle that.

Current rates, before tax: diagnostic C$200 in Canada or US$200 in the US, per robot, per visit, credited if you approve the repair; C$100 call-out in the Greater Vancouver core zone; on-site labour C$150/hour in Canada or US$150/hour in the US; travel outside the core zone and for US projects quoted per project. See North American field service for robot makers, or write to partners@keeprobots.com or use the contact page.

FAQ

What fields should a robot service ticket include?

Four sections. Intake: ticket ID, reported time with UTC offset, site, model, serial, hardware and firmware version, warranty status, severity, the customer's own words, fault codes, log bundle, remote triage result, on-site approval. On-site: arrival time, lockout, nameplate photos, diagnosis, failed-unit and failure-mode codes, actions, parts removed and installed with serials, test results, labour, restored time, sign-off. Disposition (RMA): RMA number, disposition code, battery and data status, batch and tracking. Feedback: failure analysis result, root cause, corrective action, manual update, 30-day repeat. The free CSV on this page lists all 59 fields.

When should a failed robot part be repaired locally and when returned to the factory?

Ask five questions in order: is it a battery or burned, wet or crash-damaged; can a field-replaceable unit restore operation; does the maker need failure analysis; is the part worth shipping; and if still unclear, hold it for the maker's decision with a timeout. Whole-robot returns are rare, usually a bent frame, a sealed module, factory-jig calibration or a bricked bootloader. Most cases are a local swap with the failed part returned for analysis or handled locally.

When should an RMA number be issued?

We suggest requesting it the day the part is removed, with the maker issuing it within one business day. The part is photographed, tagged with the RMA number, part number, serial and disposition code, and quarantined. The service ticket can close once the robot runs; the RMA stays open until the failure analysis result is recorded.

Can a damaged robot lithium battery be shipped back to China by air?

No. In the US, 49 CFR 173.185(f) allows damaged or defective lithium batteries by highway, rail or vessel only, each in its own non-metallic inner packaging inside a Packing Group I outer packaging marked "Damaged/defective lithium ion battery" in characters at least 12 mm high. Canada's TDG special provision 137 (amended June 17, 2026) requires a "Damaged/Defective" marking, and IATA forbids them by air, including in equipment. In practice: record the data and BMS logs locally, send the data, recycle the battery locally.

Can service data from North American customers be sent to the factory in China?

Fault codes, log bundles, BMS data, parameters, versions and equipment photos usually can. Customer contact details, camera images, site maps and failed parts with storage need confirmation first. PIPEDA requires comparable protection by contract when a third party processes personal information; the US rule at 28 CFR Part 202 restricts access by covered persons of countries of concern, including China, to bulk US sensitive personal data. Not legal advice; ask counsel.

What can KeepRobots do, and what does it cost?

Fill in field service reports with your fields and codes and return them within 24 hours; tag, quarantine and log failed parts under your RMA numbers; hold consignment spares and failed parts in Vancouver and hand batches to your forwarder; record and recycle damaged batteries locally. Customs brokerage and dangerous goods transport are done by qualified forwarders and brokers. Rates before tax: diagnostic C$200 in Canada or US$200 in the US per robot, per visit (credited if the repair is approved); C$100 Greater Vancouver call-out; labour C$150/hour in Canada or US$150/hour in the US; travel outside the core zone and US projects quoted per project.

Sources

  • US 49 CFR 173.185 (lithium cells and batteries; (d) recycling, (f) damaged, defective or recalled): ecfr.gov
  • PHMSA interpretation 24-0050 (July 2, 2024; damaged batteries cannot use 173.185(d)): phmsa.dot.gov
  • Canada, Transportation of Dangerous Goods Regulations SOR/2001-286 (special provisions 137, 138; s. 6.5 training certificates): laws-lois.justice.gc.ca
  • SOR/2026-112, Canada Gazette Part II (June 17, 2026; amends special provision 137): gazette.gc.ca
  • IATA Lithium Battery Guidance Document 2026 (D.06): iata.org
  • US 49 CFR 172.704 (hazmat employee training): ecfr.gov
  • Canada, PIPEDA Schedule 1 (clause 4.1.3): laws-lois.justice.gc.ca
  • US 28 CFR Part 202 (Data Security Program): ecfr.gov; Justice Department program page: justice.gov

49 CFR 173.185(f) re-checked on November 14, 2026; Canadian TDG, IATA, PIPEDA and 28 CFR Part 202 points as checked on October 31, 2026 for the Chinese version. Not legal, customs or dangerous goods advice. The fields, disposition codes, decision rules and time limits are KeepRobots' template and suggestions, not a standard or any maker's document. KeepRobots rates are current published rates before tax and may change.

中文版:机器人售后工单和 RMA 模板(中英双语,可下载):北美现场记什么、怎么判返厂、怎么回传研发

← Field notes

Want a local service point in North America?

Tell us your product, where your customers are and what you need. We reply within one business day, in English or Chinese.