Weave Code
Assortment Bundle Laravel Package
sylius/assortment-bundle
Sylius Assortment Bundle delivers the product catalog domain for Sylius e-commerce, modeling products, variants, options, and taxonomy with Doctrine and Symfony integration. It lets teams build flexible, variant-aware assortments and manage catalog data for online stores and sales channels.
Manage products, their variants, properties and options in your Symfony2 application.
Frequently asked questions about Assortment Bundle
- What does sylius/assortment-bundle do?
- It is the product catalog domain bundle from Sylius, built for Symfony 2. It models products, product variants, options and option values, properties, and taxonomy using Doctrine ORM mappings and Symfony dependency injection. In practice it is a reference for the canonical Sylius product model, not a library you can drop into another framework.
- Can I use sylius/assortment-bundle in a Laravel application?
- No. sylius/assortment-bundle is a Symfony 2 bundle: it extends Symfony\Component\HttpKernel\Bundle\Bundle and relies on a DI extension, compiler passes, and Symfony 2-era Doctrine mappings. Laravel's service provider and container model has no bridge to that contract, so any integration would be a rewrite wearing the package namespace.
- Which Laravel and PHP versions support sylius/assortment-bundle?
- None. The package predates Laravel's modern support matrix and targets PHP 5.x with Symfony 2 components and old Doctrine ORM/DBAL versions. Composer resolution against Laravel 10 or 11 on PHP 8.2+ will fail on PHP, Doctrine, and transitive Symfony constraints. It only ever loaded in a legacy Symfony 2.8 application, which reached end of life in 2018.
- Why does Composer fail when installing sylius/assortment-bundle in a Laravel project?
- Composer fails because the package's constraints pull in Symfony 2 components, old Doctrine ORM/DBAL releases, and a PHP version range that excludes 8.2+. It also uses PSR-0 autoloading, which does not resolve cleanly under modern Composer setups. This is not a fixable flag issue; the dependency graph is end-of-life end to end.
- Is sylius/assortment-bundle still maintained?
- No. The repository is archived, has roughly 20 stars, zero dependents, and no active upstream maintainer or security response process. There are no dependency bumps, bug fixes, or PHP-version compatibility work. Any fork becomes a long-lived internal artifact with full ownership.
- Is it safe to run sylius/assortment-bundle in production?
- No. Running EOL PHP 5.x-era code in a modern estate means unpatchable CVEs, fatal errors on PHP 8 upgrades, and Doctrine DBAL API removals. You would also own every fix with no ability to rebase on upstream. Treat production use as unsafe.
- What Laravel packages are alternatives for product variants and options?
- For Laravel, evaluate maintained commerce packages such as Lunar PHP, Aimeos Laravel, or Bagisto when catalog needs extend into pricing, carts, and checkout. If you only need products, variants, options, and properties, reimplementing the model natively in Eloquent is usually the smallest, most durable path. Do not adopt sylius/assortment-bundle as the runtime dependency.
- Can I reuse the Sylius product data model in Laravel?
- Yes, as a reference spec rather than code. The durable asset is the domain design: Product to ProductVariant, ProductOption and ProductOptionValue with a variant-option join, and ProductProperty plus ProductPropertyValue for non-variant attributes. That vocabulary became the canonical Sylius product model and is a good conceptual starting point for native Eloquent models.
- How would I migrate a Sylius Assortment catalog to Laravel?
- There is no incremental migration path; plan a greenfield implementation. Extract the entity relationships and cardinalities into a written domain spec, review the schema against real query patterns, then run a timeboxed spike with Eloquent models and a variant/option query. Use that spike as the baseline for a build-versus-buy decision against maintained Laravel commerce packages.
- Does sylius/assortment-bundle support multi-channel, multi-currency, or per-variant inventory?
- The original bundle focuses on catalog modeling, not the full channel, pricing, and inventory behavior of later Sylius versions. Multi-channel, multi-currency, and per-variant inventory semantics should be treated as out of scope for this package. Confirm those requirements explicitly before deciding between a native Eloquent design and a maintained Laravel commerce package.
Weaver
How can I help you explore Laravel packages today?