Track stock, profit and purchasing in MoySklad right in the chat

The agent connects to MoySklad with an employee API token and works with the whole account: sales and profit, stock and warehouses, counterparties, money in the accounts, documents. The agent's permissions equal those of the employee whose token is connected — the role decides which sections of the JSON API 1.2 the agent sees at all. Related entities it pulls in with the expand parameter, one request instead of a dozen, so going through documents never turns into walking card by card. The connection itself is verified with a request for the list of organizations, so an invalid or revoked token shows up immediately instead of surfacing in the middle of the first report.

The agent counts sales properly: revenue for a period adds up from wholesale shipments and retail sales, while profit and margin per product are calculated from the FIFO cost price. If there are no permissions for cost prices, the agent switches to the purchase price on its own and says so explicitly. Daily sales dynamics, money in the accounts, receivables and payables, the buyers of a specific product with their phone numbers — all straight from the account, with no manual exports. The agent detects the accounting currency automatically, be it rubles, tenge or another one, and never confuses kopecks with rubles: MoySklad returns amounts in kopecks, and that is accounted for everywhere.

Stock comes as a single overview: units and money, a breakdown by warehouse, zero and negative positions as separate counters. The most useful part for purchasing is the positions below the minimum stock level, and there is a trap here that is not visible in the API at first glance: MoySklad does not return per-warehouse thresholds in ordinary requests, so a naive check decides that no minimum is configured while dozens of positions sit below it. The agent uses the proper server-side filter and finds them all — including cases where the balance is positive but still below the threshold of that particular warehouse.

For the shortages it finds the agent prepares documents: a draft internal order to replenish a warehouse, or draft purchase orders grouped by the supplier from the product card, with demand forecast based on sales velocity and lead time. Documents are created in the account only after your explicit yes: the agent shows exactly what it is about to create and waits for confirmation. Products with no supplier in the card are listed as a separate line instead of being silently skipped.

The agent paces its own requests: no more than seven calls per second to the API and no more than three per second to the heavy stock reports, so the account does not hit the limits while the agent collects data. If the role lacks permissions, the agent names the missing section right in the chat and asks you to extend the employee role — instead of a cryptic 403 error in the middle of a report. The data itself comes straight from the API directories, entity metadata and report slices rather than from a pre-exported copy, so the numbers in the chat match what is in the account right now.