Follow MegaMarket orders and shipments from a single chat

The agent calls the MegaMarket Seller API and keeps the whole scope of the account in view: products and categories, prices and stock, orders under the FBO and DBS schemes, supplies, shipments and reports. It totals revenue for a period, breaks orders down by status, finds shipments that are stuck and names the reasons for cancellations — not as a download, but as an analysis that makes it clear where exactly the shop loses money.

The MegaMarket catalogue rests on a category tree: the set of attributes a listing has is defined by its category, so the agent starts by reading the categories and only then touches the products. Prices and stock meanwhile live in sections of their own: a price you send moves no stock, and an updated stock figure changes no price. Discrepancies between the storefront and your books are shown before they turn into cancellations.

MegaMarket sends no notifications, so new orders and stalled shipments are picked up by polling — on your question, or on a schedule when a regular digest is needed. Price and stock changes are sent in batches and the result is re-read rather than taken on trust from a successful response code, and before a bulk price edit the agent stops and shows exactly what is about to reach the storefront.

The work runs on a single seller token passed in a header of its own: there is no sign-in under your account, and deleting the token in the cabinet closes access at once — the agent then says so instead of quietly returning zero. Orders and reports come out of the Seller API in date windows, so a long period is cut into slices and stitched back together by the agent. It holds the request rate itself, and about an unavailable section it says so directly instead of showing an empty table.