Selecting and approving a power window switch should not be based on appearance, one catalog field, or a supplier statement alone. A useful RFQ must identify the vehicle application, door position, electrical architecture, connector, functions, validation evidence, commercial terms, and approval authority. The sample plan must then prove the agreed requirements without treating one passing switch as proof that the completed power-window system is safe or compliant.
This checklist is for automotive buyers, engineers, quality teams, and aftermarket program managers. It covers driver master switches, passenger or rear-door switches, direct-contact designs, resistance-coded controls, and electronic modules. The controlled vehicle drawing, wiring information, customer specification, approved sample, and destination-market requirements always take precedence over general guidance.
Table of Contents
- 1. Freeze the RFQ input before requesting a quote
- 2. Define functions, architecture, and the safety boundary
- 3. Build a sample and validation plan
- 4. Control commercial, packaging, and change inputs
- 5. Release the project with evidence
1. Freeze the RFQ Input Before Requesting a Quote
Identify the exact application
Start with vehicle make, model, model year, body style, trim, destination market, production date or VIN range, steering configuration, and door position. State whether the request is for a driver master switch, front-passenger switch, rear-door switch, or an integrated control panel. A model year alone is weak evidence because a harness, door module, bezel, or feature set can change during production.
Record the complete OE service number, including suffixes, plus any supplier number, drawing number, supersession, and customer stock code. Label each reference by source. A molded housing number may identify a subcomponent or tool rather than the complete service assembly. Use Tonful’s power window switch OE-number cross-reference guide to structure the research, but do not use a cross-reference as final fitment approval.
NHTSA vPIC can support manufacturer-reported vehicle identification data. It does not confirm switch interchangeability, pinout, power-window safety functions, audit compliance, or product acceptance.
Control the physical and electrical interface
Provide an original sample or approved master, supported by clear photographs and a controlled drawing. Photograph the front, rear connector, label, mounting points, keying features, and installed orientation. For the connector, define cavity count, populated terminals, terminal size, keying, latch, polarization, seal interface, and pin numbering orientation. A mating connector and matching pin count do not prove an identical circuit.
For the housing, define overall dimensions, mounting clips or screws, locating features, bezel profile, button clearance, grain, color, symbols, and acceptable appearance. If an initial drawing is unavailable, mark dimensions taken from a sample as provisional until the buyer releases a controlled inspection drawing.
The RFQ input should answer these questions before price comparison:
| RFQ input | Minimum controlled information | Common approval error |
|---|---|---|
| Vehicle application | Market, model year or production range, trim, LHD/RHD, door position | Assuming one switch fits every trim |
| Part references | Full OE number, suffix, source, supersession status | Treating a molded number as the service number |
| Mechanical interface | Drawing, datums, tolerances, mounting and bezel details | Approving from a front photograph |
| Connector | Mating face orientation, keying, latch, terminals and cavity map | Counting pins without checking assignments |
| Electrical definition | Pinout, schematic, architecture, load or signal requirements | Applying power to an unknown terminal |
| Function set | Position/output matrix and human-interface details | Writing only “one-touch” or “with lock” |
| Appearance | Color, grain, icons, lighting and approved master | Judging backlight from an uncontrolled photo |
For a broader pre-RFQ screening process, see the power window switch buying guide.
Conceptual illustration only—not a controlled drawing or inspection record. Verify dimensions, connector orientation, and application against project documents and approved samples.
2. Define Functions, Architecture, and the Safety Boundary
Create a position-and-output matrix
Do not describe the switch only as “master,” “single,” or “auto.” List every control and every detent: manual up, manual down, one-touch up, one-touch down, neutral, window lock, door lock, unlock, mirror selection, mirror direction, child lock, and illumination where applicable. Record whether each action is momentary, maintained, two-stage, direct-contact, resistance-coded, or electronically communicated.
Also define actuation direction, travel, force profile, detent, return, free play, sound, icon orientation, backlight color, brightness, dimming behavior, and light leakage. If manual and one-touch commands share a rocker, specify the transition between the first and second stage. Acceptance limits must come from the customer drawing, technical specification, or approved master; there is no universal tactile value for every switch.
Identify which component controls the window
A switch may reverse motor current directly, send a resistance-coded request, or communicate with a door module. Some master assemblies contain a PCB, microcontroller, LEDs, diagnostics, or a network interface; others are mainly mechanical contacts. The power window switch versus motor versus regulator guide helps separate these roles, but the vehicle schematic and interface specification are the controlling sources.
For direct-contact designs, define the terminal functions, specified electrical load, polarity-reversal logic, voltage drop or contact-resistance method, isolation, and temperature-rise limits as applicable. For resistance-coded controls, provide the commanded values and tolerances at each position. For electronic modules, add hardware and software identifiers, supply range, quiescent current, wake and sleep behavior, communication, diagnostics, transient and reverse-polarity requirements, programming, and vehicle configuration.
Never infer architecture from nominal voltage, pin count, terminal size, or exterior shape. A loose switch that responds on a bench may still be incompatible with the vehicle network, door module, motor controller, or learned position data.
Define one-touch, anti-pinch, and relearn responsibility
If one-touch or automatic closing is included, identify whether obstacle detection, automatic reversal, position learning, current sensing, and initialization belong to the switch, motor controller, door module, or vehicle system. Record which functions are implemented in switch hardware, switch software, or another controller. State the required initialization or relearn procedure after installation, battery disconnection, motor replacement, loss of learned limits, or module replacement.
Do not use “auto-up/down included” as a complete requirement. Define:
- which windows have express-up, express-down, or both;
- whether a two-stage rocker or another actuation method is required;
- which controller stores upper and lower window positions;
- how obstacle detection is performed and which component commands reversal;
- what diagnostic state or initialization is required before the feature operates;
- how manual mode, lockout, ignition state, retained accessory power, and remote commands interact; and
- who is responsible for component approval, subsystem validation, vehicle validation, and regulatory assessment.
For covered U.S. applications, 49 CFR 571.118 (FMVSS No. 118) addresses power-operated windows and includes requirements concerning operating conditions, actuation controls, and qualifying automatic-reversal systems. NHTSA’s FMVSS 118 laboratory test procedure describes an enforcement test approach, including actuation-device and automatic-reversal checks. The regulation is controlling; the laboratory procedure is not a substitute for the regulation or a complete certification plan.
This is a system-level approval boundary. A passing switch sample does not by itself establish compliance of the completed power-window system. The vehicle manufacturer or responsible system integrator must assess the applicable vehicle, switch, controller, motor, regulator, sensors, software, learned positions, wiring, and installed behavior for the destination market.
3. Build a Sample and Validation Plan
Allocate production-intent samples by purpose
Agree the sample stage before ordering: appearance mock-up, engineering sample, tooling sample, production-intent sample, or retained approval sample. Identify the manufacturing site, tooling, material, electronics, software revision, process revision, and date code for each submission. A hand-built engineering sample should not be represented as proof of a stable production process.
Define sample quantity from the test plan rather than copying a generic number. Keep separate units for dimensional inspection, functional checks, destructive teardown, environmental exposure, endurance, and vehicle installation where these tests can affect later results. Tag every unit and retain traceability from the report to the tested part. Reserve an approved master for future receiving inspection and change comparison.
Use measurable acceptance gates
The validation plan should name the method, equipment range and accuracy, conditioning, sample quantity, sequence, acceptance criteria, invalid-test rule, retest rule, report format, owner, and approving authority. Select tests according to the architecture and application environment.
| Approval gate | Evidence to review | Release question |
|---|---|---|
| Identity and traceability | Part label, revision, lot, site, tooling and sample log | Is this the part and process being quoted? |
| Dimensions and fit | Layout report, gauge result and installed evaluation | Does it fit without panel or connector modification? |
| Connector and pinout | Mating check, cavity map and terminal-function table | Are keying and every circuit assignment correct? |
| Functional matrix | Output for every rocker, detent, lock and illumination state | Does each input produce the specified result? |
| Electrical performance | Resistance or voltage drop, isolation, load or signal results | Were the specified method and limits used? |
| Electronics and software | Interface, diagnostics, current states and revision records | Does the approved hardware/software combination match? |
| Durability and environment | Test profile, interim readings, final data and failure record | Did performance remain within limits after exposure? |
| Vehicle/system behavior | Installation, relearn, one-touch, lockout and safety assessment | Has the responsible party approved the complete system boundary? |
Dimensional checks should use defined datums and tolerances. Electrical results should identify the circuit, command position, supply condition, load, stabilization time, connection method, instrument, and pre/post-test readings. For diagnostic bench methods, Tonful’s guide to testing a power window switch explains basic checks, but troubleshooting steps are not a qualification standard.
Durability evidence should include the electrical load or signal condition, actuation sequence, rate, temperature, interim inspections, completed cycles, and failure mode. Environmental testing may address temperature, thermal cycling, humidity, vibration, chemicals, dust, or ingress when required by the customer specification. Require functional and electrical measurements before and after exposure; chamber completion alone does not prove acceptable performance.
If a result is invalid because of fixture failure, power interruption, wrong software, operator error, or equipment outside calibration, document the reason and disposition. Do not quietly replace failed data. A retest plan should define whether the original result remains in the report, what corrective action was taken, and whether additional samples or a new production lot are required.
Conceptual workflow only—not a test report or approval record. Sample status and release authority must be defined in the project plan.
4. Control Commercial, Packaging, and Change Inputs
Make the quote comparable
Give every supplier the same commercial assumptions: prototype quantity, annual forecast, order pattern, price-break quantities, destination, currency, trade term, packaging configuration, label data, and required documentation. Ask suppliers to separate unit price, tooling or non-recurring engineering, samples, validation, packaging development, freight, and future change costs. Record quote validity and the conditions behind sample and production lead times.
MOQ, sample availability, tooling, validation scope, and lead time are project-specific. Obtain them in writing for the named part and revision. Do not apply a figure from another switch family, package, or customer program.
Packaging requirements should define individual protection, electrostatic controls where appropriate, connector and button protection, inner quantity, master-carton quantity, barcode format, part and revision marking, country-of-origin information, date or lot code, customer artwork approval, and transport validation. The receiving plan should identify what is checked per unit, per lot, or by sampling.
Freeze production and change control
The approved baseline should connect the drawing, bill of materials, circuit or pinout, material grades, contact system, resistor values, PCB and software revisions where applicable, appearance master, process flow, control plan, test methods, packaging, and retained sample. Define first-piece checks after startup, tool change, adjustment, maintenance, material change, or restart.
Require written notification and approval before changes to resin, color, contact material or plating, spring, lubricant, terminal, PCB, electronic component, firmware or software, tooling, manufacturing site, sub-supplier, process, test method, artwork, label, or packaging. The notification should explain the reason, affected stock and lots, validation evidence, and proposed implementation date.
Use Tonful’s power window switch manufacturer audit checklist to review traceability, process controls, sub-supplier management, nonconforming-product control, and change management. Audit findings should be closed with evidence; a supplier questionnaire alone is not approval.
5. Release the Project With Evidence
Before issuing sample approval or a purchase order, confirm that:
- the vehicle application, door position, steering configuration, and OE references are revision-controlled;
- the housing, mounting, connector keying, terminal map, pinout, and architecture match the controlled requirement;
- every manual, one-touch, lock, mirror, illumination, and communication function is defined and verified as applicable;
- obstacle detection, reversal, position learning, initialization, and system-level approval responsibilities are assigned;
- sample identity, quantity, production intent, test methods, limits, raw data, deviations, and approval status are traceable;
- pricing, MOQ, tooling, samples, lead time, packaging, labeling, logistics, warranty handling, and change notification are agreed in writing; and
- the approved sample and baseline records are retained for receiving inspection and future change review.
Use clear dispositions: approved, conditionally approved, rejected, or unverified. Conditional approval should name the open item, interim control, owner, due date, and release restriction. “Looks acceptable” or “bench test passed” is not a production release record.
Tonful’s current automotive power window switch page can be used to begin a product enquiry. Send the application list, complete OE references, original sample or controlled drawing, connector and pinout, function matrix, architecture, destination market, forecast, packaging needs, and required evidence. Ask Tonful to confirm applicable models, master or single-door scope, direct-contact, resistance-coded or electronic architecture, PCB/software/tooling/backlight options, validation evidence, samples, MOQ, lead time, and production terms for the named project in writing before relying on them.
The objective is not to collect the largest document bundle. It is to create one traceable chain from vehicle application and system responsibility to quotation, sample evidence, approval, receiving inspection, and controlled production.
