Your own product groups, with a P&L attached.

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.

  • Rule conditions match on title, SKU, bullet points, any catalog attribute, price, listing age, or last-30-day net revenue, units, return rate, gross profit, ad spend, ACOS and TACOS.
  • Manual tags take a CSV or a pasted list, and every SKU is checked against your catalog — unknown ones are flagged before anything is saved.
  • Each tag gets its own performance row and detail page, with month-trend, per-period and per-state breakdowns rebuilt on every refresh.

Illustration with sample data

Custom tags

You already group your catalogue. Amazon doesn’t.

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

Kalpavriksha Home & Living8 tags · last 30 days
Rule tags
Launch batch · Marlist14 SKUs
Vendor · Nandi Metalworkslist11 SKUs
Clearance Q1list7 SKUs
High return riskrule14 SKUs
Premium tierrule59 SKUs
ACOS leakrule11 SKUs
High return risk: Net revenue ≥ 100000 AND Return rate ≥ 0.12

Illustration with sample data

  1. Rules that read your catalogue

    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.

  2. Or hand it a list

    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.

  3. The cohorts you actually run

    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.

  4. Every tag is a P&L row

    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.

  5. And a drill-in of its own

    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

The batch that was quietly eating the ad budget.

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.

Launch batch · Mar66f1c0a4e2b7d91a4c0b7316Manual tag · 14 SKUs · last applied 2 days ago · Last 30 Days vs prior
01

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
TACOS8.8%
02

The launch batch, as one row

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.

Net revenue
₹27.44 L
Ad spend
₹3.77 L
TACOS15.1%
03

Everything else

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.

Net revenue
₹1.45 Cr
Ad spend
₹10.13 L
TACOS7.6%

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

The questions a seller actually asks.

How many tags can I have, and how big can one get?

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.

Can one product carry more than one tag?

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.

Can a rule use OR, or nested conditions?

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.

Where do tags show up once I’ve made them?

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.

How quickly do the numbers behind a tag update?

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.

Who can see my tags, and what needs a subscription?

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.

Know your numbers. Grow your store.

Connect your first marketplace in about two minutes, pick the plan that fits your store — and move up when the numbers earn it.

We use cookies for analytics, to improve Sellerbud, and for marketing, to measure our ads and the links we send. If you say no, we keep only what this visit needs. Privacy policy