Amazon Selling Partner application
Ecommerceville Stock Monitor connects to a seller account, reads its inventory, listings, orders and advertising through Amazon’s own APIs, and turns them into a daily picture of what needs attention and the reports that explain the month. Read-only throughout.
The daily view. Captured with the application’s privacy mode on, so account names and figures are masked — this is a real screen, not a mock-up.
What it does
Collection runs overnight. By the time anyone opens it, every connected account has been read, and the day opens on what changed rather than on an empty search box.
What is in Amazon’s warehouses, what is inbound, and how many days of cover each listing has at its current rate of sale. Listings are ordered by what runs out first, so a restock decision does not depend on anyone reading to the bottom of a table.
Listings that have gone inactive, suppressed, stranded or unbuyable, with the date each one changed. A listing that stopped selling because Amazon switched it off looks identical to one that stopped selling because demand fell, until something separates them.
Units and revenue per product and per day, alongside sessions, page views, conversion rate and Buy Box share, compared week against week. The emphasis is movement rather than totals: what grew, what fell, and by how much against the same stretch of the previous week.
Spend, attributed sales, ACOS, TACOS and campaign budgets across Sponsored Products, Sponsored Brands and Sponsored Display — including campaigns that are out of budget before the day ends, and campaigns spending more than they return.
The work list
A figure that has moved is only useful if somebody acts on it, so the application keeps four standing lists and carries each item until it is closed.
Notes and flags attach to the account and the product, so the history of what was raised, when, and what happened next stays with the thing it concerns.
Reports
A finished month against the month before it: sales, organic sales, advertising sales, orders and profitability, per product and in total, with a written summary that can go to the account owner as it stands.
The same figures mid-month, and a week-against-week view for the shorter cycle — what grew, what fell, and which products moved the total.
If a month is missing days — a broken connection, a report Amazon has not published yet — the comparison is withheld and the report says which side is short and why, instead of printing a confident percentage drawn from half a month.
Collection
Every connected account, every morning, with the state of each collection on one screen. A report that quietly stopped arriving is the failure that costs money, so the application tracks what it asked Amazon for and what came back, rather than assuming.
Also captured with privacy mode on. Account names are replaced and every figure is masked.
What it reads
How it connects
Connecting is done by the seller, from their own Seller Central account, through Amazon’s standard authorisation flow. No Seller Central password is seen, entered or held by the application or by anyone operating it.
Amazon issues a token scoped to the report types the application actually reads. Collection runs on a schedule from then on; no further action is needed from the seller.
Authorisation can be withdrawn at any time from Seller Central, under Apps and Services → Manage Your Apps. Access ends immediately, and data is deleted on the timetable set out in the privacy policy.
Access is read-only throughout. The application requests reports and reads them. It does not create, edit or delete listings, change prices, alter inventory, place orders or make changes to campaigns.
What it does not collect
The application stores nothing that identifies an account’s customers — no buyer names, delivery addresses, email addresses, telephone numbers or payment details — and it asks Amazon for none of the restricted permissions that would make those fields visible to it.
One of the reports it downloads, the order report, is capable of carrying buyer details for applications that hold those permissions. This one reads five columns from it — the date, the order and item status, the quantity, the item price and the currency — and keeps only the daily totals that come out of them. Every figure in every report works at the level of products, days, campaigns and totals.
What the application does hold, where it is held, how long it is kept and who else touches it are set out in full in the privacy policy.
How it is protected
TLS in transit and encryption at rest. Row-level security is enabled on every table holding collected data, and the anonymous and public database roles have no access to any of it.
Every person has their own account with a role, a hashed password and a time-based code from an authenticator app. No shared logins, and automatic lockout after repeated failed sign-ins.
Amazon refresh tokens are held as server-side secrets, never exposed to a browser, written into a report or logged. Significant actions are recorded with the person, the account and the time.
A written incident response plan with a named contact is reviewed every six months. Any incident touching Amazon data or credentials is reported to Amazon within 24 hours of detection. The full account is in the privacy policy.
Getting in touch
