How to handle conflicting sources in a supplier profile

A brochure may name one production site while a later quote names another; a register may show a changed legal name. Choosing the most convenient version hides the conflict.

What the primary source can establish

The U.S. International Trade Administration due diligence guide is the first-party reference for this guide. The guide separates country, company or partner, and purchasing risks and calls for continuing due diligence. It does not investigate or endorse any named supplier on Source Ledger. The steps below are our editorial method for making a buyer-facing field more precise.

A field-level check

Build a side-by-side note with each exact claim, source, date and scope. Ask the relevant party to reconcile the difference. If the conflict affects identity, payment, product or quality, pause the affected public field.

Write down the exact field, the party that supplied the information, the original document or page, the date seen and the scope of the check. If a reviewer took an action, record that action rather than a general “verified” label. Reopen the source when the transaction or underlying document changes.

Where the inference stops

Sources can differ for benign reasons such as a move or product revision. Do not accuse the supplier without checking. But do not merge contradictory statements into a confident composite claim.

A missing answer is a question to resolve, not permission to substitute a guess. Separate a statement by the supplier from a public record and from a documented human review. No source in this article proves a quality ranking or an existing buyer relationship.

What to record before deciding

Keep the field unresolved until a traceable explanation and current evidence support one account. If previously published, correct it with a dated note.

This entry describes how to evaluate evidence. It is not a dossier for a real company, an approval decision or a substitute for transaction-specific professional review.

Common question

Can the newest document always override the older one?

No. Confirm that the documents concern the same entity, product and field before treating one as an update.

Related guide

Continue with A final editorial review before publishing a named supplier card for another field-level check.