MPSTATS Ozon Russia single SKU daily time series performance. Returns daily sales units, price, stock, rating, and optionally search position/visibility data for one Ozon product by date granularit...
Добавьте инструмент одной командой или скачайте проверенный архив версии.
npx skills add nexscope-ai/nexscope-ecommerce-skills --skill ecommerce-ozon-product-trendThis 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.
Single-SKU scope: Each call analyzes exactly one productId. For batch per-SKU snapshots (period aggregates), use ecommerce-ozon-product-detail instead.
Daily granularity: The response is an array of daily points (top-level field data) across the [startDate, endDate] window. Each point carries a hasData boolean — if hasData=false, the day has no observation (distinct from sales=0 with hasData=true).
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 includeSearchStats: true 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
| productId | integer | yes | Ozon SKU (numeric) |
| startDate | string | no | Window start, YYYY-MM-DD; latest = yesterday |
| endDate | string | no | Window end, YYYY-MM-DD; latest = yesterday |
| includeFbs | boolean | no | Include FBS data alongside FBO |
| includeSearchStats | boolean | no | Attach search position / visibility signals |
/mpstats/ozon/productTrend (full parameters/responses/error codes in references/api.md)python scripts/ozon_product_trend.py '<JSON params>' [--inline]Output strategy (script default behavior):
<cwd>/nexscope/<YYYY-MM-DD>/<session>/data/ecommerce-ozon-product-trend-<timestamp>.json (<cwd> is the working directory when the script executes, which in Claude Code is the current project directory; <session> is taken from the SESSION_ID environment variable, automatically grouped by user task; do not write to /tmp; error if the current directory is not writable)total/costToken, length of the largest list field + first 3 samples)--inline to force full output to stdout (still writes to disk)Reading data: Check the summary first to determine if it is sufficient. When specific fields are needed, use jq or ConvertFrom-Json to extract from the saved JSON file as needed, avoiding loading the entire JSON into context.
If you encounter authentication or credit issues:
NEXSCOPE_API_KEY environment variable is not set.NEXSCOPE_API_KEY environment variable with a valid API key.1. Monthly trend for a SKU
{
"productId": 1786874757,
"startDate": "2025-03-01",
"endDate": "2025-03-31"
}
2. Trend with search visibility
{
"productId": 1786874757,
"startDate": "2025-02-01",
"endDate": "2025-02-28",
"includeSearchStats": true
}
3. Combined FBO+FBS trend
{
"productId": 151623766,
"startDate": "2025-01-01",
"endDate": "2025-01-31",
"includeFbs": true
}
ecommerce-ozon-product-search to find a SKU, then check growth / volatility here before committing.ecommerce-ozon-product-detail gives a one-number-per-metric period view; this skill shows the day-by-day shape behind those numbers.brand-products / category-products / seller-products surfaces a hot SKU, use this skill to validate whether the hotness is recent, seasonal, or sustained.date, price, sales, balance, rating, comments; do not overfit a 90-point series into a single paragraph.hasData to distinguish gaps from zero sales — hasData=false means the day has no observation; don't report it as a zero-sale day.balance=0 runs where hasData=true) should be flagged factually, not as buying advice.currency field per point carries the symbol, e.g. ₽); state the currency when showing price movement.sales * price and note it's an estimate.includeSearchStats gaps — when no search-visibility fields come back, note "search position data is not available for this niche" rather than silently omitting.productIds; loop at the Agent layer if needed.endDate cannot be today or a future date.includeSearchStats=true doesn't guarantee coverage for all niches.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 includeSearchStats) |
Not applicable — Needs beyond single-SKU time-series:
ecommerce-ozon-product-detail*-products skillecommerce-ozon-product-searchBoundary 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.
| Путь | Размер | SHA256 |
|---|---|---|
| SKILL.md | 8191 | d216f4524869d75c... |
| manifest.json | 281 | b20d2ada72c2a4e5... |
| references/api.md | 4293 | 854bb75843abe1cc... |
| scripts/ozon_product_trend.py | 6701 | ee7f578b716c162d... |
npx skills add nexscope-ai/nexscope-ecommerce-skills --skill ecommerce-ozon-product-trend или скачайте ZIP-архив.Войдите, чтобы оставить комментарий.
Комментариев пока нет.