TradeKey B2B Wholesale Scraper: Operational Workflows and Analysis

Direct answer

The TradeKey B2B Wholesale Scraper extracts public data from TradeKey.com, a global wholesale platform connecting international buyers and suppliers across 240+ countries. The tool functions across four operational modes: product keyword searches, supplier company directory lookups, detailed product page extractions, and buyer request (buy lead) searches. By setting keyword parameters, country origin filters, verified Gold Key status flags, and minimum order quantity thresholds, teams can build verified supplier matrices, identify incoming sourcing requests, and track marketplace coverage. Data teams evaluate vendor viability by specifying job outputs before choosing narrow filter sets.

Setting acceptance rules before extraction

Automated extraction yields better business outcomes when teams establish explicit filtering constraints prior to starting runs. Specify the exact review objective in a single sentence: "We are validating supplier leads for the procurement team by accepting records with explicit minimum order quantities and verified Gold Key status." Defining hard criteria upfront prevents downstream noise and ensures team leads evaluate actionable vendor records.

Separate mandatory input constraints from secondary contextual indicators. Core validation variables like country location and minimum order units determine record intake. Secondary properties like delivery terms or payment methods serve as descriptive context. Establishing clear exclusion thresholds eliminates irrelevant items before manual inspection.

Practical use cases

These use cases come from TradeKey B2B Wholesale Scraper's published documentation. Each is expanded into an operating pattern so the TradeKey B2B Wholesale Scraper output has a purpose beyond collection.

Use case 1: Sourcing / procurement

Outcome: find wholesale suppliers by keyword, country, and minimum order size.

Question to answer: Which records satisfy the decision rule clearly enough to act on, and which need a second look?

Configure: Start with searchQuery (Keyword to search wholesale product listings for, e.g. phone case, led light, garden tools.), country (Only return products from suppliers based in this country.), minOrderQty (Drop products whose minimum order quantity is below this number (e.g. 100). Products without a parseable MOQ are kept.). Use the narrowest TradeKey B2B Wholesale Scraper values that represent the real task, keep the first result set small, and record why each selected input matters to the TradeKey B2B Wholesale Scraper outcome.

Working method: Write the acceptance rule down before the first record is reviewed, apply it consistently across the batch, and change only one rule or input between batches so any shift in the result has a clear cause.

Deliverable: Create a review-ready queue split by status, with the deciding field cited next to every record. Include the TradeKey B2B Wholesale Scraper source identifier and the collected fields behind every TradeKey B2B Wholesale Scraper decision.

Stop condition: Pause when the same record gets a different classification on a second pass, or a required field is missing often enough to change the outcome. Fix the TradeKey B2B Wholesale Scraper question, comparison rule, or configuration before expanding the TradeKey B2B Wholesale Scraper run.

Use case 2: Seller lead generation

Outcome: use mode=buyLeads to find live buyer sourcing requests (RFQs) for a product category and reach out with a quote.

Question to answer: Which candidates actually meet the qualification rule, and what evidence backs each inclusion?

Configure: Start with buyLeadsQuery (Keyword to search buyer sourcing requests (RFQs / import requirements) for, e.g. led light, phone case, aluminum ingots. Returns real buyer-posted requirements from importer.tradekey.com, not seller listings.), maxItems (Hard cap on emitted records (mode=search: one record per product; mode=byCompanyUrls: one record per resolved company, with that company's product catalog nested inside - maxItems caps the number of companies processed, not the nested product count; mode=byProductUrls: one record per resolved product URL; mode=buyLeads: one record per buyer sourcing request, capped at the ~20 leads a single keyword page returns).), searchQuery (Keyword to search wholesale product listings for, e.g. phone case, led light, garden tools.). Use the narrowest TradeKey B2B Wholesale Scraper values that represent the real task, keep the first result set small, and record why each selected input matters to the TradeKey B2B Wholesale Scraper outcome.

Working method: Fix the disqualifying criteria first so obvious mismatches are removed cheaply, then apply the positive criteria only to what remains, recording the evidence field behind every qualified decision.

Deliverable: Create a shortlist split by qualification status, each entry citing the exact field and value that earned its placement. Include the TradeKey B2B Wholesale Scraper source identifier and the collected fields behind every TradeKey B2B Wholesale Scraper decision.

Stop condition: Pause when two records cannot be confirmed as distinct people or companies, or a qualification decision cannot be traced back to a specific collected field. Fix the TradeKey B2B Wholesale Scraper question, comparison rule, or configuration before expanding the TradeKey B2B Wholesale Scraper run.

Use case 3: Market research

Outcome: track TrustPoints and verified-badge distribution across a product category.

Question to answer: Compared with the last run, what is genuinely new or different, and does it cross the threshold for action?

Configure: Start with verifiedOnly (Only emit products from suppliers with a Gold Key / Gold Key Plus verified badge.), maxItems (Hard cap on emitted records (mode=search: one record per product; mode=byCompanyUrls: one record per resolved company, with that company's product catalog nested inside - maxItems caps the number of companies processed, not the nested product count; mode=byProductUrls: one record per resolved product URL; mode=buyLeads: one record per buyer sourcing request, capped at the ~20 leads a single keyword page returns).), searchQuery (Keyword to search wholesale product listings for, e.g. phone case, led light, garden tools.). Use the narrowest TradeKey B2B Wholesale Scraper values that represent the real task, keep the first result set small, and record why each selected input matters to the TradeKey B2B Wholesale Scraper outcome.

Working method: Store every run under its collection date, key records by a durable identifier rather than position or display text, and only escalate a difference once it has been confirmed against two consecutive runs.

Deliverable: Create a monitoring log that pairs every flagged change with the two runs it was confirmed across. Include the TradeKey B2B Wholesale Scraper source identifier and the collected fields behind every TradeKey B2B Wholesale Scraper decision.

Stop condition: Pause when a single run produces a spike with no second-run confirmation, or the source itself changed structure between collections. Fix the TradeKey B2B Wholesale Scraper question, comparison rule, or configuration before expanding the TradeKey B2B Wholesale Scraper run.

Step-by-step implementation guide

1. Select the appropriate operational mode (search, byCompanyUrls, byProductUrls, or buyLeads) based on your target deliverable.
2. Configure specific input parameters on the TradeKey B2B Wholesale Scraper actor form, defining constraints like searchQuery or country codes.
3. Execute an initial validation run capped at 20 to 50 records to verify payload contents against target field requirements.
4. Export the resulting Dataset into your analysis pipeline, applying downstream deduplication based on unique record identifiers.

Schema overview and configurable controls

The actor interface supports several input fields to structure your collection runs:

• mode: String selecting operational focus. Default: "search".
• searchQuery: Keyword string for product discovery (e.g. "garden tools"). Default: "phone case".
• country: String filter isolating supplier locations by country ID code. Default: "".
• sortBy: Ordering rule, using "relevance" or "trustpoints". Default: "relevance".
• verifiedOnly: Boolean restricting outputs to Gold Key / Gold Key Plus members. Default: false.
• minOrderQty: Integer floor for filtering minimum order quantity requirements.
• maxOrderQty: Integer ceiling for filtering minimum order quantity requirements.
• containsKeyword: Substring filter matching exact product title terms.
• companyUrls: Array of TradeKey supplier company links for catalog extraction.
• productUrls: Array of product URLs for detailed technical page extractions.
• buyLeadsQuery: Keyword string targeting active buyer sourcing RFQs. Default: "led light".
• maxItems: Total record execution cap across target modes. Default: 50.
• proxyConfiguration: Proxy setup handling automatic retry logic during network timeouts. Default: {"useApifyProxy":true}.

Documented technical limits

• TradeKey's /search/index.html results page typically yields 4-6 pages (roughly 60-100 cards) of distinct results for a given keyword/filter combination before the site starts repeating cards; the actor detects an identical repeated page and stops cleanly instead of emitting duplicates. Use more specific/varied keywords, or combine with country/sortBy, to gather larger volumes beyond that.
• Per-product detail pages are supported via mode=byProductUrls (place of origin, packaging, supplying ability, payment type, full image gallery). Per-SKU price-break tiers and buyer reviews are not exposed by TradeKey's server-rendered markup and are out of scope.
• mode=buyLeads returns the single keyword-listing page TradeKey serves per query (typically ~20 buy leads); the site does not expose reliable pagination for this listing, so maxItems above ~20 will not yield more records for a single keyword. Quantity-required and full buyer contact details live behind a login-gated "Quote Now" action and are out of scope.

Data quality checkpoints

Before integrating output feeds into production databases, perform key structural checks:

• Confirm unique identity across product entries using productId or exact sourceUrl strings.
• Confirm that numeric conversions for fobPriceValue and minOrderQtyValue align with raw string text.
• Verify that omitted optional fields remain absent rather than defaulting to misleading dummy values.
• Verify that proxy retry fallback handles periodic marketplace timeouts without raising unhandled exceptions.

Frequently asked questions

Does running this scraper require an active TradeKey account?

No authentication or active account login is needed. The actor extracts information directly from public marketplace directories, product cards, and buyer request pages.

What are TrustPoints on TradeKey listings?

TrustPoints represent TradeKey's internal scoring metric for suppliers. The score measures transaction history, platform longevity, buyer feedback, and corporate verification status.

Why are some numeric MOQ values missing from results?

Some listings utilize non-numeric descriptions such as "Negotiable" in their raw order requirement text. In these cases, the raw string is retained while the parsed numeric value is left absent.

How does proxy configuration handle IP blocking?

Apify Proxy is engaged automatically as a fallback only if tradekey.com blocks/times-out a direct connection from the run's datacenter IP. If secondary blocks occur, the run escalates to residential proxies.

What extra fields are provided by product URL mode?

Using mode=byProductUrls fetches place of origin, packaging specifics, supplying capacity, payment methods, and complete image galleries not present on basic search cards.

Resources

• Access the TradeKey B2B Wholesale Scraper on Apify.