Robotic Lawn Mower Pre-Shipment Inspection: A Practical Checklist for Importers

Before authorising shipment, an importer needs evidence about the actual production lot. Do the units match the approved configuration? Do the agreed functions work? Are the labels and accessories correct, and have material defects been resolved? An earlier sample test cannot answer those batch-specific questions.

A pre-shipment inspection (PSI) is one opportunity to check this before the goods leave the factory. It should not be confused with supplier due diligence, engineering validation, long-term reliability testing, or formal product conformity assessment.

For OEM and private-label buyers sourcing robotic lawn mowers from China, the following nine checks help make the shipment decision more evidence-based.

Before you start: decide what the inspection can prove

A useful inspection plan separates three kinds of evidence:

Before appointing an inspector, provide the purchase order, approved product specification, reference sample or approved photos, component and firmware version requirements, inspection plan and written acceptance rules. If these are missing, agree them first rather than asking an inspector to invent pass/fail criteria on site.

1. Confirm the production lot and select the sample properly

Start by identifying the actual goods available for inspection: purchase order, model variants, total quantities, cartons, manufacturing batches and serial-number ranges. Confirm whether production and packing are sufficiently complete for the agreed inspection method.

Samples should be selected according to the agreed sampling plan from the accessible finished lot—not from a handful of units preselected by the factory. Record how cartons and units were chosen, especially when the order contains multiple variants or manufacturing batches.

For attribute inspection, buyers may agree an approach based on ISO 2859-1:2026. The inspection level, AQL values and accept/reject rules must be defined for the project; a generic AQL number is not automatically suitable for every risk. AQL inspection also does not replace safety-critical verification. Record the sample size for each test: a smaller functional-test subset must not be reported as though every unit in the visual-inspection sample completed that test. Treat the sampling plan as a written agreement, not a claim that the lot is defect-free. ISO standard reference (ISO).

Record: lot identity, quantity, sample-selection method, serial numbers and inspection readiness.

2. Match the shipped configuration to the approved product

Compare inspected units with the purchase order and the approved specification. Check the model identification, cutting system, drive configuration, battery and charger variants, navigation hardware, wireless modules where applicable, and approved firmware or software versions.

A mower can look identical to the approved sample while using a different battery pack, board revision or firmware release. Those differences should be recorded, not waved through because the product still powers on.

Where the supplier maintains traceability records, select a serial number and ask it to retrieve the corresponding production configuration, end-of-line result and relevant rework history. Do not claim that traceability exists unless the records can actually be retrieved.

Record: model/version, observed component or label identifiers, discrepancies and written approvals for permitted changes.

3. Inspect workmanship and cutting-system assembly

With the mower powered off and made safe according to its instructions, inspect the housing, wheels, connectors, cutting deck, blade assembly, fastening, exposed wiring, seals, charging contacts and visible damage. Use the approved drawings and workmanship limits rather than subjective descriptions such as “looks acceptable.”

The cutting mechanism deserves particular attention, but inspection personnel must not improvise hazardous blade-running or access tests. Specialised checks of blade retention, stopping behavior or guarded access should follow an approved procedure and be performed by competent personnel.

Record: defect location, unit ID, photo evidence, relevant specification clause and disposition.

4. Verify agreed safety-related controls within the inspection scope

For functions fitted to the model, an approved on-site functional protocol may include the STOP control, protective interlocks, designated lift/tilt responses, fault indication and recovery behaviour. What must be tested on every unit versus on a controlled sample should be decided before the inspection.

Never put hands or objects near a moving blade or deliberately create an unsafe condition as an ad hoc test. Any safety-critical discrepancy should trigger the agreed escalation and shipment-hold process until qualified parties assess it.

For EU-bound units, conformity assessment remains a separate responsibility. EN 50636-2-107 covers specified battery-powered robotic lawnmowers; IEC 62841-4-3 excludes robotic lawnmowers. Confirm the applicable edition, amendments and market requirements for the actual configuration rather than treating either reference as a universal certificate requirement. See the NBN scope (NBN) and IEC scope (IEC).

The European Commission (European Commission) states that the new Machinery Regulation (EU) 2023/1230 generally applies from 20 January 2027. The current Machinery Directive governs machinery placed on the EU market before that date. Assess the planned market-placement date, not simply the factory shipment date.

Record: protocol/version, observed outcome, deviations, responsible reviewer and release implication.

5. Test navigation and mowing workflows in suitable conditions

Navigation architecture matters. A boundary-wire model, an RTK-equipped mower and a camera- or LiDAR-based mower do not share one universal test script.

For the functions included in the approved model, the agreed protocol may address mapped or physical boundaries, restricted zones, start/stop scheduling, loss-of-position handling, obstacle behaviour, mowing-height adjustment and task completion.

The inspection location is a real limitation. A short indoor or factory-yard demonstration cannot establish coverage on complex lawns, performance under trees, slope stability, edge quality or long-duration obstacle avoidance. Those claims should refer to a separate pre-agreed outdoor field validation with documented terrain and environmental conditions. Mark unavailable field checks as not tested, with the reason and decision owner. If a required release check cannot be completed, hold the release decision until it is resolved; do not mark that check as passed. A field test may be scheduled alongside PSI if the approved site, method and time are available.

For slope-related claims, record whether the specification uses percentage gradient or degrees, together with the surface condition and direction of travel. These units are not interchangeable; the agreed model specification must control the test.

Record: what was actually tested, environment, firmware version, result and which field tests remain unverified.

6. Check docking, power and charging functions

For sampled units, verify the approved charger and charging-station configuration, visible condition of the contacts and cables, indicators, intended docking/charging handshake, and agreed power-related functions.

If a runtime or charging-time requirement forms part of the purchase specification, the test method must specify starting state of charge, operating mode, conditions and duration. A short charging demonstration does not establish battery capacity, cycle life or long-term reliability.

Record: adapter/station ID, test conditions, observed status, exceptions and supporting production records.

7. Confirm firmware, app compatibility and fault behaviour

On connected models, verify the released firmware and app compatibility against the approved configuration. Use agreed test accounts and conditions to check setup, basic commands, mapping or zone settings where applicable, error codes and available update or recovery processes.

Network-dependent tests should distinguish satellite reception, delivery of correction data, and app/cloud access. A cellular or Wi-Fi interruption can also interrupt navigation corrections on a network-dependent model; it is not always just a loss of remote control. For example, Husqvarna describes (Husqvarna) different internet dependencies for its cloud and local-reference-station EPOS installations. Apply the selected model's documented behaviour, not a rule borrowed from another architecture.

Record which connection was interrupted, the observed response and recovery, and any manual intervention required. Do not claim an outage scenario was validated if it was not tested. Also confirm destination-market service availability with the supplier: a successful factory connection does not establish coverage in the buyer's market.

Any unapproved firmware or hardware revision should be entered in the deviation log for buyer review. If a revision is installed after inspection, identify the affected checks and agree what must be repeated before release. “Latest firmware” is not a substitute for an approved, recorded release version.

Record: firmware version, app version, connectivity conditions, function tested, result and test limitations.

8. Inspect markings, packaging, accessories and documents

Confirm the finished product is the version intended for the destination market. Check product and carton identification, required safety information, manuals/languages, brand artwork, serial or batch traceability, charger and plug variant, charging station and other contracted accessories. Inspect packing protection and shipment marks against the agreed pack-out specification.

Review whether the available declarations and reports refer to the production model and its actual configuration. This is a document-to-product consistency check, not a declaration that the inspector has certified the machine. Where regulatory gaps are identified, refer them to the responsible importer, manufacturer, laboratory or competent adviser.

Record: label and carton photos, accessory counts, document/version match and unresolved gaps.

9. Classify defects, verify corrective actions and control shipment release

A useful report lists the inspected lot, sample size and sampling method, each finding, defect category, supporting evidence, supplier response and retest outcome. Classify critical, major and minor defects against agreed definitions, rather than applying arbitrary labels after the event.

Keep pass, fail, not tested and not applicable separate at check level. Explain every omitted required test, and identify the person responsible for resolving it.

Possible shipment decisions are:

• Release: the agreed acceptance rules are met and required documents and approvals are complete.
• Hold and correct: one or more material deviations require containment, sorting, rework or clarification; verify correction before reconsidering release.
• Reject/escalate: a critical safety issue, unacceptable core-function failure or unresolved compliance concern requires review by the competent parties. Do not silently convert it into a minor cosmetic defect.

The buyer and supplier should agree in advance who authorises shipment, whether a failed batch must be sorted or reinspected, and how the evidence is retained. An inspector's report may support the decision; the contractual authority to release the goods should be clear.

Quick pre-shipment checklist

• Inspection lot and randomly selected sample are identified.
• Model, hardware, battery/charger variant and firmware match the approved specification.
• Workmanship and cutting-system assembly pass the agreed visual/physical criteria.
• Defined safety-related functions have valid recorded checks, with critical issues escalated.
• Navigation/mowing functions are verified only to the extent the test setting permits.
• Docking and charging checks are documented.
• Software versions and required connected features are recorded.
• Manuals, warnings, accessories, markings and packaging match the destination-market version.
• Deviations, corrective actions and reinspection outcomes are documented.
• The authorised buyer has made a recorded shipment decision.

Frequently asked questions

Can a one-day factory PSI prove a robotic mower's navigation or slope performance?

Not by itself. It confirms only the functions exercised under the recorded conditions. Suitable outdoor tests may be included in the visit if agreed in advance, but a short warehouse demonstration cannot establish broader terrain performance or long-term reliability.

Does passing an AQL inspection mean the shipment is defect-free?

No. Acceptance sampling supports a defined lot decision under an agreed plan; it does not prove zero defects or eliminate the need to address safety-critical issues.

Should every mower undergo a full lawn test before shipping?

Not necessarily. The appropriate mix of factory end-of-line tests, random final inspection, dedicated field tests and safety verification depends on product risks, specifications and agreed controls.

Can a pre-shipment inspection replace EU conformity assessment?

No. PSI checks an actual production lot against agreed criteria. Applicable conformity assessment, technical documentation and legal responsibilities remain distinct matters.

Make the shipment decision traceable

A useful pre-shipment inspection connects the actual shipped lot to an approved specification, records observable results, and makes unresolved risks visible before the goods move.

For a broader discussion of choosing the right product and supplier, see Robotic Lawn Mower Sourcing for Private Label and B2B Distribution. For market-specific documentation questions, see ROBOMISE Compliance Support. If you need help defining a sourcing or inspection scope, start a project with ROBOMISE.