Shopware has released core update 6.7.14.0. It brings new EU information requirements in the checkout (from 27.09.2026), extended language management for community translations and the deprecation of the Symfony XML configuration, which will be removed in Shopware 6.8. We put the changes into context, name the roles affected and recommend next steps.
For operators of German and international shops, and for plugin developers, this means decisions are due straight away.
What specific changes does update 6.7.14.0 bring for shop operators?
Update 6.7.14.0 introduces native notices and labels for new EU information requirements in the ordering process, improves the handling of multi-word product searches and extends the order status history, including a new flow for failed payments. Checkout, search and automation all change directly as a result.
Technically, this means notices covering the EU information requirements are available in the ordering process by default, so operators have less to implement themselves. Search handles multi-word queries differently, which can affect product rankings and findability. The extended order status history improves audit trails and traceability. Shopware also ships a new standard flow for failed payments, including a Flow Builder template and an email template, which standardises how payment failures are handled.
For you as a shop operator, this means: check how the new EU notices appear in the checkout before going live, and make sure your texts, labels and legal information are complete and correct. Details are in the manufacturer’s announcement: Shopware 6 Release News September 2026.
Who needs to act on the new EU information requirements, and by when?
Every shop operator selling physical goods to consumers in the EU has to observe the new notices in the ordering process. Shopware provides native support from 27.09.2026, which you should still review and adapt editorially where needed.
Shopware provides the technical means to display this mandatory information. You remain responsible for the content being correct. The requirement applies from 27.09.2026. In practice: review product texts, shipping information, recycling or disposal notes and details of physical product properties, and add any missing information to the product master data or the checkout texts.
If you run several country shops, you need to take multilingual content and regional differences into account. The revised language management helps here (see the next section). For legal questions and the accuracy of the texts, consult a legal adviser; the platform only supplies the technical basis.
What does the revised language management mean for multilingual shops?
Under Settings → Languages, more than 40 community translations can now be managed and updated directly, with no shell access and no extra plugins. This simplifies the ongoing maintenance of multilingual shops.
Translations can be maintained centrally, which saves work above all for shops with many language variants. You can install or update community translations directly, without a developer or the server console. You do, however, need to review the quality of community translations editorially. Automatically installed translations are an aid; they are neither legally binding nor guaranteed to be free of errors.
If you regularly adjust localisations or marketing copy, the new management can speed up your workflow.
What steps should developers plan because of the Symfony XML deprecation?
The Symfony XML configuration for services, routes and packages is marked as deprecated and will be removed in Shopware 6.8. Plugin developers should therefore switch to PHP or YAML configuration soon.
Plugins that currently use XML for service definitions, routes or package registration will no longer work without changes once it is removed in Shopware 6.8. Migrating means recreating service definitions in PHP (service provider pattern) or YAML and checking autowiring and autoconfigure. Allow time for code changes, testing and, where needed, adjustments to CI/CD scripts. Also check whether third-party plugins already offer compatible versions. Otherwise you will have to update or replace those plugins.
For development teams we recommend this order: list all plugins with XML configuration, prioritise them by criticality, migrate them in separate branches, test automatically and roll out via staging. As Shopware 6.8 carries out the removal, your roadmap should plan for this window.
How do the changes to product search, order history and payment flows affect day-to-day shop operations?
The adjusted handling of multi-word search queries can affect findability and conversion. The extended order status history and the new standard flow for failed payments affect reporting and automation. Testing is therefore essential.
Multi-word search queries: with the changed search logic, ranking and result lists for combined terms may turn out differently. Check your search statistics, test the phrases your customers typically search for and adjust synonyms or boosting rules.
Order status history: the additional entries make returns, complaints and compliance requirements easier to trace. You may need to adapt data exports and reporting scripts.
Payment flow: the new standard flow for failed payments comes with a Flow Builder template and an email template. This makes consistent notifications easier, but you should check the wording, timing and trigger conditions yourself.
Our recommendation: before rolling the update out to production, set up test scenarios in a staging environment for search (A/B tests), order history (spot checks and data validation) and the payment flow (simulated payment failure, email sequence).
What options do you have now, and which do we recommend for which case?
You can update immediately, test the update in staging first or adopt only individual modules. The right option depends on the size of your shop, your multi-shop configuration and your plugin set.
Option 1, direct update (for small shops with few plugins): with a manageable number of plugins and no custom checkout logic, a quick update is possible. Backups, tests and a rollback plan are still mandatory.
Option 2, staging first (recommended for medium-sized and large shops): install 6.7.14.0 in staging and thoroughly test the EU notices, search, payment flow and language management. Check your third-party plugins as well.
Option 3, gradual adoption (for complex integrations): use feature toggles or adopt only individual components at first. Migrating the XML configurations remains a priority task for the developers.
If time and resources are tight, start by checking the EU notices and taking stock of the Symfony XML configurations. If compliance is the priority, the checkout review comes first. If internationalisation matters, make active use of the new language management.
Frequently asked questions
Do I have to install the update immediately to stay compliant?
No. Shopware provides technical support for the EU notices, but legal responsibility for correct content lies with the shop operator. Install the update in staging, review the texts and only go live once the content is complete and has been legally checked.
How do I identify plugins that still use XML configuration?
Search the plugin code for XML files in the resource directories (for example services.xml or routes.xml). A list of all installed plugins with their release notes helps you prioritise. Plan to migrate all affected plugins before Shopware 6.8.
Does the new language management automatically improve translation quality?
No. It makes installing and updating community translations easier, but it does not replace editorial review. Treat community translations as an aid and check legal or promotional texts before publishing them.
Will the change to product search affect my SEO rankings?
An effect on SEO is possible, because on-site search generates user signals. After the update, monitor your search metrics and organic conversions, and optimise search synonyms, product titles and metadata where needed.
Conclusion
If you run a small, standardised shop, you can install the update promptly and check the EU notices and payment templates along the way. For medium-sized and large shops, or shops with many custom plugins, we recommend staging tests first and a prioritised migration of the Symfony XML configurations to PHP or YAML. Draw up a plugin list, test search and payment flows systematically and have all legal notices reviewed editorially. If compliance or multilingual content is especially important to you, bring forward the tests of the checkout and language management.
A sensible next step is a test checklist (EU notices, checkout labels, search, payment flow, plugin XML configuration) with a fixed timeframe for the migrations. You will find more articles on updates and technology in our Shopware knowledge section.
Planning something similar?
Tell us briefly about your system and your goal. We will get back to you with questions or a proposal.
Request a project