A Commercial Cleaning Robot Procurement Checklist

Start with a go, hold, or no-go decision

A procurement file should make it easy for an operations leader to answer one question: is there enough evidence to buy this configuration for this site? That is different from asking whether a robot looks capable in a general demonstration. A go decision needs a defined use case, a named configuration, a practical ownership model, and written answers to unresolved questions.

Use a hold decision whenever a claim is broad but the site implication is unknown. For example, a cleaning mode count does not establish that a robot can clean every floor type in a building, and a large-commercial positioning statement does not establish that it can navigate a particular mall, warehouse, airport, or cafeteria. A hold is useful: it prevents a general capability statement from becoming an unverified site promise.

For facility service companies, keep the buying decision separate from any future service contract. The product packet can identify who will operate, replenish, inspect, and maintain the machine, but it should not assume response times, service levels, labor savings, or commercial terms that have not been quoted and accepted.

• Go: the task scope, configuration, site dependencies, commercial quote, support responsibilities, and handover owner are clear.
• Hold: an important input is missing, such as floor compatibility, workstation utilities, route access, maintenance ownership, or warranty wording.
• No-go: the proposed operating model depends on an unsupported capability or on a facility condition the site cannot provide.

Build a claims and source table before comparing candidates

CleaniBot C5’s 820 × 680 × 1130mm body and 550mm main cleaning width answer different purchase questions. The body dimensions inform storage and transit review; the main width informs pass planning. Request configuration-matched route observations before signing off fit. C5 is a candidate for recurring broad-area work when those cleaning passes and the service return match the scope—not because a body specification or a demonstration proves building-wide acceptance.

Do not turn a capability into an outcome. “Supports” means a feature is presented as available under the stated conditions; it does not mean the feature will work without supervision in every building, on every floor, or with every cleaning program.

Translate facility needs into a usable cleaning scope

Create a room- and zone-level scope before selecting a model. A shopping mall may have open circulation areas, storefront thresholds, food-zone conditions, and changing pedestrian patterns. An airport may add restricted areas, irregular operating windows, and coordination with other teams. Warehouses can introduce aisles, loading activity, dust, and changing obstructions. Cafeterias may require frequent response to soil events and clear ownership of water and waste routines.

The practical question is not simply whether an autonomous cleaning robot is suitable for a venue category. It is whether the proposed robot, configuration, and workflow are suitable for the defined zones in that venue. Mark areas that are in scope, excluded, conditional, or still unverified. This avoids presenting one machine as the answer for every part of a large building.

Consider CleaniBot C5 when the planned scope includes the cleaning tasks it supports and the facility is considering a large-commercial candidate. Verify each actual floor surface, the transitions between zones, the locations for water and wastewater work, access during operating hours, and the person responsible for routine intervention. Consider CleaniBot S55 Pro when compact positioning and its six-mode offering are relevant, then verify the exact surfaces, route constraints, and selected modes rather than assuming broad compatibility.

• List each floor area, its intended cleaning task, and whether it is open, congested, restricted, or variable.
• Record the floor material, transitions, drainage considerations, and any local cleaning restrictions the facility applies.
• Identify where the robot will be stored, prepared, checked, replenished, and returned after work.
• Name the shift or role that can respond when the planned workflow cannot continue as expected.

Collect representative records, not just a general demonstration

Your evidence packet should contain records that represent the proposed use, not a claim that a single observation proves all future conditions. Keep the records simple enough for an operations manager to read: date, location or representative zone, proposed task, configuration used, observations, exceptions, and open follow-up questions.

This is not a trial-design exercise or a promised performance test. It is a procurement record of what was shown, what was discussed, and what still needs confirmation. If the supplier demonstration occurred elsewhere, label it as representative only. Do not relabel it as proof of performance in your own facility.

Lock the proposed configuration and options

A model name is not a complete purchase definition. Ask for a configuration sheet that identifies the exact machine, included equipment, selected options, workstation status, installation assumptions, training or handover items, and any site work expected before use. Keep a revision number on each version so stakeholders do not approve an earlier proposal by mistake.

Record CleaniBot C5’s separate 45L tanks as onboard facts, and separately identify whether charging/refill/discharge/self-cleaning station functions are included in the quoted and delivered setup. Attach utility responsibilities, operator checks and unresolved use holds to that configuration revision. This turns the shortlist into an accountable supply decision: buy the configuration that supports the intended recurring task and retain use holds where the site cannot yet provide its dependencies. Delivery alone does not close those holds.

Do not assume it is included, compatible, or necessary because it was mentioned in conversation. Ask which water-service alternatives are available for the exact quoted configuration and how filling, wastewater handling and daily inspection would work. Availability and inclusion need confirmation in the proposal.

• Ask: What exact model and configuration are included in this quotation?
• Ask: Which functions depend on a workstation, accessory, facility utility, or site preparation?
• Ask: What routine cleaning, emptying, inspection, and consumable work remains with the customer or facility service team?
• Ask: Which areas, surfaces, tasks, or operating conditions are outside the supplier's proposed scope?

Ask quotation, warranty, and support questions in writing

Commercial terms should be handled by the quoted documents, not inferred from marketing language. Ask for the complete warranty wording, what is included or excluded, the process for requesting support, the responsibilities of the buyer, and any optional support offerings. If a response time, replacement arrangement, maintenance visit, or training commitment matters to your decision, request that it be stated in the applicable quotation or agreement.

For multi-site operators and facility service companies, identify whether ownership sits with the building owner, service provider, or another party. Then align the quotation recipient, warranty holder, daily operator, maintenance contact, and decision-maker for changes. This reduces the common problem of a robot arriving without a clear person accountable for its routine care.

• What warranty document applies to the quoted configuration, and what exclusions should the buyer review?
• Who receives support requests, what information is required, and what buyer actions are expected before requesting assistance?
• Which training, installation, maintenance, or support items are included, optional, or excluded from the quotation?
• Who owns the equipment after delivery, who is authorized to approve changes, and who will maintain the operating records?

Complete handover and ownership signoff

Do not treat delivery as final acceptance. The handover packet should identify what was delivered, which configuration was accepted, where supporting documents are stored, and which role owns daily operation. It should also preserve open items so a buyer does not mistakenly sign off on an assumption that remains unresolved.

We suggest a single final signoff page with three outcomes: accepted for the defined scope, accepted with listed open items and a hold on affected use, or not accepted pending clarification. The signoff is an internal operating decision, not a claim that the robot will achieve a particular performance level.

• Confirm the delivered model, configuration, options, and any workstation against the final quotation.
• Confirm that the facility has accepted the storage, utility, access, water, wastewater, and routine-care responsibilities relevant to the proposal.
• Assign a business owner, daily operating owner, maintenance contact, and commercial contact.
• Attach the claims table, representative records, quotation questions and answers, warranty documents, and unresolved-items list.

Prepare the final supplier enquiry

Before requesting a final quotation, provide the supplier with the facility type, priority zones, floor materials, intended tasks, operating windows, traffic conditions, storage location, available utilities, and the roles that will operate and maintain the equipment. Ask the supplier to distinguish confirmed product capability from assumptions that require site confirmation.

For CleaniBot C5, ask whether the proposed configuration includes a suitable workstation and which supported workstation functions apply to that configuration. For CleaniBot S55 Pro, ask which of its six modes are being proposed for the identified areas and what surface or operating checks are still required. Ask these as configuration questions, not as requests for guarantees about the site.

Use the completed checklist to compare proposals on clarity as well as capability. The most useful response is one that clearly states the proposed scope, exclusions, dependencies, ownership tasks, and documents needed before a go decision.

Frequently Asked Questions