Back to Details

linkfox-mpstats-ozon-product-detail

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

MPSTATS Ozon Product Detail (Batch)

MPSTATS Ozon商品详情（批量查询）

This skill batch-fetches the full product card for one or more Ozon (Russia) SKUs via MPSTATS. Returned fields include price, Ozon Card price, discount, rating, reviews, stock, monthly sales units, monthly sales revenue, lost profit, potential revenue, first listing date, image, and more.
本技能通过MPSTATS批量拉取一个或多个Ozon（俄罗斯站）SKU的完整商品卡片信息。返回字段包括价格、Ozon Card价、折扣、评分、评论数、库存、月销量、月销售额、损失利润、潜在收入、首次上架日期、图片等。

Core Concepts

核心概念

Batch semantics: Pass up to 100 
productIds
in a single call. The server fans out concurrently and automatically retries each failed SKU once; partial success is allowed, so a mixed list is normal.
Fulfillment model per SKU: Each product card carries 
deliveryScheme
:
  • FBO
    — Fulfillment by Ozon (stock in Ozon warehouses)
  • FBS
    — Fulfillment by Seller (seller-shipped)
Pass 
includeFbs: true
to allow FBS SKUs and FBS-scoped metrics into the response; 
false
(or omitted) keeps the result FBO-centric. This switch applies to the whole batch.
Previous-period comparison: The card includes 
previousSalesUnits
/ 
previousRevenue
— sales and revenue from the equal-length period immediately before 
[startDate, endDate]
— ready for MoM / period-over-period diffs without extra calls.
Revenue potential: 
revenuePotential
projects what the SKU could have earned if it had been in stock every day of the window; compare with 
monthlySalesRevenue
to quantify stock-out drag, together with 
lostProfit
/ 
lostProfitPercent
.
Date window: 
startDate
/ 
endDate
define the period for all period-aggregated metrics. Latest selectable date is yesterday (T-1); today and future dates are rejected.
批量语义：单次调用最多传入100个
productIds
。服务器会并发处理请求，并自动重试失败的SKU一次；允许部分成功，因此返回结果中存在成功与失败的混合列表属于正常情况。
单SKU履约模型：每个商品卡片包含
deliveryScheme
字段：
  • FBO
    — 由Ozon履约（库存存放于Ozon仓库）
  • FBS
    — 由卖家履约（卖家自行发货）
设置
includeFbs: true
可在响应中包含FBS SKU及对应指标；设置为
false
（或省略该参数）则仅返回FBO相关数据。该开关对整个批量查询生效。
往期对比：商品卡片包含
previousSalesUnits
/
previousRevenue
字段，即
[startDate, endDate]
周期之前等长时间段的销量与收入数据，无需额外调用即可直接用于月环比/同期对比分析。
收入潜力：
revenuePotential
字段用于预测该SKU在统计周期内若全程有库存可获得的收入；与
monthlySalesRevenue
对比可量化缺货带来的影响，结合
lostProfit
/
lostProfitPercent
字段分析效果更佳。
日期范围：
startDate
/
endDate
定义所有周期聚合指标的统计时段。可选的最晚日期为昨日（T-1）；今日及未来日期会被拒绝。

Parameters

参数说明

ParameterTypeRequiredDescription
productIdsarray<integer|string>yesOzon SKU list, up to 100 per call
startDatestringnoStats window start, 
YYYY-MM-DD
; latest = yesterday
endDatestringnoStats window end, 
YYYY-MM-DD
; latest = yesterday
includeFbsbooleanno
true
to include FBS data; 
false
= FBO-only
参数类型是否必填描述
productIdsarray<integer|string>是Ozon SKU列表，单次调用最多100个
startDatestring否统计周期起始日期，格式为
YYYY-MM-DD
；最晚为昨日
endDatestring否统计周期结束日期，格式为
YYYY-MM-DD
；最晚为昨日
includeFbsboolean否设置为
true
时包含FBS数据；
false
则仅返回FBO数据

API Usage

API使用方式

This tool calls the LinkFox tool gateway API. See 
references/api.md
for calling conventions, request parameters, response structure, and error codes. You can also execute 
scripts/mpstats_ozon_product_detail.py
directly for ad-hoc queries.
本工具调用LinkFox工具网关API。调用规范、请求参数、响应结构及错误码请参考
references/api.md
。您也可直接执行
scripts/mpstats_ozon_product_detail.py
进行临时查询。

Usage Examples

使用示例

1. Single-SKU detail
json
{"productIds": [1786874757]}
2. Batch lookup with period
json
{
  "productIds": [1786874757, 151623766, 142257239],
  "startDate": "2025-03-01",
  "endDate": "2025-03-31",
  "includeFbs": true
}
3. FBO-only snapshot
json
{"productIds": [1786874757, 151623766], "includeFbs": false}
4. SKUs discovered upstream — full card
json
{"productIds": [<list from mpstats-ozon-product-search>]}
1. 单个SKU详情查询
json
{"productIds": [1786874757]}
2. 指定周期的批量查询
json
{
  "productIds": [1786874757, 151623766, 142257239],
  "startDate": "2025-03-01",
  "endDate": "2025-03-31",
  "includeFbs": true
}
3. 仅返回FBO数据的快照查询
json
{"productIds": [1786874757, 151623766], "includeFbs": false}
4. 上游搜索得到的SKU全量卡片查询
json
{"productIds": [<来自mpstats-ozon-product-search的SKU列表>]}

How to Chain with Other Ozon Skills

与其他Ozon技能的联动方式

  1. Search → detail: Use 
    mpstats-ozon-product-search
    to resolve a keyword / brand / seller into 
    productId
    s, then pass them here for full metrics.
  2. Detail vs trend: This endpoint is a period aggregate per SKU; for day-by-day time-series on a single SKU, use 
    mpstats-ozon-product-trend
    .
  3. Detail vs drill-downs: When the input dimension is a brand / category / seller (not a SKU list), prefer 
    brand-products
    / 
    category-products
    / 
    seller-products
    — they already return aggregated metrics per SKU under that dimension.
  1. 搜索→详情：使用
    mpstats-ozon-product-search
    通过关键词/品牌/卖家获取
    productId
    ，再传入本工具获取完整指标数据。
  2. 详情vs趋势：本接口返回的是单SKU的周期聚合数据；若需单个SKU的逐日时间序列数据，请使用
    mpstats-ozon-product-trend
    。
  3. 详情vs细分分析：当输入维度为品牌/品类/卖家（而非SKU列表）时，优先使用
    brand-products
    /
    category-products
    /
    seller-products
    ，这些工具已返回对应维度下每个SKU的聚合指标。

Display Rules

展示规则

  1. Compact table — lead with 
    productId
    , 
    title
    , 
    price
    , 
    monthlySalesUnits
    , 
    monthlySalesRevenue
    , 
    rating
    , 
    reviewCount
    , 
    balance
    , 
    deliveryScheme
    , 
    firstDate
    . Pull 
    revenuePotential
    / 
    lostProfit
    / 
    lostProfitPercent
    in when the user asks about stock-out impact.
  2. Currency — Ozon native currency is RUB; the 
    currency
    field carries the symbol. Do not silently relabel.
  3. Partial success — the response carries 
    successCount
    / 
    failedCount
    / 
    failures
    ; when 
    failedCount > 0
    , list the failed 
    productId
    s from 
    failures
    to the user rather than silently dropping them.
  4. Period-over-period — when both current and 
    previous*
    fields are present, render them side-by-side or as diff; don't report a single-period number as "trend".
  5. With-stock vs all-days — 
    salesPerDayWithStock
    / 
    dailySalesRevenueWithStock
    only count days that had inventory; distinguish from the plain 
    salesPerDay
    / 
    dailySalesRevenue
    .
  6. Delivery model — prefer the per-SKU 
    deliveryScheme
    value over assuming FBO; remind users when a batch mixes FBO and FBS.
  7. No business advice — present data; do not extrapolate "this SKU is worth selling" without a wider analysis.
  1. 紧凑表格 — 优先展示
    productId
    、
    title
    、
    price
    、
    monthlySalesUnits
    、
    monthlySalesRevenue
    、
    rating
    、
    reviewCount
    、
    balance
    、
    deliveryScheme
    、
    firstDate
    字段。当用户询问缺货影响时，再补充展示
    revenuePotential
    /
    lostProfit
    /
    lostProfitPercent
    字段。
  2. 货币单位 — Ozon默认货币为RUB；
    currency
    字段会携带货币符号，请勿擅自修改。
  3. 部分成功处理 — 响应结果包含
    successCount
    /
    failedCount
    /
    failures
    字段；当
    failedCount > 0
    时，需将
    failures
    中的失败
    productId
    告知用户，而非直接忽略。
  4. 同期对比 — 当同时存在当前周期与
    previous*
    字段数据时，需将二者并列展示或呈现差值；不得将单周期数据作为“趋势”报告。
  5. 有库存日vs全周期 — 
    salesPerDayWithStock
    /
    dailySalesRevenueWithStock
    仅统计有库存的日期；需与普通的
    salesPerDay
    /
    dailySalesRevenue
    字段区分开。
  6. 履约模型 — 优先使用单SKU的
    deliveryScheme
    值，而非默认假设为FBO；当批量结果中同时包含FBO和FBS数据时，需提醒用户。
  7. 不提供业务建议 — 仅展示数据；未经全面分析，不得给出“该SKU值得售卖”这类推断。

Important Limitations

重要限制

  • 100-SKU batch cap — split larger input lists and call multiple times; the Agent must paginate.
  • Ozon-only — this tool does not cover Wildberries or other Russian marketplaces.
  • T-1 data — 
    endDate
    must not be today or future.
  • FBS coverage — some categories have partial FBS coverage; if the input set is FBS-heavy, expect sparser cards.
  • Field set differs from brand/seller — this endpoint does not return 
    brandId
    , 
    country
    , 
    category
    , 
    minPrice
    / 
    maxPrice
    / 
    averagePrice
    , 
    balanceFbs
    , 
    frozenStocks
    , 
    warehousesCount
    , 
    daysInSite
    / 
    daysInStock
    / 
    turnoverDays
    , 
    position
    / 
    categoryPosition
    / 
    revenueSharePercent
    , 
    isFbs
    . Use 
    brand-products
    / 
    category-products
    / 
    seller-products
    if those are needed.
  • No translation — titles are returned in Russian; translate on demand when presenting to Chinese / English users.
  • 100个SKU批量上限 — 若输入列表超过该数量，请拆分后多次调用；Agent需自动分页处理。
  • 仅支持Ozon — 本工具不覆盖Wildberries或其他俄罗斯电商平台。
  • T-1数据限制 — 
    endDate
    不能为今日或未来日期。
  • FBS数据覆盖有限 — 部分品类的FBS数据覆盖不全；若输入以FBS SKU为主，返回的商品卡片可能信息较稀疏。
  • 字段集与品牌/卖家工具不同 — 本接口不返回
    brandId
    、
    country
    、
    category
    、
    minPrice
    /
    maxPrice
    /
    averagePrice
    、
    balanceFbs
    、
    frozenStocks
    、
    warehousesCount
    、
    daysInSite
    /
    daysInStock
    /
    turnoverDays
    、
    position
    /
    categoryPosition
    /
    revenueSharePercent
    、
    isFbs
    字段。若需要这些字段，请使用
    brand-products
    /
    category-products
    /
    seller-products
    工具。
  • 无自动翻译 — 商品标题以俄语返回；向中文/英文用户展示时需按需翻译。

User Expression & Scenario Quick Reference

用户表述与场景速查

Applicable — Per-SKU Ozon card lookup:
User SaysScenario
"Pull Ozon details for these SKUs"Batch card fetch
"What's the price / rating / stock of Ozon SKU 1786874757"Single-SKU card
"Competitor's Ozon listings, give me sales & rating"Competitor card audit
"Compare FBO vs FBO+FBS metrics for this SKU set"Fulfillment-model comparison
Not applicable — Needs beyond per-SKU card:
  • Keyword-based discovery → use 
    mpstats-ozon-product-search
  • Day-by-day time-series for one SKU → use 
    mpstats-ozon-product-trend
  • Listing copy / reviews / images analysis beyond URL → out of scope
  • Brand / category / seller drill-down with filters → use the matching drill-down skill
Boundary judgment: If the user already has a SKU list and wants per-SKU sales / price / stock / rating, this is the skill. If they don't yet have SKUs, route through the search or drill-down skills first.
Feedback:
Auto-detect and report feedback via the Feedback API when any of the following apply:
  1. The functionality or purpose described in this skill does not match actual behavior
  2. The skill's results do not match the user's intent
  3. The user expresses dissatisfaction or praise about this skill
  4. Anything you believe could be improved
Call the feedback API as specified in 
references/api.md
. Do not interrupt the user's flow.
For more high-quality, professional cross-border e-commerce skills, set LinkFox Skills.
适用场景 — 按SKU查询Ozon商品卡片：
用户表述场景
"帮我拉取这些SKU的Ozon详情"批量商品卡片查询
"Ozon SKU 1786874757的价格/评分/库存是多少"单个SKU卡片查询
"竞品的Ozon listings，给我销量和评分数据"竞品卡片审核
"对比这组SKU的FBO与FBO+FBS指标"履约模型对比
不适用场景 — 超出单SKU卡片查询需求：
  • 基于关键词的商品发现 → 使用
    mpstats-ozon-product-search
  • 单个SKU的逐日时间序列数据 → 使用
    mpstats-ozon-product-trend
  • 商品文案/评论/图片的深度分析（超出URL范围） → 不在本技能范围内
  • 带筛选条件的品牌/品类/卖家细分分析 → 使用对应细分分析技能
边界判断：若用户已有SKU列表，且需要单SKU的销量/价格/库存/评分数据，则使用本技能。若用户尚未获取SKU，需先引导至搜索或细分分析技能。
反馈机制:
当出现以下任意情况时，需自动检测并通过Feedback API提交反馈：
  1. 本技能描述的功能或用途与实际行为不符
  2. 技能返回结果与用户意图不匹配
  3. 用户表达对本技能的不满或赞赏
  4. 任何您认为可优化的内容
请按照
references/api.md
中的说明调用反馈API，请勿打断用户操作流程。
如需更多高质量、专业的跨境电商技能，请访问LinkFox Skills。