datawebotOzon product data: IDs, sellers and offer context
Map Ozon product articles, manufacturer numbers, category attributes, seller metrics, conditional prices and Seller API scope.
An Ozon article is different from a manufacturer's part number.
Ozon product feature pages can display both `Артикул` and `Партномер (артикул производителя)`. Keep those source fields separate: the first identifies the Ozon catalog item shown on that page, while the second is a manufacturer-supplied identifier. The official head-unit example shows the two labels as distinct fields. A product title alone is not a reliable join key.
Scroll to compare →
| Field | Keep as shown | Comparison rule |
|---|---|---|
| Ozon Артикул | The article value displayed for the exact Ozon item page | Keep it in the marketplace-ID field; do not rename it as a manufacturer part number. |
| Manufacturer part number | The value under `Партномер (артикул производителя)` | Store separately from Ozon's article and retain the original label. |
| Product description | Exact displayed name, brand and item URL | Do not merge similar titles unless a documented identifier or source-defined relationship supports the match. |
| Seller SKU | A seller's internal code only if a seller-authorized source supplies it | Do not infer one from the Ozon article, manufacturer number or title. |
Category fields need their original labels and units.
Ozon's category-specific feature pages do not share one universal attribute set. The linked electronics example lists memory, cores, interfaces and power; the air-filter example instead includes dimensions, material, shape, country and intended equipment. Preserve the source category and exact field label so a normalized catalog does not erase what the listing actually says.
Scroll to compare →
| Record element | Source example | How to preserve it |
|---|---|---|
| Category | Electronics or garden-equipment parts, as shown in the linked product pages | Attach every attribute to the exact category and Ozon item. |
| Attribute label | `Оперативная память, ГБ` or `Материал` | Retain the Russian source label; add a translated/normalized label separately if needed. |
| Value and unit | A source-published number, text value or unit such as `мм` | Keep the displayed value and unit together; do not convert or infer a missing value silently. |
| Missing attribute | Not displayed on the reviewed page | Represent as unknown/not supplied with provenance, not as zero or a category default. |
A selected configuration must stay attached to its item.
When an Ozon page explicitly presents a size, model, color or other selectable option, preserve the chosen label and the article or identifier tied to it. A related card or a collection of similar items is not automatically a variant of the current product. Confirm the relationship on the source page before grouping records.
Scroll to compare →
| Observation | Useful record | Do not assume |
|---|---|---|
| Selected option | Exact source label/value, page context and observation time | That a color, pack count or model option exists if the page does not show it. |
| Option-to-item link | The Ozon article or other identifier shown for the selected item | That all options share one article or manufacturer number. |
| Related items | Their own URLs and IDs, plus only the relationship Ozon explicitly states | That similar titles or neighboring cards are one product family. |
| Unclear relationship | Separate item records and an unresolved relation | A variant mapping created from title similarity alone. |
A seller storefront and a product card describe different entities.
Ozon seller pages can summarize a shop's catalog and shop-level activity while also listing individual products with their own ratings and offer details. Keep the storefront as a seller entity. A store rating or order summary is not the rating or sales count of every item in that shop.
Scroll to compare →
| Entity | Possible source fields | Keep separate from |
|---|---|---|
| Seller storefront | Displayed shop name, catalog context and shop-level metric labels | A particular item and its seller offer. |
| Shop metric | Store-level rating, reviews or orders where Ozon labels them as shop information | Product review count, product rating or inferred units sold. |
| Product card | Ozon article, title, category attributes and product-level rating/review summary | The seller's overall shop metrics. |
| Offer | Seller identity and the item/configuration offered in its page context | Another seller's offer for a similarly named product. |
Bank-conditioned prices and delivery are dated offer observations.
Some Ozon product-page excerpts distinguish a price associated with Ozon Bank from one shown with other banks or without Ozon Bank. Record the displayed label and eligibility context with the amount; do not describe one as a universal item price. Stock text and delivery estimates are separate observations tied to market, destination and time.
Scroll to compare →
| Offer field | What to retain | Why it stays separate |
|---|---|---|
| Displayed price | Amount, currency, exact product/configuration, seller and capture time | An amount without its item and time cannot be compared reliably. |
| Payment condition | The exact Ozon Bank/other-bank label or eligibility note | A conditional price is not available to every shopper under the same terms. |
| Promotion | Displayed discount/reference amount and the offer context | Do not treat a crossed-out price or promotion label as a stable price history. |
| Availability and delivery | Source wording, destination/market and observed time | A stock label is not an exact inventory count; a delivery estimate is not a universal promise. |
| Unknown context | Unknown or not supplied, with the reason where available | Do not fill in a bank condition, shipping cost or destination from another offer. |
Seller API product-query analytics concern a seller's own products.
Ozon for Developers' March 14, 2025 announcement describes `/v1/analytics/product-queries` and `/v1/analytics/product-queries/details` as analytics for a seller's own products, corresponding to the seller-cabinet area labeled “My product queries.” This is seller-scoped analytics. The announcement does not establish access to every marketplace listing, competitor query, public offer or general product-search dataset.
Scroll to compare →
| Scope | What the official notice supports | What not to infer |
|---|---|---|
| Seller-owned query analytics | Named Seller API methods for analytics on that seller's products | A public API for any Ozon product or another seller's private analytics. |
| Account and plan context | The notice says Premium/Premium Plus subscribers can access a longer period and expanded response data | Current account eligibility, endpoint schemas or plan terms beyond that dated notice. |
| Public product page | A marketplace item page with its own displayed fields and seller context | That a Seller API analytics endpoint is a substitute for public catalog data. |
Keep source evidence attached and verify access rules separately.
This review could not inspect Ozon's current marketplace terms or `robots.txt` because the official URLs redirected in the research tool. The page therefore makes no claim that public visibility, an indexed excerpt or the existence of Seller API authorizes collection or reuse. Before any separately authorized use, check the current official terms, crawler directives and data-source agreement; those are separate questions.
Scroll to compare →
| Data boundary | Record or review | Avoid |
|---|---|---|
| Source provenance | Canonical source URL, page/category, exact field label and capture time | A value without a traceable item and source context. |
| Market and offer scope | Market/language, seller, selected item and any destination-dependent condition | Treating a page from one locale or destination as universal. |
| Access review | Current terms, robots directives and any separate authorization or licensed feed | Treating an absent or unreadable robots rule as permission or prohibition. |
| Personal/customer data | Exclude reviewer identity/text, account details and order/payment information from this product guide | Turning user-generated or private transaction data into catalog fields. |
Content reviewed 2026-10-07.