Skip to content
Reportkey
Ozon Seller
Ozon Seller via API

Ozon seller report: orders and top products

Reportkey reads Ozon seller analytics through the Seller API and builds a report block from it: ordered amount, ordered units, trend by period and a product ranking by SKU, next to external ads and the brand website.

Sign up, add the Client-Id and API key from the seller dashboard and pick the store in a project. Your first report in 5 minutes.
  • The Ozon Client-Id and API key are entered once and reused across projects.
  • Ordered amount, units and top SKUs with a previous-period comparison.
  • Ozon orders share one report with Yandex Direct, VK Ads and Metrica, plus AI insights and branding (not on every plan).
Sample Reportkey client report
Sample Reportkey client report
Ozon Seller Orders, ordered amount, and top products
30+
integrations
5 min
setup
14 days
trial
TL;DR

Ozon Seller integration: enter the Client-Id and API key pair from the seller dashboard once, pick the store in a project, and ordered amount, units and top SKUs go into a recurring link or PDF report alongside Yandex Direct, VK Ads and Yandex Metrica.

Ozon seller report for agencies and brands

Agencies and marketplace managers report to sellers on weekly or monthly store orders and on the products driving sales, usually in the same conversation as the external ads that send shoppers to product cards. The usual routine is an export from the seller dashboard, a spreadsheet and a separate ads report. Reportkey does this step for you: it reads seller analytics through the Ozon Seller API and turns it into a section of a recurring report delivered as a link or PDF.

Ozon orders sit next to the seller’s other channels, so the client sees ad budget, brand website visits and how the ordered amount changed in the store over the same period.

Connecting Ozon Seller: Client-Id and API key

Access to Ozon seller analytics uses two values: a Client-Id and an API key. They are created in the seller dashboard under API settings by the store owner or a user with admin rights. These are Seller API keys; Ozon Performance keys belong to advertising and will not work here.

In Reportkey you enter the pair once on the integrations page. The key is checked right away and saved as a shared connection you can pick in any project. If you manage several sellers, each one has its own connection, and the client project uses the right store.

Then you choose report blocks and the period in project settings and set a delivery schedule. If Ozon stops accepting the key, for example after it was revoked in the seller dashboard, the connection is flagged for re-authorisation. You update the key on the integrations page and project settings stay in place.

Ordered amount and units by day, week and month

The analytics data method of the Seller API returns the store’s core metrics, and the report block is built from them:

  • Ordered amount — the value of orders placed in the period; the main number for discussing store trends.
  • Ordered units — items in those orders. Together with the amount, it shows whether the average order grew or simply more items sold.
  • Trend — the same metrics by day, week or month, so you can see when growth or a drop began.
  • Previous-period comparison — the change versus last week or month next to each number.
  • Impressions, sessions, conversions, returns and cancellations — for stores on an extended seller subscription.

Top products by SKU

Grouping by SKU turns the total into a ranking: which products bring most of the ordered amount, which are slipping and which sell one at a time. For an agency this is the work plan for product cards and external traffic. For a brand selling directly, it is a quick answer to which products carry the store.

Ordered amount is not revenue

The most common mistake in marketplace reports is calling the ordered amount revenue. Some orders are cancelled, some returned, fees are deducted, and the seller receives noticeably less. The report keeps Ozon’s own label, and it is worth explaining this to a client who compares the numbers with accounting.

Attribution is the second caveat. Seller analytics shows the whole store result, including organic sales, and does not tie orders to a specific campaign. Ozon and Wildberries also measure different things: Ozon’s core metric is store orders, while Wildberries reports a product card funnel from open to buyout, so the two platforms should not be added up in one line.

Seller subscription and history depth

Data depth depends on the store’s subscription. Without Premium Plus the API returns the last three months and a core set of metrics; extended plans remove these limits. Two clients of the same agency may therefore see different Ozon blocks, and the report shows exactly what Ozon opens for each store.

Ozon next to ads and the brand website

Add Yandex Direct spend and campaigns, VK Ads campaigns driving product traffic and brand website visits in Yandex Metrica to the same report. For a second marketplace, add the Wildberries card funnel; for classifieds, Avito Pro listing statistics. AI insights, branding and scheduled delivery are available, though not on every plan. See a multi-channel example in the in-house team demo report, browse all platforms on the marketplaces page, and check plans and the 14-day free trial on pricing.

Metrics

What goes into the Ozon Seller report

These are the metrics that the Ozon Seller integration already brings into Reportkey reports.

Ordered amount
Ordered units
Top products
Sales dynamics
What this integration adds to the report
Orders, ordered amount, and top products
Pricing

Ozon Seller reporting: plans and free trial

14 days free, no card required. Prices and plan limits are on the pricing page.

Use cases

Why teams connect Ozon Seller to Reportkey

Real reporting jobs, typical pain points, and the outcomes teams get from Ozon Seller in client reports.

Pain points
  • Every week a marketplace manager exports analytics from the Ozon seller dashboard and rebuilds orders by product and period by hand.
  • The seller sees external ad spend in one report and store orders in another dashboard, so the link between them is explained verbally.
  • The SKU table is rebuilt every month, and the period comparison depends on whether someone kept last month's export.
Ozon Seller
An agency running the store and external traffic

One report shows VK Ads and Yandex Direct campaigns, brand website visits and Ozon store orders for the same period. The call is about how orders moved after ads launched, not about where the numbers came from.

Ozon Seller
A brand selling on Ozon directly

The marketer connects the store once and gets a weekly summary: ordered amount, units and top SKUs compared with the previous week. No more manual exports from the seller dashboard.

Ozon Seller
A freelance marketplace manager

Each seller gets a separate project with its own Ozon store and schedule. The report goes to the client as a link or PDF, and the specialist adds a note on which product cards to work on next.

Report preview

How Ozon Seller appears inside the report

The report keeps the familiar Reportkey layout: source sections and period comparison.

Sample Reportkey client report
Sample Reportkey client report
Weekly Ozon orders block

A chart of ordered amount and units by week compared with the previous period, and a product table by SKU with ordered amount, units and change versus last week.

How to connect

Three steps to the first report

Connect the account once, choose the reporting scope, and save the setup for recurring client reports.

01
Connect the account
Save the Ozon Seller connection once so the same datasource can be reused across recurring client reports.
02
Choose the reporting scope
Choose the Ozon Seller store or account that should supply sales, product, or listing data to the report.
03
Save the setup and generate the report
Keep the selected scope in the project and reuse the same report setup next time instead of connecting the source again.
FAQ

Frequently asked questions

Short answers about how the integration works in Reportkey today.

What do I need to connect Ozon Seller to Reportkey?
The Client-Id and API key pair from the Ozon seller dashboard, created by the store owner or an admin user in the API settings. These are Seller API keys, not Ozon Performance keys. You enter the pair once on the integrations page and reuse it in every project.
Is the ordered amount the store's revenue?
No. Ozon labels it the ordered amount: the value of placed orders before cancellations, returns and fees. Seller payouts and accounting revenue are calculated differently, so the report labels the figure as ordered amount.
Why does the metric set differ between stores?
Ozon unlocks some metrics and longer history only with an extended seller subscription. Without Premium Plus the API returns the last three months and a core metric set; impressions, sessions, conversions, returns and cancellations require an extended plan. The report shows what Ozon returns for your store.
How fresh is the Ozon data?
Data comes from seller analytics at the moment the report is built. Ozon recalculates orders with some delay and the Seller API limits how often it can be called, so a large catalogue is loaded in several sequential steps. This does not affect weekly or monthly reporting.
Are Ozon advertising statistics included?
Seller analytics and on-platform advertising are separate. Ozon Performance covers promotion with its own API and keys, while this block shows store results: orders and products.
How is this different from analytics in the seller dashboard?
The seller dashboard is built for working inside the store. A Reportkey report is a client document: Ozon orders sit next to external ads and the website, with a previous-period comparison, scheduled delivery and your logo instead of the platform interface.

Ozon seller report: orders and top products

Sign up, add the Client-Id and API key from the seller dashboard and pick the store in a project. Your first report in 5 minutes.

Start free