Amazon Review Analyzer

Problem Context

Amazon review stars, keywords, trends, and competitor gaps are often scattered across large text volumes and historical windows. Manual collection and interpretation can miss sample bias, and it is hard to separate direct data readings from strategic advice. Amazon Review Analyzer turns collection, analysis, and report archiving into an auditable CLI workflow.

How It Works

• Check account state first: run check in each session to confirm email verification, credits, and usable balance.
• Quote before paying: for VOC reports, run voc to get the total price; only after explicit user confirmation, append --confirm to collect, wait, analyze, and archive.
• Support common analysis paths: beyond voc, it supports collect, charts, deepdive, analyze, and competitor comparison across amz_us, amz_uk, amz_de, amz_jp, amz_ca, amz_fr, amz_es, and amz_it.
• Keep outputs traceable: results distinguish 📊 direct data readings, 🔍 data-based reasoning, and 💡 strategy suggestions, and should end with the command, ASIN, site, sample size, statistical window, reportId, creditsUsed, and reportUrl.

Boundaries And Cautions

• Small samples or limited collection windows make conclusions only operational reference points; validate with additional sources.
• After a paid command is interrupted, do not retry immediately; check whether a report was already generated to avoid duplicate charges.
• If the version is too old, credits are insufficient, rate limits apply, or email is unverified, stop paid operations or handle the account issue rather than fabricating data the API did not return.