Using Shopware 6 Rule Builder for Dynamic Discounts Without Writing Code
Learn how to use Shopware 6’s Rule Builder to create dynamic discounts and promotions without writing code, with a concrete example, performance considerations, and next steps.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to use Shopware 6’s Rule Builder to create dynamic discounts and promotions without writing code, with a concrete example, performance considerations, and next steps.
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.
Learn how to filter and paginate Shopware 6 product listings using Doctrine Criteria, with a concrete example, version notes, and verification steps.
Deployment State Consistency In Shopware 6, the deployment process involves a sequence of Symfony kernel cache warming and the compilation of Storefront and Administration assets. Because bin/console cache:warmup is not an atomic operation, a failure during this phase can result in a hybrid state where the var/cache directory contains a mixture of legacy and
Category import after upgrading to Shopware 6.5 A custom importer that synchronizes categories from an external PIM into Shopware was built against the pre-6.5 Category API, where each category response contained a nested children array. After the planned upgrade to Shopware 6.5, the API is documented to return a flattened tree structure instead, so the exis
Shopware Messenger: Uncertain behavior of message cancellations on worker shutdown When a Shopware worker exceeds its configured process timeout, the framework does not issue a cancellation signal to any ongoing database transaction. The message simply remains unacknowledged and is scheduled for a retry according to the configured redelivery limit. After the
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 Determine the most effective caching strategy for a production Shopware 6 storefront, balancing performance, invalidation accuracy, and deployment complexity. Constraints Shopware’s built‑in reverse proxy uses tag‑based invalidation that may be limited by tag cardinality and the timing of Administration updates. External Varnish or CDN solutions require