1. Separate the Housing, Contacts and Connector Assembly

A connector inquiry can name a family while leaving the deliverable undefined. Ask whether the requirement is for an empty housing, loose contacts, a populated header, a finished cable assembly or a kit. Keep each manufacturer's complete product number beside that item. A purchasing description should make clear what the supplier must deliver and what the existing assembly already provides.

TE's public product information distinguishes a housing from a PCB connector assembly and identifies contact loading separately. These categories support a useful preparation question: are the required contacts included in the offered line? They do not show what a particular seller has packed or whether a customer's previous assembly used the same configuration. Confirm included items in the written response rather than assuming a family description covers everything.

Record housing and contact quantities as separate supply lines. These totals do not automatically establish a quantity of complete connector sets. Ask the supplier to confirm what each line includes, and keep the set quantity unresolved until the written deliverable is defined.

Keep photographs and old labels as identification leads. Link them to an existing BOM reference or assembly drawing when one is available. If the old code is incomplete, record the unknown characters instead of creating a plausible replacement code. A design owner can then explain whether the task is replenishing a known item or identifying a component whose original documentation is missing.

  • Name the physical deliverable and its complete product number.
  • Identify separately ordered contacts and accessories.
  • Keep unknown identity fields visible for clarification.

2. Identify the Exact Mating Counterpart and Drawing

Record the item already on the other side of the connection. A candidate can have familiar features while differing in the interface that must mate with that counterpart. Ask engineering to identify the controlling drawings and their revisions for both sides. TE's application specification states that the part-specific customer drawing takes priority over the application document; the product pages likewise direct design activity to the product drawing.

Use an interface review list covering polarisation, keying, contact arrangement, mating orientation, retention and installation access. These are questions for the applicable drawing and assembly, rather than conclusions from a photograph. Keep the mating interface distinct from the board attachment: a header also needs a documented relationship with the PCB and the available enclosure space.

This article provides an unnamed review workflow. It does not present a measured mating pair, drawing dimensions or a tested footprint. If the current drawings cannot be read, identify that gap and request the applicable documents from the design owner or manufacturer. An older catalogue association can help locate information, but should remain a lead until the relevant technical evidence is available.

  • Identify the counterpart and controlling document revision.
  • Review orientation and retention as well as contact layout.
  • Record unavailable drawing evidence as an open question.

3. Keep Contact and Termination Variants in the Requirement

Once the interface is identified, record which contacts and termination construction belong to the requested assembly. Ask the responsible engineer to check contact type, specified finish and the relevant wire or board connection. TE's application documentation distinguishes connector configurations and contact application contexts. Its family discussion should not be converted into a performance rating for an unidentified customer assembly.

For a wire-side requirement, keep the approved contact code with the relevant conductor and insulation requirements. For a board-side item, preserve the exact termination and mounting reference. If tooling, seals or retention accessories form part of the defined deliverable, list them individually. These checks help expose missing configuration information without treating the article as a crimping or assembly instruction.

Record proposed differences in a short exception table: original item, candidate item, changed feature, document reference and review owner. Similar finish wording or a familiar connector family is insufficient to approve a change. The design and quality teams decide which evidence and evaluation their application requires before the proposed configuration becomes a purchasing requirement.

  • Link contacts and termination details to exact identifiers.
  • List required seals, retention parts and tooling separately.
  • Keep candidate changes outside the confirmed requirement.

4. Resolve Interface Differences Before Requesting Supply

Prepare one concise interface record for the inquiry. Include the requested supply item, counterpart, relevant drawings, approved configuration and unresolved questions. Assign a reviewer to each difference. Where documentation is missing, ask for identification assistance or technical clarification rather than labelling a candidate a drop-in replacement.

Use the existing BOM revision process to control the requirement that purchasing sends. This connector review establishes the interface decision; the linked BOM guide explains population and version controls. If an engineer approves a changed connector configuration, update the affected product numbers and assembly references before comparing supplier responses against it.

For an ICULTRA sourcing inquiry, share the defined connector item and its documented counterpart information, together with quantity and delivery needs. Ask the supplier to distinguish the requested item from any proposal and identify what its offer includes. Availability and an engineering approval are separate confirmations. Retain the exception record so a later quote cannot silently substitute a different housing or contact set.

Sources and further reading

Manufacturer documents support the product categories and drawing-priority examples. The interface record is a preparation suggestion; no named pair, numeric geometry, physical fit, engineering approval or availability is established here.