DropshippingLeads / Merchant data knowledge

Researched Merchant Leads: What Sales Teams Should Receive

A screened and researched lead should explain whom to approach, why the merchant is relevant, which product angle to use and where contact can begin. Acceptance checks the agreed research and fields, so representatives can start development without repeating store-by-store research.

Updated 30 Oct 2026 · Merchant observation dates are stated separately.

By DropshippingLeads · Beijing Anbani Technology Co., Ltd.

Agree the research output sales needs

DropshippingLeads discovers merchants through public channels and prepares leads through screening, deduplication, enrichment and human review. Define the supply categories, service markets, target merchants and known-customer exclusions, then agree the product and activity research required.

The output should support a conversation: product fit, observed business signals and a useful product or service to introduce. State fields and verification depth clearly. Unavailable public information or work outside the agreement should not be assumed present in every record.

Review the delivered evidence and outreach angles

CheckWhat to reviewBoundary
Product relevanceProduct or category evidence and fit rationaleShared keywords alone do not establish fit
Advertising activitySource, observation date and recorded statusVisible advertising does not establish transactions or ad performance
Promoted products and bestseller signalsObserved evidence, product reference and outreach angleSignals do not prove actual sales or profit
Public contact routeChannel, source and verification scopeNot necessarily a decision-maker’s direct email
Duplicates and exclusionsBatch checks and supplied-list comparisonDomain deduplication is not entity resolution

Check whether representatives can start a real conversation

A representative using the batch should be able to read the product rationale, understand any ad or product observations, choose a cooperation angle and prepare contact through the recorded route. They should not have to restart research into what each store sells and why it fits.

Use the agreed sampling or review procedure to report exceptions. Distinguish missing contracted fields, evidence that cannot be checked, screening mismatches and a merchant that has not replied. These are different issues.

Keep observation dates and unknown fields clear

Advertising and product pages change. Record sources and actual observation dates; import or delivery dates should not replace them. Agree the time window for recent activity. Missing public ad evidence does not prove a merchant is not advertising or operating.

Sales markets and business location are different. Mark unknown contact roles, revenue, profit or purchasing plans. Relevant products and advertising may support an outreach rationale but do not establish a confirmed buyer.

Define the known-customer exclusion scope

If existing customers or previously contacted merchants must be excluded, provide the list this project is permitted to use and agree the matching method. Comparison with one supplied list establishes exclusions against that list only. It does not establish that every record is new to the platform’s entire customer history.

A merchant may operate more than one domain, and a domain does not necessarily map directly to a single legal entity. If entity-level exclusions are required, agree the evidence used to group related sites. URL deduplication alone is not entity deduplication.

Separate the public sample from the formal batch

The website sample illustrates store URL, sales market, contact details, best-selling product link and supplier link. Ad observations, product research, relevance explanations and dates in formal deliveries follow the agreement. Sample fields do not replace a project specification.

The free MCP’s 14 categories with 100 records each may overlap and form an experience pool, separate from formal researched leads. Quarterly pricing purchases a defined batch delivered by email, not unlimited research or automatic database access. Agree exception review, replacement or supplementation as well.

Questions answered

Does a larger list always offer better value?

Assess quantity alongside relevance and the work needed to use it. First confirm that the records meet the agreed criteria and support the sales workflow, then evaluate batch size and price.

Must our team screen every merchant again for acceptance?

A formal delivery should not require the customer to repeat initial screening. Use the agreed sampling or review procedure and report exceptions rather than assuming every record requires research from scratch.

Does a public email identify a purchasing decision-maker?

No. A public contact route and a verified decision-maker are different pieces of information. Check the delivery specification for any role-level verification.

Does every record include advertisements and bestseller information?

That should not be assumed. Public evidence and project scope differ. Agree research fields, coverage, observation dates and unknown-field handling before delivery.

Sources and scope

Continue reading