datawebotBlibli product data: seller offers, variants & IDR prices
Understand Blibli product and seller records, category-based options, IDR offer prices, seller reputation, delivery estimates and Blibli's terms.
Updated · datawebot team
One Blibli product may have several seller offers
Blibli’s buyer help says different sellers may set different prices for the same type of product. A useful record therefore keeps the shared product, each seller’s offer, the selected option and the time of observation distinct. Compare an offer only with its seller, option and page context attached.
Scroll to compare →
| Record level | Fields to preserve | How to interpret it |
|---|---|---|
| Buyer-facing product | Name, brand, category, specifications and full product URL | The URL and title identify the observed page; neither is a universal seller SKU. |
| Seller offer | Seller/store name, displayed IDR price and visible offer or availability state | Blibli says different sellers may price the same product type differently; keep their offers separate. |
| Selected option | Visible option label and value, such as a category-defined size or color | The option is meaningful only with the product and seller offer it belongs to. |
| Observation | Source URL, seller, option, displayed currency and capture time | A page observation can change and does not establish what another seller or later visit shows. |
Keep seller reputation separate from product reviews
Blibli’s help describes seller information on the product detail page: an Official Store marker when applicable, seller badges, location, operating hours and seller rating. These are seller-level signals. Record the displayed label and seller identity, then keep them separate from the product’s own reviews or rating.
Scroll to compare →
| Visible signal | What to record | Boundary |
|---|---|---|
| Official Store marker or badge | Exact badge text beside the selected seller | It is a seller status signal, not a product attribute or proof of product quality. |
| Seller profile | Seller name, location, operating hours and seller rating when shown | A seller rating describes the seller profile, not the product review score. |
| Product review | Product-level rating or review count when separately displayed | Do not attribute product reviews to the seller score or join the two without evidence. |
| Offer price | Displayed IDR amount, seller, selected option and capture time | Keep price changes and seller identity together; avoid treating promotion copy as a guaranteed saving. |
A delivery quote belongs to a destination and logistics choice
Blibli’s shipping help says the delivery fee and estimated receipt date appear after a shopper selects a logistics service in the delivery and payment view. Keep those values with the destination scenario, chosen service, selected offer and observation time. Do not turn one displayed quote into a nationwide rate or delivery guarantee.
Scroll to compare →
| Delivery field | Observation to preserve | Limit |
|---|---|---|
| Destination | City or delivery scenario used to view the offer | One destination does not describe delivery cost or availability for all locations. |
| Logistics choice | Selected service or carrier label shown by Blibli | Different services can produce different fees and estimates. |
| Displayed fee and estimate | Visible amount and estimated receipt date after the service is selected | An estimate can change and is not a guaranteed delivery date. |
| Capture time and offer | When the quote was viewed and which seller/option was selected | Keep the quote attached to the relevant offer rather than the catalog product alone. |
Review Blibli’s terms before systematic collection or reuse
Section 2.2 of Blibli’s Terms & Conditions says users may not systematically take site content to create or compile a collection, database or directory by automated or manual means without written permission. The same section also restricts certain copying, redistribution and commercial use. Attribute this boundary to Blibli’s current terms; public visibility does not by itself establish permission for a separate compilation or reuse purpose.
Scroll to compare →
| Question | What the source says | Practical reading |
|---|---|---|
| Systematic collection | Section 2.2 expressly covers automated and manual methods used to build a collection, compilation, database or directory. | The clause names systematic site-content collection; do not treat a public page as permission. |
| Written permission | The same section says written permission is required for that systematic compilation. | Review the intended purpose and applicable permission before planning collection or reuse. |
Content reviewed 2026-10-18.