Weave Code
Storefront Laravel Package
shopware/storefront
The Shopware Storefront package provides the customer-facing web frontend for Shopware 6, with Twig templates, theme assets, routing, and controllers for product, category, checkout, and account pages, enabling extensible responsive storefront experiences.
Storefront for Shopware
Frequently asked questions about Storefront
- Can I install shopware/storefront in a Laravel application?
- No. shopware/storefront is the Symfony-based Shopware 6 storefront bundle, not a Laravel package; it has no service provider, Blade integration, or Laravel facade and assumes Shopware's DI container, plugin/theme system, and shopware/core. Installing it in a Laravel app yields no usable surface. For Laravel, integrate with Shopware through the Store API or Admin API instead.
- What is shopware/storefront used for?
- It provides the customer-facing web frontend for Shopware 6: Twig templates, SCSS/Bootstrap 5 theme assets, routing, and controllers for product, category, checkout, and account pages. It also supports theme inheritance and ESI/HTTP-cache hooks. It is the default storefront bundle in a Shopware 6 deployment, not a standalone library.
- Does shopware/storefront support Laravel 10 or Laravel 11?
- No. The package does not target Laravel versions at all; its compatibility is with PHP 8.1+, Symfony 6/7, Twig, and the exact matching shopware/core version. Laravel 10 or 11 support is not a meaningful question for this bundle. Do not add it to a Laravel composer.json expecting framework integration.
- How do I install shopware/storefront?
- You do not install it standalone in Laravel. In a Shopware 6 project it arrives through shopware/core or the shopware/platform monorepo, and you should pin it to the exact core version rather than floating it independently. For Laravel, install an API client instead and consume Shopware remotely.
- Can I use Shopware 6 as a headless backend for Laravel?
- Yes. Run Shopware 6 as the commerce backend and use the Store API for catalog, cart, and checkout flows plus the Admin API for entity sync and order export. Laravel can act as a BFF or integration layer for auth, ERP/OMS sync, and custom tooling. In a headless topology shopware/storefront is not deployed at all.
- How do I customize the Shopware storefront theme from Laravel?
- Do not customize the storefront from Laravel; theme and plugin work happens inside Shopware 6 using Twig block inheritance, apps/plugins, and asset compilation. If Laravel must own presentation, build a headless frontend over the Store API and leave this bundle out of the stack. Forking the bundle creates upgrade coupling with shopware/core.
- What are alternatives to shopware/storefront for Laravel ecommerce?
- For Laravel-native commerce, evaluate Lunar, Aimeos, Bagisto, or a custom build. For headless Shopware, use Nuxt, Vue, React, or Laravel with Inertia consuming the Store API. Moving from a Laravel commerce package to Shopware is a replatform, not a Composer package swap.
- How do I test a Laravel integration with Shopware storefront?
- You should not test this bundle from Laravel. Test Shopware-side behavior with Shopware's own test tooling, and contract-test your Laravel API client against Store API and Admin API responses using HTTP fakes or mocks. Keep schema expectations pinned to the Shopware version you deploy.
- What are production risks of depending on shopware/storefront?
- The main risk is hard version lockstep with shopware/core; the bundle has no independent semver, so a core update without a matching storefront can break. Minor Shopware upgrades routinely change Twig blocks, theme inheritance, and asset compilation. Pin exact versions, budget regression testing per minor release, and route bugs to shopware/platform. Cache and ESI configuration also need production review.
- Who maintains shopware/storefront and where do I report bugs?
- Shopware maintains it as a monorepo split from shopware/platform, so bugs and pull requests belong in shopware/platform rather than this repository. Support follows the Shopware 6 lifecycle, and low standalone star or dependent counts are expected because nobody consumes it independently. Confirm commercial edition, trademark, and CLA details with legal before committing.
Weaver
How can I help you explore Laravel packages today?