The catalogue, undifferentiated
128 SKUs and one number for all of them. Advertising looks affordable, because at this grain it always does.
- Net revenue
- ₹1.72 Cr
- Ad spend
- ₹13.90 L
Define a group once — as a rule over title, SKU, price, listing age or last-30-day performance, or as a plain list of SKUs you upload or paste. Sellerbud keeps rule membership current in the background and rebuilds the numbers behind every tag on each data refresh. From then on the tag is a row in Performance: Sales, Proceeds and Advertisement side by side, with return rate and TACOS on the entity, and a drill-in for its ASINs, months, periods and states.
Illustration with sample data
Custom tags
The launch batch, the vendor, the clearance pile, the SKUs whose returns you keep meaning to look at — those groups are real, they just live in your head and a spreadsheet. Give one a name inside Sellerbud and it becomes a row with a P&L, a filter every performance view already takes, and a page of its own.
01 / 05Tags a rule keeps true
Illustration with sample data
A rule tag is a saved condition Sellerbud keeps true for you. Match on title, SKU, price, listing age, or on last-30-day performance such as return rate, ACOS and gross profit. Conditions stack with AND, and a SKU joins the tag when every one of them holds.
Some groups have no rule: they are the twelve things you shipped in March. Drop a CSV or paste the SKUs. Every row is checked against this marketplace’s catalogue before anything is written, and only the SKUs that resolve are committed.
Rule or list, both land as the same object with the same row, so a hand-curated clearance pile and an automatic returns watchlist sit side by side and are read the same way. Edit a rule and it re-applies in the background.
Pick a period and read your own taxonomy as the entity column, sorted by any of the seven metrics.
Press to tryRank the tags by .
Traffic is absent at this grain, because Amazon reports sessions per ASIN.
Open a tag and it behaves like any other grain: the ASINs inside it, its month-over-month trend, a per-period view and a state-level view. A group you invented last week has the same depth of history as a category.
Worked example
One cohort, one closed period, and the same catalogue read three ways. Illustrative figures — the arithmetic is the product’s, the numbers are an example.
128 SKUs and one number for all of them. Advertising looks affordable, because at this grain it always does.
Two clicks: tag the batch once, then read it on the Performance tab like any other entity. Same period, same metrics, a tenth of the catalogue.
The other 114 SKUs, on the same two lines. This is the comparison the tag exists to make — and it is the same two numbers, minus the cohort.
The batch is 15.9% of net revenue and 27.1% of the ad spend, and its gross margin runs ▼ 4.6 pp against the rest of the catalogue. Nothing about that is visible on a store-wide dashboard, and nothing about it needed an export — it needed the catalogue split the way you already think about it.
FAQ
Nothing in the tag routes caps the count: the list endpoint returns every tag in one response and the table pages it twenty at a time on your side. What is constrained is the name — one to sixty-four characters, no commas, no leading or trailing space, and unique within the marketplace, so a duplicate is rejected rather than silently merged. A manual tag needs at least one SKU that resolves against your catalogue before it can be created; a rule tag can legitimately match nothing, and will show a count of zero until it does.
Yes, and that is the normal case — a SKU can be in the launch batch, the vendor group and the premium tier at once. The honest consequence is that tag rollups OVERLAP: a SKU contributes its full metrics to every tag it carries, so tag totals do not sum to your marketplace total and were never meant to. Read a tag against the rest of the catalogue, as the worked example above does, rather than adding tags together.
No. A predicate is a flat AND — the root operator is fixed and sub-groups are rejected by the validator, which is why the builder says “All rules must match.” rather than offering a connector you cannot save. Text matching is substring only: contains and does not contain, no regex, no starts-with, no exact match. Where you would reach for OR, make a second tag; both will sit in the same list and both will have their own row.
Wherever the performance surfaces let you choose a grain. A tag is a row in the breakdown table with Sales, Proceeds and Advertisement, and it opens into its own page with the ASINs inside it, its month trend, a per-period view and a state-level view. What tags do NOT do is leave Sellerbud: no SP-API call, no listing attribute, nothing written back to Amazon. They are a lens on your own data, not a label on your catalogue.
Membership and analytics move on different clocks, deliberately. Saving a rule enqueues a background apply — the row shows “Applying…”, the list polls until it clears, and editing is locked for those few seconds so two writes cannot race; a stalled job unlocks itself rather than holding the tag forever. Membership on your SKUs therefore changes almost immediately. The per-tag rollups behind the trend, period and state views are rebuilt by the data refresh, so a tag you change today reads its full history from the next refresh onward. Rule conditions that reference performance read your most recent Last 30 Days period, and only that one.
Tags belong to one marketplace and live only on the seller surface; there is no cross-marketplace tag, and Sellerbud staff reach the surface only through audited impersonation. Browsing is open — any connected marketplace can see its tag list, each tag’s SKUs and the one rule every marketplace is seeded with. Tag analytics, and creating, editing, renaming, deleting or uploading a list, come with the Analytics subscription. None of it is credit-metered: no tag route touches a credit ledger.
Analytics · Related tools
Ask every eligible delivered order for a review through Amazon’s own Request a Review, automatically, every night.
See which products actually save money in an Amazon warehouse, region by region, priced on real Amazon-India rate cards.
Every listing sorted by what it needs next: restock, losing money, not advertised, weak listing or ready for FBA — with the screen that fixes it one click away.
Export from the view you are on, check every column and a sample table in the full page, then take it as CSV or XLSX.
One page for your Amazon store: last month’s P&L, 30-day sales, ad efficiency, and your Amazon account health.
See every month side by side: 24 metrics across sales, advertising and traffic, plus a projection of where the month in progress will land.
Connect your first marketplace in about two minutes, pick the plan that fits your store — and move up when the numbers earn it.