SimpleReview · for Shopware 6 · Chrome Extension

Click any element on your Shopware 6 store. Get a code fix.

Q: Which Shopware versions are supported?

Shopware 6.5 and 6.6 — full support (primary target). Shopware 6.4 — limited (older Twig namespaces, deprecated DI patterns). Shopware 5 is NOT supported — completely different architecture (Smarty + Zend Framework, not Symfony + Twig). Shopware Apps support is coming; today we cover Plugins.

Stop paying €60–120/hr Symfony/Vue dev rates for one-Twig-file edits. SimpleReview reads custom/plugins/[Plugin]/src/Resources/views/storefront/, knows the theme inheritance graph — and opens a Pull Request with the right theme:compile notes.

Download Extension Read the Shopware 6 fix guide →

mystore.de

MeinStore

Wonach suchst du?

Warenkorb · 0,00 €

Frühlings-Sale läuft jetzt Bis zu 30% auf ausgewählte Artikel · Kostenloser Versand ab 50 €

Sneaker Pro 24

89,90 €

Rucksack Stadt

49,00 €

Kapuzenpullover

39,90 €

MeinStore

Wonach suchst du?

Warenkorb · 0,00 €

✓ Cookie banner dismissable · cookie-permission.html.twig patched · PR #42

Beliebte Produkte

SimpleReview PRO

Shopware expert · ready

waiting for selection…

Detected

PlatformShopware 6.6

ThemeMyTheme

Filecookie-permission.twig

Fix plan

Restore close handler in cookie-permission.html.twig + plugin JS · 2 files

Result

× button works again. GDPR consent stored, banner stays closed.

✓ PR #42 opened

fix(cookie): repair dismiss button
cookie-permission.twig · +6 / -1

Click SimpleReview → select the stuck cookie banner → Fix it → PR opens, no Symfony dev needed

What SimpleReview can fix on Shopware 6

Storefront overrides in custom/plugins/[Plugin]/src/Resources/views/storefront/

SCSS theme overrides — Resources/app/storefront/src/scss/

Snippets in Resources/snippet/[lang]/messages.[lang].json

config.xml plugin settings

JS plugins extending core via decoration

Cookie consent banner customization

Hide "Powered by Shopware" / footer credits

Cache + theme:compile awareness in PR description

Works with Shopware 6.5+ and 6.6 (primary). 6.4 limited. Shopware 5 NOT supported (different architecture — Smarty + Zend, not Symfony + Twig). Apps (vs Plugins) — apps support coming, plugin support today.

How SimpleReview works on Shopware 6

Install the Chrome Extension

Add SimpleReview to Chrome. Drop into any Shopware 6 storefront and the panel slides in.

Shopware 6 auto-detect

Detects the platform via <meta name="application-name" content="Shopware"> and the storefront HTML signatures. Theme inheritance chain resolved from theme.json.

Connect your Git repo

GitHub, GitLab, Gitea, Bitbucket. SimpleReview indexes custom/plugins/, theme plugins, and SCSS sources on first connection.

Click the element. Get a Pull Request.

Hover any block. Type the change. The agent edits the right Twig/SCSS/JSON in your plugin and opens a PR — with post-merge notes: bin/console theme:refresh && theme:compile && cache:clear.

SimpleReview vs Hiring a Shopware Symfony Freelancer

Feature	Symfony Freelancer (€60–120/hr)	SimpleReview
Time to start (per task)	1–3 hours (Zoom + Docker setup + repo onboarding)	30 seconds (one-time Git connect, then cached)
Discovers which Twig/SCSS file owns the bug	15–90 min depending on plugin/theme familiarity	Instant — `custom/plugins/` already indexed
Knows Shopware 6 storefront override conventions	If you hire a Shopware-certified senior	Built-in — `{% sw_extends '@Storefront/...' %}` aware
Theme inheritance (theme.json + @Parent + @Storefront)	Manual	Auto-resolves the inheritance graph
Includes `theme:compile` + `cache:clear` in PR notes	Sometimes (depends on freelancer)	Always — checklist in every PR description
Opens a PR you can review	Sometimes (if they use Git)	Always
Cost for a one-Twig-line change	€60–360 (1-hour minimum, often 2-3h)	Free with your own AI key — pennies of API usage otherwise
Recommended for custom payment app / headless API / migration	Yes — pair with Vibers human review	No — escalate to Vibers for the 20% of work that needs a human

Who uses SimpleReview on Shopware 6

Shopware 6 merchants

Twig copy + theme tweaks ship the same hour, instead of waiting for the agency retainer slot.

Shopware agencies (DE-heavy)

Drafts the boring 80% of tickets so Symfony seniors focus on payment apps, ERP integrations, headless work.

Freelancers running multiple SW6 stores

One Chrome Extension across all clients; each store has its own connected repo. Bill the strategic hour, automate the trivia.

Non-technical merchants

See the broken thing on the storefront, click it, describe in plain language. Get a PR your hosting partner or junior dev can merge.

FAQ

Can I edit my Shopware 6 store without a developer?

For most cosmetic and structural edits — yes. Twig storefront overrides in custom/plugins/[Plugin]/src/Resources/views/storefront/, SCSS theme overrides, snippet JSON files, and config.xml plugin settings. SimpleReview opens a PR for those in seconds. For custom payment integrations, complex Symfony service decorators, and headless API work — pair with Vibers human review.

How does SimpleReview install — Chrome ext or native Shopware Store plugin?

Today: install the Chrome Extension and connect your Git repo. Tomorrow: native plugin on the Shopware Store (in approval — usual review cycle 4–8 weeks). Once approved, install via Extensions → My extensions → Upload extension → Activate, then bin/console plugin:refresh && plugin:install.

Which Shopware versions are supported — 6.4, 6.5, 6.6?

Shopware 6.5 and 6.6 — full support (primary target). 6.4 — limited (older Twig namespaces, deprecated DI patterns). Shopware 5 is NOT supported — completely different architecture (Smarty + Zend Framework, not Symfony + Twig). Shopware Apps support is coming; today we cover Plugins.

Does it work with custom themes inheriting from @Storefront?

Yes. Theme inheritance is a first-class concept in SimpleReview. We resolve the theme.json inheritance chain, walk @Storefront → @Parent → @YourTheme, and patch the right Twig in your theme plugin (not in vendor/shopware/storefront/) so theme:compile picks it up cleanly.

Is it safe for a live Shopware 6 store?

SimpleReview never pushes to your live branch directly. Every change is a Pull Request you review and merge. After merge, the PR description includes the post-deploy checklist: bin/console theme:refresh && theme:compile && cache:clear. Pair with a staging clone and the worst case is a PR you reject.

How is this cheaper than a €80/hr Symfony freelancer?

Speed and recurring cost. A Shopware Symfony freelancer charges €60–120/hr and takes 1–3 hours to clone the repo, set up Docker, locate the override path, and figure out theme:compile flags. The actual edit is often one Twig line. SimpleReview already knows custom/plugins/[Plugin]/src/Resources/views/storefront/ and opens the PR in seconds. For custom payment apps, headless API, and migrations — keep your dev; that is what Vibers is for.

Stop paying €80/hr for one-Twig-file Shopware edits

SimpleReview's Shopware-aware AI agent already knows the storefront override system, theme inheritance, and theme:compile workflow. Click the element, type the change, get a Pull Request.

Get SimpleReview for Chrome →

Shopware 5 → 6 migration, custom payment apps, headless? → Get a human review