---
title: "Native scraper: deodorant scents, sizes and prices"
url: https://www.datawebot.com/learn/native
description: "Map Native personal-care products by format, scent, size, formula and offer context. Preserve exact variant evidence and review the posted site-use terms."
updated: 2026-10-23
author: datawebot team
---

Independent source guide

# Native product data: deodorant format, scent and size

Map Native personal-care products by format, scent, size, formula and offer context. Preserve exact variant evidence and review the posted site-use terms.

Updated October 23, 2026 · datawebot team

Extract Native with its endpoints: [predictive search](https://www.datawebot.com/scraper/s_www_nativecos_com#search) and [product details](https://www.datawebot.com/scraper/s_www_nativecos_com#product-details) and [catalogue](https://www.datawebot.com/scraper/s_www_nativecos_com#catalogue) . Extraction Jobs are open to every account with 200 free trial credits; [connect your agent through MCP](https://www.datawebot.com/docs/agents) to run them.

## Native's catalog is broader than a list of deodorant scents

Native's public merchandising separates personal-care product families and application formats. A scent may appear as an option under one product page without defining the product type or proving that the same option exists across every format.

| Catalog level | Native-specific distinction | Keep in the record |
| --- | --- | --- |
| Product family | Deodorant and adjacent personal-care categories use different product structures. | Use the category path and exact item identity; do not classify every Native item as deodorant. |
| Application format | A stick and a spray are different product formats even when their scent names overlap. | Keep format on the parent item and link each exact variant to that item. |
| Product page | A page can expose multiple scent, size or collection choices. | Preserve the page identity and the selected option; a page title alone may not identify the purchasable variant. |
| Catalog navigation | Category pages group items for shopping, while a product page may group option combinations. | Keep category membership separate from product and variant identity. |

[Native deodorant category ↗](https://www.nativecos.com/pages/deodorant) · [Beauty and cosmetics data use cases ↗](https://www.datawebot.com/industries/beauty-cosmetics) · [Browse source guides ↗](https://www.datawebot.com/learn)

## Treat format, scent and size as separate variant dimensions

Native product selectors show why a scent string is not a complete SKU. Not every scent appears in every size or format, so build only the combinations explicitly associated with the selected item.

| Dimension | Question to preserve | Comparison rule |
| --- | --- | --- |
| Format | Which application form is the item: stick, spray or another stated type? | Do not merge formats solely because their scent labels match. |
| Scent | What is the exact selected scent label and, where shown, its source-defined collection? | Keep the source label distinct from a normalized scent family or note description. |
| Net content and pack | What size unit and package quantity belong to this exact option? | Convert units only in a derived field; retain the displayed value and unit. |
| Edition or collection | Is the option labeled as a regular collection or a limited release on that page? | Treat the label as dated merchandising metadata, not a permanent product property. |
| Variant identity | Does the selected option have its own SKU or variant identifier? | Capture identifiers only when attached to the exact displayed combination; do not synthesize missing IDs. |

[Native deodorant category and selector dimensions ↗](https://www.nativecos.com/pages/deodorant) · [Product and variant field reference ↗](https://www.datawebot.com/docs/data) · [Resolve incomplete product variants ↗](https://www.datawebot.com/learn/product-data-enrichment-incomplete-catalogs)

## Formula claims need an exact item and source version

Native's FAQ and product pages discuss ingredients, fragrance and formula claims. Those statements can differ by formula or change when an item is updated; this guide models their provenance rather than reproducing ingredient lists or offering personal-care advice.

| Claim field | Native context | Evidence treatment |
| --- | --- | --- |
| Formula identity | Standard and sensitive products may be separate formulas, not a single product with a marketing tag. | Keep formula identity attached to the item and its selected size/scent variant. |
| Ingredient declaration | Ingredient information belongs to the exact formula and the page/version that publishes it. | Retain source URL, checked date and displayed item; do not copy a formula list into this reference page. |
| Fragrance wording | Scented and fragrance-free/unscented wording can appear in product or FAQ context. | Preserve the exact claim and its source context; do not infer that two labels mean the same formulation. |
| Performance or free-from statement | Odor-control duration and ingredient-exclusion claims are brand statements, not independent testing. | Attribute claims to Native and the exact product version; do not convert them into health, allergy or safety advice. |

[Native FAQ: ingredient and product questions ↗](https://www.nativecos.com/pages/faq) · [Product-catalog enrichment ↗](https://www.datawebot.com/solutions/product-catalog-enrichment)

## A subscription or bundle changes the offer, not the product identity

Native's shopping pages expose recurring orders and bundles alongside ordinary product choices. Keep an offer or order package separate from the underlying item and selected scent/size variant.

| Commercial record | Keep separate | Avoid assuming |
| --- | --- | --- |
| One-time offer | Selected variant, market, currency, displayed price and observation time. | A page-level price applies to every scent or size. |
| Recurring order | Subscription status, order interval, selected item/variant and the currently displayed subscription terms. | The subscription discount is a permanent product discount or an entitlement for every variant. |
| Bundle | Each included item and its own selected format/scent/size where specified. | A bundle is one indivisible product or has the same contents in every promotion. |
| Shipping and return policy | Destination, item type, policy page and effective/observation date. | One shipping or return statement covers all destinations, minis, gift cards and package types. |
| Promotion | Discount basis, eligible products, order conditions and validity window. | A banner or crossed-out amount is a stable list price. |

[Native FAQ and current order questions ↗](https://www.nativecos.com/pages/faq) · [Build a product price-history dataset ↗](https://www.datawebot.com/learn/build-product-price-history-database)

## Use a rights-aware field map for Native product data

Native's posted P&G Terms limit commercial use of site content and expressly prohibit scraping, robots, spiders and other automated copying. The useful output here is a proposed field relationship—not a Native listing export, price sample or access permission.

| Relationship | Illustrative fields | Boundary |
| --- | --- | --- |
| Item and variant | product_family, item_format, scent_label, size_value, size_unit, pack_quantity, variant_id | Use only an authorized source for actual catalog values; preserve missing fields as unknown. |
| Formula evidence | formula_label, claim_type, source_page, observed_at, claim_text_reference | Attribute product claims and avoid copying protected formula descriptions or ingredient content. |
| Offer and bundle | market, currency, selected_variant, offer_type, bundle_components, effective_window | Keep promotion and subscription terms distinct from product facts; do not publish Native prices here. |
| Data rights | terms_page, checked_at, permitted_use_basis | Native's Terms say other use of site content requires prior written permission; verify current terms before any commercial collection or reuse. |

[P&G Terms governing the Native site ↗](https://www.nativecos.com/policies/terms-of-service) · [Field semantics for data records ↗](https://www.datawebot.com/docs/data) · [Source directory ↗](https://www.datawebot.com/learn)

Content reviewed 2026-10-23.