Shopee & Lazada Price & Stock Tracker (Vietnam)

Track the price and stock of products on Shopee.vn and Lazada.vn over time. Paste product URLs, get the current price, discount, stock status and sold count — plus an alert whenever the price moves or a product goes out of stock.

Built for Vietnamese sellers who want to monitor their own listings and their competitors' prices without opening every product page by hand.

What it does

For every product URL you give it, the Actor returns one dataset row:

Field	Meaning
platform	shopee or lazada
title, shop, brand	Product and seller info
price, originalPrice, discountPct	Current price in VND, pre-discount price, discount %
inStock, stock	Stock status (Shopee also returns the stock count)
sold, rating, ratingCount	Sold count and ratings (Shopee API only — not yet verified live, see below)
previousPrice, priceChange, priceChangePct	Change versus the previous run
priceAlert, stockAlert, alertReason	Alerts when the price moved past your threshold or stock flipped
checkedAt, status, error	When it was checked, and what happened

Price history is persistent. Each run saves its results in the Actor key-value store (price-history, last 30 checks per product), so the next run can compare and flag changes. Run it on a schedule (e.g. every morning) and you get a day-by-day price history for every product you watch.

Input

Field	Default	Meaning
productUrls	— (required)	Shopee.vn / Lazada.vn product URLs, max 100 per run
alertThresholdPct	5	Flag priceAlert when the price changed by at least this %
saveHistory	true	Keep price history for later runs
requestDelayMs	2000	Pause between requests (~30 req/min)
shopeeCookie	—	Optional session cookie, only if Shopee items come back blocked
lazadaCookie	—	Optional session cookie, only if Lazada items come back blocked
useProxy	false	Route through the Apify residential proxy (extra platform usage)

URL formats:

• Shopee: https://shopee.vn/<name>-i.<shopId>.<itemId>
• Lazada: https://www.lazada.vn/products/<name>-i<itemId>-s<skuId>.html

Honest limits

• Shopee blocks datacenter IPs. Its product API returns HTTP 403 without a valid session cookie. If Shopee items come back blocked, paste your browser session cookie into shopeeCookie (Chrome DevTools → Application → Cookies → shopee.vn, copy the full Cookie header value) or turn on useProxy. The Actor never fakes data: blocked items are reported as blocked. Shopee fields (originalPrice, stock, sold, rating) come from the Shopee item API and are not yet verified against a live response — every live test so far hit the 403 block. They will be verified on the platform run with a cookie or proxy.
• Lazada sold count and rating are not in the static page, so those fields are null for Lazada items. Price, title, brand and stock status are extracted from the page.
• The Actor is polite by design: sequential requests, ~2 s apart, max 100 products per run.
• HTTP/1.1 only. The Actor uses a custom HTTP client that forces HTTP/1.1 (got-scraping with http2: false). The default HTTP/2 path breaks behind egress/transparent proxies ("Requested origin … does not match server …:3128"); HTTP/1.1 works in those environments and on the Apify platform.

Tested locally (2026-11-10)

apify run with 3 real product URLs, ~47 s total, max 30 req/min:

Product	Result
Lazada XIAOYOU bone-conduction headphones (3263617202)	✅ ok — price 1,243,000₫, title, brand XIAOYOU, InStock
Lazada men's sportswear set VNO100 (2210811094)	✅ ok — price 150,000₫, title, InStock
Shopee discount link (shop 57737923, item 4938305683)	🚫 blocked — HTTP 403 (error 90309999), datacenter IP blocked as expected

Price-history/alert path verified in a single-process run with seeded history: XIAOYOU 1,400,000₫ → 1,243,000₫ = −11.21% → priceAlert: true, VNO100 unchanged 150,000₫ → no alert. Final tally: ok=2, blocked=1, alerts=1.

One Lazada test URL (CHAOMILI, 3197539687) turned out to be a removed product (HTTP 404, "Sản phẩm này không còn tồn tại") — the Actor now reports that explicitly instead of a generic parse error.

Local-testing notes: run with the egress proxy env vars unset (env -u https_proxy -u HTTPS_PROXY -u http_proxy -u HTTP_PROXY apify run), because got-scraping's proxy agent hangs against this VM's egress proxy. Also note the local memory-storage layer (Apify SDK 3.7.2) does not carry key-value-store values across processes — each local run starts with empty price history (and apify run purges local stores first). On the Apify platform the cloud key-value store persists across runs, so scheduled runs compare against real history.

Pricing

Pay per event: $0.005 per product successfully checked. Platform usage is included in that price. You only pay for products that returned data.

Use cases

• Watch your own Shopee/Lazada listings and get alerted when a competitor undercuts you.
• Track a product you want to buy and catch the next price drop.
• Build a price history table for a whole category before a sale event (11.11, 12.12, Tết).