Weave Code
Customer Bundle Laravel Package
sylius/customer-bundle
Sylius Customer Bundle provides customer management for Sylius e-commerce apps, including customer models, repositories, managers, address handling, profile forms, and integration with users and orders. It offers reusable services and UI components for creating, editing, and resolving customers.
[READ-ONLY] Customers management bundle for Symfony.
Frequently asked questions about Customer Bundle
- Is sylius/customer-bundle a Laravel package?
- No. sylius/customer-bundle is a Symfony/Sylius bundle distributed as a read-only subtree split of the Sylius monorepo, and it has no Laravel runtime integration. For Laravel, treat it as a domain reference rather than a Composer dependency.
- Can I install sylius/customer-bundle in Laravel with Composer?
- You can technically add the Composer package, but it will not work as a Laravel customer management solution. It depends on Symfony's kernel, DI container, Doctrine ORM, Sylius ResourceBundle, and the Sylius registry, so adopting it effectively means adopting Sylius. Composer require alone is not a valid integration plan for Laravel.
- What does Sylius Customer Bundle actually provide?
- It provides customer models, repositories, managers, address handling, profile forms, and customer group support for Sylius e-commerce applications. It also integrates customers with shop users and orders. Most value for Laravel teams is in its clean customer versus user domain split.
- Which Laravel versions support sylius/customer-bundle?
- None. The package targets Symfony and Sylius release lines, and its PHP and Symfony version support is dictated by the Sylius release you use. Laravel 9, 10, 11, and later are not supported as runtime environments. You would need to re-implement the domain model in Laravel.
- How do I port Sylius Customer Bundle to Laravel Eloquent?
- Start by extracting schema and semantics from the Doctrine mappings: customers, addresses, customer groups, and the shop-user link. Rebuild them as Eloquent models and migrations with explicit foreign keys and indexes on email, group, and customer_id. Reproduce validation as FormRequests and policies, and preserve the Customer/User split.
- Should I keep Customer and User separate in Laravel?
- Yes, if you need guest checkout, pre-registration customer records, or guest-to-registered cart merges. Sylius separates Customer identity and addresses from ShopUser credentials and roles, which maps cleanly onto Eloquent models plus Laravel guards. Collapsing them too early makes those flows harder to support.
- Does sylius/customer-bundle work with Symfony 5.4 or 6.x?
- It works natively within supported Sylius release lines on Symfony 5.4/6.x, arriving transitively through sylius/sylius. There is no meaningful standalone integration path; version alignment with Sylius is mandatory. For a Laravel product, this Symfony compatibility is not useful at runtime.
- Why is sylius/customer-bundle read-only and low stars?
- The repository is a read-only subtree split of the Sylius monorepo, so defects must be fixed upstream or carried in a fork. Low stars and dependents reflect that distribution model, not package quality. Adoption should be measured through sylius/sylius rather than this split repository.
- What are Laravel alternatives to Sylius Customer Bundle?
- There is no direct Laravel equivalent package that mirrors this Sylius bundle. Typical Laravel options are Laravel's own authentication and guards plus custom Eloquent models, or commerce platforms such as Lunar or Bagisto depending on requirements. Use Sylius as a reference for customer groups, addresses, and identity semantics.
- What customer features justify porting Sylius Customer Bundle to Laravel?
- Port only when requirements genuinely need customer groups, multiple addresses with default billing and shipping, B2B pricing hooks, guest-to-customer merge, or GDPR anonymization. Each adds schema and policy complexity, so avoid porting the whole bundle by default. Derive behavior from Sylius form types, validators, and state machines rather than copying code.
Weaver
How can I help you explore Laravel packages today?