Shopware Upgrade Radar OverviewHow it worksTechnicalFAQ Run a free check

Check a shop now — paste its composer.lock

No signup, no install, no shop access. The server reads the lock, returns the per-plugin verdict with the excluding constraint quoted, and stores no lock content.

A sample shop is pre-loaded so you can press Run the check and see a real report in seconds — then clear it and paste your own lock.

2 MB max · a few checks per minute per IP · the server reads the lock, returns the verdict and stores no lock content — only anonymous counters. Paste mode sees the lock only; custom/plugins needs the CLI, a one-time purchase.

Shopware Upgrade Radar

Know which plugins break a Shopware update, before you run it. The verdict for every plugin in your shop, with the excluding constraint quoted.

Hosted check + CLI · Shopware 6 · nothing stored, no shop access

What it does

Before each Shopware update window, someone checks every plugin in every shop by hand. Shopware Upgrade Radar reads the shop's composer.lock and answers the question agencies actually plan with: which plugins will conflict with the target version. Each verdict quotes the constraint that causes it, so you can verify every line, and plugins that declare nothing are reported as unknown instead of being assumed fine.

How it works

Paste your lock fileDrop the shop's composer.lock into the hosted check, or point the CLI at a repo checkout for custom/plugins coverage.
The engine reads declared constraintsA 37-rule composer-semantics engine evaluates every plugin's shopware/* requirements against your target version.
Plan from the verdictCompatible, conflict, or unknown for every plugin, with the excluding constraint quoted. Sweep it across client shops before booking windows.

Technical

Inputs
composer.lock (hosted paste, 2 MB max) · repo checkout incl. custom/plugins (CLI)
Verdicts
Compatible / Conflict / Unknown, each with the governing constraint quoted verbatim
Engine
37-rule composer version-constraint semantics; release-availability lookup for conflicting plugins
Honest limits
Declared constraints are not resolution: composer update --dry-run remains the definitive gate at update time. Upgrade Radar is what you sweep across 30 shops first.
Privacy
Pasted lock content is processed in memory and not stored; the server keeps anonymous counters only
Targets
Shopware 6.x, target versions selectable per check

Frequently asked

Is my composer.lock stored anywhere?

No. The hosted check processes it in memory, returns the report, and keeps only anonymous counters. Package lists normally contain no personal data; do not paste files containing secrets.

Hosted check or CLI, which one do I want?

The hosted check answers for one shop in seconds from a pasted lock file, free and without an account. The CLI runs on a repo checkout, also covers custom/plugins, and is built for sweeping many shops — it is what a licence buys.

Is the verdict definitive?

It is the honest declared-constraint answer, with the constraint quoted so you can verify it. Resolution can still differ, which is why composer update --dry-run stays the final gate at update time. Upgrade Radar tells you where to look before you book the window.

What about plugins that declare no constraint?

They are reported as unknown. No guessing, no green-washing your fleet report.

What exactly do I get when I buy?

The CLI, for every shop you maintain, yours to keep — no seat count, no expiry, no account to log into. Every run writes a keepable HTML and Markdown report, open formats you can archive, diff, or hand to a client. The hosted check stays free for one-off questions, so you can see real verdicts on your own stack before you decide.

Run your first upgrade check now.

Paste a composer.lock and see the verdict for your own shop in seconds.

Buy Shopware Upgrade Radar — €9