Weave Code
Shop Bundle Laravel Package
enhavo/shop-bundle
Enhavo Shop Bundle adds e-commerce functionality to the Enhavo CMS, an open-source PHP content management system built on Symfony and Sylius components. Distributed as a subtree split of the main Enhavo repository, it helps build flexible, complex data-driven shops with a clean, usable interface.
[READ-ONLY] EnhavoShopBundle
Frequently asked questions about Shop Bundle
- Is enhavo/shop-bundle a Laravel package?
- No. It is a Symfony bundle and a read-only subtree split of the Enhavo CMS monorepo, built on the Symfony fullstack framework with Sylius components. It has no Laravel service provider, no package auto-discovery, and no publishable config/shop.php. It is registered inside a Symfony kernel via bundles.php and bootstrapped by Enhavo's application scaffolding.
- How do I install enhavo/shop-bundle?
- If you already run an Enhavo application, install it through Composer and register the bundle in your Symfony config/bundles.php. Because this repository is a subtree split, the recommended approach is to consume the shop bundle from the main enhavo/enhavo repository via a VCS or path repository so issues, changelogs, tests, and pull requests stay in one place. Plan the installation together with the Enhavo core bundles it depends on rather than as a standalone drop-in.
- Does the Enhavo shop bundle work in a Laravel application?
- Effectively no. Adopting it in Laravel amounts to a rewrite, because you would have to reimplement Enhavo's resource, CRUD, and routing abstractions plus the Sylius component wiring inside Laravel's container. Container, ORM, and templating assumptions all conflict at once. For a dependency with no community traction, that is not a realistic integration path.
- Which PHP, Symfony and Sylius versions does the shop bundle require?
- There is no published version matrix beyond the bundle's own composer.json, so read its constraints before anything else. Check the PHP major, the Symfony major, the Sylius component majors, and the Doctrine ORM/DBAL ranges, and confirm none of them are already end-of-life. Sylius components have historically shipped breaking changes between majors, so pin versions deliberately and review every upgrade.
- How is the shop bundle configured?
- Configuration happens through Symfony bundle configuration in your config/packages files, on top of the Enhavo application scaffolding. There is no Laravel-style config publishing step and no .env-driven installer. Expect to configure the bundle graph, resource definitions, and commerce services rather than a single flat config file.
- Can I use it in a Symfony app that does not use Enhavo?
- Feasibility is low. The bundle assumes Enhavo core bundles for resource, routing, block, media, and user/permission handling, and it also assumes Sylius commerce primitives for product, order, pricing, and cart or checkout. You effectively inherit the whole Enhavo graph whether or not you want the CMS. It is not a composable, take-only-what-you-need library.
- How should I test or evaluate the shop bundle before using it in production?
- Do an internal spike in a staging Symfony or Enhavo application rather than evaluating it inside a Laravel codebase. Confirm whether the bundle compiles and runs standalone or hard-requires Enhavo core bundles at container compile time, and check whether it ships migrations, fixtures, and admin UI or domain logic only. Run your own smoke tests across cart, order, and pricing flows, because that is where the money risk sits.
- Is enhavo/shop-bundle actively maintained and where do I report issues?
- The split has no stars and no dependents, so there is no observable third-party production usage to lean on, and maintenance is single-vendor. Check the main enhavo/enhavo repository for releases in the last 6 to 12 months and for a supported upgrade path across Enhavo majors. Report bugs and open pull requests upstream in the main repository, since this split's own issue tracker is a dead end.
- Who handles cart, checkout, and order persistence in this bundle?
- Commerce primitives come from Sylius components, but you must verify whether order and checkout persistence is Sylius proper or a local reimplementation inside Enhavo. Also determine which parent release tag the split HEAD corresponds to and how far behind it is. For code that touches carts, orders, and pricing, confirm this before making any commitment.
- What should I use instead of the Enhavo shop bundle in a Laravel project?
- Do not plan a migration to this package from a Laravel codebase. Choose a Laravel-native commerce package or a headless commerce service such as Medusa, Saleor, or Shopify headless instead. The cost of bridging Symfony, Doctrine, and Twig into Laravel dwarfs any value you would get from this bundle.
Weaver
How can I help you explore Laravel packages today?