Skip to content

Shopware Store review and quality

Shopware Store review and quality

This section is for extension developers (plugins, apps, themes) who plan to distribute through the Shopware Store. It describes what reviewers check during publication and how you can align your implementation and tests with those expectations before you submit.

Store review complements your own automated and manual testing: it verifies that your extension stays within supported integration boundaries, behaves predictably for merchants and end customers, and meets listing, security, and compliance rules. Treat these pages as a checklist-oriented companion to the general testing guidelines.

Quality guidelines

Publication is gated on Shopware’s quality, security, and compliance rules. The guidelines summarize non-negotiable requirements that apply to every Store extension, independent of type or size.

Quality guidelines for Store extensions

Scope and integration boundaries

Reviewers validate that your extension does not rely on unsupported or fragile patterns (for example, undocumented core internals, unsafe database or filesystem usage, or API misuse). The following pages spell out prohibited behaviors and how functionality should integrate with Shopware core, persistence, and public APIs.

Not allowed store behaviors
Functionality and integration

Storefront, SEO, and compliance

Merchants expect stable storefront behavior, sensible performance characteristics, and clear handling of errors. Review also covers SEO-related output, structured data where relevant, and privacy-oriented behavior such as cookies and consent. Use these topics when defining acceptance criteria for themes and Storefront-facing plugins.

Storefront, performance, and errors
SEO and structured data
Cookies and privacy

Listing, lifecycle, and code quality

Beyond runtime behavior, review covers how you present the extension in the Store (descriptions, media, translations), what happens on install and uninstall (including data cleanup), and maintainability signals in your codebase. The common review errors page is a practical index of recurring feedback you can preempt.

Content and translations
Uninstallation and data cleanup
Code quality
Common Store review errors

Frequently asked questions

For submission logistics, timelines, and readiness questions that do not fit a single technical page, start here.

Frequently asked questions

Functional scenarios and test ideas used in the broader extension testing story are documented under testing guidelines; pair that guide with the Store-specific pages above when you plan your test matrix.

Testing guidelines for extensions
Was this page helpful?
UnsatisfiedSatisfied
Be the first to vote!
0.0 / 5  (0 votes)