Weave Code
B2B Suite Laravel Package
bagisto/b2b-suite
B2B Suite for Bagisto brings wholesale and business-to-business capabilities to Laravel storefronts, adding company accounts, customer groups, tier pricing, and quote management so merchants can serve business buyers from a single platform without custom development.
Bagisto B2B Suite extends the Bagisto e-commerce platform with business-to-business capabilities for Laravel merchants. It enables company accounts, multiple buyer sub-users, and granular role-based permissions, so purchasing teams can collaborate without sharing credentials.
- Company profiles with sub-user management
- Role-based permissions for buyers, managers, and admins
- Requisition lists for repeat and bulk purchasing
- Quick order flows for faster reordering
- Laravel-native, extensible Bagisto integration
Frequently asked questions about B2B Suite
- How do I install bagisto/b2b-suite in a Laravel Bagisto application?
- Install with composer require bagisto/b2b-suite, then register the B2BSuite service provider in bootstrap/providers.php after the Bagisto Shop provider. Package auto-discovery is intentionally disabled and must stay that way, because discovery loads the provider too early and breaks the package. Finish with php artisan b2b-suite:install. Prebuilt Tailwind assets ship with the package, so a stock install does not require npm run build.
- Which Bagisto, Laravel and PHP versions does b2b-suite support?
- The current suite targets Bagisto 2.5 with Laravel 13, PHP ^8.4 and Tailwind 4. Suite 2.0 sits on a maintenance branch and targets Bagisto 2.4 with Laravel 12 and PHP 8.3. If your estate is not already on PHP 8.4, treat this as an infrastructure upgrade rather than a composer require. Suite majors do not track Bagisto majors, so pin versions deliberately.
- Why is package auto-discovery disabled for Bagisto B2B Suite?
- Laravel auto-discovery would register the B2BSuite provider before the Bagisto Shop provider, and the package depends on core bindings being available first. That is why the provider must be added manually to bootstrap/providers.php after Shop. Leave discovery disabled even after upgrades; re-enabling it is a common cause of a broken boot. The same ordering constraint applies in any custom provider you add on top.
- Will b2b-suite affect my non-B2B storefront and anonymous shoppers?
- Yes, potentially. The company catalog swaps the core ProductRepository, so every product query in the storefront flows through B2B logic, including for anonymous and non-company shoppers. QA and on-call scope must therefore include non-B2B traffic, and you should not triage incidents as B2B-only. Plan regression tests for catalog, search and pricing on the guest path before going live.
- How do I upgrade b2b-suite without overwriting my customized vendor views?
- Views are published into resources/views/vendor/<namespace>, and republishing is file-level and silent, so the last publish wins. Before customizing a single Blade file, confirm whether b2b-suite:install has an idempotent upgrade path; that is the biggest unknown in the package. Keep your overrides in version control and diff the published tree after every suite upgrade. Where possible, extend via view_render_event listeners rather than editing published templates.
- Does Bagisto B2B Suite include purchase order approvals and spend limits?
- The package appears to expose purchasing mechanics, not approval policy. Multi-level approval thresholds, spend limits and escalation rules look like something you own rather than something shipped out of the box. Treat approvals as a state machine whose rules you implement, and validate this against the source before committing to a design. The docs are not explicit, so read the code.
- Is the RBAC storefront-only, and can permissions map to IdP or SSO groups?
- The suite provides role-based permissions for buyer sub-users with roles such as buyer, manager and admin, which is clearly storefront-scoped company account RBAC. Whether it extends to Bagisto admin scope, and whether permissions can be mapped to IdP groups, is not evidenced in the documentation. If SSO-driven provisioning is a requirement, verify the user and role models in the source early. This answer changes your identity integration design, so resolve it before building.
- Are B2B features such as company accounts, quotes and requisition lists available through Bagisto APIs?
- It is unclear from the documentation whether B2B capabilities are exposed through Bagisto's APIs or only through storefront views. That single answer decides whether B2B is a channel feature or a platform feature for your architecture, so verify it before designing headless or ERP integrations. If the capabilities are view-only, budget for custom API work. Check the package routes and controllers to confirm.
- How do I test B2B screens in CI and avoid runtime 500 errors?
- Vue @event names that collide with Blade directives produce broken compiled PHP that 500s at request time, while php artisan view:cache still reports success. Add a CI view-lint step and render B2B screens in a browser-based test so the failure surfaces in the pipeline rather than in production. Assert HTTP 200 on company account, requisition list and quick order pages. Do not rely on view:cache as a correctness check.
- Who maintains bagisto/b2b-suite and what support is available?
- The package is maintained under the Webkul namespace with a low public profile, roughly 27 GitHub stars and no dependents, so there is no Stack Overflow corpus and troubleshooting means reading the source. Commercial support from the vendor is the realistic mitigation and should be priced into the business case. Budget for a fork-and-own contingency if the package is mission critical. Plan for version lockstep risk, since a Laravel or PHP security patch can force a suite upgrade ahead of maintainer readiness.
Weaver
How can I help you explore Laravel packages today?