← Back to Blog

Parsing Shopee, Lazada, and Tokopedia: Proxies for Every Southeast Asian Country

Shopee, Lazada, and Tokopedia hold almost the entire e-commerce market of Southeast Asia, but each country is a separate showcase with login and protection against foreign IPs. Step-by-step scheme for collecting prices and stock: official API, proxies for the country, pinned sessions, speed, rollback, and metrics.

📅October 20, 2026
Parsing Shopee, Lazada, and Tokopedia: Proxies for Every Southeast Asian Country

Southeast Asia has become one of the fastest-growing e-commerce markets, and more teams from the CIS, Europe, and China want to see prices, stock levels, and promotions of competitors on Shopee, Lazada, and Tokopedia. The problem is that the usual approach of "grab a scraper, connect any proxy" breaks down almost immediately here: these platforms are divided by country, restrict data with logins, and block foreign IPs. Let's break down how to build a working scheme step by step and what proxies are needed for it.

Why These Three Platforms

According to a report by Momentum Works published on April 14, 2026, the platform-based e-commerce in Southeast Asia grew by 22.8% in 2025, reaching $157.6 billion. The three players — Shopee, Lazada, and TikTok Shop along with Tokopedia — hold about 98.8% of this market. Shopee leads with a 53% share and ranks first in all six key countries, while the GMV of the TikTok Shop + Tokopedia combination reached 65.7% of Shopee's GMV.

The fastest growth is in Thailand (+51.8% year-on-year) and Malaysia (+47.6%), while Indonesia remains the largest market with 37% of the region's turnover. For price monitoring, this means a simple thing: if you are selling in the region or sourcing products there, you need to look at several countries at once, each with its own storefront.

What Prevents Scraping Southeast Asian Marketplaces

1. Each Country is a Separate Site

Shopee does not have a single store: it consists of a set of national domains — shopee.co.id (Indonesia), shopee.com.my (Malaysia), shopee.ph (Philippines), shopee.sg (Singapore), shopee.co.th (Thailand), shopee.vn (Vietnam), a separate storefront in Taiwan, as well as Latin American sites shopee.com.br, shopee.com.mx, shopee.cl, and shopee.com.co. Lazada operates in six countries: Singapore, Malaysia, Indonesia, Philippines, Thailand, and Vietnam. Currency, assortment, promotions, and even product availability differ from country to country.

Tokopedia is a purely Indonesian platform. Since 2024, it has been merged with TikTok Shop Indonesia: at the request of Indonesian regulations, which separate social networks and commerce, transactions for TikTok Shop in the country have been moved to the Tokopedia system. For data collection, this means Indonesian IPs and Indonesian locale, no alternatives.

2. Foreign IPs Raise Immediate Suspicion

The description of a popular scraper for Lazada on Apify states clearly: Lazada blocks data center IPs not from the region through anti-bot checks, and reliable collection requires residential proxies in the target country. According to the author, data center IPs in such a scheme are usually blocked.

3. Shopee Restricts Data with Logins

Guides for Shopee in 2026 agree on one point: complete product data is only provided in an authorized session. Unauthorized requests receive empty responses or errors, with an internal response indicating is_login: false. Therefore, many ready-made scrapers require a live Shopee session cookie as input — and immediately recommend a residential proxy to avoid losing that session.

4. Multi-Layered Protection

In addition to logins, platforms use browser fingerprinting, CAPTCHAs, IP and account limits, and internal APIs and layouts change regularly. The ScrapeOps directory rates the complexity of scraping Shopee at 7 out of 10, noting protections from Cloudflare and Akamai. Providers of ready-made APIs honestly warn: when Shopee changes internal endpoints, collection may temporarily fail.

First, Check the Official API

Before building a scraper, answer the question: whose data do you need?

  • Your Store Data (orders, stock levels, prices) — use the Shopee Open Platform and Lazada Open Platform. Access is granted through the authorization of a specific store: the seller connects the application, it receives tokens, and works only with their data.
  • Affiliate Links and Catalogs for Publishers — Lazada has a separate Affiliate API for coupon and price comparison sites.
  • Competitor Prices and Assortments — there is no official access. This is the task for scraping public pages, and this is where proxies are needed.

The official API is always more stable and secure. Scraping should only be built for what is not available in the API.

Step-by-Step Data Collection Scheme

  1. Fix the "country × task" matrix. For example: prices for 500 SKUs on shopee.co.id and shopee.co.th once a day, stock levels for the top 50 on lazada.com.my every 6 hours. Each cell has its own domain, currency, and IP pool.
  2. Select geo proxies strictly for the storefront. An Indonesian storefront requires an Indonesian IP, a Thai storefront requires a Thai IP. Mixing is not allowed: an IP from Singapore on shopee.vn looks as suspicious as an IP from Germany.
  3. Separate tasks by session type. Public pages that open without logging in (Lazada listings, store pages) can be collected with IP rotation. Everything that requires a login on Shopee must be done through a sticky session: one account = one IP for the entire session's lifetime.
  4. Make the browser fingerprint "local." The time zone, interface language, and locale must match the country of the IP: Asia/Jakarta and id-ID for Indonesia, Asia/Bangkok and th-TH for Thailand. Keep the fingerprint stable within the profile and do not change the user-agent mid-session — unstable time zones, fonts, and UA are cited as the main reason for "fragile" sessions.
  5. Start with a low speed. The Pixelscan guide suggests starting with 30–100 requests per minute per account (beginning at the lower end), 1–3 parallel pages per profile, and an interval spread of ±20–40%. These are approximate numbers from the author, not measured limits from Shopee, so calibrate them with your data.
  6. Cache and avoid unnecessary requests. A product card with a price that changes once a day does not need to be scraped every 10 minutes. Caching for 5–60 minutes reduces both load and traffic consumption.
  7. Set up a rollback on protection signals. A CAPTCHA, redirect to login, or 302 is a reason to stop the profile: 3–5 retries with a pause of 5–15 seconds, then a "cooling off" period of 15–60 minutes, rather than hammering the same IP.
  8. Monitor metrics. A CAPTCHA rate above 0.5–2% and a redirect to login rate above 0.5–1% are warning signals; above 5% CAPTCHAs — it's time to change the approach. An IP that has returned an error three times in a row should be removed from the pool; how to automate such checks is detailed in the article about health checks for proxy pools.

Pitfalls

  • Cookies are the key to the account. The Shopee session cookie provides full access to the account. Do not share it with third-party services unnecessarily and do not store it in open configs.
  • Taiwan and Latin America are separate markets. If the task is about Brazil or Mexico, you need a Latin American proxy, not an Asian one.
  • Currency and price format. The Indonesian rupiah, Vietnamese dong, and Thai baht are formatted differently; without normalization, comparing prices across countries becomes meaningless.
  • TLS and headers. Even a perfect residential IP won't help if the HTTP client identifies itself with a TLS fingerprint. If you are working without a browser, check out the breakdown of JA4 and curl_cffi.
  • Platform rules. Only collect public data, comply with terms of use and local legislation, and do not touch customers' personal data. The deeper you go into areas requiring login, the higher the legal risk.

Which Proxies to Choose

Residential proxies with country selection are the basic choice for all three platforms. They provide IPs from local ISPs in the required country, which is exactly what Lazada and Shopee require. For listings, use rotation; for authorized sessions, use sticky IPs. You can select the country and rotation mode in the ProxyCove residential proxies section.

Mobile proxies will be useful where maximum "humanity" of the account is important: long-lived seller profiles, working through mobile versions of platforms, tasks with increased sensitivity to bans. They are more expensive per gigabyte, so use them selectively — on accounts, not for mass scraping of catalogs. Details can be found on the mobile proxies page.

Data center proxies are poorly suited for these platforms: according to scraper developers' experience, Lazada blocks them right at the entrance. Reserve them for auxiliary tasks — for example, checking the availability of your own services.

Conclusion

Scraping Shopee, Lazada, and Tokopedia is not a single task, but a set of tasks by country. A working scheme is built around three rules: IPs from the same country as the storefront; a sticky session for everything that requires a login; a slow start with a rollback at the first signs of protection. First, check if the official API meets your needs, and for monitoring competitors, gather a pool of residential proxies for the necessary countries in the region and measure the CAPTCHA rate from day one.