datawebotLOOKFANTASTIC beauty data: shades, ingredients & boxes
Understand LOOKFANTASTIC beauty data by shade, size, ingredients, offers and Beauty Box edition. Keep market, formula notes and subscription terms together.
LOOKFANTASTIC is a multi-brand beauty catalog, not one product family.
The UK storefront groups products by department and brand across makeup, skincare, haircare, fragrance, bodycare, grooming and home scents. A useful catalog record retains both paths: the retailer’s category and the brand’s own product identity. That makes a foundation comparable with other complexion products without flattening its shade, size or formulation into the category label.
Scroll to compare →
| Catalog layer | Fields to preserve | Comparison use |
|---|---|---|
| Department | Source category path and storefront label | Use the source taxonomy before mapping into a separate reporting category. |
| Brand and product | Brand, displayed product title, product URL and numeric path identifier when present | Do not treat similar titles from different brands as the same product. |
| Beauty Box collection | Box product or edition identity, kept apart from ordinary beauty products | A curated box and the products it contains have different record grains. |
A beauty product, selected shade and ingredient formula are linked but distinct.
A base product can offer shade variants and multiple package sizes. LOOKFANTASTIC product pages may show a shade selector, directions and a full ingredient list; the official page reviewed here tells shoppers to check the package for the latest ingredients, and other official shade pages say ingredients may vary by shade. Keep the shade and package with each ingredient statement and retain the page or package source and observation date. Present benefit wording as retailer or brand copy, not an independently tested result.
Scroll to compare →
| Record grain | Capture separately | Evidence check |
|---|---|---|
| Base product | Brand, product name, category, numeric product path and full source URL | Retain the storefront and market context in which the record was observed. |
| Selected variant | Exact shade/option label and package size or volume | Do not infer the selected shade from the family title or merge every option into one sellable unit. |
| Ingredient/formula statement | Ingredient text or source reference, tied to shade/package and checked date | Packaging is the latest reference stated by the retailer; do not assume all shades share one list. |
| Claim attribution | Directions, benefits, suitability or efficacy text with its source label | Keep marketing claims attributed; do not present them as medical or independent findings. |
An offer combines price, reward, payment and stock context.
A beauty listing can present a recommended retail price alongside a current offer, discount wording, loyalty points, an installment display and dispatch or stock language. These describe an offer at a particular time and for a selected variant. Keep each label attached to the item, currency and market; do not turn a temporary offer into a stable product attribute or compare currencies without recording their basis.
Scroll to compare →
| Offer field | Store with the observation | Avoid inferring |
|---|---|---|
| Price labels | Recommended/current amount, currency, selected shade or size and timestamp | Do not compare prices across different variants, sellers, storefronts or dates as if they were one offer. |
| Promotion and points | Discount wording, loyalty-points display, voucher conditions and eligibility context | Do not assume a points rate or discount is permanent or applies to every product. |
| Payment and fulfillment | Installment wording/provider, stock or dispatch label and source URL | A payment display is not a complete credit schedule; dispatch wording is not a guaranteed delivery date. |
A Beauty Box edition is different from a subscription plan.
The official Beauty Box collection presents recurring monthly boxes alongside limited-edition and gift boxes. Treat each dated edition as its own product with its own component list, while storing a subscription as a plan with its term, payment cadence, renewal/cancellation wording and shipment observations. Those terms and included products can change; do not reuse one month’s content or offer as a standing description of the service.
Scroll to compare →
| Entity | Useful fields | Keep separate from |
|---|---|---|
| Monthly edition | Edition identifier or date, included components, package and observed dispatch wording | Do not use the subscription plan ID as the edition or component identity. |
| Limited-edition or gift box | Standalone box title, theme, listed components and current page status | Do not assume it recurs monthly or has the subscription’s renewal terms. |
| Subscription plan | Chosen term, payment cadence, renewal/cancellation terms and shipment date | Do not attach current plan terms to every edition or treat an account setting as a public catalog field. |
Storefront, shipping country and currency define the comparison market.
The .com storefront’s Terms distinguish UK delivery from destinations where import taxes or duties may apply, and separate EU delivery provisions. Product URLs can also carry shipping-country and currency parameters. Record the storefront, visible currency, selected shipping country or destination context and observation time; a displayed UK price or stock state should not silently become an international comparison value.
Scroll to compare →
| Market context | Preserve | Why it matters |
|---|---|---|
| Storefront | Domain/locale, page URL and any country or currency parameters | One product path can display different localized amounts or variant context. |
| Currency and price basis | Shown currency, tax label where present and price timestamp | Keep the original display before any later currency conversion. |
| Delivery destination | Publicly selected country and terms source when comparing cross-border costs | The current Terms say additional import taxes or duties may apply outside the UK; destination rules vary. |
Robots rules describe crawler paths; Terms §12 sets a separate reuse boundary.
On October 2, 2026, LOOKFANTASTIC’s robots.txt had a wildcard rule disallowing search, faceted/filter and sort URLs, checkout/basket paths and selected account or action URLs. The file then disallows the root path for many named legacy bots and lists product, list, department and blog sitemaps. It contains no named Googlebot, Google-Extended, GPTBot, OAI-SearchBot, Claude or Perplexity group. A missing named rule is not permission, and a wildcard path rule does not establish rights to use the page content.
Scroll to compare →
| Evidence source | What it says | Boundary |
|---|---|---|
| robots.txt | Wildcard exclusions for query/action routes; separate sitewide denials for named legacy agents | Do not say all AI systems are expressly allowed or blocked; follow the actual user-agent and path groups. |
| Sitemaps | Product, list, department and blog sitemap locations | Sitemap presence supports discovery, not indexing or a reuse license. |
| Terms §§11–12 | Prices may change; cross-border duties may apply; one local/personal non-commercial copy is distinguished from other restricted uses | Do not infer a legal result or treat the absence of an automated-access clause as consent. |
A traceable beauty record keeps shade, package and market with the evidence.
For catalog matching or price-history work, use connected product, variant, ingredient and offer records. Keep a dated source reference for each value so that a package update, selected shade or currency change does not overwrite the prior observation. Beauty Box editions and subscription plans should remain separate linked entities.
Scroll to compare →
| Record | Candidate fields | Provenance to retain |
|---|---|---|
| Product and variant | Product path/URL, brand, category, shade, size and visible option identifier | Exact storefront, source labels and observation time. |
| Formula statement | Ingredient list or package reference, shade and package version/date | Retailer or package source; preserve changes instead of rewriting history. |
| Offer and market | Price/RRP labels, currency, promotion/points/payment, stock/dispatch and locale | Variant, page URL, destination context and timestamp. |
| Box and plan | Edition date/components or separate subscription term/payment/renewal fields | Official edition/plan page and the date those terms were checked. |
| Policy evidence | Robots file, sitemap and applicable Terms section | Keep crawler directives, index discovery and content-use rights separate. |
Content reviewed 2026-10-02.