A relationship map is a view of recorded activity within a scope. Use it to identify questions and potential alternatives, not to assume a complete supply chain.
Choose the question before drawing the network
Decide whether you are studying a competitor’s customer base, a supplier’s trading activity, or possible alternative sources for a product. Each question needs a different starting point. Write down the company or product, trade direction, countries and reporting period.
For sourcing teams, a recorded supplier relationship can suggest a business to investigate. For exporters, a buyer relationship can help identify accounts worth researching. In either case, the trade record is a starting point rather than a qualification result.
Resolve the company identity
Normalize obvious formatting differences, but do not merge entities just because their names look similar. Compare available country, address and company information. Keep branches, group companies and uncertain names distinct until you have evidence to connect them.
Document what your map includes and excludes. A partial country dataset cannot establish a company’s entire international network. Missing records should be described as not observed in the selected data, rather than proof that a relationship does not exist.
Read connections with their context
Review product relevance, activity dates, frequency and value where those fields are available. A connection involving a one-time product differs from a repeated relationship in your target category. Check the record scope before comparing the thickness or apparent importance of connections.
The published TradeDaas relationship screen links suppliers, a target company and customers, and also shows the associated countries. This demonstrates the analytical view. Its reporting period is not specified, so it should not be used to make current claims about those businesses.
View the published relationship screen ↗Compare periods before describing change
| Observation | Question to investigate | Unsupported conclusion to avoid |
|---|---|---|
| A new name appears | New relationship, name variant or coverage change? | The company has switched suppliers |
| Recorded value falls | Quantity, product mix, period or data completeness? | The business is losing customers |
| One partner dominates | Does this persist across comparable periods? | The entire supply chain is dependent on one company |
Use the map to plan verification
For each important observation, record its source and one next action. You may need to review a second period, investigate a company’s product offering, or assess whether a potential supplier can meet your requirements. Keep alternatives visible when more than one interpretation fits.
For procurement, trade history does not establish quality, capacity or contractual reliability. For competitor research, it does not reveal the reasons behind business decisions. Combine the map with direct verification and your own market knowledge.
Sources and further reading
This is an original research workflow guide. Sources below support terminology and product examples; the guide is not a market forecast or a live company report.
Put the method to work.
Define your product, market and objective before requesting a relevant dataset.
Build a research brief ↗Explore the solution ↗