Weave Code
Shop Bundle Laravel Package
kitpages/shop-bundle
KitpagesShopBundle is a Symfony bundle for building e-commerce shops, providing product catalogs, shopping carts, checkout flows, and order management with configurable entities and templates.
This bundle is used to create a shop with symfony2
Frequently asked questions about Shop Bundle
- Can I install kitpages/shop-bundle in a Laravel application?
- No. KitpagesShopBundle is a Symfony2 bundle that registers through AppKernel and relies on the Symfony DI container, Doctrine ORM entities, annotations-based routing, and the Symfony EventDispatcher. Laravel has no bundle concept and uses service providers, Eloquent, and a different event abstraction, so there is no install-and-wire path. The only realistic option is reimplementing the domain model in Laravel.
- Which Laravel versions does kitpages/shop-bundle support?
- None. The package targets Symfony 2.x and PHP 5.x-era constraints, and its last release was 2015-07-06, long before Laravel 10 or 11 existed. Composer resolution against PHP 8.x and modern Laravel will conflict on its symfony/* requirements. There is no supported combination of this package and any current Laravel release.
- Is kitpages/shop-bundle still maintained?
- No. The last release was 2015-07-06, roughly a decade ago, with around 13 stars and zero dependents. The maintainer labeled it alpha, which implies an unstable and undocumented public API. There is no realistic security response capability, so anything built on it becomes a fork from day one.
- What does KitpagesShopBundle actually provide?
- It supplies reusable shop building blocks for a Symfony application: product and category management, a shopping cart, order handling with extensible entities, and bundle configuration and services for integration. It is intentionally not a complete standalone storefront and is meant to be extended alongside other Kitpages bundles. All of that is delivered through Symfony idioms, not Laravel ones.
- How do I add a cart and checkout to Laravel if I cannot use this bundle?
- Treat the bundle as a domain reference and rebuild the behavior in Laravel. Model Cart, CartLine, Order, OrderLine, Invoice, Shipment, and DiscountRule as Eloquent models, use explicit money value objects such as Brick\Money, wrap checkout in database transactions, and enforce unique constraints on invoice numbers. Before building from scratch, evaluate maintained headless options like Shopify, Medusa, or Saleor, or Laravel-native cart and order packages.
- What is the migration path from KitpagesShopBundle entities to Laravel Eloquent models?
- Do a short read-only spike: clone the repository and inspect the entities and services for cart, order, discount, and invoice semantics. Extract the design decisions, such as how discounts stack, how order states transition, and how invoices are numbered, into a design note, then reimplement them in Eloquent. Do not add the package to composer.json, since the code itself will not survive contact with Laravel.
- Does the bundle handle payments, tax, and shipping providers safely?
- That is unresolved and must be verified before any decision, because the overview does not name the hard-coded providers or whether any are still live. Cart, order, invoice, shipping, and discount logic is money math, so tax rounding, currency precision, discount stacking order, and invoice numbering uniqueness are audit-visible risks. You should also define the PCI and PII scope of the stored order and invoice data model, and never persist card data.
- Is kitpages/shop-bundle safe to use in production?
- No. It is abandoned, labeled alpha, has zero dependents and no visible CI or PHPUnit signal, and rests on Symfony 2.x, which reached end of life in November 2018. Financial bugs in cart and checkout code are audit-visible rather than cosmetic, and the lack of hardening plus no security response capability makes production use unacceptable. Treat it as a domain reference document, not a dependency.
- Can I run Symfony alongside Laravel to use this bundle?
- Not viably. Symfony 2.x cannot run safely on modern PHP, and a parallel runtime behind a shared database doubles your operational surface while splitting your event and ORM models. The Laravel and Symfony stacks share only the PHP language, with no shared container or routing contract. If you want Symfony shop idioms at all, choose a current Symfony stack such as Sylius rather than a decade-old bundle.
- What are the best alternatives to kitpages/shop-bundle for a Laravel shop?
- Pick a managed or headless platform like Shopify, Medusa, or Saleor if speed matters more than owning the domain. If you need the code in-house, use a maintained Laravel-native cart and order package, or build Eloquent models around money value objects and transactional checkout. Only extract design ideas from KitpagesShopBundle; do not depend on it.
Weaver
How can I help you explore Laravel packages today?