Break down Wildberries sales and stock right in chat

The agent connects to Wildberries with a single API token and covers the whole seller loop: FBS and FBW stock, the sales report, unit economics, advertising, reviews, questions, chats, prices and shipments. For stock it pulls a summary across every seller warehouse and FBW balances per article number in one call rather than looping over warehouses, and builds a replenishment plan on top of it that accounts for sales velocity and safety stock. WB spreads those sections across separate APIs — content, statistics, analytics, prices, reviews — and the agent works out which one to ask instead of leaving that for you to remember.

Money is counted from the v5 sales report with correct cursor pagination: WB returns a field that looks like a cursor, but the real cursor is the identifier of the last row — the agent knows this, so it neither loops forever nor drops rows. The report is served no more than once a minute, so long periods are assembled in chunks with the agent holding the pauses itself instead of running into 429s. Commission, logistics and storage are taken from that same report rather than from a price list, so SKU margin is computed on the amounts actually withheld.

Unit economics per article number is assembled with the real advertising spend. On WB advertising lives in two independent loops — standard campaigns in advert-api and media advertising in advert-media-api — and the agent queries both, otherwise half of the spend would simply be missing from the report. On top of that it computes ad-cost share by SKU with alert levels and a month-by-month P&L for the account.

Reviews, questions and buyer chats are collected into a single feed of unanswered items: the agent replies to a review and to a question, pins the best review on the listing and measures your response speed. The reviews section on WB is limited to one request per second, so a long feed is worked through in portions; the agent learns about a new review or question from a webhook rather than by polling in circles. The unanswered feed can be put on a schedule so the summary arrives on its own.

The most valuable part is that the agent knows the character of the WB API. WB can answer «success» to a request with a typo and silently do nothing, so after every write the agent re-reads the state and confirms the change was applied. A listing update is a full overwrite, and the agent never sends a partial one; a media upload fails entirely because of a single broken URL, so links are checked in advance. While an asynchronous card upload is still running (up to 30 minutes), the agent leaves prices and stock alone — otherwise changes are applied only partially. Hard limits such as one FBS pass per 10 minutes and one warehouse rebinding per day are factored into its planning. And anything that changes data — prices, bids, replies — is first shown as a plan and applied only after your explicit confirmation.