Break down sales and stock for your Uzum Market store

The agent works through the Uzum Market Seller Open API: it reads the store's products, FBS orders and the invoices behind them, stock by SKU, returns and the finance side — charges on orders and expenses. Out of that it assembles revenue for a period broken down by product, finds the positions on the edge of going out of stock and shows how much of a sale is left after the marketplace commissions and deductions.

Everything on Uzum is tied to a store: a single seller token may cover several of them, and almost every request runs in the context of one particular store. So the agent starts with the list of stores, then holds on to the right one and never mixes the figures of neighbouring storefronts into one summary. API sections live in different versions — orders, stock and invoices evolved independently — and the agent calls the current one for each.

The financial truth here comes from two sources: charges on orders and expenses sit apart, and revenue on orders is not yet what reaches your account. The agent takes both sections and separately subtracts returns, which reduce a sale already counted. Its main work on Uzum is arithmetic and read-oriented; where a stock figure or an order has to be changed, it shows the change before sending and re-reads the result afterwards.

The agent puts the seller token into every request as it is, with no prefix, and keeps one for all sections; a token revoked in the cabinet stops working at that very moment, and the agent says so at once rather than halfway through a report. Uzum hands out long lists of orders and stock in pages, so the agent walks the period page by page and adds the total up itself. It signs a summary with the store name so storefronts do not get confused, and if a section is empty it says so directly instead of showing an empty table.