Connect a review app or import reviews from CSV
Commander reads your product reviews and analyzes them. Connect your review app, or import a CSV file if your app has no connector. All review sources sit under Settings > Integrations, in the Reviews category. Reviews you bring in feed the Sentiment tab under Insights > CX and the JTBD Insights tab under Insights > Products.
Problem and intended user
The ecommerce manager (the person who runs the store) wants to see what customers say about each product. Until reviews reach Commander, the review views have nothing to show.
Current workflow
Without Commander, a merchant reads reviews in each review app's own dashboard. To compare them, the merchant exports a file from each app and sorts it in a spreadsheet.
Prerequisites
- Integration: Install the review app on your store.
- Credentials: The app's API credentials, from its admin.
- File: For a CSV import, a file with review text, a rating and a review date in each row.
How Commander works
Commander copies your reviews from the app, or from your file, into its own store. Fixed rules check the credentials, match the columns and skip invalid rows. AI then reads each review for sentiment and themes. Saving a connection starts a first sync at once, in the background. After that, Commander syncs each connected review app once a day. The review views show the reviews when the first sync or import finishes.
Settings > Store Status lists one row for each connected review app. The row name is the name of the app, followed by "reviews sync". Its cadence is Daily. A CSV import shows as "CSV Import reviews" with the cadence Manual import. See Store Status.
Connect a review app
The steps are the same for every app:
- Go to Settings > Integrations.
- Click the Reviews category, then click your app's card.
- Click the Open ... link next to a field name. It opens the app's key page in a new tab.
- Copy each credential into the matching field.
- Click Save Connection. The button reads Validating… while Commander checks the credentials.
On success, Commander shows "Credentials saved. Syncing reviews in the background…" and closes the dialog.
| App | Fields | Link in the dialog |
|---|---|---|
| Judge.me | API Token | Open Judge.me → Settings → Integrations |
| Growave | API Key, API Secret | Open Growave → Settings → API |
| Loox | Public Store ID, API Secret Key | Open Loox → Settings → API Keys |
| Okendo | Okendo User ID, API Key (32 characters) | Open in Okendo → Settings → Integrations |
| Yotpo | Account ID, App Key, Secret Key | Open Yotpo Dashboard → General Settings |
| Reviews.io | Store Key, API Key | Open Reviews.io Dashboard → Settings → Integrations |
| Sitevibes | Enterprise API Token, and two optional fields | None |
For Judge.me, Commander finds your shop from your Shopify install, so you enter only the token. For Sitevibes, enter only the Enterprise API Token to bring in reviews. Leave App ID (loyalty webhooks only) and Loyalty Webhook Secret (optional) empty.
Re-analyze your reviews
The Review Management section of each app dialog has a Re-analyze button. It runs the AI analysis again on reviews Commander already holds. The result line says how many reviews are queued. The button stays off until reviews exist. After you import, the CSV Import dialog shows the same control under Imported reviews.
When some reviews failed analysis, the button gains a menu:
- Re-analyze all resets the analysis on every review of that app and runs it again. Figures that depend on the analysis can be incomplete until it finishes.
- Re-analyze failed (N) retries only the reviews that failed. It keeps the rest.
Re-analysis uses the month's feedback analysis allowance of your plan. When the allowance covers only part of the reviews, Commander re-analyses the newest ones first. The other reviews keep their current analysis until next month's allowance, so the result line can count fewer reviews than you hold. When nothing is left this month, Commander does not start the re-analysis and opens the Plan limit reached dialog. See When a plan limit stops an action.
The same allowance covers the analysis of new reviews after a sync. When it is used up, new reviews still sync and count, but their analysis waits for next month or for a bigger plan.
Import reviews from a CSV file
Use CSV Import for an app with no connector, or for a spreadsheet.
- Click the CSV Import card.
- Click Download template to get a file with the right column headings. This step is optional.
- Click Choose CSV file. The file can be up to 10 MB. Split a larger file and import each part.
- Check the mapping. Commander matches the columns it recognises. If it knows your app's export, it says "We recognised a Judge.me export", for example. Otherwise it says Map your columns, or All required columns matched when every required column is found. Use each list to pick the column in your file for each Commander field.
- Click Import reviews. Click Back to change the file or the mapping.
Commander shows "N reviews queued for import. Sentiment analysis follows automatically." Click Done.
Exact output
App cards and the Review Management section
A card can show a Detected on store badge. It means Commander found that review app on your store and you have not connected it yet.
After a sync, reopen the card. The Review Management section shows N reviews synced and the date of the last sync. The reviews feed the Sentiment tab, the review sync bar and the JTBD Insights tab, and the Reviews tile on a product's detail page. After Re-analyze, Commander shows "N reviews queued for re-analysis." After Re-analyze failed (N), it shows "N failed reviews queued for re-analysis."
The CSV Import card and mapping
The card shows NOT IMPORTED until you import, then IMPORTED with a review count and the date of the last import.
| Group | Field | Notes |
|---|---|---|
| Required | Review text | Rows without text are skipped. |
| Required | Rating (1–5) | A number from 1 to 5. |
| Required | Review date | An ISO date, such as 2026-09-29. Other formats skip the row. |
| Product (map any one) | Product SKU, Product name, Product ID | Links each review to a product. |
| Optional | Review title, Reviewer name, Review ID, Verified buyer, Status, Helpful votes, Unhelpful votes, Merchant reply, Photo / video URLs, Recommends product, Incentivized, Tags | Map Review ID so a re-upload updates rows and does not duplicate them. |
Commander counts each skipped row by reason: no review text, invalid rating, invalid date, missing ID, or already imported.
Reviewer name is the name the review shows, such as "Sarah Kim". Commander keeps only the first name and the initial of the last name ("Sarah K.") and never stores the full name. When the name has no first name, Commander keeps a title and an initial, such as "Mrs W.", or two initials, such as "J. S." from "J. Smith". A title with a family name only, such as "Mrs Smith", is not stored. A file without this column, or a row with an empty cell, keeps the name Commander already holds for that review.
Reviewer names on landing pages
A landing page can print a short attribution under a customer's words on a review card, for example "Sarah K. · Verified buyer". It reads the reviewer's first name and last initial that Commander stores for reviews it receives or refreshes, from your review app or from a CSV file. When the name has no first name, the card shows a title and an initial ("Mrs W.") or two initials ("J. S."). It never stores the full name or the email address. A name the reviewer chose to hide, such as "Anonymous", is not stored. A review that the app marks as verified shows Verified buyer, in the language of the page.
Reviews Commander already holds keep no name until the app sends them again, for example a new review or an edited one, or a CSV file you import again. Until then such a review shows Verified buyer when the app marks it verified, and no attribution otherwise. A page that Commander wrote earlier does not change until you generate it again. A remodel report has no Reviewer names section: under Check before you keep it lists the testimonials that mention a health condition or include contact details. Only the older report of a remodel kept some time ago can show Reviewer names, when its note asked for names; see Landing page editor. To get review cards that show a name, create the page again with the wizard. A published page shows a name that arrives later after you next publish changes to it. If you edit a page in Shopify and bring that edit into Commander, a review card that showed no attribution at that moment stays without one until you generate the page again.
If a reviewer asks you to remove a name, remove or hide it in your review app too: Commander stores the name the app sends, so a name removed only in Commander comes back when the app sends that review again. Then see Contact support.
What to do with it
| What you see | Decision or action | Owner |
|---|---|---|
| Detected on store on a card | Click the card and connect the app. | ecommerce manager |
| N reviews synced | Open Insights > CX and read what the reviews say. | ecommerce manager |
| Skipped rows, or the Unknown product warning | Fix the file, map a product column and Review ID, then import again. | ecommerce manager |
Expected value and measurement
A connected review source can help you read your reviews in one place, without exports.
To check an import, compare N reviews synced, or the IMPORTED count, with your review app's own dashboard. To check product links, look for the Unknown product warning in the import dialog.
Other changes, such as a new product, can run at the same time. Then you cannot isolate the effect of the new source.
Limitations and exceptions
- Commander connects to Judge.me, Growave, Loox, Okendo, Yotpo, Reviews.io and Sitevibes. For any other source, use CSV Import.
- Commander does not remove duplicates across sources.
- Commander does not copy reviewer names from Loox or Growave. Reviews from those apps show Verified buyer when the app marks them verified, and no name.
- AI reads each review. Its sentiment and themes can be wrong.
| What you see | What to do |
|---|---|
| The bar "Connect a review platform to measure sentiment" on Insights > CX, or the heading "Connect a platform to unlock this view" with the button Connect a review platform | Connect a review app or import a CSV file, as described above. |
| The Judge.me dialog shows an error and the link Install from the Shopify App Store | If the app is not installed, install it, then try again. If it is installed, check the token. |
| A warning in the Loox dialog that reviews you imported into Loox are counted twice. Loox can import reviews from other apps. It shows when another source already feeds Commander. | Choose one source for those reviews. This happens outside Commander. |
| "Re-analysis failed", or an error text | Try again. If it repeats, see Contact support. |
| Plan limit reached after Re-analyze | The month's analysis allowance is used up. Wait for next month, or move to a bigger plan with View plans. |
| "No reviews could be imported." with a list of reasons | Fix the listed problems in your file and import again. |
| A warning that reviews show under Unknown product | Map a product column. |
In Demo Mode, Choose CSV file is off. The dialog says "Uploads are turned off in Demo Mode." Re-analyze in the CSV Import dialog is off too.