How to Import Reviews to Shopify Without Breaking the Rules

Search for how to import reviews to Shopify and you will find a dozen tutorials that all answer the same question: which button do I click. Almost none of them answer the question sitting underneath it, which is whether you are allowed to import the reviews you are about to import.

That gap matters, because the three things people mean by "importing reviews" carry wildly different risk. Moving your own reviews from one app to another is routine housekeeping. Pulling a supplier's AliExpress reviews onto products you resell is a judgment call with real downside. Buying reviews or generating them is a federal violation carrying civil penalties of up to 53,088 dollars each.

The apps will not sort this out for you. A one-click importer looks identical whether it is pulling your own customers' words out of Loox or strangers' words off a marketplace listing. The button is the same. The exposure is not.

This post ranks the three scenarios by risk, gives you the CSV walkthrough for the safe one, and explains honestly what the other two cost you. If you are switching review apps this week, the second section is your checklist. If you are hovering over a one-click AliExpress import, read the third section before you press it.

The three import scenarios, ranked by risk

Almost every question about how to import reviews to Shopify is really one of these three, and they are not close to equivalent.

The rule doing most of the work here is the FTC's Rule on the Use of Consumer Reviews and Testimonials, 16 CFR Part 465, which took effect on October 21, 2024. It bans six categories of conduct: fake or false reviews including AI-generated ones and reviews from people with no actual experience, buying reviews conditioned on sentiment, undisclosed insider reviews, company-controlled review sites posing as independent, review suppression, and fake indicators of social media influence.

Scenario 1: Moving your own reviews between apps or stores

This is the common case and it is completely fine. Your customers wrote those reviews about your products. Changing which software displays them changes nothing about their truth. Nobody at the FTC cares which vendor renders your star widget.

What goes wrong here is never legal. It is operational, and it is usually one of three things.

Export before you uninstall anything

Reviews do not live in Shopify. They live in the review app's database, which is why Shopify's own documentation states that reviews collected through a partner app must be managed in that app, and that you need to transfer everything before uninstalling the current one.

Uninstall first and the reviews are gone. Not hidden, not recoverable from a Shopify backup. Gone. Every review app has a CSV export somewhere in its admin, usually under Reviews or Settings. Pull it, open the file, confirm the row count matches what your dashboard says, and only then touch the uninstall button.

Give yourself a week of overlap with both apps installed. One extra month of an app you are leaving is cheaper than losing three years of social proof.

The CSV cleanup step everyone skips

The column that breaks migrations is the product identifier. Apps variously key reviews to a product handle, a SKU, or a Shopify product ID, and those do not survive a move between stores or a re-platform. When Judge.me documents migrating reviews between two Shopify stores, it walks users through manual product mapping by reference column precisely because the identifiers will not match automatically.

Two more details that catch people out. First, verification toggles change your data. Judge.me's Loox migration guide notes that enabling verification on import pulls reviewer names from matching Shopify customer records instead of from the CSV, so any customer record missing a first or last name renders on your storefront as a generic "Customer." Fill in those names first or import without the toggle.

Second, media is fragile. Photos travel as URLs and generally survive. Videos usually do not import and have to be re-uploaded review by review afterward. Budget an hour if photo and video reviews are a meaningful part of your product pages.

A workable pre-import checklist: confirm every row has a product identifier that exists in the destination store, standardize the date format, check ratings are integers in the expected range, and spot-check ten rows by hand before uploading.

Import, verify, and check what survived

After the upload, read the import log rather than trusting the success message. Most apps report failed rows with a reason, and failed rows are fixable if you catch them while you still have the source app installed.

Then check verification status, because it is not cosmetic. Judge.me's Yotpo migration documentation explains that reviews verified through metaobjects appear in the Product Ratings feed used for Google Shopping, while unverified imports do not. A migration that technically succeeded but stripped verification from 800 reviews has quietly cost you your star ratings in shopping results.

Finally, reinstall your widgets. Star badges, review widgets, and the all-reviews page are app-specific theme blocks and need placing again after the switch. Then run one product URL through Google's Rich Results Test to confirm the new app is emitting review structured data.

The same export-and-remap mechanic is what makes it possible to preserve reviews when you retire a SKU, which is worth reading about separately if you sunset products regularly: migrating reviews when you discontinue a product. And if you are still choosing a destination app, comparing Judge.me and Stamped covers the tradeoffs at this store size.

Scenario 2: Can you import AliExpress reviews?

This is the question that actually drives the search volume, and the honest answer is more complicated than either side of the argument admits. It is not clearly illegal. It is also not clean, and it costs you more than the review count is worth.

What the law actually says

When the FTC finalized Part 465, it dropped the review hijacking provision it had proposed, which would have prohibited taking reviews for one product and re-displaying them for a substantially different product. As Crowell & Moring's analysis records, the Commission said it could not resolve commenters' concerns about defining "substantially different product" on that rulemaking record, and left the door open to revisiting it later.

So no line in the rule names AliExpress imports. That is the strongest thing anyone can say in their favor, and people say it constantly.

Here is the other half. Section 465.2 still prohibits reviews that misrepresent, expressly or by implication, that the reviewer had experience with the product or business being reviewed. Nothing about that turns on where the file came from. If your widget labels those imports as customer reviews of your store, or shows them under a verified badge, or sits beside a headline about what your customers say, the misrepresentation is live regardless of what the dropped provision would have covered.

The FTC has also already litigated repurposed reviews without needing Part 465. In its first review hijacking case, the Commission ordered The Bountiful Company to pay 600,000 dollars in consumer redress for merging new supplements onto established Amazon listings so the new products appeared to carry ratings and badges they had not earned.

That is not a settled question you can rely on either way. It is an unsettled one, which is a different and worse thing to build a store on.

What it costs you even if nobody ever complains

Set the legal argument aside and the practical case falls apart on its own.

Start with verification. Judge.me's own AliExpress import documentation states plainly that reviews imported from AliExpress are not marked as verified, because AliExpress does not provide verification data meeting their standard. That is the vendor who built the importer telling you what the reviews are worth.

Unverified reviews are generally excluded from the product ratings feeds that put stars next to your listings in shopping results. So the imports inflate the number on your product page while contributing nothing to the place where reviews actually earn clicks.

Then there is what shoppers see. Imported marketplace reviews carry tells: reviewer names from markets you do not ship to, translated phrasing that reads slightly off, photos of a colorway you do not stock, and timestamps that predate your store's launch. A shopper who spots one stops trusting all of them, including the real ones you collect later.

And your support workflow breaks. You cannot meaningfully reply to a review from someone who is not your customer, cannot resolve their complaint, and cannot use their feedback to fix anything. Replying to reviews is one of the higher-leverage things a small store does, and imported reviews make the whole practice theater.

Studio Niza does not import supplier reviews for clients, and it is not a moral stance. Three hundred reviews that mean nothing convert worse than fifteen that do.

Scenario 3: The line you never cross

Buying reviews, paying for a particular sentiment, or generating reviews with AI is not a gray area, a risk tradeoff, or an aggressive growth tactic. It is a rule violation with a number attached.

Part 465 covers it from several directions at once. Section 465.2 prohibits fake or false reviews, explicitly including AI-generated ones and reviews from people who never used the product. Section 465.4 prohibits compensation or incentives conditioned on the review expressing a particular sentiment, whether that condition is stated outright or merely implied, and a reviewer disclosing that they were paid does not cure it. Section 465.5 covers insider reviews from officers, employees, agents, or their immediate relatives without clear disclosure of the connection.

The penalty is where it gets real for a small store. The FTC's January 2025 inflation adjustment raised the maximum civil penalty for the relevant FTC Act provisions from 51,744 to 53,088 dollars per violation, and that figure remains in force for 2026. One outreach campaign that produces fifty conditioned reviews is not one violation. It is potentially fifty.

For a first-year Shopify store the practical translation is short. Asking your sister to leave a review without disclosing that she is your sister is covered. Offering a discount code specifically for five-star reviews is covered. Having a language model write twenty product reviews and uploading them by CSV is covered, and it is the version most likely to happen by accident because it feels like copywriting rather than fabrication.

Two things that are fine, for contrast: asking every customer for a review, and offering the same small incentive to everyone who reviews regardless of what they say. The distinction is sentiment, not money. Asking your own customers for reviews without breaking the FTC rules walks through the compliant version of that request in detail.

If the reviews you are worried about are ones a competitor left on your store rather than ones you are tempted to add, that is a removal problem instead: how to remove a fake review the right way.

If importing was your fix for zero reviews, fix that instead

Most people who search for how to import reviews to Shopify are not doing app migration. They are staring at empty product pages and looking for a shortcut past the cold start. That is a real problem and importing is a bad answer to it.

The unglamorous version works better than it sounds. Set the automated request to fire a set number of days after delivery rather than after payment, so the customer has actually used the thing. Ask for a photo in the same email, since photo reviews carry disproportionate weight on a thin product page. Then personally email your first twenty customers, because a founder's note outperforms a template while your order volume still makes that possible.

Judge.me's free tier handles all of this and remains the default recommendation for Shopify stores under 200,000 dollars a year in revenue. You do not need to pay for review software at this stage, and anyone telling you otherwise is selling something.

Fifteen real reviews on a product page outperform three hundred imported ones, because the real ones are specific, answer objections a shopper actually has, and hold up when someone reads three of them closely. Getting reviews for a brand-new store with zero sales covers the pre-first-order version of this problem.

One honest note on expectations. Nobody can promise you a number of reviews per month, because volume depends on your order count, product quality, and customer willingness, none of which a service provider controls. What can be guaranteed is that the request goes out every time, on schedule, in compliant form.

Wrapping up

Three things to carry out of this.

Moving your own reviews is safe and mostly a data problem. Export before you uninstall, map product identifiers deliberately, watch verification status, and read the import log instead of the success banner. Do that and a migration costs an afternoon and nothing else.

Importing supplier or AliExpress reviews sits in unsettled territory. The final rule dropped the provision that would have addressed it directly, but the misrepresentation sections did not go anywhere, and the reviews you gain are unverified, ineligible where stars matter most, and visibly foreign to your storefront. The upside is a bigger number. The downside is that the number stops meaning anything, including for the real reviews beside it.

Buying or generating reviews is simply off the table at up to 53,088 dollars per violation, with each review potentially counting separately.

None of this makes the cold start less frustrating. If you have twelve products and four reviews, the honest path is slower than the one-click path and still the one worth taking. The store that spends six months collecting real reviews ends up with an asset. The store that imports three hundred ends up with a decoration.

Or email contact@studioniza.com if you have a specific question about your store. I read every one.

---