Weave Code
Ecommerce Admin Livewire Laravel Package
artisanpack-ui/ecommerce-admin-livewire
Livewire-powered ecommerce admin UI for Laravel, offering ready-made components for products, orders, and store operations. Drop it into your ArtisanPack app to build responsive admin dashboards faster with less custom markup.
Livewire admin for the ArtisanPack UI ecommerce engine — products, orders, customers, promotions, tax, shipping, reports, and settings, with a command palette, activity timelines, and internal notes. Built on livewire-ui-components.
Frequently asked questions about Ecommerce Admin Livewire
- How do I install artisanpack-ui/ecommerce-admin-livewire in a Laravel app?
- Install the package with Composer into an app that already runs the ArtisanPack UI ecommerce engine and cms-framework, then run the ecommerce-admin:install command. That command publishes config, handles the front-end steps, runs access checks, and sets up notification templates. Finish by running ecommerce:sync-permissions against the engine's ability catalog so roles like shop-manager are available.
- Which Laravel and Livewire versions does this ecommerce admin support?
- The package targets Laravel 12 and 13 with Livewire 3.6+ or Livewire 4. That version matrix is relatively young, so treat it as the main upgrade risk rather than code quality. If you want a conservative first deployment, pin to Livewire 3.x and verify Livewire 4 parity in staging before switching.
- What are the prerequisites before installing this Livewire admin package?
- You need the ArtisanPack UI ecommerce engine at version 1.0, cms-framework for layout, menu, and RBAC, and a supported Livewire version. rebing/graphql-laravel is only suggested and is required only if you want real-time Echo updates. The admin is a presentation layer, so the engine must own pricing, stock, refunds, and other commerce rules.
- How does RBAC and permission syncing work in the ecommerce admin?
- Permissions are delegated to the engine's ability catalog rather than a parallel model, and ecommerce:sync-permissions registers the admin abilities. A shop-manager role is provided out of the box, and the deprecated ecommerce-admin:sync-permissions alias remains as a bridge for existing scripts. Admin middleware is enforced on every Livewire update, and mutations are rate limited.
- Do I need rebing/graphql-laravel and Echo for real-time admin updates?
- No, real-time is optional. Without GraphQL and Echo the admin silently degrades to polling, which works but can surprise support teams if nobody documented it. If you need live updates, your team owns the GraphQL plus Echo infrastructure because it is a separate dependency and not bundled.
- Can I add custom screens, widgets, and table columns without forking the package?
- Yes. The package exposes registries and filters for navigation, dashboard widgets, command palette providers, order and product panels, customer tabs, settings tabs, and table columns, filters, and bulk actions. That lets you add merchant-specific screens without forking, which is the main long-term ownership benefit. Confirm how stable those extension-point contracts are across minor releases before relying on them heavily.
- Is this a headless ecommerce admin API, or does it require Livewire?
- It is a Livewire-rendered admin presentation layer, not a headless admin API. It fits best in a Laravel plus Livewire modular monolith that already uses the ArtisanPack engine and cms-framework, where it inherits the host app's auth, middleware, rate limiter, and CSP. It is a weak fit for SPA-first React or Vue stacks or a different commerce core.
- How is the package tested, and is it accessible enough for WCAG 2.2 AA?
- Each screen is covered by a Pest and Playwright suite plus an axe accessibility check. That gives useful regression coverage, but an axe suite alone is unlikely to satisfy a WCAG 2.2 AA procurement claim. Plan for an external accessibility audit if you need a formal conformance statement.
- What are the risks of coupling to the ArtisanPack ecommerce engine across upgrades?
- The package is stable-labeled, but it couples deeply to engine internals such as DescribesConfig schemas, the ability catalog, default warehouse, table prefix, currency, and refund-limit sources. An engine patch can therefore ripple into admin behavior, so version drift rather than code quality is the main risk. Pin engine and Livewire versions and rehearse upgrades in staging before production.
- What alternatives should I consider, and when is this package the right choice?
- Alternatives include building custom Livewire admin screens or using a general Laravel admin panel, but those do not ship ecommerce-specific product, order, refund, tax, and shipping flows tied to the ArtisanPack engine. This package is the right choice when you are already on the ArtisanPack engine and cms-framework and want ready-made commerce admin screens with a command palette, activity timelines, and internal notes. If you run a different commerce core or an SPA-first front end, evaluate a different admin layer instead.
Weaver
How can I help you explore Laravel packages today?