🛍️ Applies to Product Detail only. Controls which detail profile is used. They differ in field set, depth and speed — pick deliberately:
- ⭐ Recommended (default) — the fastest and most consistently available profile, and the best choice for bulk jobs. Flat, easy-to-map fields: title, price and original price, stock, units sold, full image gallery, SKU table, shop and brand, plus extras the other profiles do not carry (
detail_url, delist_time, video, location).
- 🔋 Standard — the richest payload: full SKU matrix, tiered pricing, item description HTML, coupons, shipping and return policy. Noticeably slower, and less consistently available than Recommended. Pick it when you specifically need the deep pricing/policy blocks.
- 🆕 Full — an alternative field set for the same product. Useful mainly as a cross-check, or when a specific item resolves here and nowhere else.
- 💎 Premium — final / coupon pricing — focused on the final, coupon-adjusted price of the item and every SKU variant (
finalPriceYuan, finalSkuPrice, original-vs-final per SKU, stock). Best when accurate checkout pricing is the priority.
- ⚡ Lite — RETIRED. No longer available. Kept in this list only so existing saved tasks keep running — a run that asks for it is served by Recommended instead. Do not pick it for new work.
🔄 Automatic fallback: the profiles cover slightly different products, so if the one you pick cannot return an item the actor automatically tries the others and returns whichever answers. The profile that answers decides the raw field names — they differ a lot. Build your pipeline on the curated fields — itemId, title, pictUrls, totalStock, soldCount, originalPrice, discountPrice, recordTime — which are identical across every profile. The 💎 Premium profile is never substituted in or out: ask for it and you get it, or you get an error row.
💡 Freshness: every profile except the retired Lite one returns live, non-cached data stamped with recordTime — check that field on each row to verify capture time.