A shared white-goods connector RFQ can standardize core fields while keeping washer and refrigerator application conditions separate. The connector, mating part, harness, environment, quantity, and evidence boundary must remain explicit.

Contents

• Part 1. Define shared RFQ scope
• Part 2. Capture each appliance interface
• Part 3. Record environment and harness conditions
• Part 4. Request evidence and quantities

Part 1. Define shared RFQ scope

Start with the buyer’s question, program, connector and mating definition, and required decision. A shared template should not hide application-specific unknowns.

Part 2. Capture each appliance interface

Record connector, mating part, terminal or housing definition, keying, drawing revision, and whether the request concerns washer, refrigerator, or both.

Important: A shared checklist does not prove cross-appliance compatibility or approval. Source: IPC.

Part 3. Record environment and harness conditions

Keep appliance environment, routing, support, access, duty, and enclosure information with each program row. A loose product image cannot replace these inputs.

Part 4. Request evidence and quantities

RFQ field	Provide	Purpose
Interface	Drawings, mating definition, revision	Identify the connection
Application	Washer/refrigerator, environment, harness	Separate conditions
Quantity	Sample and expected inquiry scope	Clarify request
Evidence	Records, open questions, change notice	Make response reviewable
## Part 5. Control changes and alternates
Keep a revision and change record when a terminal, housing, route, environment, quantity, or requirement changes. Do not carry one program’s evidence into another without review.
## Part 6. Use ZUCH inquiry routes
For family discovery, review the ZUCH appliance solution route, then send controlled inputs through the sample request route. The compressor durability guide provides a separate application lens.
## FAQ
### Can one checklist cover both programs?
Yes, for shared core fields, but each program’s environment, harness, duty, and evidence boundary must remain separate.
### What interface records belong in the RFQ?
Send connector and mating drawings, terminal or housing definition, keying, and revision.
### Why separate washer and refrigerator rows?
Their application conditions and open questions may differ even when the RFQ template is shared.
### Can a product page prove fit?
No. A route is commercial discovery context, not buyer-specific fit evidence.
### When should the RFQ be revised?
Revise it after a configuration, environment, quantity, requirement, or evidence change.
### What belongs in the RFQ?
Include interface, application, harness, quantity, sample objective, requested records, revisions, and change-control expectations.
## References
– IPC: interconnection documentation context.
– IEC: application-evaluation context.