.5f521cec.png "Trivas.ai")
Alerts that follow your rules, not ours.
Rules is where you decide what counts as serious. Each rule watches for one problem and sets how serious it is, who gets it and how fast it must be fixed. Before anything saves, Trivas shows what would open, close or change level on today's data, and every change is kept as a version you can restore.
Built for brands selling on Amazon through Vendor Central or Seller Central.
Fixed alert settings flood the queue or miss what matters to you.
Every brand defines serious differently. A product that is critical in Q4 is not critical in January, and a check that does not fit your catalog only creates noise.
One-size alerts
Generic thresholds treat a hero product and a slow seller the same, so the queue does not match your own idea of urgent.
Changes made blind
Tightening an alert without seeing its effect can flood the team with new issues overnight.
Issues without an owner
New problems land unassigned and wait for someone to triage them by hand.
Inside Rules
Rule cards for the checks, a four-step builder, building blocks for shared settings, and a preview before every save.
Each tab describes one screen, with its parts numbered.
Each card shows when the rule fires, what raises its severity and what happens next, in plain words.
Rule cards: one per check, in four groups
Each card shows when the rule fires, what raises its severity and what happens next, in plain words.
- 01
Four groups
Stock & availability, Content, Live listing and Data quality, each with a count.
- 02
Filters and search
Group pills, an On, Off or All switch and a Find a rule search.
- 03
On and off
A switch on every card. An off rule shows as Off: raises nothing.
- 04
Open count
An N open badge on each card, with a red dot if any of the open issues are High.
- 05
When, If, Then
When is the trigger, If lists what makes it more serious, such as Top product, Priority A or B, or Open 7+ days, and Then shows the severity and who it is assigned to.
- 06
Exceptions
A footer note when a priority tier has its own settings, with Edit or View.
What Rules does
16 checks you can tune
Stock, content, live listing and data quality checks, each with its own thresholds and an on and off switch.
Severity that escalates
Start at a level, then raise it for top products, priority tiers and issues that linger. Always High conditions override.
Impact preview
See what would open, close, go up a level or go down before you commit, on your latest checks.
Auto-assignment
Send new issues of a given rule to a named person so they arrive owned.
Fix-by days
Set the business days allowed for High, Medium and Low. They drive due dates and Overdue chips in My work.
Your own priorities
Use the priority from your SKU taxonomy, or set one here. Exceptions let a tier have its own thresholds.
Versions and restore
Every save, restore and reset is a numbered version with who, when and why, so any earlier setting can be brought back.
Your definition of Red
Choose which checks make a product Red, can't be bought, and where Amber begins.
Who uses it, and for what
Brand admin
Sets low cover to less than 14 days and raises it to High for Priority A products only, previews the result and saves with a note about the Q4 cover policy.
Operations lead
Turns off No description for a brand whose listings legitimately have none. Its open issues close on the next run.
Content manager
Receives every new Live title differs issue automatically because the rule assigns them to them.
Brand manager
Redefines a top product for stock rules by rank and weekly revenue and checks how many products qualify today before saving.
Brand admin
Sees a surge in High issues after a change, opens History and restores the earlier version.
What changes for your team
A queue that matches your business
Severity reflects revenue, priority and age, so what the queue calls serious is what you would call serious.
Safer changes
Preview before saving and a versioned history lower the risk of misconfiguring alerts.
Less manual triage
Auto-assignment and an automatic re-run after each save mean issues arrive owned and current.
What it needs, and what it doesn't do
What it needs
- An Amazon Vendor Central or Seller Central connection so the hourly checks have data to apply the rules to.
- The Commerce Dashboard enabled for your brand.
- Brand admin rights to save, restore, reset or move priorities. Other team members get a read-only view.
- A SKU taxonomy with a Priority column if you want priority tiers to drive severity.
What it doesn't do
- It doesn't change anything on Amazon. Rules set what Trivas flags, and the fixes are made in Vendor Central, Seller Central or your own systems.
- It isn't real time. Saved rules apply on a re-run straight after saving and then on the hourly checks.
- Rules for new issues apply from now on. Existing issues keep their owner.
Frequently asked questions
Set alerts the way your business works.
Book a short walkthrough and we will show Rules and the impact preview on your Amazon data.