Demonstration Software Is Not a Transferable Robot Asset

Demonstration units often travel with robots that later appear on secondary listings. The controller hardware may be resold, but the software that makes the robot move during a demo is frequently installed under a separate arrangement with the original supplier. On a robot marketplace, buyers and due-diligence reviewers should treat the demonstration software as a distinct item to be documented, not as a bundled attribute of the machine.

Separating the Controller from the Demo Software Stack

A practical starting point is to separate physical control hardware from the software layer used only to show capability. The controller, drives, teach pendant and safety-rated inputs are the transferable hardware record. The demonstration environment — simulation scenes, path-teaching scripts, temporary API keys and cloud dashboards — usually exists so a salesperson can run a scripted routine. When a listing says a robot "includes full software," the buyer should request a written breakdown of which components remain active after handover and which expire. Recommended documentation practice is to keep one section of the asset file for controller serial numbers and another for software dependency records, so the two are never merged into a single vague claim.

This separation matters because the software supply chain behind a robot is rarely a single program. Guidance from NIST on software supply chain security notes that software is a critical component of managing cybersecurity related to supply chains, and that guidelines cover criteria to evaluate the security practices of developers and suppliers themselves (Software Supply Chain Security Guidance | NIST). For due diligence, that means asking the seller to name the supplier of each software layer and to show what written access terms were granted, rather than assuming the demo package travels with the metal.

Version Records: Why "Demo Build" Is Not a Stable Identifier

A demonstration build is often a pre-release or a custom patch. Semantic Versioning 2.0.0 explains that a pre-release version may be denoted with a hyphen and identifiers, that such a version is unstable and might not satisfy the intended compatibility requirements of the normal version, and that major version zero is for initial development where anything may change (Semantic Versioning 2.0.0 | Semantic Versioning). If a seller quotes only "demo version 0.9" or a build tag, the buyer cannot assume the same behavior will persist. Recommended documentation practice is to record the exact MAJOR.MINOR.PATCH string, any pre-release label and any build metadata exactly as printed by the system, because build metadata is ignored for precedence but may identify a custom compile.

During inspection, the buyer can photograph the version screen, save the readout to the file, and ask the supplier in writing whether the recorded string corresponds to a supported maintenance branch. The versioning specification gives the buyer a precise vocabulary for the numbers already on the screen.

Supplier-Granted Access and Written Evidence

Many demonstration setups depend on credentials: a time-limited token, a cloud seat, or a vendor portal login used to trigger the routine. The buyer should request written evidence describing which accounts remain usable after sale, when they were issued, and whether any seat is tied to the previous owner's organization. Recommended documentation practice is to store supplier emails, portal screenshots with visible dates and the exact wording of any access grant in the asset file.

Do not rely on verbal assurance during a viewing. If the original equipment supplier granted access only for the length of a trade show or a demonstration contract, the new operator may inherit a robot that powers on but cannot load the shown routine. The written record should also note whether the access was tied to a named individual, which is common for developer dashboards.

Dependency Records for Motion and Vision Packages

A modern robot may combine a motion controller with vision libraries, fleet-management agents and third-party middleware. Semantic Versioning 2.0.0 describes dependency problems in large systems, including version lock when specifications are too tight and version promiscuity when dependencies are specified too loosely (Semantic Versioning 2.0.0 | Semantic Versioning). For due diligence, the buyer should list each named dependency and the version constraint the seller claims is installed. Recommended documentation practice is to request a dependency manifest exported from the system rather than a marketing summary.

A hypothetical example: suppose a listing includes an automated palletizing cell with a demo routine built on version 2.4.1 of a vision package. The file should record "vision-core 2.4.1, constraint ^2.4.0" as observed, plus the supplier note that major upgrades require a new service contract. This is hypothetical only and must not be read as a claim about a real product. The purpose is to show that the version and the constraint are two separate fields; observing the first does not prove the second remains valid.

Observation Checklist for Marketplace Files

Build the asset file with these observed fields, all backed by written or photographic evidence:

• Controller and pendant serial numbers, plus hardware revision labels exactly as printed.
• Full software version string including pre-release or build metadata from the system readout.
• Named list of software layers and their suppliers, with dates of supplier-granted access.
• Copies of access-grant wording, portal screenshots and expiry notes if stated.
• Whether the demo routine was locally stored or cloud-triggered, recorded as an observation.
• A note that no repair, reflash or credential change was performed during inspection.

This checklist is a recommended documentation practice, not a claimed requirement of either cited source. The two sources support the general points about software supply chains and version identifiers, not this specific form.

Using Marketplace Categories to Keep Records Usable

Buyers who track several listings can file these observations under the site's own structure. The industry updates category is useful for context on when suppliers change access policies, while the technical guides section is the right place for longer notes on versioning and dependency evidence. Keeping the demonstration-software record separate from the hardware listing prevents later confusion when the same controller appears with different software bundles.

In short, a robot that performs during a viewing is not evidence that its demonstration software is a transferable asset. The due-diligence task is to record hardware identity, exact software versions, supplier access grants and dependency constraints as observed facts, and to request written evidence for each. That written file, not the demo itself, is what a buyer can use to judge what actually changes hands.