Marius
Korbmacher
Book a call
All case studies

Case study / Landig

A review setup built around Landig’s store and workflows.

Landig had no review app and needed a complete setup: reviews matching the supplied design, including search and cart, plus post-purchase requests with specific exclusion rules. The implementation covered sending rules, discount codes and moderation, custom review forms and ratings integrated into the different theme areas.

Review requests
Timing, tags & order value
After submission
Approval & Shopify discount codes
Integration
PDP, product cards, cart & search

My contribution: Social proof integration as part of a relaunch with Eshop Guide: data integration, configuration, design customisation, placement and theme development.

Landig's Fleischwolf W 50 product page with yellow rating stars and review count next to the price.
Product rating in Landig's design, right next to the price. Captured in the relaunch store with test reviews.

01

Reviews in Landig’s design, right through to the cart

Each review display was built for its position in the store: the rating beside the price, detailed reviews on the product page and compact ratings on product cards. Markup, CSS and responsive layouts were adapted to Landig’s designs. The components remain reusable through the theme editor.

Ratings from Shopify metafields
Liquid reads the average rating and count directly from product metafields. The PDP rating is part of the server-rendered HTML.
Custom design, reusable components
Star distribution, sorting, reviews and replies use customisable markup and CSS; the two-column list becomes a single column on mobile. After handover, Landig can place the sections and app blocks in the theme editor and reuse them on other templates.
Landig review list with star distribution, sorting, reviews and a merchant reply, shown with test data.
Star distribution, reviews and merchant replies based on Landig's design, with an adapted mobile layout. The displayed reviews are test data.

Ratings also appear in search and the cart drawer

Ratings were also integrated where content loads in response to an action: typing in search or updating the cart. The rating component was added to the different product cards, including collection and search results pages, featured products and cross-selling. This makes ratings available without a full page refresh.

Landig predictive search for Fleischwolf, showing rating stars and counts in dynamically loaded product cards.
Predictive search: ratings in product suggestions without a full page load. Captured in the relaunch store with test data.
A reusable rating snippet
A shared Liquid snippet passes the product ID, average rating and count to the rating component. It is integrated into the theme's different product-card variants.
Predictive search and search results
Suggestions loaded while typing also display ratings. The same presentation is used in product listings and on the regular search results page.
Cart and cart drawer
Ratings are also integrated into dynamic cart areas. Their display is not limited to components present on the first page load.
Server output combined with JavaScript
Review text is already included in the page HTML. For dynamic product cards, a web component renders the ratings using the data passed through by Liquid.

From order to review in the store

  1. 01

    Check the order

    Order tags and order value exclude specific orders; product tags exclude individual products from the request. Eligible requests are sent after the configured delay following fulfilment.

  2. 02

    Request a review

    An email links to the post-purchase review form, followed by internal approval and a Shopify discount code as an incentive.

  3. 03

    Display in the store

    Approved reviews are stored in Shopify. Ratings and review text are integrated into the different theme areas.

02

Post-purchase requests following Landig’s rules

Landig needed control over which orders trigger review requests and when they are sent. Tag and order-value exclusions, the delay after fulfilment and discount rewards were configured to meet those requirements. Configurable features provide the foundation; their setup follows Landig’s requirements.

Which orders receive a review request

A delay after fulfilment
Requests are based on fulfilment status. The requested interval of 7 to 14 days after fulfilment is configurable, instead of sending immediately after purchase.
Exclusions by order and product tags
Orders with specified tags can be excluded. Products tagged 'Seminar' can also be excluded from review requests.
Order-value exclusions
The app can exclude orders above a configurable amount, for example €5,000. This adds order-value filtering alongside the tag rules.
Discount codes and manual approval
Native Shopify discount codes provide an incentive for submitted reviews. At Landig, new reviews require the team's approval before publication.
Preview of a Landig review request email with the logo, order number and a button linking to the review form.
Review email preview with an order reference and a direct link to the post-purchase form. Example from the development store.

Review after purchase: by email or directly on the PDP

PDP review form with purchase check
The review form on the product detail page is only rendered for logged-in customers whose Shopify order history includes a purchase of that product. The check runs server-side in Liquid. Returning customers can therefore review directly on the product page, even without the link from a review request email.
Post-purchase review form
The review request email links directly to the post-purchase form in the store, where customers can review the products they ordered. Product presentation, copy, fields and buttons were adapted for this flow.
Landig post-purchase form with three ordered products, star ratings, title and text fields, and a button to submit all reviews.
Embedded directly in the Landig store: the post-purchase review form uses the same header and navigation as the rest of the shop. Reviews for multiple products can be submitted separately or together. Captured in the development store.

03

Performance & Lighthouse

Reviews integrated. Average Lighthouse score stays stable.

Reviews on product pages, in search and in the cart, with virtually no difference in the average Lighthouse score: 56.2 without the integration, 56.1 with it. Review data is stored directly in Shopify, and review text is delivered in the page HTML.

Without integration

56.2

With integration

56.1

Mean performance score across all pages and devices

Google PageSpeed Insights, 11 September 2026. Homepage, collection page and product detail page: ten runs per device and variant, 60 in total. Values are means. Tests ran on Shopify Preview (*.shopifypreview.com, pb=0), not the live store, using CPU throttling for comparable measurements.

Lighthouse scores compared side by side

Performance score from 0 to 100 · Mean values

Without integrationWith integration
Lighthouse scores compared side by sideMean · All test groups: Without integration 56.2, With integration 56.1. Mean · Mobile: Without integration 42.7, With integration 43.3. Mean · Desktop: Without integration 69.6, With integration 68.9. Homepage · Mobile: Without integration 46.0, With integration 49.5. Collection · Mobile: Without integration 43.5, With integration 40.3. Product page · Mobile: Without integration 38.6, With integration 40.2. Homepage · Desktop: Without integration 77.0, With integration 78.2. Collection · Desktop: Without integration 69.2, With integration 66.6. Product page · Desktop: Without integration 62.7, With integration 61.8.

Full measurement comparison

For each metric, the value without the review integration is on the left and the value with it is on the right. The change is shown underneath: green means better, red means worse. Higher performance scores are better; lower values are better for the other metrics. Lighthouse results vary between runs. That is why we use 10 measurements per test group, resulting in 60 before-and-after measurements in total.

Full measurement comparison. For each metric, the value without the review integration is on the left and the value with it is on the right. The change is shown underneath: green means better, red means worse. Higher performance scores are better; lower values are better for the other metrics. Lighthouse results vary between runs. That is why we use 10 measurements per test group, resulting in 60 before-and-after measurements in total.
Page / devicePerformanceFCPLCPTBTCLSSpeed IndexTransfer size
Mean · All test groups56.2 56.1(-0.1)2.7 s 2.7 s(0.0 s)7.6 s 7.5 s(-0.1 s)575 ms 673 ms(+98 ms)0.023 0.027(+0.004)5.8 s 5.9 s(+0.1 s)3,846 KiB 3,846 KiB(0 KiB)
Mean · Mobile42.7 43.3(+0.6)4.7 s 4.6 s(-0.1 s)13.3 s 13.1 s(-0.2 s)713 ms 797 ms(+84 ms)0.014 0.030(+0.016)9.0 s 9.0 s(0.0 s)3,613 KiB 3,615 KiB(+2 KiB)
Mean · Desktop69.6 68.9(-0.7)0.7 s 0.7 s(0.0 s)1.9 s 2.0 s(+0.1 s)437 ms 549 ms(+112 ms)0.031 0.025(-0.006)2.5 s 2.7 s(+0.2 s)4,080 KiB 4,078 KiB(-2 KiB)
Homepage · Mobile46.0 49.5(+3.5)5.4 s 4.8 s(-0.6 s)14.3 s 13.2 s(-1.1 s)473 ms 493 ms(+20 ms)0.000 0.000(0.000)8.9 s 8.4 s(-0.5 s)3,593 KiB 3,618 KiB(+25 KiB)
Collection · Mobile43.5 40.3(-3.2)4.2 s 4.9 s(+0.7 s)12.8 s 13.8 s(+1.0 s)665 ms 672 ms(+7 ms)0.033 0.082(+0.049)8.2 s 8.3 s(+0.1 s)3,207 KiB 3,208 KiB(+1 KiB)
Product page · Mobile38.6 40.2(+1.6)4.6 s 4.2 s(-0.4 s)12.9 s 12.2 s(-0.7 s)1,002 ms 1,225 ms(+223 ms)0.010 0.007(-0.003)10.0 s 10.3 s(+0.3 s)4,038 KiB 4,018 KiB(-20 KiB)
Homepage · Desktop77.0 78.2(+1.2)0.8 s 0.7 s(-0.1 s)1.4 s 1.3 s(-0.1 s)365 ms 385 ms(+20 ms)0.005 0.003(-0.002)2.4 s 2.5 s(+0.1 s)4,295 KiB 4,288 KiB(-7 KiB)
Collection · Desktop69.2 66.6(-2.6)0.7 s 0.7 s(0.0 s)2.7 s 2.8 s(+0.1 s)300 ms 398 ms(+98 ms)0.001 0.001(0.000)2.2 s 2.4 s(+0.2 s)3,180 KiB 3,195 KiB(+15 KiB)
Product page · Desktop62.7 61.8(-0.9)0.7 s 0.7 s(0.0 s)1.5 s 1.9 s(+0.4 s)647 ms 865 ms(+218 ms)0.088 0.070(-0.018)2.8 s 3.2 s(+0.4 s)4,764 KiB 4,750 KiB(-14 KiB)

FCP: First Contentful Paint · LCP: Largest Contentful Paint · TBT: Total Blocking Time · CLS: Cumulative Layout Shift · Speed Index: how quickly page content becomes visible

More information about Google PageSpeed Insights

Similar requirements for social proof?

On the call, we’ll look at what’s already in place, what could work better and how I can handle the implementation.