diff --git a/guides/development/monetization/quality-guidelines.md b/guides/development/monetization/quality-guidelines.md
index 09b523c6e..d17885df6 100644
--- a/guides/development/monetization/quality-guidelines.md
+++ b/guides/development/monetization/quality-guidelines.md
@@ -1,327 +1,366 @@
 ---
 nav:
-  title: Quality Guidelines for Store Extensions
+  title: Quality guidelines for apps in the plugin system
   position: 20
 
 ---
 
-# Quality Guidelines for Store Extensions
+# Quality guidelines for the Shopware Store
 
-These guidelines apply to all extensions distributed via the Shopware Store, including both plugins and apps. They define the quality, security, and compliance requirements for publication.
+These guidelines apply to all extensions distributed via the Shopware Store, including plugins and apps. They define the quality, security, and compliance requirements for publication.
 
 ## Scope and terminology
 
 * **Extension**: umbrella term for plugins and apps.
-* **Plugin**: installed in the Shopware instance; PHP code, Composer.
-* **App**: integrated via app system; no direct PHP execution in core.
+* **Plugin**: installed in the Shopware instance; PHP code and Composer packages.
+* **App**: integrated via the app system; no direct PHP execution in core.
 
 Unless stated otherwise, requirements apply to all extensions.
 
+## What kind of extension is allowed?
+
+Currently, all types of extensions are allowed, except those that violate the regulations below. Extensions with the following characteristics are not permitted and will not be approved:
+
+* Functions that are included in the Shopware B2B Components; see [Shopware 6 - Commercial Features - B2B Components](https://docs.shopware.com/en/shopware-6-en/commercial-features/b2b-components).
+* Direct SQL changes by the merchant or other security-relevant issues.
+* Extensions that are two major Shopware versions below the current supported range.
+* If your extension is a software app or interface with downstream costs, transaction fees, or service fees for the customer, a technology partner agreement must be completed before the app can be activated.
+
 ## Review process
 
 All extensions are:
 
-1. Automatically [code-reviewed](https://github.com/shopwareLabs/store-plugin-codereview) (PHPStan, SonarQube), due to our quality assurance, with special attention on impacts to the Administration and Storefront.
+1. Automatically [code-reviewed](https://github.com/shopwareLabs/store-plugin-codereview) (PHPStan, SonarQube) as part of quality assurance, with special attention to impacts on the Administration and Storefront.
 2. Manually reviewed for security, coding standards, user experience, and functionality.
-3. Tested on the latest stable [Shopware 6](https://www.shopware.com/de/download/#shopware-6) CE version.
+3. Tested on the latest stable [Shopware 6](https://www.shopware.com/en/download/#shopware-6) Community Edition.
 
-Always test against the highest supported Shopware 6 version (e.g., `shopware/testenv:6.7.6`).
+Always test against the highest supported Shopware 6 version (for example `shopware/testenv:6.7.6`).
 
 For apps, we additionally test:
 
-* `config.xml` per sales channel
-* Install/uninstall behavior
-* Styling and viewport issues
+* `config.xml` per sales channel.
+* Install and uninstall behavior.
+* Styling and viewport issues.
 
-Before publishing an extension, review the full test process to ensure fast approval.
+Before publishing an extension, review the full test process to ensure faster approval.
 
-::: info
-[Test your app for the Shopware Store (DE):](https://www.youtube.com/watch?v=gLb5CmOdi4g); EN version is coming soon.  
-:::
+## Checklist for testing
 
-## Store listing requirements
+* We use automatic code review and look for security issues and Shopware coding standards in the manual code review.
+* We check the full functionality of the extension and look for styling issues on every viewport.
 
-All extensions must:
+[Documentation for Extension Partner – preview and testing](https://docs.shopware.com/en/account-en/extension-partner/extensions?category=account-en/extension-partner#how-can-i-request-a-preview)
 
-* Be available in English, with 1:1 translation between English and German. For the German store, German language is required. All extensions will be released in both the German and International stores.
-* Use meaningful short and long descriptions.
-  * The short description (150–185 characters) teases your extension in an overview, along with "Customers also bought" and "Customers also viewed" recommendations. It is also published as a meta-description.
-  * Long descriptions (minimum 200 characters) must describe the extension's functionality in detail.
-* Accurately and clearly describe the extension and its use cases.
-* Avoid the words “plugin” and “shopware” in the display name.
-* Avoid blank spaces as filler text.
-* Include clear, complete setup and configuration instructions.
-* Use clean HTML source code. Inline styles will be stripped.
+## Extension store description
 
-These tags are allowed:
+Release to the international store is standard; the German store is optional. When an extension is released in both stores, content must accurately translate one-to-one from English to German.
 
-```markdown
-<a> <p> <br> <b> <strong> <i> <ul> <ol> <li> <h2> <h3> <h4> <h5>
-```
+### Short description
 
-### Fallback language/translations
+Minimum 150 characters, maximum 185 characters. The short description must be unique and at least 150 characters long.
 
-Extensions must work independently of the system language.
+Use the short description carefully: it appears in the overview together with "Customers also bought" and "Customers also viewed". It is also used as the meta description.
 
-If a translation is missing (e.g., Spanish), a proper fallback (usually English) must be used.
+### Description
 
-If your extension is available in multiple languages, define them in your Shopware Account under “Translations into the following languages are available,” located in the "Description & images" section.
+Minimum 200 characters. The description must describe the extension's features in detail.
 
-We review:
+* Inline styles are stripped. The following HTML tags are allowed:
 
-* Text snippets
-* `config.xml`
-* `composer.json`
+  `<a>`, `<p>`, `<br>`, `<b>`, `<strong>`, `<i>`, `<ul>`, `<ol>`, `<li>`, `<h2>`, `<h3>`, `<h4>`, `<h5>`
 
-### Reserve your extension name with a store preview
+* Describe the extension and its use cases accurately and clearly.
+* Include clear, complete setup and configuration instructions.
 
-To secure an idea early, create a preview in your Shopware Account. Request this by providing placeholder images, meaningful use cases, key features, a description, and an expected release month. No binary upload is required.
+::: info
+* Avoid the words "plugin" / "app" and "Shopware" / "for Shopware" in the display name.
+* Avoid blank spaces as filler text.
+* Avoid advertising or contact information in the description.
+:::
+
+### Configuration manual
 
-### Extension master data/license
+Explain how your extension is installed and configured, how it works technically, and how merchants achieve the desired outcome. The manual should include a setup guide and use clean HTML source code.
 
-The license selected in your Shopware Account must match the license defined in `composer.json`. The selected license cannot be changed after the extension has been created. Changes require creating a new extension with a new technical name and uploading it again.
+### Images
 
-## Screenshots and media requirements
+Include several screenshots and descriptive images from the Storefront and Administration that show the extension in use. They must show the extension in action, its configuration options, and how to use it. We recommend screenshots for both mobile and desktop.
 
+Only images that represent or illustrate the extension may be used. Advertising for other extensions or services is not permitted.
+
+::: info
 * Use English-only screenshots for the English store listing and preview images.
-* Screenshots in German for the German store description are optional.
-* Only images that represent or show the function of the extension are permissible.
+* Screenshots in German for the German store are optional.
 * Advertising for other extensions or services is not permitted.
-* Ensure that screenshots show the extension's functionality in action in the Storefront and administration, as well as configuration options and how-to-use details.
-* We recommend screenshots showing mobile and desktop views.
+* Provide at least one image for the Storefront and one for the Administration.
+* Do not mix English with other languages in the same screenshots.
 
-:::info
-[How To - Add images and icons to extensions](https://docs.shopware.com/en/account-en/adding-pictures-and-icons/how-to)
+[How to add images and icons to extensions](https://docs.shopware.com/en/account-en/adding-pictures-and-icons/how-to)
 :::
 
-## Preview requirements
+### Link to demo shop
 
-* A preview image must be available in the Extension Manager.
-* Store a valid favicon named `plugin.png` (112x112px) under `src/Resources/config/`. This favicon will help you identify your extension in the `Administration > Extension Manager` module.
-* [Themes](../../plugins/themes/index.md) require a preview image in the Theme Manager.
-* [Shopping World elements](../../../concepts/commerce/content/shopping-experiences-cms.md#elements) must include an element icon.
+If you provide a demo shop, the link must be valid and stable. Do not link to short-lived test environments; they may be removed automatically two weeks after creation.
 
-Read our [How to request a preview](https://docs.shopware.com/en/account-en/extension-partner/extensions?category=account-en/extension-partner#how-can-i-request-a-preview) guide for additional help.
+### Personal data protection
 
-## Demo shop requirements
+If personal data of customers (the merchant and/or their customers) is processed with this extension according to Art. 28 GDPR, the data processor's details must be stored in the **Subprocessor** field.
 
-* URLs must not contain `http:` or `https:`.
-* Test environments will be automatically deleted after two weeks, so do not link to them.
+If other companies are involved in processing personal data, the same information must be stored for them under **Further subprocessors**.
 
-## Manufacturer profile requirements
+### Manufacturer profile
 
-The manufacturer profile exists in your account under Shopware Account > Extension Partner > [Extension Partner profile](https://account.shopware.com/producer/profile).
+Your manufacturer profile must contain accurate English and German descriptions and a manufacturer logo.
 
-* A manufacturer logo is required.
-* No iframes, tracking, or external scripts are allowed.
-* External sources must use HTTPS.
-* Must contain accurate English and German descriptions.
+You can edit the profile under Shopware Account → Extension Partner → [Extension Partner profile](https://account.shopware.com/producer/profile).
 
 ::: info
-The source code's descriptions, profiles, and instructions do not allow iframes, external scripts, or tracking pixels. Custom styles may not overwrite the original Shopware styles. External sources must be included via https.
+* Descriptions, profiles, and instructions must not use iframes, external scripts, or tracking pixels.
+* Custom styles must not overwrite original Shopware styles. External resources must be loaded over HTTPS.
+* Manufacturer and partner certificates are loaded dynamically at the end of each app description and are published by Shopware.
 :::
 
-::: info
-You can no longer advertise Shopware certificates within an extension's description, images, or your manufacturer profile.
-Manufacturer/partner certificates are dynamically loaded at the end of each extension description and published by Shopware.
-:::
+## General technical guidelines
 
-## Data Protection
+### Testing functionality
 
-If the personal data of customers, including store operators and their customers, is processed according to Art. 28 DSGVO:
+We verify the extension's full functionality everywhere it affects the Administration or Storefront. Every extension is code-reviewed by Shopware to ensure coding and security standards.
 
-* Subprocessor information must be declared.
-* Additional processors must be listed accordingly, under "further subprocessors."
+### Fallback language and translations
 
-An extension with a name that directly reflects its functional purpose is permissible, even if it shares the same name as another extension.
+The shop language is not always English or German. If the merchant uses Spanish, for example, and your extension has no Spanish translation yet, use English as the fallback.
 
-The store display name must be used for `composer.json` and `config.xml`.
+If the extension is available in more than one language, declare this with **Translations into the following languages are available** in the **Description & images** section of your Shopware Account.
 
-Not allowed:
+We check text snippets, `config.xml`, and `composer.json`.
 
-* Inline styles.
-* Certificates in descriptions.
-* Iframes, tracking pixels, external scripts.
+### Valid preview images for the Administration
 
-We allow up to two YouTube videos embedded in your extension description.
+A preview image must be available in the **Extension Manager**. Upload a valid favicon named `plugin.png` (PNG, 112 x 112 pixels). Store it under `src/Resources/config/`. It identifies your extension in the Extension Manager.
 
-:::info
-Video content—especially explainer videos, product demos, and tutorials—increases awareness and trust and has proven to convert potential customers better than other content types.
-:::
+Also provide a preview image for themes in the **Theme Manager** and for CMS elements in **Shopping Experiences**.
+
+### Configuration per sales channel
+
+Apps that appear in the Storefront must be configurable separately for each sales channel.
+
+### External links with `rel="noopener"`
+
+Every external link in the Administration or Storefront that opens in a new tab must use `target="_blank"` together with `rel="noopener"`.
+
+### Error messages and logging
+
+Error or informational messages must be written only to the event log in Shopware's log directory (`/var/log/`). Implement your own log service.
+
+**Never write extension-specific exceptions into Shopware's default log or outside the Shopware log folder.** That reduces the risk of log files being reachable via URL.
+
+For payment extensions, we check that the plugin logger service is used for debug or error output and that logs are written under `/var/log/`. Log files must be used consistently.
+
+Name log files for example: `MyExtension-YYYY-MM-DD.log`.
+
+Alternatively, logs may be stored in the database. Avoid custom log tables unless you implement a scheduled task that purges data within a maximum retention of six months.
+
+### Avoid HTTP 400 and 500 errors
+
+Avoid **500** errors at all times. Avoid **400** errors unless they are clearly tied to an expected API response.
+
+### Install and uninstall: data retention choice
+
+When the merchant uses **Install** or **Uninstall** in the Extension Manager, they must be able to choose whether extension data (including snippets, media, and database changes) is **fully removed** or **kept**.
+
+You can verify database behavior with the [Adminer extension from Friends of Shopware](https://store.shopware.com/en/frosh79014577529f/adminer-for-admin.html) in your test environment.
+
+### Do not extend the Extension Manager
+
+The Extension Manager must not be extended or overwritten.
+
+### Composer dependencies
+
+Dependencies must be declared in `composer.json`. With `executeComposerCommands() === true` in the plugin base class, Composer dependencies can be installed dynamically by default and do not need to be bundled manually. Everything shipped in code must be traceable directly or via `composer.json`.
 
-## Functional requirements
+For private Composer repositories, follow Composer's documentation on [private repositories and authentication](https://getcomposer.org/doc/articles/authentication-for-private-packages.md) so reviewers can install the extension.
 
-All extensions must:
+### Extension Manager lifecycle
 
-* Work without 500 errors.
-* Avoid 400 errors unless they are related to an API call.
-* Be installable and uninstallable without issues.
-* During uninstall, users must be able to choose in the Extension Manager whether to "completely delete or "keep the app data, text snippets, media folder, including own media and table adjustments." The free [Adminer](https://store.shopware.com/en/frosh79014577529f/adminer-for-admin.html) extension from Friends of Shopware enables you to do this via your provided test environment.
-* Avoid extending or overwriting the Extension Manager.
-* Properly register cookies in the [Cookie Consent Manager](../../../guides/plugins/plugins/storefront/add-cookie-to-manager).
-  * Every cookie set from the store URL should be optional and not technically required for running Shopware. We differentiate between "Technically required", "Marketing," and "Comfort features."
-  * All cookies must appear (unchecked) in the cookie configuration box in the frontend.
-* Do not introduce severe performance regressions.
-* Do not break Storefront SEO, structured data, or canonical logic.
-* If the extension publishes messages to the message queue, each message must not exceed 262,144 bytes (256 KB). This limitation is set by common message queue workers.
-* After uninstalling the extension, Shopping Experiences must continue to work in the frontend.
+The Debug Console drives installation, uninstallation, reinstallation, and deletion. No **400** responses or unhandled exceptions may occur. If the extension needs special PHP settings, validate them during installation and show a clear growl message in the Administration if requirements are not met.
 
-### Plugin-specific requirements
+### No file reloading during installation
 
-These apply only to plugins:
+Apps must not load additional files during or immediately after installation in the Extension Manager.
 
-* [Composer dependencies](../../../guides/plugins/plugins/plugin-fundamentals/using-composer-dependencies) must be declared in `composer.json` so they are traceable.
-  * If `executeComposerCommands() === true` is used, dependencies are installed dynamically and do not need to be bundled.
-* `composer.lock` must not be included in the archive.
-* Deliver uncompiled (readable) JavaScript in addition to compiled assets. Uncompiled sources must be included in a separate folder to allow code review.
-  * Build `main.js` and create the minified code according to our documentation: [Loading the JS files](../../../guides/plugins/plugins/administration/module-component-management/add-custom-field.md#loading-the-js-files) and [Injecting into the Administration](../../../guides/plugins/plugins/administration/module-component-management/add-custom-field.md#injecting-into-the-administration).
-* Only production files may be included in the archive.
-* Unified logs must be written to `/var/log/`.
-* No forbidden PHP statements like `die`, `exit`, or `var_dump` are allowed. See [List of blockers](https://s3.eu-central-1.amazonaws.com/wiki-assets.shopware.com/1657519735/blocker.txt)
-* Shopware must have access to the unminified source code of the extension at all times.
+### Ship unminified JavaScript alongside the build
 
-### App-specific requirements
+Compiled JavaScript improves performance but is hard to review. Ship the original, readable JavaScript in a separate folder so others can audit it.
 
-These apply only to apps:
+Build `main.js` as described in the developer documentation and generate minified assets accordingly. For injecting into the Administration, follow <PageRef page="../../plugins/plugins/administration/module-component-management/add-custom-module" title="Add custom module" /> and for the Storefront <PageRef page="../../plugins/plugins/storefront/add-custom-javascript" title="Add custom JavaScript" />.
 
-* Per-sales-channel configuration required if using `config.xml``.
-* No loading external files during installation.
-* API integrations must include an API test button.
-* Must not modify Extension Manager.
-* STP agreement required for commission-based integrations.
-* Apps that appear in the Storefront and use a `config.xml` must be able to be configured separately for each sales channel.
+Shopware may publish extensions with minified code only after individual review, provided the developer always grants access to the current unminified sources.
 
-## Code and security requirements
+### Message queue payload size
 
-* Pass automated code reviews (PHPStan, SonarQube).
-* Do not include development files or unused resources in the binary.
-* Include only necessary dependencies.
-* Use secure cookie settings.
+If the extension enqueues messages, keep payloads at or below **256 KB**, in line with common message queue workers.
 
-## Composer and dependencies
+### Shopware Technology Partner agreement
 
-If the extension includes Composer dependencies:
+If your extension is a software app or interface with downstream costs, transaction fees, or service fees for the customer, a technology partner agreement is required before activation.
 
-* All delivered code must be traceable via Composer.
-* The extension must not exceed store size limits.
+For questions, contact the sales team at [alliances@shopware.com](mailto:alliances@shopware.com) or by phone: **+44 (0) 203 095 2445 (UK)**, **00 800 746 7626 0 (worldwide)**, **+49 (0) 2555 928 85-0 (Germany)**.
 
 ## Storefront guidelines
 
-* No inline CSS allowed in storefront templates. Use your own classes and let your CSS be compiled by the plugin. See [Add SCSS variables](../../../guides/plugins/plugins/storefront/add-scss-variables.md#add-scss-variables).
-* Avoid using the `!important` rule unless unavoidable.
-* All images must include meaningful `alt` tags, or original `alt` tags from the media manager.
-* All links must include meaningful `title` tags.
-* External links must use `target="_blank"` together with `rel="noopener"`.
-* No `<hX>` tags in the storefront templates, which are set to `<meta name="robots" content="index,follow">`. These are reserved exclusively for content purposes.
-  * However, you may employ `<span class="h2">`, for instance.
-* Performance should remain stable (Lighthouse A/B check recommended).
-* Test the frontend and the checkout for new errors throughout the entire Storefront using the Browser Debug Console, paying close attention to JavaScript errors.
+### Testing the Storefront
 
-## SEO & indexing requirements
+Test the full Storefront and checkout with the browser developer tools open and watch for JavaScript errors.
 
-* New controller URLs or XHR requests must include the header `X-Robots-Tag: noindex, nofollow`. See [robots meta tag](https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag?hl=de#xrobotstag) documentation for additional guidance.
-* Public frontend URLs created by the extension must appear in `sitemap.xml` and include a valid canonical tag, unique meta descriptions, and `title` tags (configurable via Administration or as a text snippet).
+### Markup, CSS, and accessibility
+
+* No inline CSS in Storefront templates. Use your own classes and compile CSS with the extension. See <PageRef page="../../plugins/plugins/storefront/add-scss-variables" title="Add SCSS variables" />.
+* Avoid `!important` unless unavoidable.
+* Images need meaningful `alt` text (or the original alt from the media manager).
+* Links need meaningful `title` attributes where appropriate.
+* External links use `target="_blank"` with `rel="noopener"`.
+* Do not use `<h1>`–`<h6>` in Storefront templates on pages with `<meta name="robots" content="index,follow">`; reserve real headings for content. You may use classes such as `<span class="h2">` for visual hierarchy.
+* Keep performance stable; Lighthouse audits in the A/B range are recommended.
+* Re-test the Storefront and checkout after changes, including the browser console for JavaScript errors.
+
+### SEO and indexing
+
+* New controller URLs or XHR endpoints that must not be indexed should send `X-Robots-Tag: noindex, nofollow`. See Google's documentation on the [robots meta tag and `X-Robots-Tag`](https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag#xrobotstag).
+* Public frontend URLs created by the extension should appear in `sitemap.xml` where applicable, use valid canonical tags, and have unique meta descriptions and `title` tags (configurable in the Administration or via snippets).
+
+### Lighthouse testing
+
+Run a [Google Lighthouse](https://developer.chrome.com/docs/lighthouse) audit before and after activating the extension.
+
+Significant regressions in performance, accessibility, best practices, or SEO are **not** acceptable. Do not introduce new console errors.
+
+### Structured data and rich results
+
+Validate structured data with [Schema.org's validator](https://validator.schema.org/) and Google's [Rich Results Test](https://search.google.com/test/rich-results). Test the homepage, categories, and product detail pages across typical cases (in stock, out of stock, with and without reviews, variants with dimensions and identifiers, and so on).
+
+### Fonts and external services
+
+If you load fonts or assets from third parties (for example Google Fonts or Font Awesome), state this in the extension store description. Merchants may need to update their privacy policy. A tooltip next to the relevant configuration can help.
+
+### Cookie Consent Manager
+
+Cookies set from the shop that are not strictly required for running Shopware must be optional and registered in the Cookie Consent Manager.
+
+We distinguish **Technically required**, **Marketing**, and **Comfort features**. Optional cookies must appear **unchecked** by default in the cookie configuration in the Storefront.
 
 ## Administration guidelines
 
-* Do not add new main menu entries in the Administration, to preserve look and feel consistency.
-* Create a dedicated media folder with correct thumbnail settings or use an existing one (except for uploads defined in `config.xml`).
-* Custom media folders and their contents must be removed during uninstall.
-* All links must include meaningful `title` tags.
-* All images must include meaningful `alt` tags, or original `alt` tags from the media manager.
-* If your API corresponds via API credentials to external services, provide an API test button. ([Example implementation](https://github.com/shyim/ShyimApiTest) in the system config form)
-* It is possible to validate required credentials while saving them in extension settings. Display a status message in the Administration and log the result in Shopware.
-* If API data is incorrect, an entry must appear in the `/var/log/` file or in the database event log.
-
-### Installation and lifecycle
-
-* The Extension Manager (Debug Console) controls installation, uninstallation, reinstallation, and deletion.
-* Install, uninstall, and reinstall must work without exceptions.
-* No 400/500 errors during install/uninstall are allowed.
-* Users must be able to choose whether to delete or keep extension data.
-* Special PHP requirements must be validated during installation.
-* If validation fails, a growl message must appear in the Administration.
-* Extensions must not modify or overwrite the Extension Manager.
-* Apps must not reload or load external files during installation.
+### Main menu entries
 
-### Error messages and logging
+Do not add entries to the main menu of the Administration; this is reserved for core look and feel.
 
-* Error or informational messages can only be recorded in the event log of Shopware's log folder, `/var/log/`.
-* Do not write to Shopware’s default logs or outside the system log directory. This ensures that the log file can never be accessed via the URL.
-* Log files must follow the naming pattern: `MyExtension-Year-Month-Day.log`.
-* Payment apps must use the "plugin logger" service.
-* If storing logs in a database, avoid using custom log tables. Otherwise, you have to implement scheduled cleanup (max retention six months).
+### Media folders
 
-### API integrations
+Create dedicated media folders with correct thumbnail settings, or reuse suitable existing folders, except for upload fields defined in `config.xml`. If you use a custom folder, remove it on uninstall when the merchant chooses to delete extension data.
 
-If external APIs are used:
+### API test button
 
-* API test button required.
-* Credentials must be validated on save.
-* Success/failure must display a status message in Administration.
-* Errors must be logged in `/var/log/` or the database.
+If your extension calls external APIs with credentials from the Administration, provide an **API test** action (button or equivalent). You may alternatively validate credentials when saving settings; in both cases, show a clear status in the Administration and log failures to `/var/log/` or the database event log.
 
-## Commercial and external integrations
+Example implementation: [ShyimApiTest on GitHub](https://github.com/shyim/ShyimApiTest).
 
-If your extension integrates with external services and generates revenue (e.g., interfaces with downstream fees), a Shopware Technology Partner (STP) agreement may be required.
+### Shopping Experiences
 
-Commission-based integrations must report usage data according to the STP contract:
+CMS elements must ship with an element icon. After the extension is removed, Shopping Experiences must still work correctly in the Storefront.
 
-Every external technology extension needs to track its commission. Below is an example of implementing the tracking logic:
+### Themes
+
+Themes must include their own preview image.
+
+### Shopware Technology Partner reporting
+
+External technology extensions under an STP contract must report commission-related usage. Example payload for `POST /shopwarepartners/reports/technology`:
 
 ```json
- {
-      "identifier": "8e167662-6bbb-11eb-9439-0242ac130002",
-      "reportDate": "2005-08-15T15:52:01",
-      "instanceId": "alur24esfaw3ghk",
-      "shopwareVersion": "6.3.1",
-      "reportDataKeys": [
- {
-          "customer": 3
- },
- {
-          "turnover": 440
- }
- ]
- }
+{
+  "identifier": "8e167662-6bbb-11eb-9439-0242ac130002",
+  "reportDate": "2005-08-15T15:52:01",
+  "instanceId": "alur24esfaw3ghk",
+  "shopwareVersion": "6.7.0",
+  "reportDataKeys": [
+    { "customer": 3 },
+    { "turnover": 440 }
+  ]
+}
 ```
 
-`// POST /shopwarepartners/reports/technology` allows partners to send Shopware the info based on the STP contract.
+### Automatic code review (PHPStan and SonarQube)
 
-If you have any questions regarding the STP agreement, please contact our sales team at [alliances@shopware.com](mailto:alliances@shopware.com) or call **+44 (0) 203 095 2445 (UK) / 00 800 746 7626 0 (worldwide) / +49 (0) 25 55 / 928 85-0 (Germany)**.
+Current review configurations for uploads via the Shopware Account are published on GitHub: [store-plugin-codereview](https://github.com/shopwareLabs/store-plugin-codereview).
 
-**Progressive Web App:** If your app is Progressive Web App-compatible and you would like the PWA flag, please contact us at [alliances@shopware.com](mailto:alliances@shopware.com).
+### SonarQube blockers
 
-### External fonts and services
+The following patterns are blocked, among others: `die`, `exit`, `var_dump`.
 
-If external fonts (e.g., Google Fonts, Font Awesome) or other third-party services are used, this must be clearly stated in the store description.
+[List of SonarQube blockers](https://s3.eu-central-1.amazonaws.com/wiki-assets.shopware.com/1657519735/blocker.txt)
 
-If personal data is transferred, update your data protection information accordingly. A tooltip in the extension configuration is recommended to inform users.
+### Cypress end-to-end tests
 
-## Lighthouse A/B-Testing
+Cypress tests for Shopware 6 are maintained in the core repository; see [`src/Administration/Resources`](https://github.com/shopware/shopware/tree/trunk/src/Administration/Resources) and community projects such as Friends of Shopware for contributions.
 
-Run a [Google Lighthouse](https://developer.chrome.com/docs/lighthouse) audit before and after activating the extension.
+### Shopware CLI
 
-Significant regressions in performance, accessibility, best practices, or SEO are allowed. No new console errors may be introduced.
+<PageRef page="../../../products/cli/index" title="Shopware CLI" /> helps you build, validate, and upload Shopware 6 extensions and manage store descriptions and images efficiently.
 
-### schema.org/rich snippets A/B-testing checklist
+## Automatic code review errors
 
-A/B testing can ensure that structured data is valid and that rich results behave correctly across page types.
+For a consolidated list of frequent review findings, see <PageRef page="./store-review-errors" title="Common Store Review Errors" />.
 
-Use Scheme.org's [Schema Markup Validator](https://validator.schema.org/) and Google's [Rich Result Tester](https://search.google.com/test/rich-results) to check the homepage, categories, and product detail pages — including available products, unavailable products, products with no review, single review, reviews with varied ratings, out-of-stock products, products for future release, and/or any other product configuration and product types (including EAN, MPN, width, length, height, and weight). Also, check for duplicate entries and any new bugs.
+The following issues often appear in automated checks:
 
-## Tools
+### The required `composer.json` file was not found
 
-Use the [Shopware CLI](/development/tooling/cli) to build, validate, and upload Shopware 6 plugin releases to the Community Store. It also supports efficiently managing store descriptions and plugin images.
+**Cause:** Invalid or missing `composer.json`, a mismatch between the Store technical name and `composer.json`, or an incorrect ZIP layout.
 
-## Final notes
+The technical name must match `extra.shopware-plugin-class` and the bootstrap class namespace (case-sensitive). Many failures come from a wrong technical name, for example `Swag\MyPlugin\SwagMyPluginSW6` instead of `Swag\MyPlugin\SwagMyPlugin`.
 
-An extension may be rejected if:
+Example: [valid `composer.json`](https://github.com/FriendsOfShopware/FroshPlatformPerformance/blob/master/composer.json#L20).
 
-* It violates coding standards.
-* It introduces security issues.
-* It bundles unauthorized files.
-* It breaks storefront behavior.
-* It misrepresents functionality in the store description.
+### Cross-domain messaging
+
+When using `postMessage()` or similar APIs, validate `event.origin` and avoid wildcard targets. See also the [OWASP guide on web messaging](https://github.com/OWASP/wstg/blob/master/document/4-Web_Application_Security_Testing/11-Client-side_Testing/11-Testing_Web_Messaging.md).
+
+### No bootstrapping file found
+
+The bootstrap class cannot be resolved. Typical causes: wrong ZIP structure, typos, or case sensitivity in paths or the technical name.
+
+### Class `Shopware\Storefront\*` not found
+
+Declare required Shopware packages explicitly in `composer.json`, for example `"shopware/storefront": "~6.x.0"`, instead of unconstrained `*`.
+
+<PageRef page="../../plugins/apps/app-base-guide" title="App base guide" /> for meta information and packaging.
+
+### Cookies must be set securely
+
+Use secure cookie flags and register cookies in the Cookie Consent Manager where required.
+
+### `jsonEncode()` on an unknown class
+
+Shopware uses PHP's `json_encode()`; do not rely on non-standard wrappers.
+
+### Lock file out of date
+
+Run `composer update` locally so the lock matches `composer.json`. **Do not** ship `composer.lock` inside the extension archive; delete it before packaging.
+
+### `SnippetFileInterface` not found (Early Access)
+
+Wildcard requirements such as `"shopware/core": "*"` can resolve to Early Access builds where classes do not exist yet, which fails review.
+
+Pin compatible versions and stability, for example:
+
+```json
+{
+  "require": {
+    "shopware/core": "~6.1.0",
+    "shopware/storefront": "~6.1.0"
+  },
+  "minimum-stability": "RC"
+}
+```
 
-Ensure full compliance before submission to avoid publication delays.
+This pins a supported 6.1 line and prefers release candidates until the stable release is available.