In short: Shopware 6.7.15 has two open, confirmed bugs: with SwagPayPal, a request to the PayPal merchant integration can fail with an HTTP 500 error, and extensions that read the currency from the sales channel context can crash. The 6.7.15.1 update from October 7 fixes neither of them, but it corrects the Rule Builder and the theme cache and adds a new guarantee notice at checkout. Many other fixes from this week are already merged but will most likely only ship with 6.7.16.0.

Information as of October 11, 2026. Every item links to the official sources on GitHub below.

New Shopware versions

  • 6.7.15.0 was released on October 1, 6.7.15.1 on October 7, 2026.
  • The 6.6 line received 6.6.10.28 (October 1) and 6.6.10.29 (October 7).

6.7.15.1 is a maintenance update. The release notes mark two fixes as critical:

  • Rule Builder: Since 6.7.14.0, most line item conditions only evaluated line items of type "product". Credits, custom line items and line items added by extensions were ignored, which could hide shipping methods or block promotions. All line items are evaluated again.
  • Theme files: After recompiling a theme, the previous theme directory was sometimes deleted right away. Pages served from an HTTP cache or CDN then referenced CSS and JS files that returned 404. Unused directories are now kept for at least 24 hours.

Everything else in 6.7.15.1 is covered in a separate article: Shopware 6.7.15.1: Legal Guarantee Notice at Checkout and Rule Builder Fixes.

Known bugs that are still open

  • PayPal (SwagPayPal): With 6.7.15.0 and SwagPayPal 10.8.4, a request to the PayPal merchant integration can fail with an HTTP 500 error because the PayPal SDK accesses an uninitialized property.
  • Currency in the sales channel context: Since 6.7.15.0, getSalesChannel()->getCurrency() returns null in the sales channel context. Extensions that rely on it can crash at checkout or elsewhere. The issue names, among others, the Lyra payment plugin, the Brevo newsletter plugin, Unzer and SwagPayPal. According to the issue, 6.7.15.0 and 6.7.15.1 are affected.
  • CMS drafts: Publishing a draft in Shopping Experiences fails when a section or block was deleted in the draft.
  • Registration page: One issue collects several flaws of the storefront registration page, including a privacy text that is shown even though its checkbox is disabled.
  • Social Shopping and Agentic Commerce: With both extensions installed, new Social Shopping sales channels cannot be created.

Fixed and already included in 6.7.15.1

  • Guarantee notice at checkout: The legal guarantee notice was only available via a link or modal. A new setting shows the complete notice directly below the terms and conditions at checkout.
  • Order confirmations during blue-green updates: During an update containing the migration for GARAN labels in mails, no order confirmations were sent. The labels are now passed as a template variable.
  • Custom line items are evaluated correctly in Rule Builder conditions again (see above).
  • Social Shopping sales channels can be created again. The error when saving due to the currency assignment is fixed.
  • Guarantee status of variants: Variants show the guarantee confirmation inherited from the parent product correctly in the Administration again.

Fixed, but not shipped yet

These fixes are already merged at Shopware but are not listed in the 6.7.15.1 release notes. They will most likely ship with 6.7.16.0:

  • E-invoicing: ZUGFeRD and XRechnung cancellation invoices with a discount were rejected by the validator.
  • Database migration: An update to 6.7 could fail on an index migration with certain MySQL versions.
  • S3 storage: asset:install --force could lose files on S3-compatible storage.
  • Document numbers: A document number is only allocated once the document is actually created.
  • Cookie banner: On touch devices, the banner reappeared on every page after choosing "Only technically required".
  • Media uploads: File names with umlauts or special characters are handled correctly.
  • Closeout for variants: An inherited change of the closeout setting now also updates the availability of the variants.
  • Shopping Experiences: The horizontal scrollbar on full-width sections (since 6.7.13.0) is gone.
  • Rule Builder: Stored values in conditions can be expanded and edited completely again.

Also fixed, but outside the Shopware core:

  • PayPal plugin: After a cancelled PayPal attempt and a switch to prepayment, the "paid" flow did not complete properly. The fix is in SwagPayPal and arrives with a plugin update.
  • Apple Pay: The issue about blocked Apple Pay payments with "Block transactions without 3D Secure" enabled was closed as completed.

Outlook on Shopware 6.7.16.0

The 6.7.16.0 milestone on GitHub is set for November 2, 2026. Dates can change. Two changes are already merged:

  • SEO help for categories: The SEO form shows the recommended length for the meta title (70 characters) and meta description (150 characters) and highlights when they are exceeded.
  • Document numbers: Invalid configurations are rejected before a number is allocated. Automatic number allocation moves from the Administration to the backend.

What should you do now?

  1. Before updating to 6.7.15.x: Do you use SwagPayPal or extensions that read the currency from the sales channel context? Then test the update on a staging system first, especially checkout and payment methods.
  2. Already on 6.7.15.x: Check checkout, PayPal and newsletter sending for errors and ask the plugin vendor for an update if something breaks.
  3. Install 6.7.15.1 if you use Rule Builder conditions for shipping or promotions or run your store behind an HTTP cache or CDN.
  4. Guarantee notice: Check with your legal advisor whether you should show the complete notice at checkout, then enable it in the cart settings.
  5. E-invoices and media with umlauts: Only 6.7.16.0 helps here. Until then, keep an eye on cancellation invoices with discounts and uploads with special characters.

Small, regular updates are safer than one big version jump. I explain why in Shopware Maintenance 2026. If you would rather not do it yourself: I take care of maintaining your Shopware store.

Sources

Releases

Open bugs

Fixed

Outlook

Tags:

Shopware Shopware 6 Shopware News Update