Every number,
one date range
Fifteen reports across the two apps. What you sold, what it cost to ship, how fast it went out the door, which listings earn their shelf space and which quietly do not. Each one is built from your own orders, your own labels and your own marketplace figures — no estimates, no models, no other seller's numbers mixed in.
One date range
Today, yesterday, this year against last, or any window you pick.
Your figures only
Built from your orders and labels, never pooled with anyone else's.
Readable over the API
Every report is a documented endpoint as well as a screen.
Permission per report
A packer can be given labels and no numbers at all.
Eleven reports about what you shipped
These are built entirely from data that already lives in your own instance: the orders your shops sent you, the labels you bought, and what the carriers charged for them. Nothing here needs a marketplace analytics permission.
| Report | The question it answers | Built from |
|---|---|---|
| Orders due today | What has to leave the building before the day ends, including anything with a promised ship-by date. | Your orders |
| Shipments by status | What is bought, in transit, delivered, stuck or returned right now, with each status clickable through to the parcels behind it. | Your shipments and carrier scans |
| Tracking sent to shops | Which orders have had their tracking number pushed back to the marketplace, and which have not yet. | Your shipments and channel confirmations |
| Sales & revenue | Order count, revenue and average order value over any range, with the shape of it over time. | Your orders |
| This year vs last year | The same window a year apart, so seasonal work is compared with seasonal work rather than with last month. | Your orders |
| Carriers & shipping cost | Postage spend, label count, the average cost of a label, and how the spend splits between carriers and services. | Your labels and carrier charges |
| Fulfillment speed | How long orders actually take from arriving to going out, and where that number is drifting. | Your orders and shipments |
| Products & SKUs | What moved, in units and in revenue, at the SKU level rather than the order level. | Your order line items |
| Where orders ship | The geographic spread of your parcels, which is what tells you whether a zone-based service is worth it. | Your shipping addresses |
| Sales channels | Which shop is actually carrying the business, side by side over the same range. | Your orders |
| USPS adjustments | Every re-weigh and reclassification the carrier billed after the fact, so a quiet leak shows up as a number. | Your carrier adjustments |
Four reports about what sells
These are the ones that need a marketplace's own figures. A sale is visible from an order, but a view is not — only the marketplace knows how many people looked at a listing and walked away. That single number is the difference between "this product does not sell" and "nobody is finding it", and it is why these reports exist.
| Report | The question it answers | Built from |
|---|---|---|
| Best sellers | What actually earns its place, by units or by revenue, per marketplace and over any range. | Your own listing sales figures |
| What isn't selling | Listings carrying no sales over the window, so dead stock is a list rather than a hunch. | Your own listing sales figures |
| Views but no sales | Listings people find and then leave. High views with no orders is a price, photo or description problem, not a demand problem. | Your own listing views and sales |
| Trends & price bands | How sales move over time, which price bands convert, and which categories carry the shop. | Your own listing views, sales and prices |
Per marketplace, or all of them together
Every Listing Manager report takes a marketplace filter. Look at one shop on its own when you are working on it, or put them side by side when you are deciding where a product belongs. The same date range applies across all of them, so the comparison is honest.
What Arub reads, and what it is for
Reporting is the only reason Arub asks for analytics access at all. This is the full accounting of what is read from each marketplace, which report it feeds, and who ever sees it.
| Source | What Arub reads | What it powers | Who can see it |
|---|---|---|---|
| Etsy | Per-listing views and favorites, and the shop's own transactions, for shops the seller has connected. | Best sellers, what isn't selling, views but no sales, trends and price bands | Only users of that seller's instance |
| Amazon | Per-listing sales and traffic figures for the seller's own catalog, plus their own orders. | The same four reports, plus the Shipping Hub order reports | Only users of that seller's instance |
| eBay | Per-listing traffic and sales for the seller's own listings. | The same four reports | Only users of that seller's instance |
| Walmart | Orders and fulfillment only. No per-listing analytics is read today. | Shipping Hub reports | Only users of that seller's instance |
| Shopify | Orders and fulfillment only. No per-listing analytics is read today. | Shipping Hub reports | Only users of that seller's instance |
| Carriers | The seller's own labels, costs, scans and post-purchase adjustments. | Carrier and shipping cost, fulfillment speed, shipments by status, USPS adjustments | Only users of that seller's instance |
Read on a schedule, stored by day
Analytics figures are collected on a regular background job and stored as daily totals per listing, which is the grain every report reads. Arub does not re-request a marketplace's history it already holds, and it backs off rather than hammering an endpoint when a marketplace rate-limits it.
Kept in the seller's own instance
Each customer's data lives in its own database rather than a shared table with a customer column. A report can only read the instance it is running in, so one seller's figures are not reachable from another seller's account by design rather than by filter.
Shown back, and nothing else
Marketplace analytics data is used for one purpose: rendering these reports to the seller whose shop it came from. It is displayed, charted, filtered by date and exported at that seller's request. That is the whole list.
What Arub never does with marketplace analytics data
It is never pooled or aggregated across sellers. There is no benchmarking product, no market-trends dataset, no "sellers like you" comparison built out of it. It is never sold, licensed, shared with advertisers or given to another customer in any form, aggregated or otherwise. It is not used to train models. It is not used to compete with the seller it belongs to, and Arub does not use it to make sourcing, pricing or purchasing decisions of its own.
Retention and removal
Daily analytics totals are kept for as long as the account needs them to report on, and go when the account does. Disconnect a shop and its figures stop being collected; ask for them to be removed and they are removed, along with the listings they belonged to. Buyer personal information is not part of analytics data at all — these reports count views, units and money, not people.
Access inside the seller's own team
Reports are permissioned one key per report, not as a single "reports" switch. A packing station can be given labels and no financial screens; a bookkeeper can be given revenue and nothing that spends money. The reports a user cannot open do not appear in their navigation, so nothing is protected by simply being hard to find.
The full detail lives in the Privacy Policy, the Amazon Data Handling Policy and the security summary. If a marketplace review team needs something here in a different form, ask and we will produce it.
Every report is also an endpoint
Anything on a report screen can be read by your own systems over the REST API, at the same date range and with the same permission rules. Pull revenue into a spreadsheet each Monday, push fulfillment speed into a dashboard you already have, or hand an AI assistant the MCP server and ask it in words.
- Same permissions as a person. A key that cannot open a report in the app cannot read it over the API.
- Export from the screen too. Any report downloads as a file without touching the API at all.
- Your data leaves when you do. If you close the account, the reports come with you as files.
# the same numbers the screen shows curl -H "Authorization: Bearer $ARUB_KEY" \ "https://ship.arub.com/v1/reports/sales?from=2026-01-01&to=2026-03-31"
See your own numbers.
Connect a shop and the reports fill themselves in. Free plan, no expiry, no card.