Features
Action Centre
The dashboard needs-attention card ranks your catalogue by what a fault is actually costing you, and catches the failures Amazon never reports.
Action Centre
The Needs attention card on your dashboard answers one question: of everything in my catalogue, what should I fix first this morning.
This feature is in early access. If you do not see it on your dashboard yet, contact support to have it enabled.
Ranked by cost, not by noise
Most tools rank by severity, which answers "how broken is this". That is not the question a seller with a hundred flagged products is asking. They are asking what this is costing them, and a suppressed live listing is losing every sale while a draft with five faults is losing nothing.
So Action Centre ranks by commercial exposure first and severity second:
| Rank | Badge | What it means |
|---|---|---|
| 1 | Not selling | Listed on Amazon and suppressed. Buyers cannot reach it, so it is losing every sale until it is fixed |
| 2 | Live | Live on Amazon, so anything wrong with it is costing sales today |
| 3 | Not on Amazon | An active product with no ASIN. Fixing it prepares a listing rather than recovering sales |
| 4 | Draft | A draft or archived product. Nothing is lost while this waits |
Live rows carry no badge on purpose. It is the normal case, and a badge on every row tells you nothing.
Drafts are hidden by default for the same reason: letting them in is what buries the listings that are actually losing money. There is an "Include drafts" toggle when you do want them.
Within a tier, worse severity comes first, and where severity ties, the product with more problems comes first. Child variations are excluded so one parent with ten children cannot fill the card with ten near-identical rows. The sweep covers up to 500 products at a time, scoped to your active brand.
Channel badges
Each row shows where the product lives, Amazon or Shopify, worked out from its ASIN and how it was imported. A product that is only in Rufusly gets no channel badge.
The silent failures it catches
Some of these produce an Amazon error. Most do not, which is the point: without a check like this there is no way to learn why a listing quietly underperforms.
Search terms over the byte limit. Backend search terms have a 250 byte limit. Go one byte over and none of them index at all, and Amazon reports nothing. This is treated as critical because it is invisible and total.
Placeholder text in your copy. Words like nan, null, undefined and a stray none leak out of broken source data and into live listings, where they read as an error to customers. Rufusly only flags them where a value belongs, such as "Size: none", so ordinary English like "contains none of the top 14 allergens" is not flagged.
Amazon's own sample row. Amazon's flat file templates ship with an example product on them. Import the template without deleting it and that example becomes a real product in your catalogue, skewing every count you look at.
Price wording in your content. Prices, "no extra cost", "value for money", "cheaper than" and price-match claims inside bullets or descriptions. They go stale, and comparison claims are a content policy risk.
FBA and fulfilment values that are not quite right. Fulfilment channel, condition, country of origin and unit spellings are checked against Amazon's accepted values in the flat file tools, where a wrong value blocks the whole row. See Flat File Tools for that side.
Alongside those, the card raises the ordinary faults: suppressed listings, no image, a title over 75 characters or missing, fewer than three bullets, no description, no backend search terms, and content Rufusly has not read from Amazon in 90 days.
One thing it will not do
If Rufusly has never fetched a listing from Amazon, the card says "Content not synced" once, rather than reporting no title, no bullets, no description and no search terms as if your listing were empty. That distinction matters: the absence of our copy is not the absence of yours. Run a Sync and the row resolves itself.
Every chip is a link
Each issue on a row links straight into the product editor with the offending field focused and a one-line note about why you were sent there. Search terms over the byte limit takes you to the search terms box, title too long to the title, no image to the Images tab.
Continue where you left off
Underneath Needs attention sits a companion card listing the products and A+ designs you touched most recently, so coming back to a half-finished job is one click rather than a search.
Where the same issues appear
Action Centre, the Amazon Listings table and the product editor's health panel all read from one shared list of issues, so the same product shows the same problems in the same words wherever you look at it. The dashboard shows the worst few, the table draws chips, the editor counts them per tab.
Frequently asked questions
What is the Rufusly Action Centre?
Action Centre is the Needs attention card on the Rufusly dashboard. It sweeps your catalogue and lists the products that need fixing, ranked by what the fault is costing you commercially rather than by severity alone.
How does Rufusly decide which product to fix first?
Commercial exposure first, severity second. Suppressed listings that buyers cannot reach come first, then live listings with faults, then active products not yet on Amazon, and drafts last and hidden by default because a draft is not losing sales.
What listing problems does Amazon not tell you about?
Backend search terms over the 250 byte limit stop indexing entirely with no Amazon error, placeholder text like nan or undefined leaks into live copy, Amazon own template sample row gets imported as a real product, and price wording in bullets goes stale. Rufusly checks all of these.
Why does a product show Content not synced instead of listing its problems?
Because Rufusly has never fetched that listing from Amazon, so it has nothing to check. Rather than reporting your listing as empty, it says so once and points you at Sync. Running a Sync resolves the row.
Does Action Centre cost credits to run?
No. The catalogue sweep is a set of deterministic checks against data Rufusly already holds, with no AI call, so it costs nothing. Credits are only spent when you ask the AI to rewrite something.
Why are drafts hidden from the Rufusly dashboard by default?
A draft is not selling anything, so a fault on one costs nothing, and including drafts buries the live listings that are actually losing money. There is an Include drafts toggle on the card when you do want to see them.