Official, Source-Supported & Company-Reported Relationships
Updated
Compare relationship labels by their original source, product-line scope, territory and checked date.
Read a relationship label as a description of its source. A direct brand confirmation, a relationship published in a brand-owned source and a company-reported claim should retain their distinct attribution. Check the current scope with the named OEM for a specific transaction.
Read a relationship label as a description of its source. A direct brand confirmation, a relationship published in a brand-owned source and a company-reported claim should retain their distinct attribution. Check the current scope with the named OEM for a specific transaction.
DistributorIndex is a manufacturer. Our brand, country and industry resources also retain attributed records about third-party companies. Their channel relationships and OEM policies belong to the named organisations; our own supply scope is defined in the project proposal.
Identify what supports the relationship
Read a relationship label as a description of its source. A direct brand confirmation, a relationship published in a brand-owned source and a company-reported claim should retain their distinct attribution. Check the current scope with the named OEM for a specific transaction.
Compare the evidence rather than a risk ranking
Our relationship labels identify the basis of a record. They do not assign an ISO supplier tier, a failure rate, an inspection sample size or a payment threshold.
Scroll horizontally to see all table columns on smaller screens.
| Source basis | What to read | Order follow-up |
|---|---|---|
| Direct brand confirmation | The named entity, scope and confirmation date | Confirm relevance to your product and territory |
| Brand-owned directory or announcement | The original entry and its product-line scope | Check the current entry and quotation entity |
| Company-reported relationship | The company’s attributed statement | Seek relevant current OEM confirmation |
Check entity, territory and product scope
Match the quoted legal entity and branch with the source. Review the products, territory and any validity period actually stated. Request clarification when an old letter or a group-level logo is used for a different business unit.
Apply the OEM’s actual commercial policy
Rockwell Automation’s policy states that its warranty and firmware/software eligibility depend on authorised purchasing. Apply that policy to Rockwell products; check each other OEM’s own terms for its products.
For another brand, use that brand’s current warranty, licence and support policies. Fees or restrictions must be tied to the applicable product and contract; a directory label cannot establish an automatic penalty.
Set inspection and commercial terms for the order
Choose checks with the responsible quality team and agree payment, inspection and delivery milestones in writing. Different labels do not automatically require different deposit percentages, destructive tests or sample quantities.
Ask for the relevant current records
Keep source links, dates and the written product scope with the quotation. Use our correction contact when the public record needs updating.
Scroll horizontally to see all table columns on smaller screens.
| Input | Purpose | Useful format |
|---|---|---|
| Product identity | Match the offered equipment or component | Complete part number, revision, condition and quantity |
| Destination and site | Define regional and installation requirements | Country, site, utilities and access information |
| Software and interfaces | Define the integration and entitlement scope | Firmware, licence, controller and interface references |
| Inspection and acceptance | Agree the applicable checks | Samples, conditions, acceptance criteria and responsible team |
| Delivery and support | Compare the complete commercial scope | Packing, named delivery point, installation and support responsibilities |
Sources and application
Reviewed 20 October 2026. OEM and government links below support their stated scopes. Inspection methods and sample quantities must come from the applicable product requirements, contracted inspection plan and current standards used by the responsible quality team. The planning examples use stated assumptions; they are not measured failure rates, market averages or mandatory purchasing thresholds.
Rockwell Automation’s policy states that its warranty and firmware/software eligibility depend on authorised purchasing. Apply that policy to Rockwell products; check each other OEM’s own terms for its products.
Our third-party research records preserve the named company and original source. Explore the distributor records, brand records, country records and industry records. Our own manufacturing scope is described in About and the quality process.
Related product and channel guides: what a listing on this directory means, how to verify a distributor listing, how to use brand × country pages, ADI US account approval guide, ADI credit application document checklist, used Cisco license transfer cost evidence, Cisco grey-market warranty checklist, Hikvision firmware region mismatch checks, Axis project pricing distributor handoff, how to find a brand distributor, how to research security camera distributors, how to research networking distributors.
Frequently asked questions
What should I include in a supplier enquiry?
Send the complete product or system requirement, destination, quantity and desired delivery scope. Ask for the selected configuration, applicable documents, inspection plan and support terms in the quotation.
Do relationship labels determine inspection or commercial terms?
No. Read the cited source, scope and checked date, then agree the checks and commercial terms for the particular product and order.