Custom Mobility Scooter Accessory Brief: Dealer Confirmation First

Your brief should ask the authorized dealer to confirm three things in writing before anyone opens a design file: which accessory categories the manufacturer supports on the exact scooter model, who installs the add-on, and what installation does to warranty support. Everything downstream, from the candidate list to samples and quotes, hangs on those answers. The reference material behind this article is a stored Pride Go Go accessory page, so the specifics are model-scoped examples for that series rather than a rule for every scooter sold in the US.

The exception that reshapes the whole document is short. Pride Mobility does not provide support for equipment or upgrades you add to your device that isn't made by Pride or installed by a Pride dealer. An add-on can bolt on cleanly and still leave the scooter in a configuration the manufacturer will not stand behind. For anyone carrying maintenance cost and downtime risk, that gap between a cheap part and a cheap ownership cost is the entire argument for rewriting the brief.

Start With Supported Accessories, Not Ideas

Opening with the accessory idea and a target unit price is the first mistake. The document then reads like a shopping list, and sourcing starts chasing molds and samples for an add-on the dealer may never stand behind. Put the confirmation order first: exact model, supported categories, installer, warranty effect. Price, tooling and lead time come after those answers exist, because a quote on an unsupported part is wasted work.

On the stored Go Go page, the manufacturer-made options are extra storage for groceries, canes, oxygen tanks and cell phones, plus rearview mirrors and cup holders designed by Pride to fit the device. That list is where the brief's candidate section should start: those are the categories already framed as fitting that device, and they give the dealer something concrete to confirm or reject instead of an open-ended request.

Warranty effect is the question that decides whether a candidate survives, and a vague answer is not an approval. Ask the dealer plainly what happens to support once the add-on is fitted, and treat an answer that avoids the question as a no. Getting that on paper early is cheaper than discovering it after the first replacement order.

Why a Physical Fit Is Not Dealer Approval

Sourcing teams routinely treat a clean fit, or an online listing that says the part works with the model, as approval. It is not. The consequence shows up months later: the scooter sits in a configuration the manufacturer will not support, the add-on fails, and the dealer and the accessory seller point at each other while the unit is idle and the operator is short a vehicle.

The fix is procedural and cheap. Require the authorized dealer to state in writing whether the specific add-on is supported, and whether dealer installation changes that answer. The Pride page is direct about the boundary: support does not cover equipment or upgrades that are not made by Pride or installed by a Pride dealer. Hold that to the Go Go reference and the version stored today; it says nothing about other makes, other series, or parts that look interchangeable.

Compare Pride-Made Add-Ons With Third-Party Ideas

Shortlisting every third-party equivalent because the category looks simple is the tempting error here. Storage bins, mirrors and cup holders read like low-risk commodity items, so they get priced in parallel with the manufacturer-made versions before anyone knows who carries support. The result is a shortlist that mixes supported and unsupported candidates with no label distinguishing them.

Build the list in two tiers instead. Tier one is the manufacturer-made storage, mirrors and cup holders shown on the Go Go reference page, since those are documented as designed to fit that device. Tier two is third-party equivalents, and those stay excluded or conditional until the dealer confirms fit, installation and post-installation support in writing. Nothing in tier two moves up on the strength of a photo, a marketplace listing, or a seller's assurance.

Keep the model line visible in the brief itself. The Go Go page supports a statement about Go Go accessories, not about scooter accessories in general, and it does not establish that a custom or OEM part of the same category will behave the same way. Writing the model into each row prevents a later reader from generalizing the list into a category-wide claim.

Put Battery Changes Behind a Written Warranty Check

Treating a battery-type change as an ordinary accessory customization is a common and expensive mistake. The Go Go page warns that mechanical changes, especially changing the battery type, could void your warranty. A sourcing team that folds a battery variant into the same RFQ line as a cup holder is inviting a warranty argument it cannot win, and the word could is doing real work in that sentence: it is a risk flag, not a guarantee either way.

Give battery changes their own written confirmation item. Name the exact model, state the intended battery type, and require the dealer's warranty position in writing before any design work or quote is accepted. Until that answer exists, the battery line stays out of the approved scope. This is a procurement gate, not an instruction for how to modify a scooter, and it applies to the reference model rather than to the category.

Ask Who Installs It and Who Supports It

Buying the accessory without assigning an installer and a support owner is how small parts become long outages. When the add-on fails, the dealer says the part was not theirs, the seller says the installation was not theirs, and the scooter waits. Two separate brief lines prevent that: who installs, and who provides support after installation. Both need a named party, not a verbal understanding.

Installer identity matters because the support boundary on the reference page is tied to who made the part and who fitted it. The accessory page shows Pride-designed storage and mirrors as the examples of what fits the device, which gives a dealer something specific to accept or decline. Nothing there defines the obligations of an independent installer, and the brief should not invent them. Ask, leave the field blank, and wait for the answer.

The Obvious Objection Is Dealer Volume

The obvious objection is that this slows the buy down. A dealer can source a cheaper accessory today, the unit price is right there on the quote, and support confirmation looks like paperwork between the team and a working scooter. Look, the cheap part stops being cheap the moment nobody will support it. Downtime, a replacement cycle nobody owns, and a warranty conversation after a failure usually cost more than the delta on the purchase order.

Banning third-party parts is not the answer. Keep the cheaper option as a candidate only if the dealer confirms in writing that it is supported and names who installs it. If that confirmation does not come back, exclude it from the brief rather than leaving it in as an unresolved line. The exclusion on that reference page is the reason the question gets asked; it is not evidence that every third-party part fails, and the brief should not claim otherwise.

A Skeptic's Test for Downtime Reduction

A skeptic would say this just adds forms and makes sourcing slower without changing how often something breaks. The mistake behind that criticism is real: a brief with no stop rule lets unsupported items slide into the RFQ anyway. So give it one. Suppose a single proposed accessory goes through the gate: dealer answers on support status, installer, and warranty effect are required before the item enters the RFQ. If any of the three is missing, the item stays out of the approved brief. That is a process test on one candidate, not a prediction about failure rates, and no test data exist here to predict one.

Run the same scrutiny on the supply side, because dealer confirmation answers only half the brief. Customization capability, MOQ, tooling availability, quoting basis, lead time and the certificates attached to a specific configuration are all open questions until a supplier answers them for the model in question. Log them as RFQ items with a blank answer field. A brief that quietly assumes any of those numbers is worse than one that admits the field is empty.

Today's action is small and mechanical: add three fields to every candidate row, supported yes or no, installer, warranty effect, and hold the RFQ until each field has a written answer from the authorized dealer. Anything still blank stays out of the scope you send for quoting.