MPSTATS Ozon Product Detail (Batch)
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.
Core Concepts
Batch semantics: Pass up to
100 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
:
- — Fulfillment by Ozon (stock in Ozon warehouses)
- — Fulfillment by Seller (seller-shipped)
Pass
to allow FBS SKUs and FBS-scoped metrics into the response;
(or omitted) keeps the result FBO-centric. This switch applies to the whole batch.
Previous-period comparison: The card includes
/
— sales and revenue from the equal-length period immediately before
— ready for MoM / period-over-period diffs without extra calls.
Revenue potential:
projects what the SKU could have earned if it had been in stock every day of the window; compare with
to quantify stock-out drag, together with
/
.
Date window:
/
define the period for all period-aggregated metrics. Latest selectable date is
yesterday (T-1); today and future dates are rejected.
Parameters
| Parameter | Type | Required | Description |
|---|
| productIds | array<integer|string> | yes | Ozon SKU list, up to 100 per call |
| startDate | string | no | Stats window start, ; latest = yesterday |
| endDate | string | no | Stats window end, ; latest = yesterday |
| includeFbs | boolean | no | to include FBS data; = FBO-only |
API Usage
This tool calls the LinkFox tool gateway API. See
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.
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>]}
How to Chain with Other Ozon Skills
- Search → detail: Use
mpstats-ozon-product-search
- 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
- Detail vs drill-downs: When the input dimension is a brand / category / seller (not a SKU list), prefer / / — they already return aggregated metrics per SKU under that dimension.
Display Rules
- Compact table — lead with , , , , , , , , , . Pull / / in when the user asks about stock-out impact.
- Currency — Ozon native currency is RUB; the field carries the symbol. Do not silently relabel.
- Partial success — the response carries / / ; when , list the failed s from to the user rather than silently dropping them.
- Period-over-period — when both current and fields are present, render them side-by-side or as diff; don't report a single-period number as "trend".
- With-stock vs all-days — /
dailySalesRevenueWithStock
- Delivery model — prefer the per-SKU value over assuming FBO; remind users when a batch mixes FBO and FBS.
- No business advice — present data; do not extrapolate "this SKU is worth selling" without a wider analysis.
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 — 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 , , , / / , , , , / / , / / , . Use / / if those are needed.
- No translation — titles are returned in Russian; translate on demand when presenting to Chinese / English users.
User Expression & Scenario Quick Reference
Applicable — Per-SKU Ozon card lookup:
| User Says | Scenario |
|---|
| "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:
- The functionality or purpose described in this skill does not match actual behavior
- The skill's results do not match the user's intent
- The user expresses dissatisfaction or praise about this skill
- Anything you believe could be improved
Call the feedback API as specified in
. Do not interrupt the user's flow.
For more high-quality, professional cross-border e-commerce skills, set LinkFox Skills.