Where a Custom Mobility Scooter's Medical Purpose Boundary Belongs

Does a battery, wheels and a seat make a custom mobility scooter a medical device? Not on their own. The regulatory description turns on intended medical purpose, and purpose is not a component a buyer can inspect. That distinction decides how the rest of a sourcing brief should be written.

Everything below sits inside one scope label: a Pride Go Go scooter accessory and battery procurement reference. The manufacturer statements used later apply to that series and to the stored version of those pages, not to the scooter category at large. Inside that boundary, the medical-purpose question belongs in a custom mobility scooter brief as a recorded intended-use and change-control decision rather than as an inference from hardware. A brief that lists materials, dimensions and colors while leaving purpose unstated has documented everything except the part that decides classification.

Does a Battery and Wheels Make It Medical?

21 CFR 890.3860 describes a powered wheelchair as a battery-operated device with wheels that is intended for medical purposes to provide mobility to persons restricted to a sitting position. The description mixes physical elements with a use statement. A battery, wheels and a structure for a seated user can be checked against a specification. The phrase intended for medical purposes to provide mobility cannot be checked that way, because it describes a purpose rather than a part.

Purpose is carried by documents. It lives in labeling, in the product page text, in the sales script and in the specification sentence the buyer sends to the supplier. Those are the places a procurement reader can read a purpose from, which means a buyer who asks only for a bill of materials has asked for three quarters of the answer and called it complete.

Two scooters assembled from identical components can therefore sit on different sides of the line, and no inspection of either one will show which. The difference is not hidden in the machine. It is missing from the paperwork.

What Your Brief Must Fix Before Any Quote

One sentence has to be written before a supplier is asked for anything, and it names who the device serves: a user restricted to a sitting position, or a user who stands and walks and wants to cover ground faster. Those are different products with different frames, different stability demands and different liability questions, and a supplier cannot quote against a sentence that has not been decided. Write the sentence, put it at the top of the brief, and stop treating it as a marketing line to be softened later.

The second field is the environment the device is specified for. Indoor flooring, thresholds between rooms, outdoor pavement, loading into a vehicle: each one changes what the supplier has to answer for, and each one changes which configuration is even worth quoting. A brief that omits this field gets a quote for whatever the supplier had on the shelf.

The third field is the claim text that is allowed to appear in the manual, on the product page and in distributor material. The reason to lock it early is inheritance: every downstream document copies that sentence, and none of the people who copy it will go back and question it. An unfixed sentence propagates into drawings, labels and listing drafts that nobody re-reads, and by the time someone does, the run is already built.

Why 21 CFR 890.3860 Is a Comparison, Not a Label

The phrase in 890.3860 describes one device entry. It is not a test that any other product can pass or fail, and the reason is structural: a description of what one entry covers tells you what to look at, not what to conclude. Treating it as a classifier is how a sourcing team ends up writing a regulatory category into a purchase order that no document supports.

What the text can do is serve as a comparison checklist. For each element the brief records whether the proposed configuration matches, differs, or cannot be determined from the documents on hand. Four lines, three possible states each, and the value is in the unknowns, because a row marked undetermined is a question for the supplier rather than a conclusion for the buyer.

The similar-looking trap is version drift. The quoted text comes from the 2025 edition of Title 21, and an annual edition plus later rulemakings is not a complete compilation of everything in force at the moment of shipment. Name the edition the brief worked from, and re-check the current text and the certificate scope for the exact configuration before goods leave.

Where Custom Parts Move Warranty and Support Responsibility

Pride Mobility states that it does not provide support for equipment or upgrades added to the device that are not made by Pride or installed by a Pride dealer, and separately that mechanical changes, especially changing the battery type, could void the warranty. Both statements are tied to the Go Go series pages they appear on and to the version stored, so they describe that series, not a rule for every scooter on the market.

Take a side here, because a brief that stays neutral on this point gets argued about after delivery. Support and warranty responsibility should follow the party that made and installed the part, not stay with the original equipment maker by default. The condition attached to that position is narrow and worth saying out loud: it rests on two model-page statements about one series, it says nothing about any other supplier's policy, and it does not predict how a specific warranty claim would be decided.

Which means a custom part does two things at once. It changes the hardware, and it reassigns who answers the phone when something fails. The brief has to name that party in writing, as a condition of the order rather than as a courtesy note, and keep the original maker's coverage out of the promise column once the part is no longer theirs.

A Hypothetical Battery Change, Traced End to End

This is a thought exercise, not a test result and not an instruction to modify anything. Suppose a buyer specifies a battery type different from the reference configuration on the Go Go pages those manufacturer statements come from. Several fields move and one stays fixed.

The fixed field is the intended-use sentence, because it describes the person the device serves and a cell chemistry does not change who sits in the seat. If the purpose statement has to change when the battery changes, it was never a purpose statement.

The support answer moves, because coverage on those pages is tied to parts made by the manufacturer or installed by its dealer, and a battery sourced elsewhere is neither. The warranty exposure moves with it, and that shift is the one a procurement brief most often forgets to record.

Charging and electrical compatibility turns into an open supplier question. Neither page carries a voltage window, a charge profile or a compatibility list, so the brief asks the supplier for documentation on the proposed configuration instead of importing a number from an unrelated product. The permitted claim text stays capped at whatever the eventual file covers; if the documents do not describe the new configuration, the product page cannot either.

The value of walking the trace is the arithmetic it exposes: one change re-prices several fields besides the one changed, and the buyer who budgets for a battery has budgeted for a fraction of the work.

Which Parameters Actually Define the Boundary

The parameters that carry the boundary are defined by function, not by numbers. The first is user posture and seating configuration, because that decides who the device serves and therefore whether the purpose sentence can be written as mobility for a seated user at all. The second is battery type and charging architecture, because that is what has to be re-verified every time the power source moves, and it is the change the manufacturer page singles out.

The third is control and interface layout, because it decides how the user operates the device and whether the operating instructions describe the unit that was actually shipped. The fourth is the labeling sentence itself, because it decides what is claimed, and a claim is often the first part of the boundary a regulator or a distributor reads.

None of those four comes with a value attached here. The acceptable value for each arrives from the chosen product's own documents and from the agreement between buyer and supplier, which means a brief that fills them from a different model's sheet has filled them with someone else's answer.

Five Blocks That Must Agree in the Same Brief

The brief holds five blocks, and the useful test is whether they agree with each other rather than whether each one is filled in. The first is intended use and the user population the device serves. The second is the market and classification status still to be confirmed from that product's own documents. The third is the configuration and the change log measured against the reference unit. The fourth is the split of warranty and support duties. The fifth is the evidence file plus the open questions that go out with the RFQ.

They behave as one chain because block three drives the others. Change a part there and block one must be re-read to confirm the purpose sentence still describes the same user, block four must be re-read because the support answer follows whoever made the part, and block five must be re-read because the new part needs its own paper. A checklist lets a team tick four boxes and miss the fifth without noticing. The chain does not, which means the block that moved stays visible in the three that depend on it.

Three Beliefs That Quietly Break the Boundary

Three beliefs corrupt a brief even when every individual sentence in it is accurate. The first is treating the phrase FDA approved as a synonym for a listed classification. It is not the same thing, and it cannot be written into a sourcing document unless that specific product's own paperwork says so; a clearance reference for one device does not describe a configuration that has not been filed.

The second is assuming that matching the words of a definition is the same as being assigned to it. The 890.3860 description turns on intended purpose, so selling and labeling a battery-operated, wheeled device for recreation does not by itself place it in that entry. The reason this belief survives is that it is half right: the hardware does match, and the matching is exactly what makes the mistake feel settled.

The third is carrying a reference series across as if it were an OEM product. A dimension, a connector choice or a warranty sentence lifted from a Go Go page belongs to that series and the stored version of that page. None of them transfer to a custom build from a different supplier, and a brief that copies them forward has imported assumptions nobody agreed to.

When the Supplier Says It Is Already Medical

The objection that survives all of this is short: the supplier already said it is a medical device, so why is the field still open? The reply is not an argument. Keep the classification field in the brief as a visible placeholder until four items arrive: the classification or listing document naming that exact product, the labeling draft, the scope of whatever certificate is offered, and the name of the party that will support the custom configuration.

A sales assertion is not a document, which leaves an open field as the only honest position until paper that names the product lands on the desk. That costs the buyer a little schedule room and saves the far larger cost of a promise written into a purchase order that no certificate, label or support agreement ever backed.