Connected Amazon features

See the work.
Understand the next step.

Explore five connected Amazon seller tools: Refund Logic for reimbursement cases, Perfect Price for price tests, NevahOOS for inventory forecasting, Search Query Performance and the AI brand manager. Follow the evidence, investigate a finding and choose your next step.

Brands: $297/month. Book a demo for your recommended setup.

01 / Refund Logic

From a report line to a resolved case.

See what needs your action, review a prepared message and keep every case moving. Payment matching closes the loop.

US Seller Central · FBAExplore Refund Logic
Coverage and boundaries

Positive report lines become cases; this is not a warehouse or shipment audit. You file in Seller Central and record Amazon’s replies. Payment detection needs the exact case ID. Managed filing is a separate service.

RRefund LogicIllustrative workflow
01Amazon reimbursement report
02Case board + prepared message
03You file and record replies
Ready to file
Filed
Follow-up needed
RETURN · $48You · Follow up14 days without a recorded reply
Approved
Resolved
LOST · Sample case$126.00SKU TRAIL-01Payment matchedSUCCESS

Five case stages · Scroll the board to explore

Case record · illustrative

Potential value: $126 · Actual recovered: $126

Recorded case ID: EXAMPLE-1042 · Matched on Amazon’s reimbursement report.

01 / Report → board

A positive reimbursement-report line becomes a Ready to file case. Amazon decides eligibility and the amount.

02 / Review the message

Open the case and review its prepared message. Copying it does not file anything.

03 / You file + record

Submit in Seller Central, then record the Amazon case ID. Record replies yourself; 14 days without a recorded reply triggers a follow-up.

04 / Payment matched

When Amazon posts a payment matching the recorded case ID, the case closes as won. The time between these steps varies.

Time compressed · Sample data
  1. A positive reimbursement-report line becomes a Ready to file case. Amazon decides eligibility and the amount.

  2. Open the case and review its prepared message. Copying it does not file anything.

  3. Submit in Seller Central, then record the Amazon case ID. Record replies yourself; 14 days without a recorded reply triggers a follow-up.

  4. When Amazon posts a payment matching the recorded case ID, the case closes as won. The time between these steps varies.

Illustrative interface and prewritten example. No live connection or account action.

02 / Perfect Price

A careful price test. With the evidence.

Review a small, rule-based test and the figures behind it. Decide whether to make the change, then ask AI to compare the results.

US marketplaceExplore Perfect Price
Coverage and boundaries

Test steps never exceed 5%. Recommendations are rules, not demand predictions. Promotions, coupons, ad changes and competitor prices are caveats. Before/after comparisons use Ask AI; a built-in price-change timeline is not available.

RPerfect PriceIllustrative workflow
0190-day sales, conversion + FBA stock
02Observed → interpretation → test
03You change the price
Current price$24.80
→
Suggested test$25.10
L30 units300
ConversionNot falling
EvidenceHigh
Ask AI · illustrative comparison

“Compare conversion and revenue per day for the 7-day test against the previous 14 days. Show the covered dates and any missing traffic data.”

01 / Review evidence

Read the sales, conversion and stock evidence, including the dates covered by the traffic report.

02 / Consider the test

The illustrative $24.80 → $25.10 test is a 1.2% increase. Review the reasoning and caveats.

03 / You change the price

If you agree, copy the test price and change it yourself in Seller Central. Copying changes nothing on Amazon.

04 / Compare with Ask AI

After a 7-day test, ask AI to compare conversion and revenue per day against the previous 14 days. This sample conversation is not a built-in tracking report.

Time compressed · Sample data
  1. Read the sales, conversion and stock evidence, including the dates covered by the traffic report.

  2. The illustrative $24.80 → $25.10 test is a 1.2% increase. Review the reasoning and caveats.

  3. If you agree, copy the test price and change it yourself in Seller Central. Copying changes nothing on Amazon.

  4. After a 7-day test, ask AI to compare conversion and revenue per day against the previous 14 days. This sample conversation is not a built-in tracking report.

Illustrative interface and prewritten example. No live connection or account action.

03 / NevahOOS

See the gap before placing the order.

Follow a SKU’s stock outlook, check your lead time and inbound dates, then review the send-in quantity.

US Seller Central · FBAExplore NevahOOS
Coverage and boundaries

This example uses recent average sales with no seasonality. Seasonal forecasts are used only after validation. Context notes do not change the math. NevahOOS never places orders or creates shipments.

RNevahOOSIllustrative workflow
01Sales + FBA stock + dated inbound
02Forecast + your SKU assumptions
03You place orders and shipments
Cover18 days
Custom lead time30 days
Potential gap12 days
12-day gapTodayDay 18Day 30Day 54
━ No change┄ Recommended order▧ Out of stock
Suggested send-in · modeled720 units

30-day lead time + 60-day target cover · No earlier inbound

01 / Read stock cover

180 sellable units at a modeled 10 units/day gives 18 days of cover.

02 / Check lead time

A custom 30-day lead time leaves a potential 12-day stock gap if there is no earlier inbound arrival.

03 / Review the forecast

Check the solid baseline, dashed recommended-order projection and red stockout band. Review lead time, target cover and dated inbound in the SKU panel.

04 / Plan the send-in

With 30 days lead time, 60 target days of cover and no inbound, the modeled quantity is (30 + 60) × 10 − 180 = 720 units. Your team makes the order decision.

Time compressed · Sample data
  1. 180 sellable units at a modeled 10 units/day gives 18 days of cover.

  2. A custom 30-day lead time leaves a potential 12-day stock gap if there is no earlier inbound arrival.

  3. Check the solid baseline, dashed recommended-order projection and red stockout band. Review lead time, target cover and dated inbound in the SKU panel.

  4. With 30 days lead time, 60 target days of cover and no inbound, the modeled quantity is (30 + 60) × 10 − 180 = 720 units. Your team makes the order decision.

Illustrative interface and prewritten example. No live connection or account action.

04 / SQPR

Find the search step worth investigating.

Compare your brand with the market, then open a flagged query and bring its context into Ask AI.

Selected ASINs · completed weekly reportsExplore SQPR
Coverage and boundaries

Reports cover completed past weeks and only ASINs selected for the report. A share drop prompts investigation; it does not prove a cause. No year-over-year comparison is available yet.

RSQPRIllustrative workflow
01Amazon Search Query Performance
02Brand / market funnel + keyword flags
03You review the listing or ads
Impressions8%Brand 8,000 / Market 100,000
Clicks6%Brand 600 / Market 10,000
Cart adds3%Brand 150 / Market 5,000
Purchases2%Brand 60 / Market 3,000
Conversion problem

insulated trail bottle
Purchase rate: your brand 10% · market 30%.

Illustrative completed week · Oct 5–11
01 / Read the funnel

Compare impressions, clicks, cart adds and purchases with market totals for the same completed week.

02 / Spot the share drop

In this example, brand share falls from 6% of clicks to 2% of purchases. Investigate what happens after the click.

03 / Open the query

“Insulated trail bottle” has a sample conversion problem label. Check the query’s weekly history and the market comparison.

04 / Ask AI with context

Continue from the flagged keyword. Review the listing, price and shopping experience before deciding to spend more on traffic.

Time compressed · Sample data
  1. Compare impressions, clicks, cart adds and purchases with market totals for the same completed week.

  2. In this example, brand share falls from 6% of clicks to 2% of purchases. Investigate what happens after the click.

  3. “Insulated trail bottle” has a sample conversion problem label. Check the query’s weekly history and the market comparison.

  4. Continue from the flagged keyword. Review the listing, price and shopping experience before deciding to spend more on traffic.

Illustrative interface and prewritten example. No live connection or account action.

05 / AI Brand Manager

The finding comes with you.

Bring a feature finding into a conversation. Saved goals and source dates help turn the evidence into a useful next check.

Read-only Seller Central + Advertising dataExplore AI Brand Manager
Coverage and boundaries

Amazon data usually runs 2–4 days behind. Answers stay in the app. Your team makes account changes; scheduled skills and custom requests are reviewed and configured by Rivet Rocket.

RAI Brand ManagerIllustrative workflow
01Connected Amazon data + finding
02Saved goals + Chat / Skills / Context
03Answer with sources and date range
From NevahOOSGoal: protect availabilityRead-only
“What should we check before running this price test?”
Illustrative AI answer

Confirm the inbound arrival first. Your 18 days of stock cover is shorter than the 30-day lead time. With no earlier replenishment, the modeled gap is 12 days.

The price suggestion does not predict demand or solve the stock gap. Use the confirmed shipment timing to decide when to test.

Example sources: stock snapshot Oct 9 · sales Oct 1–7 · saved SKU assumptions
“What changes if the shipment arrives sooner?”
01 / Bring the finding

Ask AI from the NevahOOS stock finding: 18 days cover against a 30-day lead time.

02 / Apply saved context

Example saved goal: protect availability. The goal shapes the answer; it does not alter the inventory forecast math.

03 / Read the answer

The example answer identifies the 12-day gap and asks you to verify inbound arrival. Important figures still need checking.

04 / Continue the review

Ask a follow-up or run a ready-made restock check. Skill results land in Chat and include sources and date ranges.

Time compressed · Sample data
  1. Ask AI from the NevahOOS stock finding: 18 days cover against a 30-day lead time.

  2. Example saved goal: protect availability. The goal shapes the answer; it does not alter the inventory forecast math.

  3. The example answer identifies the 12-day gap and asks you to verify inbound arrival. Important figures still need checking.

  4. Ask a follow-up or run a ready-made restock check. Skill results land in Chat and include sources and date ranges.

Illustrative interface and prewritten example. No live connection or account action.

Questions, answered

Before your demo.

The data, coverage and setup.

Are these live product demonstrations?

These are simplified, illustrative interfaces with sample figures and prewritten explanations. Book a demo to see the current account-connected product for your setup.

How fresh is the data?

Data refreshes daily at 9:00 am Pacific, but Amazon reports usually run 2–4 days behind. SQPR uses completed weekly reports. A daily refresh is not real-time Amazon data.

How are the features priced?

The Brands offer is $297/month. FBA Builders and Agencies have their own offers. Confirm account scope, usage and any separate managed filing on your demo.

Start with your work

Find your next
useful move.

Show us what you manage or want to build. We’ll walk through the features, confirm your setup and give you clear next steps.

Book a demo No account connection needed for the call.