The parts drawing belongs to a product generation

Start with the whole product’s identity

The US product page identifies VIDGA single track rail, included ceiling fittings, article 204.929.16. It describes a pack containing one rail, two ceiling fittings, two connectors and two end caps. Those are named contents of the listed product, not a list of spare components available to order individually.

The article number belongs in a whole-product field. It is not the identifier for every small piece supplied with the rail. Similarly, “white” describes the listed finish; it cannot establish the exact identity of an unknown loose fitting found in a drawer. Keep the actual rail’s own product information with the record if it is available, rather than attaching the current article number to it by appearance alone.

Give the instruction document its own reference

The assembly-instructions link on that exact current US page resolves to AA-2234187-5. The retained document’s final panel prints the date 2024-04-10. Record the whole reference including its final 5, instead of shortening it to VIDGA instructions. A document identifier and a product article number are different kinds of information.

The PDF is arranged as foldout panels covering different configurations. Its parts illustrations show the end-fitting identifiers 146958 and 10078455 beside the depicted piece. The useful record preserves both numbers as printed and the document reference containing them. It does not decide, from two adjacent numbers alone, that every physical piece carrying one is interchangeable with the other.

Nor does the revision number establish that an older rail has become obsolete. This comparison has not established an older product’s identity, its original instruction edition or a manufacturer statement about a generation change. A new document date is evidence of that document, not proof that a fitting in someone’s home has changed.

Make the missing link visible in a filled example

In an original fictional example, Jo wants to ask about an end fitting on an existing rail. The current-page record is filled: “Listed article 204.929.16; linked document AA-2234187-5; printed date 2024-04-10; illustrated end-fitting references 146958 and 10078455.” The separate existing-item record reads: “Actual installed rail article and original document not yet established; existing fitting not identified.”

That is not a failed record. It locates the exact gap between finding a reference and identifying the actual replacement. Jo should not quietly copy the current article number into the existing-item field merely to make the request look finished. No rail has been dismantled or fitting physically inspected for this fictional example.

The current product page’s pack contents also remain separate from a support answer. It does not establish whether an individual end fitting is supplied separately, whether a replacement request is accepted or whether a particular part is in stock. Those questions need the actual support response for the identified item.

Send a request that preserves the distinction

A complete unsent enquiry reads: “I need help identifying the end fitting for my existing VIDGA rail. Your current US article 204.929.16 links instructions AA-2234187-5, dated 2024-04-10, whose end-fitting illustration carries 146958 and 10078455. I have not established that my existing rail is that article or that these references fit it. What information do you need to identify my actual rail and the correct replacement, and is that piece available separately?”

Provide actual product evidence through the support service’s appropriate private route when available. Do not force, remove or modify installed hardware merely to complete an administrative description. The document’s assembly pictures are not being converted here into a dismantling procedure.

The useful next state is a manufacturer-supported match, an explicit non-match or a request for further identifying information. Until that answer exists, keep the replacement undecided. A precise part-code request can move the conversation forward without pretending that a product name and a familiar-looking shape have already solved it.