George-Octoparse commited on
Commit
0ab0272
·
verified ·
1 Parent(s): e1a3e54

feat: v2.0.0 real data - README.md

Browse files
Files changed (1) hide show
  1. README.md +236 -0
README.md ADDED
@@ -0,0 +1,236 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ ---
2
+ license: cc-by-nc-4.0
3
+ language:
4
+ - en
5
+ tags:
6
+ - ecommerce
7
+ - temu
8
+ - price-monitoring
9
+ - competitor-price-monitoring
10
+ - sku-variants
11
+ - product-matching
12
+ - dynamic-pricing
13
+ - web-scraping
14
+ - retail
15
+ - anti-bot
16
+ pretty_name: Temu E-commerce Pricing & SKU Variant Dataset
17
+ size_categories:
18
+ - n<1K
19
+ task_categories:
20
+ - text-classification
21
+ - other
22
+ task_ids:
23
+ - multi-label-classification
24
+ annotations_creators:
25
+ - no-annotation
26
+ multilinguality:
27
+ - monolingual
28
+ source_datasets:
29
+ - original
30
+ ---
31
+
32
+ # Temu E-commerce Pricing & SKU Variant Dataset
33
+
34
+ **85 products · 382 SKUs · $2.14–$219.72 price range · avg 29.5% discount where measurable**
35
+
36
+ A real, production-quality sample of Temu product listings and SKU-level pricing data, captured by **[Octoparse Managed Data Service](https://www.octoparse.com/managed-data-service)** via a managed anti-bot pipeline. Every row is real market data — no synthetic expansion, no mock prices.
37
+
38
+ Built for teams working on **competitor price monitoring**, **dynamic pricing models**, **product matching**, and **e-commerce AI pipelines**.
39
+
40
+ > **v2.0.0** — Complete rebuild. Previous version contained synthetic data; this release contains 100% real scraped data normalized into a clean two-table schema.
41
+
42
+ ---
43
+
44
+ ## Why This Dataset
45
+
46
+ Most public e-commerce datasets are:
47
+ - **Stale** — from Kaggle uploads years old, prices meaningless
48
+ - **Synthetic** — generated to look like pricing data, not real market signals
49
+ - **Flat and noisy** — video metadata and SKU variants collapsed into one bloated table
50
+
51
+ This dataset is different:
52
+ - **100% real** market data from Temu's live catalogue
53
+ - **Normalized schema**: `products.parquet` (SPU-level) + `skus.parquet` (variant-level), joined on `spu_id`
54
+ - **Anti-bot provenance**: captured through Akamai Bot Manager bypass and TLS fingerprint randomization — the hard infrastructure problem solved for you
55
+ - **Pricing signal transparency**: `discount_pct` computed where Temu surfaces both prices; sparsity documented, not hidden
56
+
57
+ ---
58
+
59
+ ## Dataset Structure
60
+
61
+ ```
62
+ temu-ecommerce-pricing-workflow-sample/
63
+ ├── products.parquet ← 85 rows, 5 columns (SPU-level)
64
+ ├── skus.parquet ← 382 rows, 14 columns (SKU-level)
65
+ ├── schema.json ← Machine-readable field definitions
66
+ ├── data_dictionary.md ← Business context for every field
67
+ ├── workflow_stats.json ← Pipeline provenance and anti-bot metadata
68
+ └── LICENSE ← CC BY-NC 4.0
69
+ ```
70
+
71
+ ### `products.parquet` — SPU Level
72
+
73
+ | Field | Type | Description |
74
+ |---|---|---|
75
+ | `spu_id` | string | Product ID (join key) |
76
+ | `product_url` | string | Temu product URL |
77
+ | `is_on_sale` | boolean | Currently purchasable |
78
+ | `not_on_sale_reason` | string | Reason if inactive (null for all active) |
79
+ | `goods_property_summary` | string | Semicolon-delimited property bag |
80
+
81
+ ### `skus.parquet` — SKU Level
82
+
83
+ | Field | Type | Description |
84
+ |---|---|---|
85
+ | `sku_id` | string | Variant ID |
86
+ | `spu_id` | string | FK → `products.spu_id` |
87
+ | `sku_main_pic` | string | CDN image URL |
88
+ | `sku_original_price` | float64 | List price USD (null if Temu not showing strikethrough) |
89
+ | `sku_discounted_price` | float64 | Current selling price USD |
90
+ | `discount_pct` | float64 | `(original - discounted) / original` |
91
+ | `sale_attr_color` | string | Color variant |
92
+ | `sale_attr_size` | string | Size variant |
93
+ | `sale_attr_quantity` | string | Bundle/quantity variant |
94
+ | `sale_property_summary` | string | Pipe-delimited summary of all variant attrs |
95
+
96
+ ---
97
+
98
+ ## Quick Start
99
+
100
+ ```python
101
+ import pandas as pd
102
+
103
+ products = pd.read_parquet("hf://datasets/Octoparse/temu-ecommerce-pricing-workflow-sample/products.parquet")
104
+ skus = pd.read_parquet("hf://datasets/Octoparse/temu-ecommerce-pricing-workflow-sample/skus.parquet")
105
+
106
+ # Join: full product + SKU view
107
+ df = skus.merge(products[["spu_id", "product_url", "goods_property_summary"]], on="spu_id")
108
+
109
+ # Products with highest discount (where data available)
110
+ top_discounts = (
111
+ skus[skus["discount_pct"].notna()]
112
+ .groupby("spu_id")["discount_pct"]
113
+ .max()
114
+ .sort_values(ascending=False)
115
+ .head(10)
116
+ )
117
+
118
+ # Price spread per product (variant pricing range)
119
+ price_spread = (
120
+ skus.groupby("spu_id")["sku_discounted_price"]
121
+ .agg(["min", "max"])
122
+ .assign(spread=lambda x: x["max"] - x["min"])
123
+ .sort_values("spread", ascending=False)
124
+ )
125
+
126
+ # SKUs with strikethrough pricing (visible discount signal)
127
+ has_strikethrough = skus[skus["sku_original_price"].notna()].copy()
128
+ print(f"{len(has_strikethrough)} SKUs with measurable discount — avg {has_strikethrough['discount_pct'].mean():.1%}")
129
+ ```
130
+
131
+ ---
132
+
133
+ ## Dataset Stats
134
+
135
+ | Metric | Value |
136
+ |---|---|
137
+ | Products (SPUs) | 85 |
138
+ | SKUs (variants) | 382 |
139
+ | Avg SKUs per product | 4.5 |
140
+ | SKUs with strikethrough price | 120 (31.4%) |
141
+ | Avg discount (where measurable) | 29.5% |
142
+ | Max discount | 81.9% |
143
+ | Price range | $2.14 – $219.72 |
144
+ | All products on sale | Yes (100%) |
145
+
146
+ ---
147
+
148
+ ## The Hard Problem: Why Temu Data is Difficult to Scrape
149
+
150
+ Temu runs one of the most aggressive anti-bot stacks in consumer e-commerce:
151
+
152
+ - **Akamai Bot Manager** with TLS/JA3 fingerprinting — blocks standard HTTP clients instantly
153
+ - **Device fingerprinting** — canvas, WebGL, and font enumeration checks
154
+ - **Dynamic price rendering** — prices are injected via JavaScript after page load; HTML-only scrapers return empty price fields
155
+ - **Signed CDN URLs** — image URLs rotate signatures; naive URL caching breaks within hours
156
+ - **Algorithmic discount visibility** — Temu controls when strikethrough prices appear; the same SKU may show or hide the original price depending on session context, geo, and time
157
+
158
+ This dataset was captured through Octoparse's managed pipeline that handles all of the above. The `sku_original_price` sparsity you see (69% null) is a **real market signal**, not a data quality failure — it accurately reflects which SKUs Temu was displaying comparison pricing for at scrape time.
159
+
160
+ ---
161
+
162
+ ## Pricing Signal Notes
163
+
164
+ **Why is `sku_original_price` 69% null?**
165
+
166
+ Temu uses algorithmic price display — the strikethrough "was" price is only rendered when Temu's system determines it increases conversion for that session. This means:
167
+ - Null `sku_original_price` ≠ no discount
168
+ - Null `sku_original_price` = Temu chose not to show the comparison at this moment
169
+ - For true discount rate measurement, you need **repeated captures** at different times and sessions
170
+
171
+ For production-cadence pricing (hourly snapshots, session rotation), see our managed pipeline service.
172
+
173
+ ---
174
+
175
+ ## Use Cases
176
+
177
+ ### 1. Competitor Price Monitoring Pipeline Design
178
+ Use `sku_discounted_price` + `discount_pct` as features in a price alert system. The `sale_attr_*` columns let you track price moves at variant granularity (not just product level).
179
+
180
+ ### 2. Product Matching & Deduplication
181
+ `spu_id` + `sku_id` + `sku_main_pic` give you the triplet needed for visual and text-based product matching across platforms.
182
+
183
+ ### 3. Dynamic Pricing Model Training
184
+ The `discount_pct` distribution (mean 29.5%, max 81.9%) and the presence/absence of `sku_original_price` are themselves signals for modeling Temu's promotional logic.
185
+
186
+ ### 4. E-commerce Schema Design
187
+ Use `goods_property_summary` to build a product taxonomy. The ~178 unique property keys across 85 products show the schema complexity of a live multi-category catalogue.
188
+
189
+ ### 5. Anti-Bot Research
190
+ `workflow_stats.json` documents the specific bot-management systems encountered during collection, useful for anti-scraping research and pipeline architecture planning.
191
+
192
+ ---
193
+
194
+ ## Data Limitations
195
+
196
+ | Limitation | Detail |
197
+ |---|---|
198
+ | Price is a snapshot | No time-series in this sample. Temu prices change multiple times daily. |
199
+ | `sku_original_price` sparsity | 69% null — intentional (see Pricing Signal Notes above) |
200
+ | `sale_attr_*` sparsity | Each SKU uses at most 1–2 of 7 attribute columns |
201
+ | Property key inconsistency | `goods_property_summary` has ~178 keys with typos/case variations |
202
+ | Sample size | 85 products — sufficient for schema/pipeline design, not for statistical price benchmarking |
203
+
204
+ ---
205
+
206
+ ## Want Production-Scale Temu Data?
207
+
208
+ This is a **sample dataset**. If you need:
209
+ - **Hourly price capture** across thousands of SKUs
210
+ - **Multi-category coverage** (apparel, electronics, home, beauty)
211
+ - **Session-rotated scraped** to expose hidden discount pricing
212
+ - **Delivery to Snowflake, BigQuery, or S3** in Parquet or JSONL
213
+
214
+ → **[Talk to Octoparse Managed Data Service](https://www.octoparse.com/managed-data-service)**
215
+
216
+ We operate the anti-bot infrastructure so your team doesn't have to.
217
+
218
+ ---
219
+
220
+ ## Citation
221
+
222
+ ```bibtex
223
+ @dataset{octoparse_temu_pricing_2025,
224
+ title = {Temu E-commerce Pricing and SKU Variant Dataset},
225
+ author = {{Octoparse Managed Data Service}},
226
+ year = {2025},
227
+ publisher = {Hugging Face},
228
+ url = {https://huggingface.co/datasets/Octoparse/temu-ecommerce-pricing-workflow-sample},
229
+ license = {CC BY-NC 4.0},
230
+ note = {Real scraped Temu product and SKU pricing data, anti-bot pipeline provenance documented}
231
+ }
232
+ ```
233
+
234
+ ---
235
+
236
+ *Built by [Octoparse Managed Data Service](https://www.octoparse.com/managed-data-service) · [LinkedIn](https://www.linkedin.com/company/octoparse) · [GitHub](https://github.com/octoparse)*