Alibaba Scraper & Supplier Profile Details

Alibaba Supplier Scraper — Products, Profiles and OEM/ODM Tags

Alibaba Supplier Scraper turns an Alibaba search or category URL into two linked layers of structured JSON: the product listings behind the query, and a public company profile for every unique supplier those listings surface — business type, years on Alibaba, factory floor area, store rating, location, and structured OEM/ODM service-capability tags. Every row is typed JSON, ready to pass to an LLM, load into a spreadsheet, or feed a supplier-monitoring pipeline. Paste one or more listing URLs and both layers come back from a single run.

What is Alibaba Supplier Scraper?

Alibaba Supplier Scraper is an Apify Actor that reads Alibaba trade-search and category-listing pages, extracts every product on them, and then — for each unique supplier behind those products — fetches the supplier's public company_profile.html minisite and emits a second, linked record. No Alibaba account, login, or cookie is required; everything returned is already visible to an anonymous visitor on the listing page or the supplier's public storefront.

What sets this Actor apart from a plain product scraper is the second layer: it does not just tell you who sells a product, it tells you what kind of supplier they are — Manufacturer or Trading Company, how many years they've been on the platform, their factory size, their store rating, and a structured serviceTags array naming their OEM/ODM and customization capabilities, each with a stable identity code you can filter and diff on. You never have to already know a supplier's URL — the Actor discovers every supplier itself from the product search results.

It is built for:

• 🛒 Product listings — title, price, MOQ, images, review score, certifications, and 30+ other fields per product, identical to the base product-only extraction.
• 🏭 Supplier company profiles — business type, years on Alibaba, factory floor area, store rating, and location, pulled from the supplier's own public minisite.
• 🏷️ OEM/ODM service tags — structured capability tags (Competitive OEM factory, ODM services available, R&D capabilities, customization levels) with stable identity codes.
• 🔗 Automatic supplier discovery — no need to already have a list of supplier URLs; the Actor derives them from the products it finds.

What data can you get with Alibaba Supplier Scraper?

One run can return product listings, full supplier company profiles, and each supplier's OEM/ODM capability tags — all keyed together by companyId.

Result Type	Extracted Fields	Primary Use Case
Product listing (parent row)	title, price, moq, moqV2, productUrl, mainImage, multiImage, companyName, companyId, countryCode, reviewScore, reviewCount, soldOrder, certifications, badges, and 24 more — 38 fields total	Pricing, MOQ and demand screening across a category
Supplier company profile (child row)	businessType, yearsOnPlatform, factoryArea, storeRating, location, serviceTags[], profileStatus	Supplier verification and manufacturing-capability screening

OEM/ODM service tags

serviceTags is a structured array on every supplier_profile row (when includeServiceTags is on), parsed from the capability badges Alibaba renders on the supplier's own minisite. Each entry is an object, not a plain string, so you can filter on the stable identity code instead of doing text matching on a label Alibaba might rephrase:

"serviceTags": [
  { "name": "Competitive OEM factory", "identity": "competitive_oem_factory" },
  { "name": "ODM services available", "identity": "odm_services_available" },
  { "name": "R&D capabilities", "identity": "high_rd_capability" },
  { "name": "Design-based customization", "identity": "design_based_customization" }
]

This is what tells you whether a supplier can actually manufacture-to-spec for you, versus simply resell a catalog item — a distinction the raw product listing never carries, because it lives on the supplier's profile page, not the product page.

Product listings

Product rows carry the same 38-field shape as a standalone product scrape: commercial terms (price, moq, moqV2), identity and images (title, productId, productUrl, mainImage, multiImage), and Alibaba's own trust and demand signals (reviewScore, reviewCount, soldOrder, goldSupplierYears, certifications, badges). These are what let you shortlist products before you ever look at the supplier behind them.

Why not build this yourself?

Alibaba does not publish a general search API that returns arbitrary category or keyword results to anonymous callers, and it does not publish a bulk supplier-profile API either — a DIY build means writing and maintaining two separate scrapers, and the maintenance load is the real cost.

Alibaba embeds product-listing data in an inline page payload (window.__page__data_sse*._offer_list), not in the rendered HTML — a CSS-selector scraper breaks on every layout change, while a payload parser has to locate the blob, balance its braces through escaped strings, then walk an unstable nested structure to find the offers array. The supplier minisite is a second, different problem: its data lives inside a differently-encoded field-value payload ("fieldName":"…","value":"…"), and Alibaba serves a distinct g.alicdn.com/sd/punish interstitial to flagged IPs requesting it — a different block signature than the one search pages return, so a scraper built only against search-page blocking will misread a punished supplier page as a normal empty result.

The third cost is access. Alibaba blocks datacenter IPs aggressively on both surfaces. Getting consistent results on the supplier minisite in particular means residential egress, browser-accurate TLS and header fingerprinting, sticky sessions reused while they work and rotated when they stop, and a retry ladder underneath all of it — for two request types, not one.

What is the difference between a verified supplier and an OEM/ODM tag?

A verified supplier's trust signals — businessType, yearsOnPlatform, storeRating, factoryArea — describe how established and reputable the company is. An OEM/ODM tag describes something different: what the supplier is actually capable of manufacturing to your specification, right now.

The distinction matters because the two don't always move together. A Trading Company can carry years of tenure, a strong store rating, and Gold Supplier badges without operating a single factory — it resells other manufacturers' output. A smaller Manufacturer with fewer years on the platform can carry exactly the odm_services_available or design_based_customization tag a buyer needs and a trading company cannot offer. Reading only the trust signals answers "is this a real, reputable business" — reading the serviceTags array answers "can they actually build what I'm asking for."

Alibaba Supplier Scraper returns both on the same supplier_profile record: businessType, yearsOnPlatform, storeRating, factoryArea and location for identity and trust, and serviceTags[] for manufacturing capability — so a buyer or sourcing tool can screen on both axes from one object instead of cross-referencing two separate lookups.

How to scrape Alibaba supplier profiles with Alibaba Supplier Scraper?

1. Open Alibaba Supplier Scraper on the Apify Store and click Try for free
2. Paste one or more Alibaba search or category URLs into productListUrls — copy the address bar after applying your keyword and category filters, since those filters travel with the link
3. Set maxProducts to the total number of product rows you want across all URLs, and leave enrichSupplierProfile and includeServiceTags ON to get supplier company profiles and capability tags in the same run
4. Leave proxyConfiguration on Apify Residential — Alibaba blocks datacenter IPs on both the search pages and the supplier minisites
5. Click Start, then download the dataset as JSON, CSV, or Excel, or read it through the Apify API

How to run multiple queries in one job

productListUrls is a list — paste as many Alibaba listing URLs as you need, and each is processed in order. Both plain strings and { "url": "..." } objects are accepted. maxProducts is a total across all of them, not a per-URL figure; the Actor derives roughly how many result pages that needs from Alibaba's ~48-products-per-page pattern and opens only that many. Every unique supplier discovered across all of your URLs is enriched once, no matter how many of its products appear across your queries.

⬇️ Input

Parameter	Required	Type	Description	Example Value
productListUrls	✅ Yes	array	Alibaba search or category listing URLs, one per line (stringList editor). Copy the address bar after applying keyword/category filters — they travel with the link. urls is still accepted as a base-compatible alias.	["https://www.alibaba.com/trade/search?fsb=y&IndexArea=product_en&keywords=led+flashlight&page=1"]
maxProducts	No	integer	Total product (parent) rows to collect across all URLs. Minimum 1, maximum 100000, default 10. Supplier-profile child rows are additional and not counted here. maxItems is still accepted as a base-compatible alias.	50
enrichSupplierProfile	No	boolean	When ON, emits a type: "supplier_profile" child row per unique supplier with business type, years on Alibaba, factory floor area, store rating, and location. Default true.	true
includeServiceTags	No	boolean	When ON, adds a serviceTags array (OEM/ODM/customization capability tags, each with a stable identity code) to every supplier-profile child row. Default true.	true
maxSupplierProfiles	No	integer	Cap on how many unique supplier profiles to fetch, to bound extra requests. Minimum 0, maximum 100000, default 0 (0 = enrich every unique supplier found).	0
proxyConfiguration	No	object	Apify Proxy configuration (proxy editor). Prefilled with {"useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"]} — Residential is recommended since Alibaba blocks datacenter IPs on both product and supplier pages.	{"useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"]}

Advanced / undocumented: the code also reads a maxPages key (inp.get("maxPages")) to override how many result pages are opened per URL, clamped to a 1–5000 range internally. It is not declared in this Actor's input schema, so it does not appear in the Console form — it only takes effect if you pass it directly through the Apify API. Leave it unset to let the Actor auto-derive page depth from maxProducts.

Example JSON input

{
  "productListUrls": [
    "https://www.alibaba.com/trade/search?fsb=y&IndexArea=product_en&keywords=led+flashlight&page=1"
  ],
  "maxProducts": 30,
  "enrichSupplierProfile": true,
  "includeServiceTags": true,
  "maxSupplierProfiles": 0,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"]
  }
}

Common pitfall: productListUrls must be a search or category listing page, not a single product-detail page. The Actor reads product data out of the window.__page__data_sse*._offer_list payload, which only exists on listing pages — a product-detail URL has no such payload, so the page is treated as blocked and silently skipped rather than returning a fabricated row.

⬆️ Output

Two row shapes share one dataset, distinguished by type and isChild. Product rows carry type: "product", isChild: false; supplier rows carry type: "supplier_profile", isChild: true. Because the two shapes have almost no fields in common, most columns in the default table view are populated by only one row type and blank on the other — filter on type before reading a column that isn't universal. Export as JSON, CSV, or Excel, or read the dataset through the Apify API.

Scraped results

Product row — 40 keys total: the 38-field base product object plus type and isChild, added by this variant. Missing values come back as typed empty defaults ("", [], false) rather than a missing key.

Field	Description
title	Product name, with Alibaba's keyword-highlight markup stripped
productId	Alibaba product identifier
productUrl	Absolute product page URL
mainImage	Primary product image URL
multiImage	Additional product image URLs
price	Listed price or price range as displayed
moq	Minimum order quantity as displayed
moqV2	Alibaba's alternate MOQ representation
soldOrder	Units sold / order volume signal
reviewScore	Product review score
reviewCount	Number of product reviews
productScore	Alibaba's internal product score
companyName	Supplier company name
companyId	Supplier company identifier — the join key to the supplier-profile row
companyLogo	Supplier logo URL
countryCode	Supplier country code
goldSupplierYears	Consecutive years as a Gold Supplier
supplierHref	Absolute supplier page URL — the source for the supplier-profile fetch
supplierHomeHref	Absolute supplier storefront URL
supplierService	Supplier service label
supplierServiceScore	Supplier service score
shippingScore	Shipping performance score
displayStarLevel	Displayed star level
certifications	Certification labels attached to the listing
badges	Badge labels attached to the listing
isShowAd	Whether the row is a sponsored placement
showCrown	Crown / top-listing flag
showAddToCart	Add-to-cart availability flag
lyb	Alibaba listing flag
customGroup	Alibaba listing grouping value
contactSupplier	Contact-supplier link target as published
chatToken	Chat entry token as published
eurl	Alibaba tracking URL
trackInfo	Alibaba tracking payload
loopSellingPoints	Selling-point labels
pcLoopSellingPoints	Desktop selling-point labels
id	Offer identifier
tmlid	Alibaba template identifier
type	Row type — always "product" on this row
isChild	Always false on a product row

Supplier-profile row — 14 keys, or 15 when includeServiceTags is on.

Field	Description
type	Row type — always "supplier_profile" on this row
isChild	Always true on a supplier row
parentCompanyId	Same value as companyId today — join key back to the product row(s) that discovered this supplier
companyId	Supplier company identifier, shared with its product rows
companyName	Supplier company name
countryCode	Supplier country code, carried over from the product row that surfaced this supplier
supplierUrl	Absolute URL of the company_profile.html page that was fetched
profileStatus	"ok" (profile data found), "no_data" (page loaded but no recognizable fields), or "blocked_or_unavailable" (the minisite request was blocked)
businessType	e.g. "Manufacturer, Trading Company" — null when profileStatus isn't "ok"
yearsOnPlatform	Years the supplier has been on Alibaba, as an integer — null when unavailable
factoryArea	Factory floor area as displayed, e.g. "1,115 m²" — null when unavailable
storeRating	Supplier's average store rating as displayed — null when unavailable
location	Supplier's registered location, e.g. "Guangdong, China" — null when unavailable
serviceTags	Array of {name, identity} OEM/ODM/customization capability tags — present only when includeServiceTags is on; empty array when the page couldn't be read
scrapedAt	UTC ISO-8601 timestamp for when this supplier row was fetched

profileStatus fields come back null, never guessed, when the page is blocked or empty — nothing is fabricated to fill a gap. The default dataset view shows 16 of these columns across both row types; profileStatus and parentCompanyId exist in the raw row but are not part of that view — read the raw dataset through the API or the "Full dataset" export to see every key.

[
  {
    "badges": ["Verified Supplier"],
    "certifications": ["BSCI", "OEKO-TEX"],
    "chatToken": "",
    "companyId": "218307374",
    "companyLogo": "https://s.alicdn.com/@sc04/kf/H9c2f1e8a.jpg",
    "companyName": "Shenzhen Yihosin Technology Co., Ltd.",
    "contactSupplier": "//message.alibaba.com/message/messenger.htm",
    "countryCode": "CN",
    "customGroup": "",
    "displayStarLevel": "5",
    "eurl": "https://www.alibaba.com/trade/search?fsb=y&IndexArea=product_en&keywords=led+flashlight&page=1",
    "goldSupplierYears": "13",
    "id": "1600981574830",
    "isShowAd": false,
    "loopSellingPoints": ["Custom logo", "Sample available"],
    "lyb": false,
    "mainImage": "https://s.alicdn.com/@sc04/kf/H0a1b2c3d.jpg",
    "moq": "50 pieces",
    "moqV2": "50",
    "multiImage": ["https://s.alicdn.com/@sc04/kf/H1a2b3c4d.jpg"],
    "pcLoopSellingPoints": ["Custom logo"],
    "price": "$3.20 - $5.80",
    "productId": "1600981574830",
    "productScore": "0.87",
    "productUrl": "https://www.alibaba.com/product-detail/Rechargeable-LED-Flashlight-Custom-Logo_1600981574830.html",
    "reviewCount": "213",
    "reviewScore": "4.8",
    "shippingScore": "4.7",
    "showAddToCart": true,
    "showCrown": true,
    "soldOrder": "1240",
    "supplierHomeHref": "https://yihexin4356.en.alibaba.com",
    "supplierHref": "https://yihexin4356.en.alibaba.com/company_profile.html",
    "supplierService": "Trade Assurance",
    "supplierServiceScore": "4.9",
    "title": "Rechargeable LED Flashlight Custom Logo Waterproof Torch",
    "tmlid": "",
    "trackInfo": "",
    "type": "product",
    "isChild": false
  },
  {
    "type": "supplier_profile",
    "isChild": true,
    "parentCompanyId": "218307374",
    "companyId": "218307374",
    "companyName": "Shenzhen Yihosin Technology Co., Ltd.",
    "countryCode": "CN",
    "supplierUrl": "https://yihexin4356.en.alibaba.com/company_profile.html",
    "profileStatus": "ok",
    "businessType": "Manufacturer, Trading Company",
    "yearsOnPlatform": 13,
    "factoryArea": "1,115 m²",
    "storeRating": "4.7",
    "location": "Guangdong, China",
    "serviceTags": [
      { "name": "Competitive OEM factory", "identity": "competitive_oem_factory" },
      { "name": "ODM services available", "identity": "odm_services_available" },
      { "name": "R&D capabilities", "identity": "high_rd_capability" }
    ],
    "scrapedAt": "2026-07-25T09:14:02Z"
  },
  {
    "type": "supplier_profile",
    "isChild": true,
    "parentCompanyId": "309981122",
    "companyId": "309981122",
    "companyName": "Ningbo Export Trading Ltd",
    "countryCode": "CN",
    "supplierUrl": "https://ningboexport.en.alibaba.com/company_profile.html",
    "profileStatus": "blocked_or_unavailable",
    "businessType": null,
    "yearsOnPlatform": null,
    "factoryArea": null,
    "storeRating": null,
    "location": null,
    "serviceTags": [],
    "scrapedAt": "2026-07-25T09:15:41Z"
  }
]

How can I use the data extracted with Alibaba Supplier Scraper?

• 🧾 Sourcing and procurement managers shortlist products with moq and price, then filter their suppliers on businessType == "Manufacturer" and the odm_services_available or competitive_oem_factory identity codes before sending an RFQ — so the inquiry only goes to suppliers who can actually build to spec.
• 🤖 AI engineers and LLM developers index title, companyName, businessType, and serviceTags into a vector store or agent context, so a sourcing assistant can answer "which CN manufacturers making this product also offer ODM services" against live data instead of a static export.
• 📊 Market researchers re-run the same category URLs on a schedule and diff storeRating, yearsOnPlatform, and serviceTags per companyId to track how a supplier base's capability mix shifts over a quarter.
• 🧩 Product and sourcing-tool teams join productId-keyed product rows to companyId-keyed supplier rows to build a two-sided catalog — commercial terms on one side, manufacturer credibility and capability on the other — without a second scrape.

How do you monitor Alibaba suppliers over time?

Supplier monitoring means re-running the same productListUrls on a schedule and diffing the resulting supplier_profile rows against the previous run, keyed by companyId. Between runs, storeRating and yearsOnPlatform move slowly and predictably (tenure only increases), while serviceTags and businessType change when a supplier meaningfully changes what it offers — a Trading Company adding a competitive_oem_factory tag, for example, is a real signal that its manufacturing relationship changed, not noise.

The fields worth diffing between runs: storeRating (reputation drift), serviceTags[].identity (capability changes — new tags appearing or disappearing), businessType (a reclassification between Manufacturer and Trading Company), and profileStatus (a supplier moving from "ok" to "blocked_or_unavailable" between runs is worth a manual check — either the profile page changed, or Alibaba tightened its anti-bot posture against the IP range in use).

A concrete workflow: schedule a weekly run across your tracked category URLs → build a companyId → serviceTags map from each run's supplier rows → alert when a supplier gains an OEM/ODM tag it didn't have last week. Apify's built-in Schedule feature (Console → Schedules, or the API's schedule endpoint) triggers the run on a cron interval; the dataset from each run is addressable independently through the Apify API, so the diff itself runs outside the Actor, in whatever job triggers on the schedule's completion.

Integrate Alibaba Supplier Scraper and automate your workflow

Alibaba Supplier Scraper works with any language or tool that can send an HTTP request.

REST API with Python

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")

run = client.actor("<YOUR_USERNAME>/alibaba-scraper-supplier-profiles").call(run_input={
    "productListUrls": ["https://www.alibaba.com/trade/search?fsb=y&keywords=led+flashlight&page=1"],
    "maxProducts": 30,
    "enrichSupplierProfile": True,
    "includeServiceTags": True,
    "proxyConfiguration": {"useApifyProxy": True, "apifyProxyGroups": ["RESIDENTIAL"]},
})

for row in client.dataset(run["defaultDatasetId"]).iterate_items():
    if row["type"] == "supplier_profile":
        print(row["companyName"], row["businessType"], row.get("serviceTags"))

Works in Go, Ruby, Node.js, cURL — any language that can make an HTTP request. Branch on type to route product rows and supplier rows to separate handlers.

Scheduled monitoring and delivery

Use Apify's Schedule feature (Console → Schedules, or the API) to trigger recurring runs on a cron interval, and Apify webhooks to notify an external endpoint — your own service, or a no-code tool like n8n or Make — when a run finishes, so the resulting dataset can be pulled and diffed automatically without polling.

Is it legal to scrape Alibaba supplier data?

Yes — scraping publicly accessible business listings is broadly permitted where no authentication is bypassed, and Alibaba Supplier Scraper reads only what an anonymous visitor already sees on a listing page and a supplier's public company_profile.html minisite.

Company name, business type, years on platform, factory size, store rating, and product commercial terms are business records about a company, not personal data about an individual — so GDPR and equivalent personal-data regimes do not attach to this output the way they would to a personal-profile scraper. What does apply is contractual and database-related: Alibaba's terms of service, and any local database or unfair-competition rules covering systematic reuse of a compiled catalog. Scraping for one-off supplier verification and scraping to build or resell a competing supplier directory carry different risk profiles.

Consult your legal team for commercial use cases involving bulk data storage or republishing extracted supplier data as a standalone product.

❓ Frequently asked questions

Can I target a specific Alibaba language or country site?

There's no separate region or language parameter — whatever locale is baked into the URL you paste in productListUrls is what the Actor requests. Apply your language/region settings in the browser first, then copy the address bar link.

Can I control sort order or result count per URL?

Not through a dedicated input field. Set sort order, keyword, and category filters in the browser before copying the URL into productListUrls — those settings travel with the link, as noted in the field's own description. maxProducts then caps the total row count across all URLs you supplied.

How does Alibaba Supplier Scraper handle Alibaba's anti-bot measures?

Requests use curl_cffi with a Chrome TLS/header fingerprint rather than a default HTTP client signature. Fetching escalates through a ladder: a caller-supplied proxy first (if CUSTOM_PROXY_URL is set as an Actor environment variable, tried up to 4 times), then direct or Apify datacenter, then Apify Residential with up to 6 attempts on fresh sticky sessions, backing off exponentially with jitter between attempts. Search pages and supplier minisites use different block signatures: a search page is treated as blocked on a non-200 status, a body under 800 bytes, or a missing _offer_list payload marker; a supplier page is treated as blocked on the same status/length checks plus Alibaba's g.alicdn.com/sd/punish interstitial, or the absence of recognizable profile markers (companyBusinessType, tagNameValue, esiteSubDomain) in the decoded page. A page that still can't be recovered is skipped and logged; the run continues with the rest.

Does Alibaba Supplier Scraper extract OEM/ODM service tags?

Yes — as a serviceTags array on every supplier_profile row, each entry an object with a human-readable name (e.g. "ODM services available") and a stable identity code (e.g. "odm_services_available") you can filter on directly. It's controlled by the includeServiceTags input (default true) and comes back as an empty array when the supplier page couldn't be reached.

How many products and supplier profiles does it return per run?

maxProducts accepts 1–100,000 and caps product (parent) rows only, across all URLs combined — default 10. Alibaba returns roughly 48 products per result page, and the Actor opens only enough pages to reach your target. Supplier-profile child rows are additional, one per unique supplier found, capped separately by maxSupplierProfiles (0–100,000, default 0 = every unique supplier). Internally, the number of result pages opened per URL is capped at 5,000 as an engineering safety ceiling — that's this Actor's own limit, not a published Alibaba restriction.

How do I monitor a supplier's capability tags and rating over time?

Schedule a recurring run across the same productListUrls, keep the supplier_profile rows keyed by companyId, and diff storeRating, businessType, and serviceTags[].identity against the previous run. A newly-appearing or disappearing service tag is the signal worth alerting on — see "How do you monitor Alibaba suppliers over time?" above for the full workflow.

Does Alibaba Supplier Scraper work with Claude, ChatGPT, and AI agent frameworks?

Yes. It's callable as a standard HTTP endpoint through the Apify API, so any framework that can make a request — LangChain, CrewAI, n8n, or a hand-written tool definition — can trigger a run and receive typed JSON with no parsing step. There's no MCP server for this Actor; integration is via the Apify API directly.

How does Alibaba Supplier Scraper compare to other Alibaba supplier scrapers?

Checked on the Apify Store on 2026-07-25: nifty.codes/alibaba-supplierdetails-scraper is the closest real comparison — its README documents supplier fields only (company details, verification badges, staff counts) and requires you to already have direct supplier store or company_profile.html URLs as input; it does not discover suppliers from a product search, and its capability data ships as a single joined Ability Tags string (example given: "OEM, ODM, Customization") rather than a structured, filterable array. That listing's README doesn't publish per-event pricing. Alibaba Supplier Scraper starts from a product search URL, discovers every unique supplier behind the results automatically, and returns serviceTags as individual objects with stable identity codes. The other two Actors that matched on "seller/profile" terms — a generic company-URL contact scraper and a Bark.com seller-review scraper — don't target Alibaba at all, so they aren't real alternatives for this data.

Can I use Alibaba Supplier Scraper without managing proxies or platform credentials?

Yes. Select Apify Residential in proxyConfiguration (it's the default) and the Actor handles session creation, sticky-session reuse, rotation on failure, and the retry ladder on both the product-listing pages and the supplier minisites. You only need your Apify account; no Alibaba login is ever used. If you already have your own residential proxy, set CUSTOM_PROXY_URL as an Actor environment variable and it's tried first.

🔗 Related scrapers

Scraper Name	What it extracts
Alibaba Scraper	Product listings only — no supplier enrichment
Alibaba Scraper With Supplier Contact Leads	Product rows plus outreach-ready supplier contact records
Alibaba Scraper By Price MOQ Supplier Filter	Product rows filtered on commercial thresholds during the run
Alibaba Scraper Supplier Trust Reorder Report	Supplier trust and repeat-order scoring

💬 Your feedback

Found a bug, or need a supplier field that's on Alibaba's public minisite but missing from the output? Open an issue on the Actor's Issues tab on Apify. Reports that include the exact productListUrls value and a sample supplierUrl are the fastest to reproduce and fix.