AliExpress Product Detail Scraper

Turn an AliExpress product URL into a complete, structured product record — the full detail page, not just the search-listing surface. For every product you pass in, this Actor returns the per-variant price matrix, shipping cost and delivery estimate to your target country, the seller's rating, country and store tenure, the complete specifications table, the product rating and review count, live stock, and the image gallery — all as clean JSON.

Most AliExpress scrapers stop at the listing card: title, a single price, an image, a URL. The moment you need to know which variant costs what, how much shipping adds to the landed price, whether the seller is trustworthy, or what the actual specifications are, those tools return empty fields. This Actor is built for exactly that depth.

---

What you get per product

Field	Description
product_id, title, url	Product identity and canonical link
price, sale_price, original_price, discount_pct, currency	Effective price, sale vs. list price, and the discount
variants	Per-variant matrix: each color/size/option combination with its own sku_id, label, price, stock, and availability
variant_count	Number of purchasable variants
shipping_cost, shipping_currency, free_shipping, delivery_estimate	Shipping to your target country and the delivery ETA when published
seller_name, seller_id, store_url, seller_rating, seller_total_reviews, seller_level, seller_country, seller_open_year	Seller intelligence — positive-feedback rate, store link, country and how long the store has operated
rating, review_count	Product star rating and number of reviews
specifications	Full attribute table as a key→value map (material, model, features, …)
available_inventory	Total units in stock
images, main_image	Image gallery URLs
category_path, category, description_url	Category taxonomy and the description page link
parse_confidence, warnings, scraped_at	Quality score (0–1), parse warnings, and the capture timestamp

---

Who it's for (use cases)

• Dropshippers & resellers — pull the per-variant price matrix and shipping cost to compute your true landed cost and margin before importing a product.
• Price & competitor monitoring — track sale vs. list price and discount depth across a basket of products on a schedule.
• Product research & sourcing — compare seller rating, store tenure and specifications across candidate suppliers for the same item.
• Catalog enrichment — feed your store or PIM with structured specifications, variants and images instead of hand-copying them.
• Market & pricing analysts — build datasets of AliExpress pricing, shipping and seller trust signals for modeling.

This Actor pairs naturally with a listing/search scraper: discover product URLs in bulk, then enrich each one here with the deep detail fields.

---

How to use it

1. Open the Actor and paste one or more AliExpress product URLs into productUrls (e.g. https://www.aliexpress.com/item/3256806779925038.html). Bare numeric product ids work too.
2. Set your target country and currency so prices, shipping and the delivery estimate reflect your market.
3. Keep the default Apify Residential proxy (recommended) — AliExpress needs a residential IP for reliable access. It's billed to your run; no external account is required.
4. Run. Each product becomes one row in the dataset; export to JSON, CSV, Excel, or pull it via the API.

Example input

{
  "productUrls": [
    "https://www.aliexpress.com/item/3256806779925038.html"
  ],
  "country": "US",
  "currency": "USD",
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "US"
  }
}

Example output (abridged)

{
  "product_id": "3256806779925038",
  "title": "Digital Display Bluetooth Earphones with Mic TWS …",
  "price": 2.02,
  "sale_price": 2.02,
  "original_price": 5.48,
  "discount_pct": 63.1,
  "currency": "USD",
  "variant_count": 5,
  "variants": [
    { "sku_id": "12000038883449394", "variant": "Color: green", "price": 3.17, "stock": 6, "available": true }
  ],
  "shipping_cost": 13.57,
  "shipping_currency": "CNY",
  "seller_name": "Stone's Store",
  "seller_rating": 100.0,
  "seller_country": "China",
  "rating": 4.9,
  "review_count": 13883,
  "available_inventory": 2046,
  "specifications": { "Brand Name": "…", "Model Number": "E6S" },
  "parse_confidence": 1.0
}

---

Pricing

This Actor uses pay-per-result: you are charged per product detail record returned. You only pay for products successfully scraped — failed or unavailable products are skipped and not charged. Platform/proxy usage is billed to your own Apify account at standard rates.

---

Reliability

• Structured-contract parsing. The Actor reads AliExpress's own structured product data by stable contract keys — not by fragile CSS class names that change on every front-end redeploy. Each record carries a parse_confidence score so you can detect any upstream drift programmatically.
• Resilient access. AliExpress protects its product-detail data behind a challenge layer. The Actor handles this with a resilient browser session and rotates to a fresh residential exit when a request is rate-limited, so runs stay reliable without any manual setup on your side.
• Graceful degradation. A missing optional field (e.g. a delivery ETA that the page didn't render for a region) becomes null rather than failing the record.

---

FAQ

Do I need my own proxy or any external account? No. Apify Residential proxy is recommended and billed to your run. No third-party key is required.

Can I scrape many products at once? Yes — pass as many product URLs as you like in productUrls. Each is processed and charged individually.

Does it return variant-level prices? Yes. The variants array holds each purchasable combination with its own price, stock and availability — a field most listing scrapers leave empty.

Which countries / currencies are supported? Set any standard country and currency code (US, GB, DE, FR, ES, BR, …). Prices, shipping and delivery reflect that market.

Is this legal? This Actor collects publicly available product information that any visitor can see on a product page. You are responsible for using the output in compliance with applicable laws, AliExpress's terms, and data-protection rules. No login, no private or personal data is accessed.

---

Integrations

Pipe the output into Google Sheets, Airtable, your database, or any app via the Apify API, webhooks, or the available integrations. Schedule runs to keep a price/stock dataset fresh.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.