Shopper Approved Integration: Reviews & Ratings In Your Product Pages
Keep Shopper Approved and put your reviews inside your product pages. Post-purchase review requests raised off the order events your store already fires, an hourly review sync, and reviews rendered on the server with Product structured data attached, so your customers and Google are reading the same page.
Contact Shopper Approved
Reach out to us for any inquiries or support, and
let’s connect!
-
Phone
888.497.3270 -
Website
www.shopperapproved.com
Get in touch with us
Reach out to us for any inquiries or support, and let’s connect!
Keep Shopper Approved. Put the reviews inside your product pages.
You already pay to collect the reviews. The usual way to show them is a script pasted into your template: the page loads, then the script runs, then the reviews appear, and whatever rating data comes with them appears at the same time. Web Shop Manager 6.0 does it the other way around. It pulls your reviews through Shopper Approved’s own API, renders them into the product page on the server, and attaches Product structured data to that same HTML. Same account, same reviews, same seals. Your reviews stop being an attachment to the page and become part of it.
Shopper Approved has been the reviews platform behind Web Shop Manager stores for years and is a long-standing Web Shop Manager partner. Twenty two Web Shop Manager merchants run verified Shopper Approved accounts today. This is that relationship rebuilt as a first-class Web Shop Manager 6.0 application: post-purchase review requests raised off the order events your store already fires, an hourly review sync, and server-rendered reviews with product structured data in both Web Shop Manager 6.0 storefront lineages. Same build standard as our Rithum and SureDone integrations: one platform, one outbox discipline, one test bar.
See what the page actually contains · See the comparison · Read the FAQ
You collected the review. The question is whether your product page contains it.
Reviews earn their keep twice: on the page, where a shopper decides to buy, and in the search result, where a shopper decides whether to click at all. The second one depends entirely on what is in your product page when Google fetches it. A widget can show a shopper stars and still leave the product’s rating data out of the document that got indexed. Google’s own guidance is direct about where product star ratings come from, and about what disqualifies them: put the review data in structured data on the product page, from your own reviews, and do not aggregate ratings from other sites. That is exactly the shape this integration builds.
The reviews are rendered by the server
On a Web Shop Manager 6.0 product page the reviews are already in the HTML of the first response. Nothing is fetched afterwards, nothing shifts into place once it arrives, and no third party script has to execute before a shopper can read what your customers said. The crawler and the shopper are handed the same document.
Product structured data on every product page
Each product page carries Product structured data with the aggregate rating and the individual reviews attached to that product, built from the same reviews the page displays. Visible reviews and schema reviews come out of one source in one render, so they cannot drift apart and leave you publishing a rating the page does not show.
Review requests raised off the order
When an order is paid, or when it is fulfilled, whichever suits how you ship, the request is raised against Shopper Approved automatically. The follow-up delay is a setting, seven days out of the box and anything from same day to a year, so the ask lands when the part has actually arrived rather than while it is still on the truck. One trigger is active at a time, so nobody gets asked twice for the same order.
A request that fails is retried, then it tells you
Every outbound request goes through a guarded outbox rather than straight out of the web request. A delivery that fails is retried on a widening backoff, up to eight attempts, and is keyed to the order so it cannot be sent twice. One that keeps failing stops retrying into the void and parks in a needs attention queue where somebody can see it, which is the difference between a quiet gap in your review flow and a problem you get to fix. Fix the cause, save your credentials, and everything parked goes back in the queue rather than being written off.
Reviews come back on their own
A scheduled sync reads your reviews and your rating aggregates back out of Shopper Approved every hour, so the storefront is working from what your buyers actually wrote rather than a snapshot somebody exported once. New reviews appear on the product pages they belong to without anyone touching the site, and an hour in which nothing changed writes nothing at all: it reads, compares, and leaves your database alone.
Store reviews for any account, product reviews where they are enabled
Your store level reviews and overall rating are read for any Shopper Approved account. Per product reviews, the ones that put stars on an individual part, depend on product review collection being enabled on yours. The integration works out which of the two your account allows instead of guessing, and if product reviews are not enabled it says so in plain English and stops asking, rather than retrying a rejected call forever or leaving product pages that look like nobody has ever bought anything.
Your Shopper Approved account, untouched
Nothing migrates and nothing is recreated. You paste your Shopper Approved site id and API token into a settings screen and the integration reads the account you already have, with the reviews you have already collected in it. Your seals, your Shopper Approved dashboard and your existing review collection carry on exactly as they are.
Your rating, not somebody else’s
A reviews integration pointed at the wrong account shows your shoppers a stranger’s stars, and it is a specific and embarrassing way to fail. Blank, placeholder and shared demonstration account numbers are refused: the feature hard-fails to off rather than rendering a rating that is not yours. Off is recoverable. Publishing the wrong company’s reviews is not.
A rating it cannot stand behind is not published
A rating outside the scale, a review missing its author or its date, a request to Shopper Approved that timed out: in every one of those cases the block is left out rather than patched up. Nothing is clamped into range to make the stars look right, and nothing arrives late and shoves the page around under a shopper’s thumb. The page is either correct or it is quiet.
Built into the platform, not bolted on
This is a first-party Web Shop Manager 6.0 application. Your Shopper Approved token is encrypted at rest and is never handed back out, every record it touches is scoped to the store it belongs to, the sync and the review requests run on the platform’s own background workers, and the storefront half ships in both Web Shop Manager 6.0 storefront lineages. No middleware subscription and no separate vendor to call when reviews stop appearing.
What your product page actually contains
This is the difference in one screen. Both approaches can put stars in front of a shopper. Only one of them puts the rating in the document.
GET /products/your-part-number
200 OK text/html
<section class="reviews">
<h2>4.8 out of 5, 37 reviews</h2>
<article>Bolted straight on, no trimming. J. R., Jul 2026</article>
...
</section>
<script type="application/ld+json">
{ "@type": "Product",
"aggregateRating": { "ratingValue": 4.8, "reviewCount": 37 },
"review": [ { "@type": "Review",
"author": "J. R.",
"reviewRating": { "ratingValue": 5 },
"reviewBody": "Bolted straight on, no trimming.",
"datePublished": "2026-07-14" } ] }
</script>
Your Shopper Approved reviews through their widget, and through the platform
Shopper Approved publishes two ways to get reviews onto a website, and this is the honest comparison because it is their own documentation on both sides. The widgets are the fast route: paste a snippet, reviews appear, works on any site anywhere. The API is the route they recommend once you have a backend, and their own specification says so in the first paragraph: this API is “provided for clients who need to pull data into their own backends”, and “is not intended for use in a browser client-side context.” Web Shop Manager 6.0 is a backend. The right-hand column is what Shopper Approved’s own published documentation says the widget install does, read in July 2026 and cited below. Nothing here is a criticism of the widgets. It is what changes when the platform can take the other route.
| What you actually get | Web Shop Manager 6.0 | The documented widget install |
|---|---|---|
| What ends up in the page | ||
| Review text is in the HTML of the first response | ●rendered on the server, before the browser asks for anything | ○their published snippet appends a script to the head and fills an empty div in the browser |
| Individual reviews carried in structured data, not only a rating | ●Product schema with the aggregate rating and the reviews themselves | ◙their schema setting injects “the Aggregate Rating schema” onto product pages |
| Structured data without rearranging the rest of your page’s schema | ●the platform owns the Product block, so reviews are added to it, not layered over it | ◙documented preconditions: a JSON-LD @id holding the product URL, and all non JSON-LD schema removed first |
| A product with no reviews of its own shows no rating | ●no reviews means no review block and no aggregate, rather than a substitute | ◙documented default: the product page widget shows store reviews until a product review is collected |
| How it gets there | ||
| Nothing to paste into your templates | ●a settings screen: site id, token, done | ◙documented as copy and paste the code snippet to the desired location of your website |
| No per product id to maintain by hand | ●reviews are matched to products from your own catalog keys | ◙their instructions: replace the [PRODUCT ID] placeholder anywhere you place this code |
| Review requests raised from the real order event | ●order paid or order fulfilled, through the API, retried if it fails | ◙documented as a code snippet placed on your order confirmation page |
| A collection or sync failure lands somewhere a human sees it | ●guarded outbox, backoff, then a needs attention queue in your dashboard | ○not documented |
● Live in the current WSM 6.0 integration ◙ Available, with a manual step or a documented condition ○ Not available, or not documented
- 1. The right-hand column describes what Shopper Approved’s own public documentation states about its widget install, read in July 2026. Where their documentation is silent we have marked it not documented rather than assumed a limitation. Individual accounts and configurations vary, and Shopper Approved’s widgets remain the right answer on platforms that cannot take the API route.
- 2. Server-side is Shopper Approved’s own recommendation for backends. Their published API specification states the API is “provided for clients who need to pull data into their own backends for processing they would like to do on their own servers (for example building a custom widget)”, and that it “is not intended for use in a browser client-side context”. Web Shop Manager uses it exactly that way.
- 3. Rendering: Shopper Approved’s published product widget snippet creates a script element pointed at their widget host, appends it to the document head, and populates an empty container element. That is a browser side render by construction. Their documentation makes no statement about page speed, async or deferred loading, and we make no measured performance claim about their widget here.
- 4. Structured data: their product review integration guide documents a setting named “Inject JSON-LD schema”, which when enabled has “the product review widget automatically inject the Aggregate Rating schema onto your product pages”, and states two preconditions: that your schema is in JSON-LD format with an @id attribute containing the product URL, and that “all non json_ld schema on your product pages should be removed”. Individual Review objects are not part of what that setting is documented to inject.
- 5. Empty products: their seals and widgets documentation states that “By default, the product page widget displays store reviews until a product review has been collected for the item.” Web Shop Manager renders no review block and no aggregate rating for a product that has none of its own.
- 6. Installation: their store integration guide documents placing a code snippet on your order confirmation page to begin collecting store reviews, and their product guide documents copying the snippet to the desired location of your website and replacing a [PRODUCT ID] placeholder wherever it is placed.
- 7. Store ratings in paid search and Shopping are a separate surface, and they stay with Shopper Approved. Shopper Approved describes itself as an official Google Review Partner and syndicates store ratings to Google on your behalf. Google’s own store rating partner requirements state that reviews sent through that feed must be collected by a review provider rather than by the merchant, which is precisely why that role is not one a platform should be trying to take over.
- 8. Product review counts and ratings shown on a product page come from your own Shopper Approved account through their API. Both storefront lineages read the same review shape, so a store on either one gets the same page contents.
Score your current setup against this table, book 20 minutes
Shopper Approved collects the reviews. Web Shop Manager publishes them.
Shopper Approved’s job is collection and independence: it asks your buyers for reviews, holds the corpus, and is the accredited party that feeds store level ratings to Google and Bing. That is a role a retailer cannot fill for itself, which is why it stays with them. Web Shop Manager’s job starts once the review exists: getting it onto the product page it belongs to, in the HTML, with structured data attached, fast, on your own domain. Neither side is doing the other’s work, and nothing about your Shopper Approved account has to change for both to happen.
One consequence worth being clear about, because it is the question every merchant asks second. The stars that appear on your paid search ads and Shopping listings come from the store ratings program, and that program requires an accredited review collector. Shopper Approved is one. Keeping them is how you keep those. The stars that can appear on a product page in ordinary organic results come from product structured data on that page, which is what this integration builds. They are two different surfaces, they are fed two different ways, and you want both.
Web Shop Manager is a fitment-native platform built for aftermarket parts, where year, make and model decide whether a product is relevant at all. Reviews land on products that already carry their vehicle data, alongside the same fitment convention our Google, Meta and Klaviyo integrations read. See the rest of our platform integrations, or the wider picture in automotive eCommerce.
Shopper Approved and Web Shop Manager: what dealers ask
Straight answers for aftermarket and auto parts retailers already collecting reviews, or about to start.
Does this work with my existing Shopper Approved account?
Yes, and that is the whole point. You paste your Shopper Approved site id and API token into the integration’s settings screen, test the connection against your live account from the same screen, and the token is stored encrypted and never handed back out again. Nothing is migrated, nothing is recreated, and no new Shopper Approved plan is needed to read what you already have. The reviews you have been collecting for years are the reviews that start appearing on your product pages.
Do I get store reviews, product reviews, or both?
Both are read. Your store level reviews and your overall rating come back for any Shopper Approved account. Per product reviews, the ones that put stars on an individual part in a search result, depend on product review collection being enabled on your account, and Shopper Approved documents that you must also be collecting store reviews with them in order to collect product reviews. The integration works out which of the two your account allows rather than guessing, and if product reviews are not enabled it says so in plain English and stops asking, rather than retrying a rejected call forever or leaving product pages that look like nobody has ever bought anything. Enabling them later is a conversation with Shopper Approved, and once it is done the reviews arrive on the next sync with no work on your side.
Does this slow my product pages down?
No, and it is one of the reasons to do it this way. The reviews are rendered into the page on the server, so there is no third party review script on the product page’s critical path, no request to another company’s domain before your content can appear, and no block of stars arriving late and pushing the page around under a shopper’s thumb. Speed matters on a parts site more than most: the shopper is often standing next to the vehicle on a phone with one bar. Reviews should not be the reason the page is late.
How do my reviews actually reach Google?
Two different surfaces, fed two different ways, and you want both. The stars that can appear on a product page in ordinary organic results come from Product structured data on that page, and Google asks for the review data to be in the markup of the page being reviewed, collected by you, not aggregated from other sites. That is what this integration writes: aggregate rating plus the individual reviews, on every product page, from your own account. The stars that appear on paid search ads and Shopping listings come from the store ratings program, which requires an accredited review collector, and that stays exactly where it is. Shopper Approved describes itself as an official Google Review Partner and syndicates your store ratings on your behalf. Keeping them is how you keep those.
Who asks my customers for the review, Shopper Approved or my store?
Shopper Approved still runs the asking, the surveys and the follow-up email, on their schedule and with their deliverability. Their documented default is a follow-up ten days after checkout, and it is theirs to tune. What Web Shop Manager changes is how the order gets to them. Instead of depending on a snippet firing on a confirmation page, your store raises the request through Shopper Approved’s API when the order is actually paid or actually fulfilled, whichever you choose, with a follow-up delay you set. If that call fails it is retried, and if it keeps failing it is escalated rather than lost. A customer who never got asked is a review you never got.
What happens to the reviews I have already collected?
They stay where they are, in your Shopper Approved account, which remains the system of record. The integration reads them. The first sync pulls your existing reviews and aggregates in, and after that a scheduled sync keeps them current on the hour. Reviews are matched to your products using the key you nominate, so a store whose historical reviews were submitted against SKUs and a store that used internal product ids are both handled by a setting rather than by a data migration.
Do I have to remove my Shopper Approved seals and widgets?
Your seals, badges and award widgets are visual trust marks and they can stay exactly where they are. The one thing worth turning off is Shopper Approved’s own “Inject JSON-LD schema” setting on any page where the platform is now emitting product structured data, because two sources writing the same aggregate rating onto one page is the kind of duplication that helps nobody. That is a single toggle in your Shopper Approved dashboard, and we will point at it on the call.
Bring your Shopper Approved account. We will show you your own reviews in your own product page.
Book 20 minutes. We will connect to your Shopper Approved account, pull your real reviews, and show you a product page that contains them, in the HTML, with the structured data attached. Bring the product page you wish had stars on it.
Get Started Now: Put Your Reviews Where Google Reads Them
Bring your Shopper Approved account. We will pull your real reviews and show you a product page that contains them, in the HTML, with the structured data attached.
See Shopper Approved Integrated On Your Store
Ready To Grow Your Business?
Ready to grow your aftermarket eCommerce presence and lift conversions across auto, truck, powersports, marine, and more? Connect with
Web Shop Manager for tailored solutions: strategy, platform, and performance in one team.