Weave Code
Ecommerce Storefront Livewire Laravel Package
artisanpack-ui/ecommerce-storefront-livewire
ArtisanPack UI Ecommerce Storefront Livewire provides ready-to-use Livewire components for Laravel storefronts, including product listings, cart, checkout, and responsive UI. Integrate with your ecommerce backend to ship a polished shopping experience faster. Built for Laravel and Tailwind CSS.
Livewire storefront for the ArtisanPack UI ecommerce engine — catalog, product pages, cart and mini-cart, multi-step or single-page checkout, customer accounts, guest order lookup, faceted search, and visual-editor commerce blocks. Built on livewire-ui-components.
Frequently asked questions about Ecommerce Storefront Livewire
- How do I install artisanpack-ui/ecommerce-storefront-livewire in Laravel?
- Install it with Composer, then run php artisan ecommerce-storefront:install. The install command publishes the configuration and prints the Tailwind @source lines you need to add. You should also confirm your host app has login and registration routes, a layout, and at least one configured payment gateway. This package assumes the ArtisanPack UI ecommerce engine is already installed.
- Is this package a standalone Laravel ecommerce storefront?
- No. It is a Livewire storefront satellite for the ArtisanPack UI ecommerce engine, not a standalone commerce platform. It owns no tables and calls engine services in-process for catalog, cart, order, customer, and payment-domain data. You still need the engine as the source of truth for commerce persistence and core contracts.
- Which Laravel, Livewire, and PHP versions are supported?
- The documented baseline is Laravel 12 or 13, Livewire 3.6+ or 4, PHP 8.3+, and ext-intl. The package is built for the ArtisanPack UI ecommerce engine 1.1 and Tailwind CSS. Validate Laravel 13 and Livewire 4 against your actual host matrix before production, because those combinations should be tested rather than assumed.
- How do I add storefront routes or embed Livewire components in existing pages?
- You can use the package routes or embed its Livewire components in existing pages. Route prefixes, routes_enabled, the standalone layout, and account middleware are configurable. Plan the route and layout strategy first to avoid conflicts with your host application's existing storefront routes. Embedding components is often the safer choice when you already have a branded layout and auth flow.
- Does it support cart, mini-cart, and multi-step checkout?
- Yes. It provides product listings, product pages, cart and mini-cart components, and both multi-step and single-page checkout flows. Checkout orchestration lives in the storefront, while cart and order persistence remain in the engine. Test your chosen checkout mode against your payment gateway and fulfillment rules.
- How are payments handled and is Stripe supported?
- Payments are contract-based through a driver registry and RendersClientPayment. The package includes Stripe Payment Element with 3DS support and generic redirect drivers. You remain responsible for gateway credentials, webhook handling, retries, fraud-review states, and operational SLAs. Run sandbox payment and webhook tests before going live.
- Can customers check out as guests and look up orders?
- Yes. The storefront includes customer accounts and guest order lookup. Guest checkout still depends on your engine configuration and payment flow. Confirm account middleware and auth routes in the host app so account pages behave as expected.
- What Tailwind CSS setup is required?
- The install command prints the Tailwind @source lines to add to your CSS setup. You need a working Tailwind CSS pipeline and the layout include expected by the storefront. If you use the standalone layout, review it against your CSP, nonce, and asset-loading rules. If you embed components, make sure your existing Tailwind build scans the package views.
- Does it include faceted search, product pages, accounts, and visual-editor blocks?
- Yes. The package covers catalog browsing, faceted search, product types, product pages, cart and mini-cart, checkout, accounts, guest lookup, and visual-editor commerce blocks. Optional satellites such as SEO, media library, security, and CMS framework add capabilities but are not mandatory. The visual editor integration is additive, so plan which optional packages your host actually needs.
- What should I test before using it in production?
- Treat it as a bounded pilot until sandbox payment and webhook tests, accessibility review, and a pinned version matrix are complete. The main risks are ecosystem version coupling, engine contract stability, checkout and webhook ordering, optional-package compatibility, and accessibility gaps inherited from livewire-ui-components. Verify Laravel 13 and Livewire 4 on your host before committing. Also confirm the upgrade policy for engine 1.1 and future engine releases.
Weaver
How can I help you explore Laravel packages today?