Calculate Ozon unit economics and answer buyers in chat

The agent calls the Ozon Seller API directly — finance, analytics, products, FBS and FBO orders, reviews and questions, supplies. Finance is the strong side here: a monthly P&L is assembled with a single request to financial transactions, and the sum of the rows is reconciled against Ozon's own totals — a discrepancy gets shown, not hidden. Unit economics is calculated per SKU: revenue, commission, logistics, returns, tax, profit — with service charges allocated proportionally to postings. On top of that sit an ABC×XYZ classification of the portfolio, a plan/fact profit forecast and a reconciliation of compensations for returns and losses: the agent runs through every class of claim and honestly flags what could not be calculated instead of quietly understating the amount.

With reviews and questions the agent works the way Ozon is actually built: an unanswered question is identified by the answer counter, not by the status, because status in Ozon is a manual seller flag. Negative reviews are filtered by rating, your reaction speed is measured alongside, and the agent drafts replies in the brand tone of voice and surfaces whatever hits the listing rating. Listing questions and buyer chats are kept in a single unanswered feed so nothing gets lost between sections of the account.

In FBS shipping the agent knows the main trap: an HTTP 200 from Ozon does not mean the shipment went through. After every shipment it checks the actual posting status and repeats the assembly on failure, and it validates Chestny ZNAK marking codes before shipping. FBO supply requests are created through the current v2 process: draft, timeslot, request and only then a confirmed order number. New postings, cancellations, a changed assembly cutoff, a moved delivery date and a stock deficit arrive from Ozon as notifications, so the agent learns about them without polling the account in circles.

The agent is careful with prices and listings, because the Ozon API overwrites rather than merges. Bulk price updates always carry a minimum price so a promo cannot drag the price below cost. A listing import is a full replacement: the agent assembles the whole card, checks the moderation status before editing and re-reads the card afterwards. Photos are uploaded only as a complete list — the old ones plus the new ones, otherwise Ozon wipes them — and product creation limits are checked before a bulk upload rather than discovered from an error halfway through.

The agent holds the request rate for each Seller API endpoint separately: placement reports are handed out by Ozon only a few times a day, analytics and search queries far more often, and the quota is not burned on repeat exports. Heavy reports arrive asynchronously: the agent queues the job, waits for the finished file and parses it itself. Dates are converted to Moscow time, the day Ozon counts by, so the edge of a period does not push revenue into the neighbouring month. If there is no data for the period, it says so directly instead of showing an empty table.