datawebotOclean product data: toothbrushes, water flossers & variants
Plan authorized Oclean product data around toothbrush and water-flosser models, set and color variants, market-specific prices, and product relationships.
Map Oclean’s oral-care catalog by product family.
Oclean’s official US store separates smart toothbrushes, basic toothbrushes, and water flossers, with related brush-head refills and other accessories. Preserve those product types instead of grouping every listing as a toothbrush or dental-floss product.
Scroll to compare →
| Catalog area | What to identify | Keep separate |
|---|---|---|
| Smart toothbrushes | Model family, named model, published features, available color and configuration | Product-level specifications versus selectable variant values |
| Basic toothbrushes | Model name, color, and product-page specifications when shown | A similar name does not establish the same model or feature set |
| Water flossers and accessories | Product type, model, bundle choice, and any explicitly listed pack size | A related product or brush-head refill is not automatically a compatible accessory |
Keep the product, configuration, and variant distinct.
Oclean product pages can expose a named toothbrush model, a selectable set style, and a color as separate choices. For example, the US X Pro Elite page lists Style choices of Single and Premium Set, Color Gray, and certified model Y2088. Store each value in its own field; do not treat the certified model as a SKU unless the source labels it that way.
Scroll to compare →
| Record | Capture when published | Interpretation |
|---|---|---|
| Product | Product title, source URL, product identifier, family/type | Identifies the catalog item; retain the original title |
| Configuration | Single/set/premium set or other named selector value | A set is a distinct purchase configuration, not another color |
| Variant | Color, selectable options, variant ID or SKU if explicitly present | Leave an absent identifier unknown; do not manufacture a stable key |
| Specification | Model code and model-specific feature/value with its source wording | Keep product-page claims separate from variant identity and attach units |
Build a field map that preserves the evidence.
A useful Oclean record links the visible product data to its source page and storefront context. Keep unavailable fields blank or marked unknown rather than inferring identifiers, compatibility, or specifications.
Scroll to compare →
| Field group | Useful fields | Quality rule |
|---|---|---|
| Identity | Storefront, product URL/ID, title, product family, model code when labeled | Do not merge similarly named generations without a shared verified identifier |
| Options | Style/configuration, color, variant ID/SKU if shown, pack quantity | Preserve the option labels and selected values from the same page |
| Product details | Description, image URLs, product type, published specs and units | Attribute claims to the exact model page; do not turn marketing claims into independent test results |
| Offer state | Displayed amount, compare-at amount, ISO currency, availability label | Treat price, promotion, and stock as time-bound storefront observations |
| Observation context | Market/locale, canonical source URL, retrieval timestamp | Compare only records captured from a defined market and time window |
Treat sets and product recommendations as different relationships.
An Oclean listing may expose a set choice or show other products under a “Pairs well with” heading. Those structures answer different questions: a set is a selected offer configuration, while a recommendation is a merchandising link. Neither heading alone proves which parts are in the box or whether an accessory is compatible.
Scroll to compare →
| Source relationship | Record it as | Avoid inferring |
|---|---|---|
| Single versus named set | Separate configuration/variant, with bundle quantity or contents only when stated | That a set contains a particular head, charger, case, or other item when contents are not listed |
| Pairs well with | A recommended-product relationship with its own source URL | Mechanical, electrical, model, or refill compatibility |
| Replacement brush head or accessory | Separate catalog item; link to a model only when Oclean explicitly documents compatibility | Compatibility based only on product family or cross-sell placement |
Keep each regional storefront as its own observation.
Oclean maintains regional storefronts, and the pages reviewed use different currencies and assortments. Preserve the store domain and market with the title, option values, amount/currency, and availability. A US listing and an EU listing are not one global offer, even when their model names look alike.
Scroll to compare →
| Context | Record | Why it matters |
|---|---|---|
| Market | Store domain, locale, and stated shipping market when available | A currency symbol or language alone may not identify the complete market context |
| Price | Amount and currency; compare-at amount as a separate source field | Oclean terms say prices can change; do not reuse an old offer as current |
| Availability | Exact page’s in-stock/sold-out label and observation time | Availability can vary by variant and can change after capture |
| Cross-market match | Verified shared product/model identifier plus both source URLs | Do not join records on a translated title or similar image alone |
Confirm permission and keep the scope to public catalog data.
Oclean’s posted terms say that reproducing, copying, selling, reselling, or exploiting any portion of its service requires express written permission. Public visibility does not grant reuse rights. Confirm current terms, robots directives, and written authorization before any systematic or commercial collection. Keep the planned dataset to authorized public product and collection information; exclude accounts, checkout, orders, app activity, brushing records, device identifiers, location, and personal information.
Scroll to compare →
| Boundary | Keep in scope | Leave out |
|---|---|---|
| Authorization | Only the pages and reuse rights covered by written permission and current site rules | Assuming a public URL or robots allowance is permission to reuse content |
| Catalog information | Product, option, published specification, and time-stamped offer fields authorized for the project | Private account, cart, checkout, or purchase/order information |
| Personal/app data | No personal data is needed for an assortment catalog | App usage, brushing histories, device/location signals, or identifiable customer data |
Content reviewed 2026-10-05.