Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
linkfox-ai avatar

Linkfox Mpstats Ozon Seller Products

  • 248 installs
  • 64 repo stars
  • Updated August 3, 2026
  • linkfox-ai/linkfox-skills

List and analyze Ozon seller catalogs through MPStats to map Russian marketplace assortment, pricing bands, and rival storefront strategies.

About

Connects to MPStats to retrieve and analyze products sold by Ozon marketplace sellers. Useful for mapping competitor catalogs, pricing clusters, and category concentration when exploring Russia/CIS ecommerce expansion or benchmarking local incumbents.

  • MPStats Ozon seller catalog export
  • Russian marketplace competitor mapping
  • Assortment and pricing band review
  • Cross-border expansion research
  • Agent-friendly seller intelligence

Linkfox Mpstats Ozon Seller Products by the numbers

  • 248 all-time installs (skills.sh)
  • +36 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #269 of 853 Sales & Marketing skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/linkfox-ai/linkfox-skills --skill linkfox-mpstats-ozon-seller-products

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs248
repo stars64
Last updatedAugust 3, 2026
Repositorylinkfox-ai/linkfox-skills

What it does

List and analyze Ozon seller catalogs through MPStats to map Russian marketplace assortment, pricing bands, and rival storefront strategies.

Files

SKILL.mdMarkdownGitHub ↗

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

ParameterTypeRequiredDescription
sellerIdstringyesOzon seller ID as numeric string, e.g. "3628678"
startDatestringnoStats window start, YYYY-MM-DD; latest = yesterday
endDatestringnoStats window end, YYYY-MM-DD; latest = yesterday
pageintegernoPage number, starts at 1
pageSizeintegernoRows per page, 1-100, default 100
sortFieldstringnosnake_case column (sales, revenue, ...)
sortDirectionstringnoasc / desc
currencystringnoCurrency code, default RUB
currencyRateintegernoCustom rate for non-default currency
includeFbsbooleannoInclude FBS data
filtersarraynoNumeric 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 Usage

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_seller_products.py directly for ad-hoc queries.

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 dataendDate 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 SaysScenario
"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.

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.

<!-- LF_LARGE_RESPONSE_BLOCK -->

Handling Large Responses

To avoid overflowing the agent context, persist the response to disk and extract only the fields you need:

python scripts/response_io.py run --script scripts/mpstats_ozon_seller_products.py --out-dir <DIR> '<params>'
python scripts/response_io.py read <file> --fields "<paths>"   # or --path "<JMESPath>"
Pick --out-dir outside any git working tree (e.g. /tmp/... on Unix, %TEMP%/... on Windows). Persisted responses may contain PII, pricing, or auth-sensitive data — do not commit them. Files are not auto-deleted; clean up when the task is done.

run writes the full response to a file and emits only a schema preview + file path. read projects specific fields, with --limit/--offset for slicing and --format json|jsonl|csv|table for output.

When to prefer this pattern — apply your judgment based on the response characteristics, e.g.:

  • High field count per record, or fields you don't need
  • Batch/paginated results (multiple items per call)
  • Long-text fields (descriptions, reviews, HTML, time series)
  • Output reused across later steps rather than consumed immediately

For small, single-use responses, calling the main script directly is fine.

⚠️ The preview is a truncated schema + sample, not the full data. Any field-level decision must read from the persisted file via read. <!-- /LF_LARGE_RESPONSE_BLOCK -->

--- For more high-quality, professional cross-border e-commerce skills, set [LinkFox Skills](https://skill.linkfox.com/).

Related skills

Sales & Marketingecommercepricing

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.