Weave Code
Channel Bundle Laravel Package
sylius/channel-bundle
Sylius Channel Bundle adds channel management to Sylius e-commerce applications, letting you define multiple sales channels with their own currencies, locales, tax and shipping settings, and manage them through the admin panel for multi-channel storefronts.
[READ-ONLY] Sylius multichannel component integration.
Frequently asked questions about Channel Bundle
- Does sylius/channel-bundle work with Laravel?
- No. It is the Symfony dependency-injection and admin UI integration layer for Sylius's Channel domain object and requires the Symfony kernel, Doctrine ORM, Twig, and Sylius Resource/Registry abstractions. There is no Laravel service provider, facade, Eloquent model, or Blade view, so installing it in a Laravel app pulls a large unused Symfony/Doctrine tree. For Laravel, treat it as reference material for channel semantics, not as a Composer dependency.
- How do I install sylius/channel-bundle?
- In a Sylius application you normally do not require it directly. It arrives transitively through sylius/sylius, and integration is configuration and admin-UI enablement rather than standalone installation. Pin sylius/sylius and let the monorepo split resolve the bundle. Direct Composer installation outside Sylius is not a supported path.
- What is a channel in Sylius and what can it control?
- A Sylius channel is a sales channel that carries its own currencies, locales, tax zones, payment and shipping methods, catalog visibility, and price lists. The bundle provides the Symfony DI and admin UI integration for managing those channel records. It builds on Sylius's Resource and Registry abstractions and Doctrine ORM persistence. Multi-channel storefronts use these settings to partition carts, orders, pricing, and presentation.
- Is sylius/channel-bundle a standalone package I can use in any PHP project?
- No. It is a read-only monorepo split from Sylius and depends on the Symfony kernel, DI container, Form and Validator components, Twig, Doctrine ORM, and Sylius Resource/Registry. It has no publishable config, no service provider, and no framework-agnostic entry point. Its runtime value only exists inside a booted Sylius application.
- What Laravel versions are supported by sylius/channel-bundle?
- None. The package targets Symfony and Sylius, not Laravel, so Laravel version compatibility does not apply. There is no Illuminate support package, no facade, and no Eloquent integration. If you need multichannel behavior in Laravel, reimplement the channel model or integrate with Sylius over an API or message boundary.
- How do I test a Sylius channel setup?
- Test inside the Sylius application, where the bundle is already wired through the container. Cover channel resolution by hostname or request context, per-channel locale and currency defaults, and channel-scoped pricing, catalog visibility, cart, and order partitioning. Use Sylius fixtures and the admin UI for provisioning scenarios. There is no standalone test harness for this repository outside Sylius.
- Can I use sylius/channel-bundle to build a multi-storefront Laravel application?
- You can use it as a reference implementation of multichannel semantics, but not as an installed dependency. The transferable concepts are channel resolution by hostname or request context, per-channel default locale and currency, channel-scoped pricing and catalog visibility, channel-aware carts and orders, and per-channel payment and shipping assignment. A bridge with an embedded Symfony kernel and dual ORM is technically possible but economically indefensible for a component this size. Prefer a native Laravel implementation or an API-level integration with a running Sylius instance.
- Is sylius/channel-bundle maintained and safe for production?
- In a Sylius application, code risk is low: it is versioned in lockstep with the platform, has no third-party surface, and is MIT licensed. The practical risks are discoverability and support, because this read-only split has no issue tracker or standalone documentation and every route leads back to the Sylius monorepo and docs. The low star and dependent counts reflect the monorepo split design, not code quality. Production safety depends on your Sylius version pin and upgrade process.
- What are alternatives to sylius/channel-bundle for multichannel commerce in Laravel?
- For Laravel, consider native multichannel modeling in your own domain layer, or integrating with Sylius or another commerce platform through APIs and messages. Do not look for a Laravel port of this bundle; none exists and the package has no framework-agnostic core. If you stay on Sylius, the bundle is the first-party path and should arrive transitively through sylius/sylius. Evaluate alternatives by where channel, assortment, and price data are mastered.
- Why does sylius/channel-bundle have so few stars and dependents?
- It is a read-only monorepo split from Sylius, so direct Composer-level consumption is near zero by design. Popularity metrics do not measure quality here; the real signal is demand for multichannel commerce capability in PHP. The 45.27 opportunity score reflects ecosystem demand, not demand for this artifact. Judge the package by your platform fit, not by its star count.
Weaver
How can I help you explore Laravel packages today?