MPSTATS Ozon Russia SKU full detail batch query. Pass up to 100 Ozon product IDs at once, returning each SKU's price, discount, Ozon Card price, rating, review count, stock, sales, revenue, revenue...
Добавьте инструмент одной командой или скачайте проверенный архив версии.
npx skills add nexscope-ai/nexscope-ecommerce-skills --skill ecommerce-ozon-product-detailThis 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.
Batch semantics: Pass up to 100 productIds 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 deliveryScheme:
FBO — Fulfillment by Ozon (stock in Ozon warehouses)FBS — Fulfillment by Seller (seller-shipped)Pass includeFbs: true to allow FBS SKUs and FBS-scoped metrics into the response; false (or omitted) keeps the result FBO-centric. This switch applies to the whole batch.
Previous-period comparison: The card includes previousSalesUnits / previousRevenue — sales and revenue from the equal-length period immediately before [startDate, endDate] — ready for MoM / period-over-period diffs without extra calls.
Revenue potential: revenuePotential projects what the SKU could have earned if it had been in stock every day of the window; compare with monthlySalesRevenue to quantify stock-out drag, together with lostProfit / lostProfitPercent.
Date window: startDate / endDate define the period for all period-aggregated metrics. Latest selectable date is yesterday (T-1); today and future dates are rejected.
| Parameter | Type | Required | Description |
|---|---|---|---|
| productIds | array<integer|string> | yes | Ozon SKU list, up to 100 per call |
| startDate | string | no | Stats window start, YYYY-MM-DD; latest = yesterday |
| endDate | string | no | Stats window end, YYYY-MM-DD; latest = yesterday |
| includeFbs | boolean | no | true to include FBS data; false = FBO-only |
/mpstats/ozon/productDetail (full parameters/responses/error codes in references/api.md)python scripts/ozon_product_detail.py '<JSON params>' [--inline]Output strategy (script default behavior):
<cwd>/nexscope/<YYYY-MM-DD>/<session>/data/ecommerce-ozon-product-detail-<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. Single-SKU detail
{"productIds": [1786874757]}
2. Batch lookup with period
{
"productIds": [1786874757, 151623766, 142257239],
"startDate": "2025-03-01",
"endDate": "2025-03-31",
"includeFbs": true
}
3. FBO-only snapshot
{"productIds": [1786874757, 151623766], "includeFbs": false}
4. SKUs discovered upstream — full card
{"productIds": [<list from ecommerce-ozon-product-search>]}
ecommerce-ozon-product-search to resolve a keyword / brand / seller into productIds, then pass them here for full metrics.ecommerce-ozon-product-trend.brand-products / category-products / seller-products — they already return aggregated metrics per SKU under that dimension.productId, title, price, monthlySalesUnits, monthlySalesRevenue, rating, reviewCount, balance, deliveryScheme, firstDate. Pull revenuePotential / lostProfit / lostProfitPercent in when the user asks about stock-out impact.currency field carries the symbol. Do not silently relabel.successCount / failedCount / failures; when failedCount > 0, list the failed productIds from failures to the user rather than silently dropping them.previous* fields are present, render them side-by-side or as diff; don't report a single-period number as "trend".salesPerDayWithStock / dailySalesRevenueWithStock only count days that had inventory; distinguish from the plain salesPerDay / dailySalesRevenue.deliveryScheme value over assuming FBO; remind users when a batch mixes FBO and FBS.endDate must not be today or future.brandId, country, category, minPrice / maxPrice / averagePrice, balanceFbs, frozenStocks, warehousesCount, daysInSite / daysInStock / turnoverDays, position / categoryPosition / revenueSharePercent, isFbs. Use brand-products / category-products / seller-products if those are needed.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:
ecommerce-ozon-product-searchecommerce-ozon-product-trendBoundary 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.
| Путь | Размер | SHA256 |
|---|---|---|
| SKILL.md | 9312 | 9f0cc8b4afa2c81a... |
| manifest.json | 285 | 3c953c862794b5fa... |
| references/api.md | 6279 | 841fbcfa3a662c88... |
| scripts/ozon_product_detail.py | 6710 | e378e9ef6f94d815... |
npx skills add nexscope-ai/nexscope-ecommerce-skills --skill ecommerce-ozon-product-detail или скачайте ZIP-архив.Войдите, чтобы оставить комментарий.
Комментариев пока нет.