MPSTATS Ozon Product Trend (Daily Time-Series)
This skill returns a daily time-series of a single Ozon (Russia) SKU — sales units, price, stock, rating, and optionally search-position / visibility metrics. It is the go-to for validating growth, seasonality, or anomalies for a specific product.
Core Concepts
Single-SKU scope: Each call analyzes exactly
one . For batch per-SKU snapshots (period aggregates), use
mpstats-ozon-product-detail
instead.
Daily granularity: The response is an array of daily points (top-level field
) across the
window. Each point carries a
boolean — if
, the day has no observation (distinct from
with
).
T-1 delay: MPSTATS trend data is delayed by one day; the latest selectable end date is yesterday. Today or future dates are rejected.
Search-visibility add-on: Set
to append search-position / visibility signals. Some niches (especially small categories) may not have search-stats coverage — expect partial or empty fields in those cases.
Parameters
| Parameter | Type | Required | Description |
|---|
| productId | integer | yes | Ozon SKU (numeric) |
| startDate | string | no | Window start, ; latest = yesterday |
| endDate | string | no | Window end, ; latest = yesterday |
| includeFbs | boolean | no | Include FBS data alongside FBO |
| includeSearchStats | boolean | no | Attach search position / visibility signals |
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_trend.py
directly for ad-hoc queries.
Usage Examples
1. Monthly trend for a SKU
json
{
"productId": 1786874757,
"startDate": "2025-03-01",
"endDate": "2025-03-31"
}
2. Trend with search visibility
json
{
"productId": 1786874757,
"startDate": "2025-02-01",
"endDate": "2025-02-28",
"includeSearchStats": true
}
3. Combined FBO+FBS trend
json
{
"productId": 151623766,
"startDate": "2025-01-01",
"endDate": "2025-01-31",
"includeFbs": true
}
How to Chain with Other Ozon Skills
- Discovery → trend: Use
mpstats-ozon-product-search
- Aggregate vs time-series:
mpstats-ozon-product-detail
- Drill-down → trend: After / / surfaces a hot SKU, use this skill to validate whether the hotness is recent, seasonal, or sustained.
Display Rules
- Prefer a simple table or sparkline-friendly output — one row per date with , , , , , ; do not overfit a 90-point series into a single paragraph.
- Use to distinguish gaps from zero sales — means the day has no observation; don't report it as a zero-sale day.
- Call out anomalies — large single-day spikes or stockouts ( runs where ) should be flagged factually, not as buying advice.
- Currency is RUB unless upstream layer is already converting (the field per point carries the symbol, e.g. ); state the currency when showing price movement.
- Revenue is not returned per day — if the user asks for daily revenue, estimate via and note it's an estimate.
- gaps — when no search-visibility fields come back, note "搜索位次数据在该赛道暂不可用" rather than silently omitting.
- No business advice — present the shape; leave "should we buy this listing?" to the user.
Important Limitations
- Single SKU per call — cannot pass a list of s; loop at the Agent layer if needed.
- T-1 data — cannot be today or a future date.
- Search stats optional — doesn't guarantee coverage for all niches.
- Ozon-only — Wildberries and other Russian marketplaces are not covered.
- Missing days — the series may have nulls / gaps where no data was captured; do not treat nulls as zero sales.
User Expression & Scenario Quick Reference
Applicable — Single-SKU temporal analysis:
| User Says | Scenario |
|---|
| "What's the sales trend of Ozon SKU 1786874757 last month" | Monthly time-series |
| "Is this Ozon listing seasonal or stable" | Seasonality check |
| "Did this Ozon product have stockouts recently" | Stock anomaly detection |
| "Price walk for this Ozon product over Q1" | Price movement |
| "Did this listing's search position improve" | Search visibility (requires ) |
Not applicable — Needs beyond single-SKU time-series:
- Batch snapshot of many SKUs →
mpstats-ozon-product-detail
- Brand / category / seller drill-down → matching skill
- Pre-IDed discovery →
mpstats-ozon-product-search
Boundary judgment: Use this skill when the question starts with "how did this ONE product change over time". For multi-SKU comparisons or dimension-level filtering, go elsewhere.
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.