Shopware 6 Extension Decision Guide: Plugin or App?
A decision guide for Shopware 6 extensions: when a plugin beats an app, when cloud hosting decides for you, and how to validate either choice on staging.
Loading…
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
A decision guide for Shopware 6 extensions: when a plugin beats an app, when cloud hosting decides for you, and how to validate either choice on staging.
Marketing needs a cart-value discount tomorrow without a code deploy. Shopware 6 Rule Builder lets you model conditions and actions declaratively, with clear trade-offs around performance and custom logic.
Learn how to design efficient Shopware Rule Builder rules for pricing, avoid performance pitfalls, and verify results with concrete examples.
Learn how to diagnose and fix 'Allowed memory size exhausted' errors in Shopware 6 during DAL indexing and plugin updates using memory limits and batch size tuning.
Guide on choosing between Shopware 6 Custom Fields and Entity Extensions for product data. Learn when to use JSON-based attributes versus relational database extensions.
Learn how to implement server‑side pagination in Shopware 6 using the Store API to prevent over-fetching and optimize headless commerce performance.
Diagnosing intermittent connection pool exhaustion The goal is to determine why a Shopware 6 installation occasionally fails with 502/503 errors under high load, suspected to be caused by Doctrine DBAL’s limited connection pool. Key constraints: Default pool size is 5 connections per connection type. Persistent connections are disabled by default but can be
Goal On Shopware 6, I want to use a single Rule Builder rule (for example, cart value above a threshold combined with a customer group) to control shipping and payment method availability at checkout, while making sure the same rule does not implicitly change what anonymous visitors can see in the catalog. Constraint and uncertainty Rules are shared entities