MPSTATS Ozon Seller Products

This skill drills into all Ozon (Russia) products sold by a given seller, returning per-SKU sales, revenue, price, rating, stock, turnover, lost profit, and more. Designed for store-structure audits, bestseller dissection within a shop, and head-to-head competitor-store comparison.

Core Concepts

Seller ID, not name: sellerId must be a numeric string — the sellerId field Ozon / MPSTATS uses to identify a shop. Do not pass a brand name, category path, or human-readable seller name. If you only have the seller name, resolve the ID via mpstats-ozon-product-search (seller-filtered) and read sellerId from the result.

Filters & ops: Same AND-combined numeric filter model as brand-products and category-products. See Filter Reference.

Currency: Default RUB; override with currency / currencyRate for USD / EUR / CNY views.

FBO / FBS: includeFbs: true folds FBS into the numbers; false keeps FBO-only.

Parameters

Filter Reference

Each filters entry: {"field": "", "op": "", "value": , "value2": }.

Common fields: sales, final_price, rating, comments, balance, revenue, days_in_stock, turnover_days, lost_profit, category_position.

Operators: GTE, LTE, GT, LT, EQ, NOT_EQ, BETWEEN (requires value2).

调用方式

• API 端点：POST /mpstats/ozon/sellerProducts（完整参数/响应/错误码见 references/api.md）
• Python 脚本：python scripts/mpstats_ozon_seller_products.py '' [--inline]
• 成本约束：本工具会消耗积分；同一会话同一参数组合默认只调用一次，脚本带 24h 本地缓存。失败/空结果不得自动换关键词、翻页或改邮编连续试探；需要继续检索时先向用户说明会产生额外消耗。

输出策略（脚本默认行为）：

• 始终将完整响应写入 /linkfox///data/linkfox-mpstats-ozon-seller-products-.json（ 为脚本执行时的工作目录，在 Claude Code 里即当前项目目录； 取自环境变量 SESSION_ID，按用户任务自动聚合；禁止写入 /tmp，当前目录不可写则报错）
• 响应体 ≤ 8 KB：落盘后把完整 JSON 打印到 stdout
• 响应体 > 8 KB：落盘后 stdout 只输出摘要（顶层字段、常见计数如 total/costToken、最大列表字段的长度 + 前 3 条样本）
• 加 --inline 强制全量打印到 stdout（同样落盘）

读数据建议：先看摘要判断是否足够；需要具体字段时优先用 jq或ConvertFrom-Json 从保存的 json 文件按需抽取，避免整份 JSON 进入上下文。

Usage Examples

1. Seller's top-100 by sales

{
  "sellerId": "3628678",
  "sortField": "sales",
  "sortDirection": "desc",
  "pageSize": 100
}

2. Store's revenue top-20

{
  "sellerId": "3628678",
  "sortField": "revenue",
  "sortDirection": "desc",
  "pageSize": 20
}

3. High-turnover star products

{
  "sellerId": "3628678",
  "filters": [
    {"field": "sales", "op": "GTE", "value": 30},
    {"field": "turnover_days", "op": "LTE", "value": 20}
  ],
  "sortField": "revenue",
  "sortDirection": "desc"
}

4. Stockout pain points for the store

{
  "sellerId": "3628678",
  "filters": [{"field": "lost_profit", "op": "GTE", "value": 100000}],
  "sortField": "lost_profit",
  "sortDirection": "desc"
}

5. USD-converted store audit

{
  "sellerId": "3628678",
  "currency": "USD",
  "sortField": "revenue",
  "sortDirection": "desc"
}

Display Rules

1. Compact store table — key columns: productId, title, brand, price, monthlySalesUnits, monthlySalesRevenue, rating, balance, turnoverDays, lostProfit, position.
2. Revenue share = within this seller query — 0-100%; clarify the base.
3. Russian titles — preserve; translate on user request.
4. Currency labeling — if converted, note "已按 USD 换算".
5. Pagination — for stores with thousands of SKUs, suggest tighter filters before paging deep.
6. No buying advice — the skill shows the store's book, not whether their SKUs are worth copying.

Important Limitations

• Numeric seller ID only — passing a seller name will not resolve; go through mpstats-ozon-product-search first.
• Page cap — max 100 rows per page.
• T-1 data — endDate cannot be today or a future date.
• No business advice — data-only.
• Ozon-only — Wildberries / other Russian marketplaces are separate.

User Expression & Scenario Quick Reference

Applicable — Seller-scoped Ozon product metrics:

Not applicable — Needs beyond seller drill-down:

• Only seller name known → use mpstats-ozon-product-search to resolve the ID
• Brand-scoped drill → mpstats-ozon-brand-products
• Category-scoped drill → mpstats-ozon-category-products
• Single-SKU time-series → mpstats-ozon-product-trend
• Wildberries / other Russian marketplaces → not covered

Boundary judgment: Use this skill when the dimension is a specific seller and you want the per-SKU table under that shop. For "who are the top sellers in category X" you'd use category drill-down and group by seller client-side.

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.