Weave Code
Core Laravel Package
shopware/core
Shopware 6 Core is the PHP/Symfony foundation of the open-source Shopware e-commerce platform, providing the framework, data abstraction, and business logic to build scalable storefronts, APIs, and extensions.
Shopware platform is the core for all Shopware ecommerce products.
Frequently asked questions about Core
- Is shopware/core a Laravel package?
- No. shopware/core is the Symfony-based application core of Shopware 6, with its own DI container, DAL, plugin system, Store API and Admin API. It has no ServiceProvider, facade or Laravel contract binding, so it is not designed to be dropped into a Laravel application.
- Can I install shopware/core with Composer inside a Laravel project?
- You can add the Composer package, but co-installing it under one Laravel root is not a supported or safe pattern. Both frameworks overlap on symfony/* pins such as Console, HttpFoundation and Process, and they bring competing kernel bootstraps and global helpers. Even if dependency resolution succeeds, the runtime models do not compose. Run Shopware as a separate service instead.
- How do I integrate Shopware 6 with Laravel?
- The realistic approach is headless: deploy Shopware independently and consume it over HTTP. Use the Store API for catalog, cart and checkout, the Admin API for back-office operations, and webhooks for order and customer events. Laravel should own its existing domain data such as users, subscriptions and entitlements, while Shopware remains the system of record for catalog, orders and stock.
- Does shopware/core support Laravel 10 or Laravel 11?
- shopware/core does not declare or target Laravel versions because it is not a Laravel package. It is a Symfony application core with its own release train, and its version numbers follow Shopware 6.x rather than Laravel. Your Laravel version is therefore irrelevant to installing Shopware, but it matters for the HTTP client and queue code you write on the Laravel side.
- How do I call the Shopware Store API from Laravel?
- Treat Shopware as an external HTTP service and use Laravel's HTTP client with a configured base URL, credentials and timeouts. The Store API covers catalog, cart and checkout flows, while the Admin API covers back-office operations. Put the integration behind your own service classes or contract so your domain code does not depend directly on Shopware response shapes. Version and document that contract.
- Is shopware/core the main Shopware repository for issues and pull requests?
- No. shopware/core is a read-only subtree split generated from shopware/platform, so pull requests and issues belong upstream. The low star count and dependent count on this repo are not maturity signals; real community activity lives in the canonical repository. Confirm the canonical repo before setting up monitoring or upgrade processes.
- What infrastructure does Shopware 6 require alongside Laravel?
- Shopware needs MySQL or MariaDB, with Redis strongly recommended and a message queue such as RabbitMQ or the database transport for async work. At catalog scale it also needs OpenSearch or Elasticsearch. That is additional infrastructure your Laravel team may not currently operate, so plan for ownership and on-call before integration.
- How do Shopware upgrades work, and are minor versions breaking?
- Shopware uses minor version numbers for breaking releases, so moving from 6.4 to 6.5 or 6.5 to 6.6 is a migration project, not a patch. You also inherit two independent release trains, because Laravel and Shopware upgrade on their own cadences. Budget for Shopware migrations separately from Laravel upgrades.
- How do I handle Shopware webhooks and order events in Laravel?
- Use webhooks or a queue or event bridge to hydrate Laravel-side read models, and make consumers idempotent because deliveries can repeat. Keep Laravel as the system of record for data it already owns, and let Shopware remain authoritative for catalog, carts, orders and stock. Define that ownership boundary in writing before writing integration code. Avoid a shared database between the two systems.
- What are alternatives to embedding Shopware in a Laravel app?
- If the requirement is to add commerce primitives to an existing Laravel domain, a lighter Laravel-native cart and checkout may be a better fit. If the requirement is to sell at real catalog and fulfilment scale, integrate Shopware as a headless commerce service over its APIs. A Shopware plugin written in Shopware's Symfony bundle model is an option only when logic must live commerce-side. Do not attempt a shared Composer root or shared database.
Weaver
How can I help you explore Laravel packages today?