Skip to main content
skill CX Codex

linkfox-mpstats-ozon-seller-products — Claude Code skill for Ozon

This skill pulls every product a given Ozon seller has, with sales, revenue, price, rating, stock, turnover and lost profit per SKU.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add linkfox-ai/linkfox-skills --skill linkfox-mpstats-ozon-seller-products -a claude-code
Open on GitHub

What linkfox-mpstats-ozon-seller-products does

The skill queries MPSTATS and returns a per-SKU table for one Ozon shop. You can sort by any column, stack numeric filters with AND, and convert currency: RUB by default, USD, EUR or CNY via currency and currencyRate. Setting includeFbs to true folds FBS numbers into the FBO ones.

Under the hood there is a Python script, scripts/mpstats_ozon_seller_products.py, which takes a JSON argument and calls POST /mpstats/ozon/sellerProducts. The full response always lands in <cwd>/linkfox/<YYYY-MM-DD>/<session>/data/; stdout gets either the whole JSON or a short summary when the body exceeds 8 KB. Pulling fields out of the saved file with jq keeps the context clean.

One hard rule: sellerId has to be a numeric string. A shop name or brand will not resolve, so find the ID through mpstats-ozon-product-search first. You also need LINKFOX_AGENT_API_KEY in your environment, or the call comes back 401 or 402. Data runs on a T-1 lag, so endDate cannot be today or later. A page holds at most 100 rows, and each call burns 12 compute units — worth remembering before you fire off a batch of queries.

What it helps with

  • map every SKU in an Ozon shop from its numeric sellerId
  • find products with turnover under a set number of days
  • estimate how much a shop loses to stockouts
  • compare two Ozon stores by SKU count and sales
  • export a seller's top products by revenue in USD

Example prompts for the agent

  • Show me everything seller 3628678 sells, sorted by sales
  • Which products bring this Ozon store the most revenue?
  • How many SKUs does this shop have with turnover under 20 days?

How to install linkfox-mpstats-ozon-seller-products

1Skills CLI (Vercel)

npx skills add linkfox-ai/linkfox-skills --skill linkfox-mpstats-ozon-seller-products -a claude-code

2Manually: put the files in place

~/.claude/skills/linkfox-mpstats-ozon-seller-products/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/linkfox-mpstats-ozon-seller-products/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about linkfox-mpstats-ozon-seller-products

How do I install linkfox-mpstats-ozon-seller-products in Claude?

Run npx skills add linkfox-ai/linkfox-skills --skill linkfox-mpstats-ozon-seller-products -a claude-code. The skill file then sits at ~/.claude/skills/linkfox-mpstats-ozon-seller-products/SKILL.md.

What does linkfox-mpstats-ozon-seller-products do?

It returns every product sold by an Ozon seller with sales, revenue, price, rating, stock, turnover and lost profit per SKU. Useful for auditing a store's structure and benchmarking it against competitors.

Why can't the skill find a seller by name?

sellerId only accepts a numeric string. If you have just the shop name, resolve the ID with mpstats-ozon-product-search and read the sellerId field from the result.

Source text

SKILL.md · MIT
---
name: linkfox-mpstats-ozon-seller-products
description: MPSTATS Ozon 俄罗斯站按卖家 ID 下钻商品列表。返回该卖家下全部 SKU 的销量、销售额、价格、评分、库存、周转、损失销售额等完整指标,支持多维数值筛选、排序、货币换算。用于店铺结构分析、卖家爆款拆解、竞争对手店铺对标。当用户提到 Ozon 卖家商品、Ozon 店铺分析、Ozon 卖家下钻、Ozon 卖家 SKU、Ozon 店铺爆款、Ozon 竞争店铺、MPSTATS seller, Ozon seller drill-down, Ozon shop audit, Russian marketplace seller SKUs, Ozon store structure 时触发此技能。即使用户未明确说"MPSTATS",只要意图是按 Ozon 卖家 ID 看该店铺下全部商品的销售表现,也应触发此技能。
---

# 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| sellerId | string | yes | Ozon seller ID as numeric string, e.g. `"3628678"` |
| startDate | string | no | Stats window start, `YYYY-MM-DD`; latest = yesterday |
| endDate | string | no | Stats window end, `YYYY-MM-DD`; latest = yesterday |
| page | integer | no | Page number, starts at 1 |
| pageSize | integer | no | Rows per page, 1-100, default 100 |
| sortField | string | no | snake_case column (`sales`, `revenue`, ...) |
| sortDirection | string | no | `asc` / `desc` |
| currency | string | no | Currency code, default `RUB` |
| currencyRate | integer | no | Custom rate for non-default currency |
| includeFbs | boolean | no | Include FBS data |
| filters | array | no | Numeric filter list |

## Filter Reference

Each `filters` entry: `{"field": "<snake_case>", "op": "<OP>", "value": <num>, "value2": <num?>}`.

**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 '<JSON 参数>' [--inline]`
- **成本约束**:本工具会消耗算力;同一会话同一参数组合默认只调用一次,脚本带 24h 本地缓存。失败/空结果不得自动换关键词、翻页或改邮编连续试探;需要继续检索时先向用户说明会产生额外消耗。

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

**读数据建议**:先看摘要判断是否足够;需要具体字段时优先用 `jq`或`ConvertFrom-Json` 从保存的 json 文件按需抽取,避免整份 JSON 进入上下文。
## 解决认证和算力问题
发生以下异常情况时,采用 references/onboarding.md 引导解决问题:

### 异常情况
- **未配置API Key**:环境变量未配置 `LINKFOX_AGENT_API_KEY`,也未配置 `LINKFOXAGENT_API_KEY`。
- **响应401或402状态码**
- **响应提示算力或余额不足**:消息含"算力余额不足/计费不足/余额不足/quota exceeded/insufficient balance/套餐到期/需充值/请充值",或类似含义的内容。

## Usage Examples

**1. Seller's top-100 by sales**
```json
{
  "sellerId": "3628678",
  "sortField": "sales",
  "sortDirection": "desc",
  "pageSize": 100
}
```

**2. Store's revenue top-20**
```json
{
  "sellerId": "3628678",
  "sortField": "revenue",
  "sortDirection": "desc",
  "pageSize": 20
}
```

**3. High-turnover star products**
```json
{
  "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**
```json
{
  "sellerId": "3628678",
  "filters": [{"field": "lost_profit", "op": "GTE", "value": 100000}],
  "sortField": "lost_profit",
  "sortDirection": "desc"
}
```

**5. USD-converted store audit**
```json
{
  "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:

| User Says | Scenario |
|-----------|----------|
| "Show me everything seller 3628678 sells, by sales" | Store SKU map |
| "What are this Ozon store's top revenue products" | Store bestseller drill |
| "How many SKUs does the store have with turnover <20 days" | Operational health filter |
| "Where is this store losing money to stockouts" | Lost-profit scan |
| "Compare two Ozon stores' SKU counts and sales" | Store-vs-store benchmarking (call twice) |

**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.

## 算力消耗规则

按动态规则计费:消耗算力 = 12。列表为空返回 0

> **重要**:本技能的服务按倍数动态计算,可能一次性消耗大量算力,必须提醒用户,由用户决定是否继续。

**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](https://skill.linkfox.com/).*

© linkfox-ai · MIT · linkfox-ai/linkfox-skills

Similar skills

Everything for Marketing and content →

From the same set15

linkfox-mpstats-ozon-product-search Searches Ozon products in the MPSTATS database by Russian keyword or SKU list. Returns product ID, title, brand and seller — the entry point for competitor research. CX Codex +1 447installs linkfox-mpstats-ozon-product-detail Pulls the full MPSTATS product card for one Ozon SKU: price, discount, rating, reviews, stock, sales and lost revenue. CX Codex +1 421installs linkfox-mpstats-ozon-product-trend Pulls a day-by-day series for a single Ozon listing: sales, price, stock, rating. Useful when you need to tell growth apart from a seasonal spike. CX Codex +1 414installs linkfox-walmart-search The skill searches and browses Walmart listings by keyword, category and price. Useful for price comparison and competitor research. CX Codex +1 410installs linkfox-multimodal-extract-attributes Runs product main images through a multimodal model and returns color, shape, material and style as structured fields. CX Codex +1 409installs linkfox-product-title-analyze Tokenizes product titles and counts word frequencies: scene, audience, material. Useful when you rewrite listings against competitors. CX Codex +1 408installs linkfox-mpstats-ozon-brand-products Pulls every product a brand sells on Ozon with sales, price, rating and lost profit. Handy for auditing a competitor's shelf or your own. CX Codex +1 404installs linkfox-multimodal-product-similarity Compares product main images and sorts a list into visual groups. Useful for spotting near-identical listings or lookalikes from other brands. CX Codex +1 400installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor