Namshi Fashion Catalog Scraper
Pricing
from $3.00 / 1,000 results
Namshi Fashion Catalog Scraper
Extract public Namshi fashion products, brands, prices, discounts, sizes, colors, availability, ratings, images, SKUs, breadcrumbs, and pagination results.
Pricing
from $3.00 / 1,000 results
Rating
0.0
(0)
Developer
coolinbex
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Share
Extract public Namshi catalog and product-page data for fashion discovery, assortment analysis, price research, and marketplace benchmarking. The Actor does not log in, call private APIs, bypass CAPTCHAs, or bypass access controls.
What it extracts
Product URL, SKU, title, brand, gender/category when publicly exposed, breadcrumbs, sizes, colors, current/original price, discount percentage, currency, availability, rating, review count, images, and description. Listing pages are followed with bounded pagination and product URLs are deduplicated.
Input
Provide startUrls with public namshi.com listing/search/category/product URLs. maxProducts (1–500), maxPages (1–20), low maxConcurrency (1–3), optional price/currency/title filters, and optional authorized Apify proxy settings are supported. Example:
{"startUrls":[{"url":"https://www.namshi.com/uae-en/women/"}],"maxProducts":50,"maxPages":2,"includeImages":true}
Output and limits
One dataset record is emitted per product that passes filters. status is ok for complete-looking records, partial when public markup omits key fields, blocked when a page is unavailable/challenged, and error for an extraction failure. A SUMMARY key-value record reports counts and run status. A blocked-only run completes successfully with status: "blocked" and an explicit dataset record; genuine request or runtime failures still make the run fail.
Markup, regional availability, currency, consent screens, and anti-automation responses can change. Use conservative schedules, respect Namshi terms and robots guidance, and verify lawful use. Runtime is primarily network/browser time: a small 50-product run normally uses several minutes and browser compute; exact cost depends on Apify compute-unit pricing, proxy usage, page count, and retries. For customer pricing, use pass-through Apify compute/proxy cost plus a service margin (for example, $5–$15 per 1,000 products for standard runs, excluding proxy charges), with a minimum run fee for very small jobs.
Local quality gate
npm installnpm testnpm run buildnpm start
The default local smoke run requires a public network and may be blocked by Namshi; blocked pages are reported explicitly and are not treated as products.